Project source index template
By Kivrelune Studio

Project source index
Create a reliable index for the briefs, decisions, evidence and deliverables of a project.
Project front page
Project: [name]. Purpose: [one sentence]. Lead and decision owner: [roles]. Latest status and immediate milestone: [links/date].
Document register
For each artifact record [purpose], [canonical link], [owner], [status] and [last revision]. Include requirements, decisions, delivery plan and acceptance evidence.
Maintenance rules
Create a new entry when [trigger]. Supersede old versions with [pointer to current source]. At close, [owner] moves final deliverables and decisions to [archive].
Using this template
Start the index with the documents a new project member needs to understand purpose, status and recent decisions. Add canonical links as new artifacts are created, making ownership and revision status visible before final handover or archiving.
Questions & answers
Looking for more help? Visit the Help center.
How can we prevent the index itself from becoming another copy of the project?
Keep one short description, owner and link per artifact. Put detailed content in its maintained source and assign index updates to the person creating or superseding an artifact.
What is included in this template?
Project front page · Document register · Maintenance rules. Each section includes prompts you can adapt to your team.
Which details are worth keeping after delivery?
Keep the original constraint, the important trade-off and the check that confirmed the result. Link the service or release record that can verify the decision.
How do I use my own copy?
Choose “Start with this doc” to open an editable copy on this device. You can also copy the Markdown or download the file and use it in your own editor.

