A group opens a presentation file before anyone has agreed what the assignment is asking. One student chooses a theme. Another claims the introduction. Someone volunteers for the conclusion. A week later, the slides look coordinated, but the argument changes direction every few minutes. The team has divided a file without first designing the work.
The alternative starts with a smaller document: a shared account of the question, the evidence needed and the decisions still unresolved. It need not be elaborate. Its value lies in making assumptions visible while there is still time to change them. Slide design can wait until the group knows what it needs to explain.
This guide offers an original planning example for a permitted university group assignment. It draws on institutional teaching guidance, with the sources linked where relevant. The students and project below are fictional. Their process is a practical illustration, not a study showing that a particular template produces higher grades.
Start with the assignment, not a preferred division
Read the instructions together. Identify the question, the required submission, the assessment criteria and any separate individual component. Check the due date and submission method. An impressive video will not satisfy a requirement for a written report unless the instructor has allowed that change.
Nila, Omar and Jo, our fictional students, must compare two proposed uses for a campus courtyard. They initially suggest taking one option each and letting Jo assemble the slides. That arrangement leaves no owner for the comparison itself. Before assigning sections, they write a question: which option best meets the stated accessibility, maintenance and student-use criteria, given the evidence available?
The wording matters. Their task is now a comparison using specified criteria, rather than three loosely connected opinions about outdoor spaces. They keep the assignment sheet beside the outline so that a later design choice can be checked against the actual requirements.
Establish where collaboration is allowed
Permission to work together is specific to the course and assignment. Waterloo's academic integrity guidance distinguishes assignments permitting collaboration throughout from those permitting it only at certain stages. Read that guidance here: https://uwaterloo.ca/academic-integrity/integrity-students/group-work
Before sharing work beyond the assigned group, check the instructor's rules. The same applies to outside editing, reused material and generative tools. If an individual reflection must be written independently, the group should not jointly compose it simply because the main presentation is collaborative.
For Nila's group, a short question to the instructor resolves whether they may interview other students. Until permission and any required procedures are clear, they plan around the sources already authorized. They do not invent survey responses to fill an empty slide. An unanswered research question belongs on the work list, rather than becoming an unsupported fact.
Make a small agreement people can actually use
Waterloo's teaching guidance describes group contracts as a way to make expectations, responsibilities, deadlines and responses to problems explicit. It also recommends deciding how feedback will happen during the project: https://uwaterloo.ca/centre-for-teaching-excellence/catalogs/tip-sheets/making-group-contracts
The students translate that idea into a brief working agreement of their own. It records their shared document location, an agreed communication channel, availability, the next review date and how to flag a blocked task. They choose expectations they can meet, rather than promising to answer messages instantly at any hour.
They also write down what happens if a deadline looks unlikely: notify the group early, state what is already done and propose a revised handoff. The agreement does not let students impose penalties, change grades or override accommodations. Course procedures and the instructor remain the authority for those matters.
Separate a task from a role
A task produces something: a source note, a comparison table or a draft explanation. A role helps the group work: guiding a discussion, recording a decision or questioning a weak assumption. A student can complete a research task while taking a different role at the next meeting.
Waterloo's assignment-of-roles resource discusses facilitation, monitoring discussion, keeping notes and critically checking the group's reasoning. It allows roles to be allocated around strengths or rotated: https://uwaterloo.ca/centre-for-teaching-excellence/catalogs/tip-sheets/group-work-assignment-roles
In the fictional project, Omar facilitates the first evidence meeting. Jo records decisions, and Nila checks whether each proposed claim answers the assignment question. At the next meeting they change responsibilities. These are their chosen arrangements, not a mandatory university role system. Nobody becomes the permanent designer simply because they know the presentation software best.
Define a handoff that another person can use
An instruction such as research maintenance costs leaves too much unsaid. Does the group need a current invoice, a published estimate, a general explanation or a comparison with assumptions? The person assembling the work cannot resolve those differences merely by making the text shorter.
The students instead agree that a useful source note will identify the claim, link the original material, record its date and scope, and explain any limitation. A proposed estimate must say what it includes. If the source describes a different campus or an older project, that difference stays visible.
Jo's first note therefore does not claim a precise cost for the fictional courtyard. It explains what a source can establish and what local information is still missing. That is a usable handoff because the group can decide whether to qualify the comparison, seek better evidence or remove a claim it cannot support.
Build in a review before the final assembly
A deadline for separate sections is not the same as a deadline for a coherent presentation. Plan a review when there is still time to reconcile definitions, remove duplication and check whether the conclusion follows from the evidence. Leave the actual submission deadline clearly marked.
For the courtyard project, the students choose three checkpoints: review the question and source plan, review the comparison in plain text, and rehearse the complete presentation. Their dates depend on the assignment's duration and their availability. This is an example schedule, not a universal number of meetings that every group needs.
At the plain-text review, they discover that one section evaluates initial expense while another evaluates continuing upkeep. Those ideas may both matter, but they are not interchangeable. Catching the mismatch now gives them a chance to make a fair comparison before the slide layout encourages everyone to defend a finished-looking section.
Record decisions without documenting everyone's private life
A simple decision log can say what the group agreed, why it agreed and who will make the next change. It should also distinguish a settled decision from a proposal. A message saying perhaps we should drop option two is not evidence that everyone approved dropping it.
Keep the log proportionate. Students need not disclose medical details, family circumstances or private conversations to justify every adjustment. Where a difficulty requires support or an accommodation, use the institution's appropriate channel. Share only what is necessary for the group to coordinate its work.
Nila records that the comparison will discuss access routes as well as seating, with the source still to be checked. Omar acknowledges the assigned follow-up. That short entry gives the group a shared reference without turning the workspace into a record of personal judgments or a surveillance system.
Address a missing contribution while change is possible
When work has not arrived, start with the agreed task and deadline. Ask what is complete, what is blocking the handoff and what can realistically happen next. A concrete question is more useful than a label such as lazy, especially when the group has not checked whether its own instructions were clear.
If a pattern continues, preserve a factual account and contact the instructor through the course's process. Do not secretly remove a student's name, threaten a grade reduction or submit an accusation as if it were an established finding. The group can report observable events without claiming authority to determine sanctions.
In our example, a missing source note turns out to depend on an unavailable document. The students agree on a narrower alternative and record the change. If that had not resolved the problem, they would have raised it before submission. A late surprise is harder to address than an early, specific explanation.
Check understanding across the whole project
Each member should have an opportunity to explain the overall question and the reasoning behind the conclusion. Knowing only one's own slides can leave the final presentation fragile. Ask a colleague to summarize the connection between two sections, then invite the original writer to correct any misunderstanding.
Cornell's instructor guidance separates assessment of the product, teamwork and individual contribution. It recommends making evaluation criteria clear and using feedback during the project, rather than relying solely on a final impression: https://teaching.cornell.edu/teaching-resources/active-collaborative-learning/collaborative-learning/how-evaluate-group-work
The group does not invent its own marking weights from this advice. It uses the instructor's rubric. During rehearsal, Jo can explain why a visually attractive option remains uncertain because the available evidence does not answer an important maintenance question. The presentation becomes more credible when the uncertainty is stated clearly.
Give feedback about an action and its effect
Peer feedback is easier to act on when it names something observable. Explain which contribution helped the work and which specific change is needed. For example, a source note may have helped distinguish installation from upkeep, while an unsupported comparison still needs revision. Both statements describe the project rather than a person's character.
If the course requires confidential peer assessment, submit it through the designated process. Do not circulate private ratings to pressure teammates. Keep factual contribution records consistent with what actually happened, including revisions and support work that may not appear as a separate slide.
The same principle applies to self-reflection. A student can describe learning to qualify a claim or improve a handoff without pretending the project went smoothly throughout. Honest reflection is more informative than a polished account that erases disagreement and gives every member identical praise regardless of their contribution.
Finish with a shared submission check
Before submitting, compare the completed work with the original instructions again. Confirm that names, citations, required files and individual components are correct. Check that links open for the intended recipient and that the final version is identifiable. Assign the submission action explicitly and agree how the group will know it succeeded.
For the fictional courtyard presentation, the final rehearsal reveals that the conclusion sounds more certain than the comparison supports. The students revise it to recommend the better-supported option while identifying the information still needed. They remove an attractive but unverified claim instead of hoping nobody will ask about it.
After submission, retain the confirmation and any records required by the course. For a separate approach to using feedback after an assessment, see our guide: https://monetizearticle.com/article/after-the-exam-turn-feedback-into-a-study-plan-you-can-test-6c660c
Keep the shared file readable
Agree on a few practical conventions before combining sections. Use descriptive headings, distinguish comments from finished text and keep a clear record of unresolved questions. A reader should not have to guess whether a highlighted sentence is approved wording or a reminder to find evidence.
The fictional students keep one working version and label their submission copy separately. They check that charts have understandable labels and that essential points do not depend on colour alone. Before deleting a disputed passage, they explain the proposed change in the shared discussion. These small choices make revision easier to follow without demanding expensive software or a complicated project-management system.
Conclusion: design the shared work first
A group project needs more than a division of pages. It needs an agreed question, permitted collaboration, usable evidence and a chance to resolve differences before the final file is assembled. A brief working agreement helps only when people return to it and adjust the plan honestly.
Start with what the group must understand and demonstrate. Then assign tasks, agree on handoffs and build the presentation around the argument. The resulting slides may still be simple, but the reasoning behind them will be easier for every member to explain.
Sources and research note
Four primary university guidance pages linked above were read on 30 October 2026. They provide institutional teaching and integrity guidance, not evidence for a guaranteed grade improvement. Assignment-specific rules take precedence. All students, dialogue-free scenarios and planning choices here are invented illustrations. The original AI-generated conceptual image depicts a fictional study group and is not a photograph of students participating in research.