The hidden cost of treating email as the contract record

Ask a project where the record lives and somebody will point at the common data environment. Ask where the last instruction came from and somebody will hold up a phone. Both answers are honest, and a job can run for two years with them sitting quietly side by side: folders named to the convention, suitability codes applied, the published set current, and nobody yet asking anyone to prove the one sentence that changed the works.

That sentence is usually not in the container. It is in an inbox.

Where the instruction actually lives

On a mid-size job the published set is not the only thing site builds from. A coordinator writes “proceed as discussed — hold the Level 4 riser until the architect issues Rev D.” A contract administrator confirms a verbal instruction in a reply-all that never becomes a numbered CVI. A designer attaches a marked-up PDF to a thread whose subject line has mutated fourteen times since anyone last read it properly. A package manager forwards the lot to the subcontractor at 18:40, because the CDE upload will happen in the morning.

By morning the work has moved. The CDE still shows yesterday’s published revision. The instruction people acted on sits in a mailbox, in a forwarded chain, sometimes in a screenshot of a message that started life on somebody’s phone and was passed round a gang.

Email wins the working day for honest reasons. It is fast, it is already on every device, and it does not wait for a suitability code. Those same qualities make it a poor place to keep a contract record. A mailbox belongs to a person rather than to the project: no state, no revision, no recipient list the project can still retrieve once the sender has left, and no reliable way of showing that the attachment sitting on a laptop today is the file that went out that afternoon.

The contract forms all assume an instruction can be found. NEC compensation events, JCT architect’s instructions, FIDIC Engineer’s instructions and the ordinary confirmation of a verbal instruction each presume a dated, attributable, complete record. None of them presume a thread somebody will one day locate by remembering a word in the subject line.

A tidy environment and a messy job

A CDE can be properly set up, properly governed and properly audited, and still be a stage set, if the instructions that change issued information never cross into it.

It looks like this. The BEP describes WIP, Shared, Published and Archive. Containers follow the naming convention. Transmittals go out on time. The information manager can walk an auditor through the environment in twenty minutes and come out clean. Meanwhile the decision that superseded a detail — hold, omit, invert, proceed in advance of the revision — sits in mail, where it has sat since Tuesday. The published set is tidy because the messy part of the job never came near it.

The audience for that performance is as much internal as external. Leadership sees a licence count, a training record and a green dashboard. Site sees the last email. When those two pictures drift apart, the official record shows the play the project intended to run rather than the one that was performed.

None of which is an argument against having a CDE. It is a question about what yours is actually holding. If it holds issued files but not the instructions that qualify them, you have a very well-run drawing store, and your contract record is still an inbox.

Four costs nobody puts in the budget

The cost here is hidden because it never arrives as a software fee. It arrives as time, as a variation that will not settle, as a file that is no longer there, and as a mailbox the project never owned.

Search time. Nobody reconstructs “the email that told us to hold Level 4” with a search box. It takes archaeology, across people, devices and years. A quantity surveyor loses most of a Thursday to it: the project mailbox, then a package manager’s personal folder called Site, then a chain forwarded without the earlier replies, then a call to somebody who left in March and thinks she might still have it. A solicitor asks, months later, for the complete thread. None of that time is billed as records. It goes down as coordination, or commercial, or legal, or it is simply somebody’s evening. The project pays it most weeks and has never once named it.

Disputed variations. Work done on an informal instruction still has to be valued. The employer’s position is cheap to state — it was never instructed, it was always in scope, it was a contractor proposal — and expensive to rebut when the only contemporaneous record is tone. “Yes, go.” “As discussed.” “Don’t wait for the revision.” A variation that cannot point at a dated instruction, the person with authority to give it, and the issued container it modified is not a variation. It is a story. Stories tend to settle at a discount, when they settle at all.

Missing attachments. People remember the body of an email. The evidence is usually the attachment: the marked-up drawing, the sketch, the specification extract, the photograph of the soffit. Attachments go missing in entirely ordinary ways. The mailbox quota bounced the file and nobody checked. The shared link expired. An archiving policy stripped the binaries out. The copy you kept says “see attached” and attaches nothing. You can prove somebody wrote to you. You cannot prove what they sent.

Personal mailboxes. This is the custody failure sitting underneath the other three, and in my experience it is the one that surprises people. If the instruction lives in a personal mailbox, the project never had it. When that person leaves, IT runs the leaver process. The archive may hold a snapshot; the snapshot may be complete, or it may quietly omit the folder they kept on a laptop. Forwards into private accounts are worse — outside the organisation’s hold, not produced when they ought to be, not available when they must be. Custody that depends on one individual’s filing habits was never project custody.

When the bill arrives

All of this stays invisible while the job is busy. It becomes a bill the moment somebody else asks you to prove what you were told at the time.

On a claim, you have to show what you were instructed to do, when, by whom, and against which issued set. A pack reassembled from personal inboxes months afterwards, with holes in the chain and attachments that no longer open, is not the same artefact as a record captured on the day. Neither the other party nor the contract administrator is much moved by the fact that the team all knew. They ask for the file.

In adjudication the clock is brutal. There is no six weeks in which to interview leavers and restore a personal archive. The adjudicator wants the contemporaneous material: the instruction, the notice, the programme that sat beside it, the drawing revision it qualified. Hand over an incomplete mail export and the other side will say so, at length. Entitlement that was perfectly real on site can fail for want of a complete instruction.

At handover the shape changes but the kind does not. The owner, the facilities team and — in England — anyone following the golden thread need the history that produced the as-built. An inbox is not an asset information model, and a thread is not a health and safety file. If the instruction that changed a fire-stopping detail lives only in a leaver’s mailbox, the building inherits the gap. Somebody pays to recreate it, or the building is operated without it.

One test runs through all three settings. Can you produce the instruction as it existed at the time — complete, attributable, still in the project’s custody, tied to the container it changed — without relying on anyone remembering where they filed it?

If the honest answer is no, email is already your contract record, and you do not have one.

Try this on Monday

This takes about an hour and needs no consultant. Put last week’s published set next to last week’s mail.

List every message that told somebody to hold, omit, invert, proceed, or build in advance of a revision.
For each one, ask whether the same instruction exists as a project-owned record: numbered, dated, complete, pointing at a named container and revision.
Open the attachments from the project copy rather than from memory. Note every “see attached” that attaches nothing.
Mark every instruction that exists only in a personal mailbox, a private forward, or a thread whose owner has left or is about to.
Take one instruction and try to retrieve it as though the sender and the first recipient were both gone.

Whatever you cannot retrieve in that hour is the hidden cost. You are already paying it in search time, you will pay it again on a variation that will not settle, and you will pay it in full when a claim, an adjudication or a handover asks for the contemporaneous file.

The dull fix, and who has to pay for it

Decide at the start of a job, rather than in the middle of a claim, which communications count as instructions — and route those, and only those, through a channel the project owns, numbered and dated and pointing at the container and revision they change. Everything else can stay in mail, which is where it belongs and where it works well. Then give somebody a name and a few hours a week to sweep for instructions that never made the crossing, because a duty owned by everyone is owned by nobody; that usually sits best with the document controller working alongside the contract administrator. Ask IT now, rather than in year three, what happens to a mailbox on the day a package manager resigns, and get the answer in writing.

The leverage for the rest of it belongs to the client or appointing party, at procurement. Write the route for instructions into what you ask for alongside the information standard, then ask the bidders to exercise it on a live job while you watch, rather than describe it in a BEP. Expect to pay for the discipline: it costs somebody’s time every week, it makes Tuesday afternoons slower, and it will be resisted by people who are right that email is quicker. It is quicker. It is just not yours.