Rescue starts with a subtraction
Open the rubric and put a value against every required component. Then sort them by points against the hours each would still take. The components at the top get written completely. The ones at the bottom get a short honest treatment or a stated limitation.
This is a resource decision and it should be made like one. You have a fixed budget of hours and a scoring function printed in front of you. Spending six hours on a small appendix while a heavily weighted analysis sits empty is the mistake almost every rescue makes, usually because the appendix is the easier thing to start.
Do the sort in one message to the group rather than in your own head. A rescue with two people quietly working to different priority lists produces two half-finished sections, which is precisely the outcome the sort exists to prevent.
Write in dependency order
Sections depend on each other, and writing them out of order wastes the little time you have.
- Whatever the analysis rests on comes first: the data, the case facts, the model. Nothing above it can be written until it is settled.
- The analysis itself, next, and at full length. It usually carries the most points and everything else refers back to it.
- Recommendations or conclusions, drawn from the analysis you actually have rather than from what the group intended to find.
- The introduction and any summary, written last so that they describe the document that exists.
- Formatting, references and the contents page, in one pass at the end, by one person.
Say what is reduced, and say it plainly
A deliberately narrowed scope, stated in the document, reads as judgment. The same narrowing left unmentioned reads as an omission. One paragraph at the start of the affected section is enough: what was examined, what was not, and why that boundary is defensible.
Never invent content to fill a gap. Fabricated figures or a source nobody opened is a different category of problem from a thin section, and it outlasts the grade by a long way.
The same principle covers sources. A thin section built on three papers you have read is defensible. A thick one built on ten you skimmed is not, and it takes a grader one click to find out which of the two you did.
What to send the instructor, and when
Contact before the deadline is a status report. The same message afterward is an excuse. The difference is one day.
- Write once, from one person, on behalf of the members who are participating.
- State facts: what has gone into the shared document, by whom, and on what dates.
- Ask a question rather than requesting a remedy. Whether credit can be assessed individually is something only they can answer.
- Attach nothing accusatory. Version history is already available to them, and it speaks without adjectives.
After the grade
Keep the record, complete any peer evaluation factually, and then let it go. Where more group work is coming in the same program, the useful change is structural rather than social: agree the internal deadline and the coverage rule in the first week of the next one, before anybody has a reason to take it personally.
The reckoning belongs at the end rather than during. Deciding at hour twenty who should have done what costs hours you do not have, and it has never once improved a document.
Where the schedule genuinely cannot absorb a rescue, handing the missing sections to a specialist for a weekend is a narrower request than people assume, and it is among the more common reasons students write to us about urgent deadlines.
Questions
Is it worth asking for an extension for the whole group?
Ask once, early, with a specific date attached. An open request to move a deadline is easy to decline, while a request for two days with a stated reason and a plan is often granted. Ask before the deadline passes. Afterward the same message becomes an explanation rather than a request, and it is judged on different terms.
How should a rescue be split between the members still working?
By component, with the largest scoring component going to whoever writes fastest in that subject rather than to whoever nominally owned it. Ownership from week one stops being useful in a rescue. Assign in one message, list who has what, and set a handover time that leaves the person assembling the document a clear half day.
Does a reduced deliverable always lose points?
It loses the points attached to what is missing, and it protects everything else. A document covering most of the requirements completely usually scores above one covering all of them thinly, because rubrics generally award depth within a criterion rather than mere presence. Choose which criteria to cover on exactly that basis.
What if a member submits their own version separately?
Report the facts and let the instructor resolve it. Duplicate submissions from one group raise a question about which document is being assessed, and only the person grading can settle that. Send the shared document's version history alongside the group's submission so the record is available without anyone having to argue about it.
How do I stop a rescue from wrecking the rest of my week?
Cap it before starting. Decide how many hours the rescue gets, write that number down, and stop when it is spent even if the document is imperfect. Group work has a way of consuming the courses around it, and one weak assignment in one course is far cheaper than three courses slipping at the same time.
