The Closed File: Giving Unfinished Work a Discreet Afterlife
Photo: Agriculture And Stock Department, Publicity Branch, Public domain, via Wikimedia Commons
Every practice accumulates them: the commission that stalled at the second draft, the identity that never left the presentation stage, the essay commissioned for a publication that quietly changed direction. The work is real, but the outcome is not. On a shelf in the studio, or in a folder called 'old', these projects can become a source of low-level unease. They are too finished to discard and too unresolved to show.
The temptation is either to bury them or to extract a portfolio piece from them before the dust settles. Neither is especially useful. A more disciplined approach is to give unfinished work a closed file: a private, well-labelled record that preserves what was learned, protects what was entrusted, and makes a clear separation between professional memory and public presentation.
Start with a boundary, not a tidy-up
Before moving any files, establish why the work stopped. Was it a change of client strategy, a budget that vanished, a scope that grew beyond the brief, or a decision on your part not to continue? The reason matters because it determines what can responsibly be kept and what should be archived with restrictions.
For UK practitioners, client confidence is not an abstract courtesy. It sits alongside data protection, contractual terms and ordinary professional discretion. If a project ended under an NDA, a termination agreement or an informal understanding that the material would not be shared, that boundary should be recorded at the top of the file. A single line such as 'private: no public reuse without written permission' is more useful than a vague memory two years later.
Make the closed file do some work
A closed file should be small enough to review and detailed enough to be useful. I would give it four parts.
First, a short factual note: client or collaborator, dates, scope, stage reached and reason for closure. Keep it to a paragraph. This is not the place for grievance or interpretation.
Second, the material itself. Retain the final working files, the key presentation documents and any research that would be costly to recreate. Remove duplicates and stray exports. If the project involved sensitive personal data, client financials or unpublished strategy, delete what is not needed rather than keeping it 'just in case'.
Third, a lessons page. This is the part most people skip. Write down what you would do differently in plain language: the question you should have asked at kick-off, the warning sign in the second meeting, the estimate that omitted a round of revisions, the point at which the brief became a different project. Keep it specific. 'Better communication' is not a lesson; 'ask for the decision-maker's name before scoping' is.
Fourth, a reuse status. Mark the file as one of three things: closed and private, partially reusable with anonymisation, or potentially reusable with permission. This prevents the slow erosion of judgement that happens when a folder is opened years later and the original context has faded.
Extract the lesson without flattering yourself
Unfinished work is a poor teacher if the only lesson is that someone else was difficult. The useful questions are more ordinary. Did the proposal promise more than the fee could support? Was the approval process unclear? Did you mistake enthusiasm for authority? Did the work fail because it was wrong, or because it was never properly tested?
A short post-mortem written on the day the file closes is usually more honest than one written at year end. It should be blunt but not theatrical. The aim is not to relitigate the project. It is to notice a pattern before it repeats on a paid commission.
Test any reuse against three questions
There is a legitimate middle ground between hiding work away and publishing it. But reuse should pass a simple test.
Would the client recognise this as their project? If yes, permission is needed, even if names and logos are removed. Would a competitor recognise the strategic idea? If yes, anonymisation may not be enough. Would you be comfortable explaining the reuse to the client in person? If not, the answer is probably no.
Minor fragments are often easier to redeem: a type pairing, a research method, a structure for a workshop, a paragraph that can be rewritten into a general guide. Distinctive concepts, unpublished names and client-specific systems should stay in the closed file. Responsible reuse is less about what can be legally defended than what can be professionally explained.
Keep learning and showing apart
The public portfolio has a different job from the private archive. It should show finished work with clear permission, accurate credits and enough context to be useful. The closed file is where uncertainty belongs. Mixing the two produces the familiar portfolio problem: a page that looks impressive but cannot be discussed candidly when a prospective client asks about it.
A clean line also protects the work that did happen. If every near-miss is forced into a case study, the portfolio begins to overstate. If every abandoned project is deleted, the practice loses its own history. The closed file is the compromise: not a monument, not a bin, but a record with a lock on it.
A small annual review
Once a year, set aside an hour to review the closed files. Delete what no longer serves a purpose. Promote a genuinely reusable fragment into a separate ideas folder. Check that permissions still match the way the material is stored. Add one sentence to any file whose lesson has since been confirmed by another project.
This is modest housekeeping, but it changes the character of the shelf. The almosts stop being a quiet reproach and become what they are: evidence of work attempted, boundaries respected and judgement gradually improved. That is a more honest legacy for unfinished work than either a polished portfolio entry or a forgotten folder.