A small plan should show what must happen, who owns it, and what blocks the next task. Dates alone cannot explain why printing must wait for a checked handout or why a workshop cannot rely on an unconfirmed room.
The original project plan CSV describes a fictional workshop. It is a teaching example, not a client schedule or a measured forecast. All dates below are planned calendar dates in November 2026.
Define a visible finish
For this example, the finish is a workshop on 28 November with a confirmed room and twelve checked handouts. Scope excludes registration software, a public website, and ongoing event management. A clear finish prevents the plan from growing into every possible improvement.
Break the finish into actions with observable results: confirm the room, draft the handout, review it, print, and hold the workshop. Assign fictional owners so you can see where a handoff occurs.
Link the prerequisites
| Task | Owner (fictional) | Planned dates | Depends on |
|---|---|---|---|
| Confirm room | Morgan | Nov 18–19 | None |
| Draft handout | Riley | Nov 20–22 | Room confirmation |
| Review handout | Sam | Nov 23–24 | Draft complete |
| Riley | Nov 26 | Review complete | |
| Workshop | Team | Nov 28 | Printed materials ready |
These are finish-to-start dependencies: the predecessor must finish before the next task starts. Microsoft documents that relationship in Project, but this example is a plain CSV plan and has not been run in Microsoft Project.
A dependency is not just a nearby date. If the room is still uncertain on the 19th, the draft’s venue details cannot be treated as confirmed merely because the calendar says the 20th.
Make buffer days visible
The example leaves 25 November between review and printing, and 27 November between printing and the event. Each is one calendar day of buffer. They are not hidden estimates and not a promise that any delay will fit.
From 18 November to 28 November, the base calendar difference is ten days. Counting both listed dates with this site’s inclusive option gives eleven dates. Use the Date Difference tool and write the rule beside the result. Neither value is a working-day calculation.
Test one delay
Suppose the draft finishes on the 23rd instead of the 22nd. Ask Sam whether review can move to the 24th–25th. That uses the first buffer day; printing on the 26th may still be possible if the reviewed output is actually ready. Do not simply overlap review and printing while pretending the dependency stayed intact.
If the review slips beyond the 25th, choose an explicit response: reduce scope, find an authorized alternate print route, or move the event. Do not erase the buffer column to make the old date look achievable.
Here is the recomputed delay case: the draft takes one extra calendar day; review keeps its two-day duration, printing keeps its one-day duration, and the workshop date stays fixed:
| Task | Revised dates | Remaining buffer after task |
|---|---|---|
| Draft | Nov 20–23 (delayed finish) | 0 days before review |
| Review | Nov 24–25 | 0 days before printing |
| Nov 26 | Nov 27: 1 calendar day | |
| Workshop | Nov 28 | Not applicable |
The downloaded CSV defines buffer as the free calendar days after that row’s task and before its successor. The original review row therefore owns Nov 25; the original print row owns Nov 27. A companion delay CSV records the revised dates. Review ending Nov 25 leaves zero free dates before printing on Nov 26; printing on Nov 26 still leaves Nov 27 free. These are arithmetic examples, not newly agreed availability for Sam or Riley.
Review facts separately from plans
Keep actual completion dates and status separate from planned dates. A row marked 24 November is not evidence that the review happened. At each short check-in, update the next blocker and owner, then change only affected tasks.
The plan is useful when a person can explain the next action, the critical handoff, and the consequence of a delay. A small readable table can do that without a scheduling application, an automatic dependency engine, or a promise of certainty.
References & scope
These official references support the software instructions. Practice documents are original, fictional teaching examples; labels can vary by release.
- Link tasks in a project
Finish-to-start dependencies require the predecessor to finish before the next task starts. - Date.UTC()
UTC date construction avoids local DST offsets; invalid calendar components normalize and need explicit validation.