Current for construction — say it clearly

Article Documents & communications ~8 minutes

Site walks up to a drawing. The stamp says Rev C. Someone on the tablet shows Rev D from an email last Tuesday. The supervisor asks the only question that matters: which one are we building?

If the answer takes more than a few seconds — or depends on who you ask — the document system has already failed its first duty. Registers, file servers, and cloud folders are worthless on the day if they cannot settle that conversation before the concrete truck arrives.

Revision discipline is not pedantry. It is how design intent, site method, inspection, and commercial entitlement stay aligned through time. “Current for construction” is a promise with a date on it. Vague “latest” is not a promise; it is a rumour with a PDF attached.

What good revision practice looks like

Controlled documents are not “files with dates.” They are a living promise about what is approved for a purpose — construction, information, tender, or approval — and how that promise changes without erasing how you got there.

In practice that means:

• Each meaningful change becomes a new revision, not an overwrite that quietly erases history and leaves no way to explain yesterday’s work.
• The project can name which revision is current for construction (or for approval, or for information) without a committee meeting every time someone opens a sheet.
• Superseded revisions remain readable for audit and investigation, but are not the default site copy pinned at the workface.
• Issue to parties always names the revisions that travelled, so receipt is not ambiguous.
• Questions, defects, and variations point back to the exact revision that caused confusion — not “the drawing generally.”
• Disciplines stay reconciled: related sheets do not drift out of step without someone noticing which package ruled.

Information requirements from owners and clients almost always protect this idea: fitness for purpose, single source of truth, and a trail through time. Contract suites differ in vocabulary — IFC, for construction, approved for use — but the site test is blunt. Can two competent people independently name the same authority revision before they commit labour and materials?

Good revision practice also respects that not every PDF in a mailbox was meant to be built from. Working copies, markup sketches, and “for information only” extracts have a place. Confusion arises when status is unspoken and informal distribution outruns the controlled statement of current.

Where projects slip

Revision chaos is rarely dramatic. It is habitual — and habits feel faster than process until the first expensive mismatch.

• People reprint from the last convenient PDF in Downloads because walking to the register felt like delay.
• “Marked-up as-built” scans replace controlled revisions without a conscious status change; soon nobody knows which red pen was approved.
• Two disciplines update related sheets out of step; the package that “ruled” exists only in someone’s head.
• Email subject lines say “latest” without a revision letter anyone trusts, and the thread that contained the answer has scrolled away.
• Site packs mix sheets from different issue dates because packaging started from a pile of attachments rather than a named set of controlled revisions.
• Inspectors check against one copy while fabricators cut from another — both convinced they were following instructions.

The result is quiet rework: fabricators cut from yesterday, installers follow today, and the variation conversation arrives next month. Safety and quality conversations get harder when the evidence trail cannot name the sheet that sat in front of the crew. Commercial teams then argue entitlement against a fog of “what everyone thought was current.”

How Cynilo supports the practice

Cynilo keeps documents in a version-aware register. Revisions are first-class — you can see what is current, what was issued, and what belongs to history — without treating email as the archive or asking the longest-serving person on the project to remember.

When a transmittal goes out, it references those revisions so formal issue names what travelled. When someone raises a question or an issue, they can point at the same controlled item instead of attaching yet another orphan PDF. Review trays can gather related sheets without dissolving the register underneath. The practice is industry-standard; Cynilo makes it the default path instead of the optional one you rediscover after a claim workshop.

How-tos explain how to raise a revision in product language. This article is the leadership reminder: current is a decision the project must own, not a vibe that floats between inboxes. Document controllers and design leads set the culture; the register makes that culture durable.

What good looks like in a week

On a job with clear revision discipline:

• Site packs state revision letters explicitly, and supervisors treat that letter as part of the work order.
• Superseded sheets are hard to mistake for current — history is available, authority is not ambiguous.
• Design changes leave a trail a stranger can follow a month later without interviewing the author.
• “What did we build from on that day?” is answerable in minutes, not days of archaeology.
• Formal sends and RFIs that cite drawings name the revision, so later commercial reading does not require guesswork.

The weekly test is simple. Ask three people independently what is current for construction on a critical sheet. If they agree without checking someone’s phone, the practice is working.

A short story from a stations package

On an urban stations package, architectural elevations and structural steel details moved in parallel through a late change window. Site received “updated elevations” by email on Thursday evening. Steelwork fabrication continued from the structural package issued for construction the previous week. Over the weekend the architectural sheet that affected canopy clip details changed again — still by informal send to a familiar contact.

By Monday the canopy clips had been cut to the wrong geometry. Everyone involved could produce a PDF and a timestamp. Almost nobody could show, without argument, which revision had been named current for construction for that coordination zone at the moment steel left the shop. The rebuild cost less than a major claim and more than a careful revision habit. The project’s lasting change was not a new stamp — it was an agreement that current for construction lives on the register, and informal “updated” emails never outrank it.

Closing

Register discipline starts in When “send me the latest drawing” fails. Formal send closes the loop in “I emailed it” is not a formal issue. Revisions are the middle hinge: the promise about what “current” means on the day the work happens.

Previous: When “send me the latest drawing” fails