M. Korman All articles
Guides

The Lights Left On: A Quiet End-of-Project Dossier

M. Korman
The Lights Left On: A Quiet End-of-Project Dossier

Projects rarely end with a ribbon-cutting. They end with a final invoice, a folder of files and a slightly awkward silence. The work has been signed off, the last call has taken place, and both sides move on. What happens next is usually left to chance. A small, deliberate handover closes that gap. It need not be elaborate. A short dossier, assembled with care, can do more for a client relationship than another round of networking.

Care after the invoice

Most clients do not need a manual. They need reassurance. They need to know what they have received, where it lives and what to do when something changes. In a London market where studios, freelancers and small workshops are often judged on the calmness of their process, the handover is one of the few moments when that calm can be demonstrated without a pitch.

The temptation is to treat the handover as administration: send the files, close the job, move on. That is understandable. By the end of a project, attention is already turning to the next brief. But the client is often at their least confident precisely then. They have a website, a printed item or a made object in front of them, and no clear sense of what happens if a domain expires, a supplier changes or a new colleague asks why a decision was made.

A handover dossier answers those questions before they are asked. It is not a sales document. It is a quiet form of client care.

The one-page summary

Start with a single page in plain English. It should state what was commissioned, what was delivered, when it was delivered and where the working files can be found. Include the main contact for future questions and the agreed scope in one or two lines. If something was explicitly excluded, say so here rather than leaving it to memory.

This page is also the right place to set expectations. A short line such as “this package covers the design and build of the site; ongoing content changes are handled separately” prevents a great deal of confusion later. It is not defensive. It simply makes the boundary visible.

For a writer, the summary might list the articles delivered, the agreed word counts and the publishing locations. For a maker, it could record materials, dimensions, care instructions and the supplier of a particular finish. For a designer, it might note the final logo suite, the typefaces licensed and the files intended for print versus screen. The principle is the same: one page, no jargon, useful on its own.

A file map worth keeping

A folder of files is not the same as a file map. Clients often receive a compressed archive with names that made sense inside the studio but mean little outside it. A short map solves that. It can be a single text file or a page in the dossier. It should explain the folder structure, the difference between master files and exports, and which versions are final.

Be specific about formats. State which files are for editing and which are for handing to a printer, developer or fabricator. Note any licensed fonts, images or components, and make clear what the client may and may not do with them. If files are archived, say where and for how long. If credentials are involved, do not place passwords in the same document as the public summary; use a separate, secure method and say so.

The aim is not to impress with complexity. It is to leave the client with a folder they can navigate in six months, when the original conversation has faded.

Maintenance notes that prevent small crises

Every project has a maintenance tail, even if it is short. A website needs hosting, domain renewal and software updates. A printed piece may need a reprint specification, a paper stock reference and a printer contact. A physical object may need cleaning guidance or a note about replacement parts.

Write these notes as a short list of what needs attention, when and by whom. Separate the essential from the optional. A client does not need a lecture on best practice; they need to know that the domain renews in March, that the content management system should be updated quarterly, or that a particular finish should not be cleaned with solvent.

For a London client with a small team, this section is often the most appreciated. It turns an abstract sense of ownership into a few manageable tasks.

A short record of decisions

Projects accumulate decisions. Some are obvious in the final work; others are invisible. A brief decision record — five or six bullets is usually enough — can save hours later. Note the main alternatives considered, the constraints that shaped the outcome and any approvals given.

This is not a set of minutes. It is a memory aid. It helps when a new marketing manager asks why the tone is restrained, why a particular colour was chosen or why a supplier was preferred. It also protects the designer or maker from being asked to justify a settled matter from scratch.

Keep the language neutral. The record should explain, not defend. “The darker palette was selected to meet accessibility contrast requirements” is more useful than a long account of personal preference.

The covering note

Send the dossier with a short covering note. Confirm that the project is complete, point to the most important document and offer a brief walkthrough if the client would find it useful. Do not attach a large archive to an email without explanation. Do not use the handover as an opportunity for an upsell. The restraint is part of the message.

A handover is not a performance. It is the last useful thing you do on a piece of work. Done well, it leaves the client with a sense of order and leaves you with a reputation for finishing properly — which, in a city full of recommendations, is rarely a small thing.

All Articles

Related Articles

The Closed File: Giving Unfinished Work a Discreet Afterlife

The Closed File: Giving Unfinished Work a Discreet Afterlife

The Considered Nudge: Writing to Clients Between Decisions

The Considered Nudge: Writing to Clients Between Decisions

From Spoken Note to Signed Scope: A Disciplined Way to Handle a Rushed Brief

From Spoken Note to Signed Scope: A Disciplined Way to Handle a Rushed Brief