Split by rubric row, not by topic
Groups divide work by subject because subjects are easy to name. The rubric does not score subjects. It scores criteria, and a split by topic leaves criteria half answered in four different sections.
Take the rubric and assign rows instead. One person owns the analysis row wherever it appears in the document. Another owns the evidence row and the citations that satisfy it. This feels awkward for about a week, and then it ends the argument about whether something is finished, because finished has a definition printed on the grid.
Write the split into the document as a comment beside each section. A group that can see who owns what stops asking, and a member returning after a quiet week finds their row without needing a conversation about it.
- Every rubric row has exactly one owner.
- Everyone writes into the shared document rather than into a separate file.
- The internal deadline sits two days before the real one, and it is the only date anyone quotes.
- One person is the integrator, and that person writes nothing else.
The integration pass is the assignment
A stitched document announces itself. Five registers, three citation habits, headings that do not match, and a conclusion answering a question the introduction never asked. Graders read hundreds of these, and the seam is visible within a paragraph.
So plan the pass rather than hoping for it. The integrator takes the last two days with one job: one voice, one heading structure, one reference list, and a check that every rubric row is answered where a grader will look for it. Rotate the role between assignments so the same person is not carrying it every time.
Name the quiet plan in week one
Someone will go quiet. That is not cynicism, it is scheduling. Five adults with jobs and clinical hours rarely stay synchronized for six weeks. A group that has agreed what happens next loses a section. A group that has not agreed loses the assignment.
The agreement is short. Work goes into the shared document by the internal date. If nothing is there and there has been no message for two days, the owner of the next row picks it up and the group tells the instructor what it did, factually. Post it in the first thread so it is a policy rather than an accusation aimed at whoever it eventually applies to.
Keep the record boring
Documentation protects the people who did the work, and only while it stays unemotional.
- Keep decisions in the group thread rather than in private messages.
- Let the shared document's version history prove who wrote what, since it does that better than anyone's account of it.
- Summarize each meeting in three lines: decisions, owners, dates.
- When you write to the instructor, describe what was submitted and by whom, then ask a question rather than making a case.
If it is already the last weekend
Reduce before you write. Find the rubric rows carrying the most points, cover those completely, and let a thin section stay thin rather than leaving a heavy one empty. A complete document scoring in the middle everywhere beats an excellent half.
Inkhours is not affiliated with Grand Canyon University and holds no authority over its rules, so follow your own course instructions wherever they differ from anything here. Where a benchmark is at stake and the group has gone silent, students usually hand the integration and the missing rows to a specialist through GCU class help rather than writing five sections in two days.
Questions
How early should the internal deadline be?
Two days before the real one, and no less. Integration is a genuine task rather than a formatting pass, and it cannot be done in an hour on the due date. A group treating the internal date as the actual date finishes calmly. A group treating it as a suggestion discovers on the last night that two sections answer the same rubric row.
What if two people write the same section?
That is a split problem rather than a personality problem. Duplication almost always means the work was divided by topic instead of by criterion, so two people wrote toward one requirement from different angles. Keep the version that answers the row more directly, fold in anything specific from the other, and re-cut the remaining rows so nobody is left without one.
Do participation posts count separately from the group grade?
Usually yes. Class participation and the group deliverable are typically scored on different instruments, so quiet weeks in the discussion cost you even when the project goes well. Keep your own posting rhythm running through the project weeks. It is the part of the grade the group cannot affect in either direction.
Is any of this official guidance?
No. Inkhours is independent, unaffiliated with Grand Canyon University and neither endorsed nor sponsored by it. What is described here comes from specialists who have worked inside collaborative assignments across many programs since 2010. Follow your course policies and your instructor's instructions wherever they differ from this page.
What if the group cannot agree on a topic?
Settle it against the rubric rather than by preference. Whichever option makes the criteria easiest to evidence is the right one, and that is a question with an answer rather than a matter of taste. Where the group is still split, take the option with the most accessible sources. A topic nobody can find evidence for costs more later than a compromise costs now.
