M. Korman All articles
Guides

The Week After Handover: A One-Page Record for Finished Commissions

M. Korman
The Week After Handover: A One-Page Record for Finished Commissions

Photo: Unknown, CC BY 4.0, via Wikimedia Commons

Most commissions end with a handover, an invoice and a brief exchange of thanks. The file is closed, the work is collected, and the reasoning that held the project together begins to disperse. Within a fortnight, the client's original constraint may be remembered only vaguely; within a month, the small compromise that made the outcome possible is often lost altogether. A one-page case study, written while the commission is still warm, is a modest remedy.

It is not a portfolio entry and it is not a testimonial. It is a working record: a single A4 page that captures what was asked, what got in the way, what was decided and what resulted. The discipline lies in keeping it short enough to complete and specific enough to be useful later. Written within a week of handover, it preserves the texture that final files and finished photographs rarely retain.

Why the first week matters

Memory is at its most reliable immediately after a project closes. The brief is still legible, the client's hesitations are still audible and the reasons behind a particular material, format or schedule are still present. Waiting until the next portfolio review or proposal deadline is a false economy. By then, the commission has been flattened into a set of images and a one-line description, and the useful part — the judgement — has gone.

The first week is also when the client's response is freshest. A short note about what they noticed, what they questioned and what they accepted can be recorded without turning the exchange into marketing copy. This is not about collecting praise. It is about capturing evidence of how the work functioned in its actual setting.

A page, not a report

The temptation with any written record is to let it grow. A case study can easily become a project history, then a technical appendix, then a document nobody reads. The one-page limit is therefore not arbitrary. It forces selection. If a detail cannot justify its place on the page, it probably belongs in the project archive rather than in the case record.

The page should be plain in both senses: plainly written and plainly formatted. A simple heading with the project name, client type and date is enough. There is no need for a designed template unless the template itself helps you write. A text document or a printed sheet kept in the project folder will serve better than an elaborate system that takes longer to maintain than the commission took to complete.

The four fields

A useful one-page record can be built from four fields. They are deliberately ordinary, and they can be completed in twenty minutes if the project is still fresh.

Brief

State what the client asked for in one short paragraph. Avoid reproducing the full brief. The aim is to record the shape of the request: the purpose, the audience, the deadline and any fixed constraint that shaped the work. This paragraph should be understandable to someone who was not in the room.

Friction

List two or three points of resistance. These might be practical, such as a restricted budget, a difficult site or a short lead time. They might be interpersonal, such as a decision-maker who changed midway or a approval process that required patience. They might be material, such as a supplier delay or a colour that proved impossible to match. The friction is often the most useful part of the page because it explains why the finished work looks the way it does.

Decision

Record two or three decisions made in response to that friction. Keep them specific. Rather than writing that the project required a flexible approach, note that the shelving was reduced by one bay to protect the walkway, or that the print run was split into two batches to meet the launch date. Specific decisions are reusable evidence; general claims are not.

Outcome

Close with a short paragraph on what was delivered and how it was received. This need not be celebratory. A factual note — that the client installed the work on schedule, that the piece required one minor adjustment after fitting, that the final cost came in within the agreed range — is more valuable than a sentence about exceeding expectations. Add a line noting where the relevant files, photographs or correspondence are stored.

What to leave out

A one-page record should not become a place for scores to be settled or for private irritation to be preserved. If a project was difficult, the friction section can say so without assigning blame. The page is a professional document, not a diary.

It should also avoid the language of promotion. Phrases such as 'bespoke solution' and 'seamless delivery' tell a reader nothing. The same applies to client testimonials pasted in without context. If a client said something useful, paraphrase the substance and note the date. The page should read as a record of work, not as an advertisement for the maker.

Where the page earns its keep

These short records become useful in three places. The first is the proposal. When a potential client asks whether you have handled a tight timescale or a listed building, a one-page record gives you a precise example rather than a vague assurance. The second is the portfolio update. Instead of trying to remember why a project was significant, you can draw on the friction and decision fields to write an accurate caption or project note. The third is the client conversation. A concise record of what was agreed and why can be a calm reference point if a similar question arises later.

None of this requires the records to be published. They can live in a folder alongside the project files, reviewed only when needed. Their value lies in being available, not in being broadcast.

A routine that survives deadlines

A one-page case study is only useful if it is actually written. The most reliable routine is to attach it to an existing step: the final invoice, the archive of files or the return of borrowed samples. Keep a blank template in the project folder and complete it before the folder is closed. If a project is unusually complex, allow two pages, but treat that as an exception rather than a new standard.

A modest habit of this kind will not transform a practice on its own. It will, however, prevent the quiet loss of the detail that makes finished work legible. In a small studio, that detail is often the most valuable thing left after the handover.

All Articles

Related Articles

The Despatch Bench: A Calm Method for Posting Small Work from London

The Despatch Bench: A Calm Method for Posting Small Work from London

A Ledger of Quiet Time: Quoting Small Commissions With Confidence

A Ledger of Quiet Time: Quoting Small Commissions With Confidence

A Fortnight on a Neighbour's Wall: Practical Notes on Borrowed Exhibition Space

A Fortnight on a Neighbour's Wall: Practical Notes on Borrowed Exhibition Space