Project notes
Free Project Notes Template (Word, PDF, and Markdown)
Copy a project notes template that keeps the current plan, decisions, tasks, risks, and dated history together. Includes Word, PDF, and Markdown.
Copy the template below or download it in Markdown, Word, or PDF. It keeps the answer to “Where does the project stand?” at the top, while dated decisions and updates preserve how the work got there.
Download the project notes template
Copy the project notes template
Project
| Field | Details |
|---|---|
| Project name | |
| Owner | |
| Team | |
| Status | Not started / On track / At risk / Blocked / Complete |
| Start date | |
| Target milestone | |
| Last updated | |
| Source of truth | Link to the plan, ticket board, brief, or folder |
Current snapshot
- Outcome: What must be true when this project is done?
- Current status: What is happening now?
- What changed: What changed since the previous update, and why?
- Next milestone: What is the next visible checkpoint and date?
- Needs attention: What requires a decision, help, or escalation?
Decisions
| Date | Decision | Why | Owner | Status | Source |
|---|---|---|---|---|---|
| YYYY-MM-DD | Current / Superseded | Meeting, message, document, or link |
Tasks and follow-ups
| Task | Owner | Due | Status | Source |
|---|---|---|---|---|
| Not started / In progress / Blocked / Done |
Blockers and risks
| Type | Description | Owner | Response | Status |
|---|---|---|---|---|
| Blocker / Risk | Open / Watching / Resolved |
Open questions
| Question | Owner | Needed by | Answer or next step |
|---|---|---|---|
Dated notes and updates
YYYY-MM-DD
- Update:
- Evidence or source:
- Decision made:
- Follow-up:
Completed and superseded archive
Move finished tasks and replaced decisions here. Keep their dates, owners, and sources so the project history remains readable.
| Closed date | Item | Final state | Replaced by or outcome | Source |
|---|---|---|---|---|
| YYYY-MM-DD | Completed / Superseded / Cancelled |
Why the template has two layers
The current snapshot is for someone who needs the state of the project in a minute. The dated history answers a different question: what changed, who decided it, and what source supports the record?
That split prevents a common failure. If a launch date moves, replacing the old date everywhere makes the current plan look tidy but erases the decision history. Keep the new date in the snapshot. Mark the old decision as superseded and link it to the replacement.
California’s Project Management Framework treats status reports, schedules, risk logs, issue logs, change records, and archived project records as separate but connected project artifacts. Its meeting agenda and minutes guidance also records what was decided, who owns each action, and when it is due. New York’s official action-minutes template pairs a decision with its rationale and assigned responsibilities. This template pulls those useful fields into one lightweight working note.
Filled example: Alder & Finch website launch
Alder & Finch is fictional. The example shows how to update the current plan without rewriting the past.
Project
| Field | Details |
|---|---|
| Project name | Alder & Finch website launch |
| Owner | Maya Chen |
| Team | Maya, Luis, Priya, Rowan |
| Status | At risk |
| Start date | 2026-09-14 |
| Target milestone | Public launch on 2026-11-19 |
| Last updated | 2026-10-30 |
| Source of truth | Launch brief and weekly project notes |
Current snapshot
- Outcome: Publish the new product site with approved copy, working lead forms, and a rollback plan.
- Current status: Development is ready for final content, but legal review of the pricing page is still open.
- What changed: The launch moved from November 12 to November 19 because legal review will finish after the original content-freeze date.
- Next milestone: Final copy approval by November 6.
- Needs attention: Priya needs a legal reviewer confirmed by October 31.
Decisions
| Date | Decision | Why | Owner | Status | Source |
|---|---|---|---|---|---|
| 2026-10-02 | Launch on November 12 | Allowed two weeks for the campaign before the holiday period | Maya | Superseded | Weekly launch meeting |
| 2026-10-30 | Launch on November 19 | Pricing copy cannot freeze before legal review finishes | Maya | Current | Launch review notes |
The November 12 row stays in the notes. Its status tells the reader not to follow it, while the source and reason explain why the date existed.
Tasks and follow-ups
| Task | Owner | Due | Status | Source |
|---|---|---|---|---|
| Confirm legal reviewer | Priya | 2026-10-31 | In progress | Launch review notes |
| Add approved pricing copy | Luis | 2026-11-09 | Not started | Decision dated 2026-10-30 |
| Run lead-form and rollback checks | Rowan | 2026-11-13 | Not started | QA checklist |
Blockers and risks
| Type | Description | Owner | Response | Status |
|---|---|---|---|---|
| Blocker | Legal reviewer is not confirmed | Priya | Escalate to operations on October 31 if still unassigned | Open |
| Risk | Moving the launch leaves less time for campaign testing | Maya | Run campaign QA against staging before final content approval | Watching |
Open questions
| Question | Owner | Needed by | Answer or next step |
|---|---|---|---|
| Can the campaign use the approved product copy before pricing review closes? | Maya | 2026-11-02 | Ask legal to separate product and pricing approvals |
Dated update: 2026-10-30
- Update: Legal review will finish after the original content freeze.
- Evidence or source: Launch review notes and legal review schedule.
- Decision made: Move launch from November 12 to November 19.
- Follow-up: Priya confirms the reviewer; Maya updates the campaign and stakeholder calendar.
The filled example PDF includes the complete fictional note on a printable layout.
Use the source column as a memory check
A source can be a meeting note, message, ticket, brief, or document. The link does not prove that a decision was good. It shows where the wording came from, which helps when someone remembers the decision differently or asks why a date moved.
Use labels such as proposed, approved, current, and superseded carefully. A discussion is not a commitment. If a person did not accept a task, do not turn the conversation into an assigned action.
Where this template stops
This is a working project note. It does not replace a signed project plan, formal meeting minutes, a risk register, a contract record, or a task system where those records are required. Large, regulated, or high-risk projects need their organization’s approval, retention, security, and change-control process.
The template also cannot decide whether a note is accurate. The note owner should confirm owners, dates, decisions, and source links with the people responsible for the work.
License and attribution
The blank template text and the fictional Alder & Finch example are licensed under Creative Commons Attribution 4.0 International. You may copy and adapt them, including for commercial use, if you give credit, link to the license, and say whether you changed the material.
Use this attribution:
“Project Notes Template” by Vyxora Editorial, available at https://vyxora.app/blog/project-notes-template, licensed under CC BY 4.0.
If you modify it, add: Changes were made. The Vyxora name, logo, product screenshots, website design, and software are not included in this content license.
Sources
- California Project Management Framework, California Department of Technology
- CA-PMF templates and meeting minutes guidance, California Department of Technology
- CA-PMF key elements, California Department of Technology
- Action Minutes Template, New York State Office for the Aging
- Meeting agenda and notes example, Arizona State University
- CC BY 4.0 deed, Creative Commons