Two clocks, running at different speeds.
Every project-based course at Southern New Hampshire University runs two schedules at once inside the Brightspace courseroom. One is weekly and recurring: an initial post, replies, a quiz, a short exercise. It resets each Sunday and it forgives nothing, but it also asks for nothing in advance. The other is a single long deliverable, submitted once, assembled from work produced across the whole term.
Students who treat both clocks as the same clock end the term doing the long deliverable at weekly speed, which is where the trouble begins. The weekly clock is a habit. The project clock is a plan, and a plan has to exist on paper before week two if it is going to survive the middle of a term.
Schedule it backwards, the way any deadline is scheduled.
Open a calendar and put the submission date in it. Then work backwards, subtracting each stage rather than adding one: a day for assembly and a cohesion pass; several days for the final revision; the turnaround for feedback on the last drafted section; the drafting time for that section; and so on to the point where you must have chosen a subject. What remains at the front of the calendar, if anything, is your float.
Doing this once produces the single most valuable number in the term, which is the date by which the subject must be settled. It is nearly always earlier than it feels. Feedback turnaround is the part everyone forgets to subtract, and it belongs on the critical path because you cannot revise against a comment that has not arrived.
The eight-week map.
What follows is the shape that works in a term with no dead weeks. Names and numbering differ by course; the sequence does not.
- Week one: read the final project rubric before anything else, list its required components in your own words, and choose a subject with sources or figures you can actually obtain.
- Week two: draft and submit the first milestone. Whatever it decides, later sections inherit, so spend the hours here rather than saving them.
- Week three: the feedback on the first milestone arrives; fold it into a single master document the same week, even though nothing is due.
- Week four: draft the next milestone directly inside the master document rather than in a separate file, so revisions accumulate in one place.
- Week five: collect whatever external evidence the later sections need, since anything requiring another person has a lead time you do not control.
- Week six: draft the remaining section and reconcile the whole document against the final rubric, criterion by criterion.
- Week seven: assembly. Introduction, conclusion, transitions, formatting, references, and a read-aloud pass for a document that has been written in pieces.
- Week eight: revise against your own rubric self-score and submit with a day in hand, because upload problems are a category of risk rather than an excuse.
Four dependencies that cause almost every delay.
Delay in a term this short is rarely caused by writing speed. It is caused by waiting, and waiting is predictable enough to plan around.
- A subject with no obtainable data, chosen because it was interesting rather than because the evidence was reachable
- Feedback treated as a gate: nothing on the next section begins while the last one is being read, which idles the writer for days at a time
- Formatting and references deferred to the final week, where they compete with the only cohesion pass the document will get
- Anything that requires a third party, from a firm's published figures to a colleague's answer, requested in the week it is needed rather than a fortnight earlier
Float, and what to do once it is spent.
A schedule without float is a forecast, not a plan. Put the reserve in two places: a spare day inside the assembly week, and one section drafted a week earlier than the map requires. Both are recoverable if the term goes smoothly and both are the difference between an inconvenience and a crisis if it does not.
When the float is gone and the calendar has already slipped, stop drafting and re-plan for an hour, because a term that is behind cannot be rescued by working the old plan faster. Identify which rubric criteria carry the most weight, finish those sections properly, and let the lightest criteria be merely adequate. That prioritization is the same arithmetic described in the triage order, and where a milestone chain has already broken in the middle of a term, rebuilding it while the weekly clock keeps running is ordinary work for the SNHU bureau.
Questions to the desk.
When should the subject of the final project be settled?
In the first week, and in writing. Every later section inherits the choice, so changing it in the middle of a short term means rebuilding completed work while new work is still due. Choose something whose evidence you can already name and reach: a company that publishes its figures, a dataset you have access to, a setting you know well enough to describe accurately.
Should I wait for feedback before starting the next section?
No. Feedback usually concerns execution rather than direction, so waiting idles you for days in a term with none to spare. Draft the next section while the last one is being read, then apply the comments to both when they arrive. The only exception is feedback that questions your subject or scope, which does need answering before more work is built on top of it.
How long does final assembly actually take?
Longer than the word count suggests, because assembly is editing rather than writing. Sections drafted weeks apart carry different vocabulary, inconsistent tense and repeated background. Budget a full working day for an introduction, a conclusion, transitions, formatting, references and one read-aloud pass. A document revised as it went needs only that day; one assembled from untouched drafts needs considerably more.
Is Scribehall affiliated with Southern New Hampshire University?
No. Scribehall is an independent academic desk with no affiliation, endorsement or sponsorship from Southern New Hampshire University. The scheduling described here comes from our editors' experience of project-based courses across many institutions with short terms. Your own course announcements and rubric take precedence over any general guidance, including this.
