Fifteen compact project-document templates with copyable field structures and filled extracts from a visitor-badge pilot, covering authorisation, planning, control, acceptance and closure.
The templates share a six-week pilot case and a consistent funding summary. Use the fields to create connected project records with visible ownership, versions, evidence and approval states.
Use documents to support decisions
A compact template should make ownership and evidence easy to find. Authorise a defined project with an accountable sponsor. Define the boundary and the evidence that will establish completion. Explain one work package clearly enough to estimate and accept it.
1.2 Desk Configuration. Owner: IT lead. Output: approved badge setup on two reception desks. Input: authorised badge design. Acceptance: both setups pass the agreed print-and-scan scenarios.
04 / Activity and dependency log
Turn work packages into dated, owned delivery activities. Keep approved delivery budget distinct from total funding. Connect uncertain events to owned responses and review triggers. Control problems that already exist and require action.
I01: the test printer is unavailable for the planned rehearsal. IT lead confirms a loan unit by day 10. Escalate to the project manager if availability remains unconfirmed at the agreed checkpoint.
08 / Stakeholder register
Plan engagement around real interests and responsibilities. Clarify delivery and accountability for specific outputs or decisions. Match the message, audience and decision timing. Provide a dated assessment that supports the next decision.
At the week-four review, desk configuration is accepted and rehearsal is pending. Approved baseline 7,500; current EAC 7,800, an anticipated excess of 300. Explain the estimate basis and response options.
12 / Change request
Make a proposed change reviewable before committing the project. Preserve the outcome, authority and reasoning people rely on. Document what was reviewed and exactly what was accepted. Leave a controlled record of completion and continuing responsibility.
Pilot outputs are accepted and handed over. Final cost is 7,700 against baseline 7,500, an excess of 200. Operating lead owns the later performance review; sponsor decides closure from the evidence.
Keep the templates connected
A small, consistent record set is more useful than fifteen isolated files.
For each document, show purpose, owner, current version, approval state and location. Archive superseded versions so people can trace history without accidentally relying on them.
Contents
- Use documents to support decisions
- 01 / One-page project charter
- 02 / Scope and acceptance statement
- 03 / WBS dictionary entry
- 04 / Activity and dependency log
- 05 / Cost baseline and funding summary
- 06 / Risk register
- 07 / Issue log
- 08 / Stakeholder register
- 09 / RACI responsibility matrix
- 10 / Communication plan
- 11 / One-page status report
- 12 / Change request
- 13 / Decision log
- 14 / Acceptance record
- 15 / Closure and lessons summary
- Keep the templates connected
Using the PDF
Each numbered page contains an explanation, an original worked situation and a practical action. The bookmarks navigate the learning pages. A templates advertisement follows content page 5 and a Coursera Plus advertisement follows content page 15. The entire advertisement image is linked. Promotional links may earn Coursya a commission. A purchase is optional.
Frequently asked questions
Who is this guide for?
Fifteen compact project-document templates with copyable field structures and filled extracts from a visitor-badge pilot, covering authorisation, planning, control, acceptance and closure.
How can I practise the ideas?
Follow the running case, work through the page actions and use the PDF bookmarks to revisit a topic. The final learning pages help you apply the decisions to your own project.
What does the download contain?
The PDF contains 20 pages, including 17 numbered learning pages, a cover and two linked advertisements. The book is written in English.


