Agree who archives project files when work finishes

Choose someone who worked closely with the files throughout the project, knows where everything is stored, and has time after the deadline to gather and organise them. It helps if they understand which files matter for future reference and which are working drafts. The person should be someone the group trusts to finish the task without needing reminders. If everyone is equally busy, pick whoever has the clearest calendar in the week after the project ends. Avoid splitting the job between people because it creates confusion about what still needs doing.

Finished means every file the group agreed to keep is in one archive, stored in the place you agreed, with a clear label everyone recognises. Working drafts, duplicate copies, and temporary notes should be removed unless the group decided to keep them. The person doing the archiving sends a message saying the job is done, where the archive lives, and what it is called. Once that message arrives, no one should need to ask whether the archiving happened or hunt for files. The group can move on knowing everything is stored safely.

Talk through the file list together before the project ends and agree which files have future value. Keep final versions, approved designs, important correspondence, and anything you might need for similar work later. Delete working drafts, test files, duplicate copies, and anything created only for internal discussion. If someone is unsure about a file, agree as a group whether it stays or goes. Writing down the decision in your chat means the person archiving does not have to guess. This conversation takes ten minutes but saves hours of confusion later.

Store the archive wherever your group already keeps shared files, so everyone knows where to look if they need something later. Choose a location everyone can access without needing special permissions or passwords from the person who did the archiving. Label the folder with the project name and the month or year it finished, so it is easy to find months later. Avoid storing it only on one person's computer or in a location that might disappear if someone leaves the group. The goal is permanent storage that does not depend on one individual.

If the person realises they will miss the deadline, they should tell the group as soon as they know and propose a new date. Someone else can offer to take over if the delay is a problem, or the group can agree to wait. The important thing is updating everyone before the deadline passes, not after. If the person goes silent and the deadline arrives with no archive, someone else should volunteer to do it rather than waiting. One message asking for a new date or offering to help keeps the task moving.

The label needs enough detail that someone looking six months later knows exactly what the archive contains without opening it. Include the project name and the month it finished, like April Redesign Archive or Workshop Planning Jan to Mar. If your group runs similar projects regularly, add a year or a location to avoid confusion. Avoid vague labels like Final Files or Project Archive because they become meaningless when you have several. A clear label takes thirty seconds to write and saves everyone time hunting through folders later on.

You can, but it creates more work coordinating who does what and checking both halves are finished. One person handling the whole task means one conversation about the deadline, one confirmation when it is done, and no confusion about whether someone else covered a particular folder. If the job genuinely needs splitting because the files are spread across systems only certain people can access, agree exactly which person archives which part and have both confirm separately when their section is complete. Usually it is faster to give the job to one person.

If you discover a mistake after the archive is complete, the person who did the archiving can update it and send a new confirmation message. If they are unavailable, someone else can fix it and tell the group what changed. Mistakes happen when the group did not clearly agree what to keep, so if you find yourself correcting the archive, take a minute to write down the updated decision for next time. Most errors come from ambiguity during the planning conversation, not from the person doing the work. Clear instructions at the start prevent corrections later.