Confirm the completion condition
Before archiving, verify that the project outcome is actually complete, not merely that the main work stopped. Save receipts, approval messages, result links, or delivery evidence when they matter.
Close or deliberately transfer remaining tasks so nothing disappears accidentally.
Record actual time and important dates
Capture the real start, important milestones, completion date, and approximate time spent. This history improves future estimates and helps you recognize recurring bottlenecks.
Do not reconstruct perfect time records after the fact; a useful approximation is better than invented precision.
Preserve source documents and decisions
Keep the final version of important documents, the source notice or brief, and decision notes that explain why the project ended the way it did.
Remove redundant temporary files if they make future retrieval harder.
Extract reusable checklists
If several steps are likely to repeat, turn them into a reusable checklist or project template before archiving. Examples include application documents, release checks, travel preparation, and recurring reporting steps.
A template should contain stable process, not outdated dates.
Write one short retrospective
Record what worked, what caused delay, and one change you would make next time. A short retrospective attached to real project data is easier to reuse than a long postmortem nobody reads.
Then archive the project so active views contain only work that still needs attention.
Keep fixed dates on the calendar, executable actions as tasks, and multi-step outcomes inside projects. Preserve source evidence whenever a date came from a document.
Make the archive searchable
Use a project title that describes the outcome, retain useful categories and source evidence, and keep the final documents that someone would realistically search for later. An archive is valuable when you can recover the reasoning and reusable materials without reopening every file.
Do not depend only on the project title. Dates, labels, people, source notes, and attachments can all become retrieval clues months later.
Separate reusable process from one-time history
A reusable checklist should contain steps that are likely to recur. The archive should contain what actually happened this time. Keeping those two layers separate prevents old dates, names, and assumptions from leaking into the next project.
This final separation turns a completed project into both a trustworthy record and a starting point for future work.
Make the archive useful for the next project
Use a project title that describes the outcome, retain useful categories and source evidence, and keep the final documents that someone would realistically search for later. Dates, labels, people, source notes, and attachments can all become retrieval clues months after the project is finished.
Separate reusable process from one-time history. A reusable checklist should contain stable steps that are likely to recur. The archive should preserve what actually happened this time, including real dates, decisions, delays, and final files. That separation turns a completed project into both a trustworthy record and a better starting point for future work.