Archive old projects and files

Archive the client project folder named Project Redline, which finished last month. Move all final deliverables into an Archive/Project Redline folder, set folder permissions to read-only for the client and active team, and delete draft subfolders older than six months. Add a short README that lists the final deliverables and who to contact for retrieval. Do this by Friday and confirm the client can still access the final files.

Before I archive completed project folders, help me make retrieval painless: create a checklist that surfaces what must remain writable versus what can be read-only, identify any files legal or finance will still need, and suggest a naming and README template that makes future searches easier. Also flag any links shared externally that need updating after the archive.

I moved Project Redline to Archive and set everything read-only. Finance just asked to update a final invoice inside that archive and now they’re blocked. I didn’t know they’d need write access. I can restore write permissions, but I’m worried about accidental edits and about which files truly need to stay editable. What’s the practical next move that fixes finance quickly and prevents this repeating?

Every time we archive projects to clear active workspace, someone later needs to edit a supposedly final file, and we either restore permissions or rework history. It costs us time and trust. What archive policy will reduce these interruptions: which files should never be locked down, who decides that, and one workflow change to prevent last-minute edits becoming emergencies?