Keep a letter book you can defend

Article Documents & communications ~9 minutes

Most programmes do not lose arguments because nobody wrote anything. They lose because the writing lived in the wrong places — a personal mailbox, a forgotten Word file, a draft that was “meant to be sent” but never became a durable record.

When the commercial temperature rises, someone asks a simple question: where is the letter book? If the answer is a shrug toward Outlook, a shared drive labelled “comms,” or “ask whoever sent it,” the project has already spent the goodwill that careful correspondence was meant to preserve. Formal writing is how the contract speaks on paper. Papers that cannot be found do not speak.

What good correspondence practice looks like

Formal correspondence — notices, directions, claims, responses, and other statements of position — is not decorative paperwork. It is how parties record entitlement, instruction, and disagreement with a date and an author the project can still produce under scrutiny.

Mature teams keep that conversation in one place the project owns.

In practice that means:

• Outgoing and incoming letters sit in a project correspondence register, not only in Outlook or a personal archive.
• Each item has a type and status people can scan — draft, sent, received, closed — so the book remains navigable under stress.
• Related documents and queries can be linked without copying the whole file into every email and spawning five conflicting attachments.
• The same register survives staff holidays, resignations, and company changes on either side of the fence.
• Search is by contract reality (subject, parties, dates), not by “who might still have the thread.”
• Tone matches consequence: friendly coordination stays friendly; contract language lives where later readers expect to find it.

This is not bureaucracy for its own sake. It is how you show, calmly, what was said and when — before external advisors arrive and ask for a continuous chain. Good letter books also respect proportion. Not every email is a letter. Treating every hello as formal correspondence buries the notices that matter. Treating every notice as an informal email pretends there is no letter book at all.

Where projects slip

Slippage usually looks polite — which is why it continues until it is expensive.

• Important notices begin life as informal emails “to get things moving,” then never graduate into the register.
• Drafts circulate in personal folders; the register stays empty until someone remembers after a workshop invitation arrives.
• Attachments replace links — five versions of the same letter appear across devices and nobody agrees which one was sent.
• Contractors keep their own book; the principal keeps another; neither matches in a dispute workshop, and half a day disappears to reconciliation.
• Softened language and soft storage travel together: a direction that changed the job sounds casual and lives somewhere unfindable.
• Incoming formal letters are acknowledged in chat but never recorded as project records, so one side’s book is fuller than the other’s by accident.

When external advisors finally ask for the chain, the team spends weeks assembling a story that should already have been continuous. The cost is not only photocopying and time. It is credibility — the sense that the project’s formal voice was serious in the moment, not improvised in hindsight.

How Cynilo supports the practice

Cynilo’s Correspondence register is the project letter book — formal communications you may need later, kept with the same discipline as documents and RFIs.

Letters are project records. They can travel with evidence (linked documents) and sit beside the questions and answers that shaped the commercial position. You still write carefully; Cynilo makes sure the writing has a home the project can defend. Formal questions belong next door in the RFI habit when the need is information rather than a statement of contractual position. Document control and formal issue remain upstream: letters about drawings are stronger when the drawings themselves are controlled and issued properly.

Button-level steps live in Help How-tos. Learn’s job is to remind the leadership team why the book matters when the programme is “too busy for paperwork.” Busy programmes are exactly when selective memory and private folders do the most damage. The platform removes one excuse — “we had no place for this” — and leaves the only real choice: whether the team will use the place it has.

What good looks like in a week

On a job with a letter book that holds:

• Notices and directions land in the register the same day they go out — not “when someone has time.”
• Incoming formal letters are recorded, not only acknowledged in chat.
• Related drawings or RFIs sit near the letter, not buried in a forgotten zip.
• A new contract administrator can take over without inheriting someone’s laptop culture.
• Dispute or steering meetings start from the register instead of a scramble of printed emails with missing attachments.

A healthy weekly habit is a short pass across open or recent formal items: what went out, what arrived, what still needs a response. That pass is lighter than reconstructing a chain under claim pressure — and it trains the team that the book is live, not ceremonial.

A short story from a road corridor upgrade

On a long corridor upgrade, a contractor issued a sequence of delay notices by email to familiar addresses during a difficult weather window. The principal’s site team acknowledged receipt informally and kept moving. Months later, in a commercial workshop, both sides agreed weather had been ugly. They could not agree which notices had been received in what form, on which dates, with which attachments supporting the claim narrative. One side produced a tidy binder assembled after the fact. The other produced partial inbox exports. Neither looked like a continuous project letter book owned jointly as a living practice.

The settlement took longer than the weather event. Afterward the joint governance table insisted that formal notices lived in the project correspondence register with links to supporting documents, and that chat acknowledgements were not a substitute for recording receipt. The writing still had to be careful. At least the papers now had somewhere honest to live.

Closing

Formal questions belong next door in the RFI habit — see Ask it so you can rely on the answer. Formal statements of position belong here: a letter book the project owns.

This article closes the Documents & communications reading path that began with controlled documents, revisions, review trays, and formal issue: When “send me the latest drawing” fails → Current for construction — say it clearly → Stop running the job from fourteen inboxes → “I emailed it” is not a formal issue → Ask it so you can rely on the answer → here.

Previous: Ask it so you can rely on the answer