Start here

Choose the version worth keeping and add a short note explaining the project's purpose, status and last decision. Link relevant material stored elsewhere and label drafts clearly. Preserve information needed for reuse or retention while moving closed work out of active lists.

You finish or pause a project and move the folder out of the way. Months later you open it and cannot tell which version was final or why a particular decision was made. The files survived, but the context did not.

Before archiving, identify the version worth keeping. Add a short note explaining what the project contains, its current status and the last important decision. Include the location of any material stored elsewhere.

Keep only the context you may use

You do not need a complete diary of the project. Write the details that would help you reuse the work or resume it without repeating the same investigation. Remove unnecessary duplicates where doing so is safe.

If the archive contains private information, store it appropriately and avoid copying it into a public folder. Review older archives when they begin to interfere with finding current work. A closed project can remain available as a reference without continuing to occupy your active task list or asking for attention every week.

Closing a community-event folder

An illustrative example

Imagine saving the files from a community event. The folder contains several schedules named final, a materials list and messages about a late change. Create a closing note identifying the schedule actually used and explaining why one activity was removed. Include where the final budget and approved photos are stored, with access appropriate to their contents. Label earlier schedules as drafts instead of leaving them beside the usable one with identical names. A future organiser can then find the working plan and understand its limits. Keep sensitive attendee information in suitable private storage. The archive gives the next event a starting reference without leaving this event on your weekly task list.

Make an archive readable

Tick the steps as you work through them.

0 of 5 steps checked

When archiving becomes another project

You rarely need to reorganise every old file before closing the folder. Start with the final version and a context note. If filenames are confusing, rename the few files someone would need first. Leave material you are uncertain about intact until you know whether it must be retained. A paused project also needs a restart condition, such as a confirmed venue or available period. Put that condition in the note so opening the archive later does not automatically restore the entire project to active work.

Write the closing note

Your notes stay in this page. Copy them before leaving; they are not saved or sent to us.

Next useful stepHow to decide whether to finish an unwanted project →

Written by the Painless Success editorial team. Our upcoming book, Painless Success, brings these ideas together. Preview its contents or join the release waitlist.