Correspondence is a contractual record, not a conversation. The personal inbox is where project memory goes to die.
Last updated
Zepth Core module
14+ months
the average duration of a construction dispute — the period over which this correspondence will be searched, read and argued about
Arcadis Global Construction Disputes Report (2025)
The value of the average US dispute is cited on our transmittals and daily-reports pages. The DURATION is the number that matters here: fourteen months of somebody reading your emails.
$18–20K/GB
the cost of producing a gigabyte of documents in eDiscovery — of which review, by humans, is roughly three-quarters
RAND Institute for Civil Justice (2012 study)
A 2012 figure, labelled as such, and still the standard citation. The mechanism has not changed: cost scales with CUSTODIANS. One project record beats fifteen personal inboxes, and it beats them at that rate per gigabyte.
~42%
of institutional knowledge is held by individuals in a form nobody else can reach
Workplace knowledge-management research
Attributed loosely — this figure circulates through secondary sources. The order of magnitude is the usable part, and the mechanism is not in doubt: the engineer leaves, the mailbox is deactivated, and three years of instructions leave with them.
Project correspondence is where the contract is actually administered: the notice that starts a clock, the instruction that changes the work, the letter that takes a position somebody will be held to three years from now.
And it is almost universally managed as though it were chat. Filed in personal mailboxes, searchable only by the person who sent it, deactivated by IT ninety days after they resign.
This is the part that catches good projects with good arguments. A notice does not become valid because everyone knew about it. It becomes valid because it was served by the contract’s method, to the contract’s addressee, within the contract’s time.
FIDIC 2017 made this explicit and unforgiving: a Notice must identify ITSELF as a notice, cite the clause it is given under, and travel by the agreed channel. An email that describes a problem in detail, to the right person, inside the window, is not a notice if it does not say it is one. And the courts have been consistent about this for a very long time — actual knowledge does not cure defective notice. The other side knowing perfectly well what happened is legally irrelevant if you did not tell them in the manner you agreed to tell them.
Which means the question “is email a valid notice?” has exactly one correct answer: only if the contract says so, and only to the address the contract names. Not the project manager’s personal address. Not the WhatsApp group. The addressee in the contract, by the method in the contract.
The personal-inbox silo is a single point of failure that everybody accepts. The project engineer resigns. IT deactivates the mailbox on a ninety-day policy nobody on the project was consulted about. And three years of instructions, agreements, clarifications and understandings — the entire operational memory of a workstream — go with them. Correspondence addressed to the PROJECT, filed in a register, survives people. Correspondence addressed to a person does not, and it does not fail gradually; it fails completely, on a date set by an HR process.
Letters carry positions. Email carries coordination. Do not confuse them. In GCC consultant culture, positions are taken by numbered letter — sequentially numbered, referenced, logged in a correspondence register with an action-by date against each one. That is not bureaucratic ceremony; it is how a position becomes findable, attributable and dated. Email is excellent for coordination and terrible for positions, because it has no sequence, no register, and no natural way to tell the important message from the four hundred around it.
Discovery cost scales with custodians, and that is a decision you make years in advance. Producing documents in a dispute runs at eighteen to twenty thousand dollars a gigabyte, and roughly three-quarters of that is human review. That number is from 2012 and it is still the standard citation. But notice what it means operationally: fifteen personal inboxes, each holding overlapping copies of the same threads, is fifteen custodians to collect, de-duplicate and review. One project record is one. The cost difference is not marginal.
Incoming correspondence carries clocks, and clocks do not live in inboxes. A determination to respond to. A consent to give or withhold. A submission deemed accepted if you say nothing. These arrive as email, and an email is an object that sits still — it does not remind you, it does not escalate, and it does not care. Anything with a contractual response window belongs on a deadline board with an owner against it, not in a folder that somebody intends to look at.
A meritorious claim dies on formality — the right facts, the right timing, the wrong channel or the wrong addressee — and no amount of the other side having obviously known cures it.
A key person leaves and takes the record with them. Nobody notices for months, because the absence of a document is invisible until you go looking for it.
And a dispute begins. Fourteen months, on average, of people reading your correspondence. Except it is not one correspondence: it is fifteen inboxes, half-overlapping, at nearly twenty thousand dollars a gigabyte to produce — and the position your consultant took in 2024 is in there somewhere, unless the person who received it has left.
Mail addressed to the project rather than to people, threaded and held in registers — so the record survives resignation, reorganisation and the ninety-day mailbox policy. Numbered letters with references and action-by dates, which is how a position stays findable.
Response deadlines tracked on a board rather than intended in an inbox. And every piece of correspondence linked to what it actually references — the RFI, the instruction, the claim — so the thread and the record are the same object rather than two systems and a gap.
A notice is served by the contract’s method to the contract’s addressee — so a good claim does not die on formality.
The record survives the people, because it was addressed to the project rather than to a mailbox.
Response clocks are visible and owned, rather than sitting in an inbox waiting to be noticed.
A dispute means producing one project record, not fifteen overlapping personal inboxes at twenty thousand dollars a gigabyte.
Threaded and registered against the project, so it survives resignations and the ninety-day mailbox policy.
Sequential numbering, references, action-by dates — which is what makes a position findable and dated years later.
Method, addressee and timing checked against the contract, including FIDIC 2017’s requirement that a notice identify itself and cite its clause.
Determinations, consents and deemed acceptances tracked with owners — because an email does not escalate.
The RFI, the instruction, the claim — so the correspondence and the record are one object rather than two systems.
Ten years where decennial liability applies. The dispute arrives long after the project team has gone.
Registers rather than personal silos. The mailbox is deactivated ninety days after someone resigns, on a policy nobody on the project was asked about.
Sequential numbering, references, and an action-by date in the register. Positions are taken by letter; coordination happens by email. They are different instruments.
Right method, right addressee, right time — and, under FIDIC 2017, a notice that identifies itself as one and cites its clause. Actual knowledge does not cure a defective notice.
Determinations, consents, deemed acceptances. Anything with a contractual window goes on a deadline board with an owner, because an email will not remind you of anything.
Not against the project. UAE decennial liability runs ten years, and the correspondence either still exists then or it does not.
An email that describes a delay event, a change, or a disagreement in the language of a claim — but which was never served as a notice. This is the highest-value catch on the page, because the entitlement is dying while everyone is busy being reasonable.
Determinations, consents, deemed acceptances — surfaced before the window closes rather than after, which is the only time the information is worth anything.
Assembled from the RFIs, instructions and correspondence that a position actually rests on — so the letter cites the record rather than the writer’s recollection of it.
A forty-message thread contains, typically, three positions and thirty-seven acknowledgements. Extracting the three is the whole job, and it is the job nobody has time to do.
The engineer’s judgment stays in charge; the AI removes the latency and the blind spots.
The correspondence register by number, reference and action-by date. Notices served, with their method, addressee and timing checked against the clause. Open response clocks by owner and days remaining. Correspondence linked to the RFIs, instructions and claims it references. And the disclosure view: one project record, produced as a query — rather than fifteen personal inboxes, collected, de-duplicated and reviewed at RAND rates.
Only if the contract says so, and only to the addressee the contract names. And under FIDIC 2017, a Notice must identify itself as a Notice and cite the clause it is given under. An email that describes the problem perfectly, to the right person, inside the window, is not a notice if it does not say it is one. Actual knowledge does not cure a defective notice — the other side knowing exactly what happened is legally irrelevant if you did not tell them in the manner you agreed to.
Read the full answerA sequential log of every formal letter in and out: number, date, from, to, subject, the records it references, and an action-by date. It is what makes a position findable, attributable and dated three years later — which is the only test that matters, because that is when somebody will be looking for it.
Read the full answerSequentially, per correspondence stream, with a scheme published at mobilisation and never changed mid-project. The number is not decoration: it is how a letter is referenced by other letters, how a gap becomes visible, and how “our letter of the 14th” stops being a phrase and becomes a document.
Read the full answerIf it was addressed to them, it goes with them — and it does not fade, it disappears, on the date IT applies the mailbox policy. Estimates put a large share of institutional knowledge in individual hands and nowhere else, and the mechanism here is brutally simple. Correspondence addressed to the PROJECT and filed in a register survives resignation, reorganisation and retirement. Correspondence addressed to a person does not.
Read the full answerRAND put document production at roughly eighteen to twenty thousand dollars per gigabyte, with human review accounting for about three-quarters of it. That is a 2012 figure and still the standard citation. The operational point is what scales: cost scales with CUSTODIANS. Fifteen personal inboxes holding overlapping copies of the same threads is fifteen collections and fifteen reviews. One project record is one.
Against the limitation period, not the project. In the UAE, decennial liability for structural defects runs ten years from completion — and the average construction dispute lasts more than fourteen months once it starts. Retention gets decided once, deliberately, by somebody thinking about a dispute that has not happened yet. Or it gets decided by a storage clear-down nobody was consulted about.
Related answers
In the guides
Terms defined here
Zepth is the construction project delivery platform — it runs construction, procurement and asset management on one record, and does the work: reading the drawings, reviewing the submittals, matching the invoices and flagging the risks, with a human sign-off on anything consequential.
A short, tailored walkthrough on your real workflow — no generic demo.