Document Control on a Bid and a Job: The Version That Went Out Was Not the One You Meant

A tender closes at two o’clock. At half past one someone notices that the pricing schedule attached to the submission is the one downloaded on the first day, not the revised one issued with Addendum 3. The bill has an extra item and different quantities. There is no time to re-price.

Or: a crew forms up a headwall from a drawing on the site trailer. The drawing is Revision C. Revision D, issued eleven days ago and emailed to the project manager, moved the outlet. The concrete is placed on Thursday.

Both are document control failures, and both are entirely ordinary. They happen in businesses with capable people because the volume of documents on a modern civil tender and a modern civil job exceeds what anyone can hold in their head, and because nobody decided who owns the current version.

What a version failure actually costs

Failure	Consequence
Priced from a superseded schedule	A non-conforming submission, or a conforming one with a hole in it
Missed an addendum	Scope or conditions not priced; potentially an invalid bid
Submitted an old version of a returnable	Wrong personnel, wrong pricing, outdated insurance certificate
Built from a superseded drawing	Rework at your cost, unless you can show you were never issued the revision
Subcontractor working from a different revision	Clash, rework, and an argument about who had what
Cannot prove what you were issued	A variation claim that fails on evidence
Conformance records against the wrong revision	Handover documentation that does not match the asset

The last row is the one that reaches furthest. Where a variation or a delay claim turns on what you were issued and when, the document register is the evidence — and a business without one is arguing from memory against a client with a transmittal log. That is the same evidentiary problem our guide to contract administration for civil SMEs identifies across the whole contract.

The tender stage: where documents multiply

A civil tender of modest size arrives as a large set of documents, and then grows.

• Issued documents — conditions of tender, conditions of contract, specification, drawings, schedules, returnables, reports.
• Addenda, each of which may replace documents, add new ones, or answer questions.
• Your own working documents — the estimate, the programme, methodology drafts, subcontractor quotes, supplier quotes.
• Quotes that get revised, sometimes several times, and which have expiry dates — the problem described in our guide to materials supply agreements.
• Returnable schedules in the client’s format, completed.
• Reference material pulled from your library.

The single highest-value control at tender stage is a nominated document controller for the bid — one person, even if it is the estimator, who owns the folder structure, downloads everything, records what was received and when, and distributes. On a small bid this is fifteen minutes a day. Without it, three people each download their own copy and one of them is working from Monday’s set.

Addenda, and the acknowledgement that is a compliance item

Addenda are the most dangerous documents in a tender because they arrive late, they change things selectively, and acknowledging them is usually a formal requirement.

• Check the portal, do not rely on the email. Notification emails go to one registered contact, get filtered, or arrive while that person is on leave. The portal is the source of truth — the platforms covered in our guide to where to find civil construction tenders.
• Check on the closing day. Addenda are issued late in the period with striking regularity, including on the final morning.
• Read what actually changed. An addendum that replaces a drawing set may change one detail, and the covering note may not say which.
• Acknowledge them in the submission, in the form required. An unacknowledged addendum can render a bid non-conforming, which is a wholly avoidable way to lose — one of the errors in our guide to common tender mistakes.
• Re-check your price against the change, rather than assuming an addendum is administrative.
• Record each one in the register with the date received and what it affected.

Where an addendum arrives too late to price properly, that is a request for an extension of the closing time, and clients grant them more often than contractors ask. Asking is a better outcome than submitting a price you do not trust.

The document register, which is the whole system

Everything else in this guide is an application of one artefact: a register listing every document, its revision, its date, where it came from and where it went.

• Document number and title as the issuer named it.
• Revision and date of that revision.
• Date received, which is frequently different and is the one that matters for claims.
• Source — portal, transmittal, email, site instruction.
• Status — current or superseded.
• Distributed to — who received it, and when.

The “date received” and “distributed to” columns are the ones that earn their keep, because they are what convert the register from a filing aid into evidence. A claim that you were not issued a revision until a certain date is provable from a register and unprovable without one.

A spreadsheet is entirely adequate for a civil SME. The tool matters far less than the discipline of one person maintaining it.

Naming, versioning and the conventions that survive

• Keep the issuer’s document number and revision in the filename. Renaming a client’s drawing to something you find friendlier destroys the link to their transmittal and to any correspondence.
• Never use “final”. There is always a document called final-v2-revised-USE-THIS, and it is never clear which one anyone used.
• Date format that sorts — year, month, day — so a folder listing is chronological.
• One current folder, one superseded folder. Do not delete superseded documents; move them, because you may need to prove what you had.
• Mark superseded copies so a printed one cannot be mistaken for current.
• Consistent structure across jobs, so anyone can find anything on any job.
• Distinguish your documents from theirs — issued documents and your working documents in separate trees.

The convention matters less than having one and applying it. A mediocre convention followed by everyone beats a perfect one followed by the person who devised it.

Controlling the submission itself

The bid you send is itself a controlled document, and the failures here are the ones that show.

• A returnables checklist from the conditions of tender, ticked against what is attached — the compliance discipline in our guide to addressing selection criteria.
• One person assembles the final submission. Multiple people uploading is how two versions of a schedule end up attached.
• Check currency of attachments — insurance certificates, licences, prequalification letters and personnel CVs all expire, and an expired certificate is a visible failure.
• Check for other clients’ names in reused text. This is the most embarrassing and most common document control failure in tendering, and it comes from copying without controlling.
• Check file sizes and formats against the portal’s limits before the last hour.
• Keep a complete copy of exactly what was submitted, with the submission receipt. When a question arises about what you offered, this is the answer.
• Submit early. Portals fail, uploads stall, and no extension is granted for either.

On the job: drawings, the superseded set and the site copy

After award the problem changes shape. There are fewer documents but they change more often, and the people using them are not at a desk.

• Issue for construction is a status, not a formality. Building from a drawing not issued for construction is a decision with consequences.
• Superseded drawings must physically leave the site. An old print in a trailer will be used. Remove it or mark it clearly.
• One place people look. A single current set, whether printed or on a tablet, and a rule that it is the only source.
• Distribution has to be confirmed. Sending a revision is not the same as it being received and understood by the leading hand.
• Talk about revisions at the pre-start when something changes, because a crew that has built a detail once will build it that way again without looking.
• Machine control models are documents too, and a superseded model is worse than a superseded drawing because nobody visually checks it — see machine control and GNSS in civil delivery.

The machine control point deserves emphasis. A drawing revision that does not flow through to the model means a machine building precisely and confidently to the wrong surface. Establish who updates the model when a drawing is revised, and how the crew knows.

RFIs, instructions and the documents that arrive informally

The most consequential documents on a civil job frequently arrive as an email, a marked-up sketch or a conversation.

• An RFI register — number, question, date raised, date answered, and what the answer changed. This is both a document control tool and the backbone of any delay or variation claim, as our guide to extension of time and delay claims sets out.
• Instructions must be in writing, and where one is given verbally, confirm it in writing the same day. The contract almost certainly requires it, and a direction that was never confirmed is a direction that did not happen.
• A sketch is a document. Date it, number it, register it and issue it — a marked-up detail handed over at a site meeting is the thing that will be disputed.
• Answers to RFIs may change scope, which makes them variations, and the register is where that is identified — see variations in civil construction contracts.
• Email is not a filing system. Documents received by email must be registered and filed, or they exist only in one person’s inbox.

Passing control down the chain

• Issue documents to subcontractors formally, with a record of what and when — not by forwarding an email.
• Reissue revisions, and confirm receipt. A subcontractor building from a superseded drawing is your problem commercially even if it is their error.
• Their quotes reference a revision. A price given against Revision B is not a price for Revision D, and this is a common source of dispute.
• Suppliers need the current specification, particularly where a change affects a product already ordered with a lead time.
• Include document obligations in the subcontract so the requirement to work from current documents is a term rather than an expectation.

The revision-referenced quote is worth a specific habit. Requiring every subcontractor and supplier quote to state the drawing and specification revision it was priced against costs nothing and resolves a whole category of argument later.

Records, retention and the contemporaneous file

• Keep everything for the period the contract and the law require, which extends past the defects period and, for some purposes, considerably further.
• Keep superseded revisions, because proving what you had at a point in time requires them.
• Back it up. A single copy on a site laptop is not a record.
• Close the job out properly — the final document set, the as-constructed information and the conformance records against the correct revisions, which is what the asset owner needs, per our guide to asset management plans and whole-of-life cost.
• The contemporaneous file is the claim. Registers, diaries, instructions and correspondence assembled as the job runs are worth more than any reconstruction, and reconstruction is visible to anyone assessing a claim.

Tools, from a folder to a platform

Approach	Suits	Watch for
Structured folders and a spreadsheet register	Most civil SMEs	Depends entirely on discipline; fine when one person owns it
Cloud storage with sync	Teams needing site access	Sync conflicts creating duplicate versions; offline copies going stale
Construction document platform	Larger jobs, or where the client mandates one	Cost, and that it only works if everyone uses it
Client’s platform	When mandated	Your records live in their system; export your own copy

Where the client mandates their platform, keep your own copy of everything. Access is typically withdrawn at completion, and the documents you may need for a claim or a defects dispute are then in a system you cannot reach. Export at handover, as a matter of routine.

Where document control meets the content library

There is a second body of documents that needs controlling: your own reusable material — capability statements, CVs, methodology sections, policies, certificates and past project descriptions.

• One current version of each, in one place, owned by a named person — the system described in our guide to building a tender content library.
• Expiry dates tracked for insurance certificates, licences, prequalification and competency records — the matrix in our guide to tickets, VOCs and competency records.
• Update at the source, not in the bid. Fixing a CV inside a submission means the next bid uses the old one again.
• Review dates on policies, because an undated policy last revised four years ago is visible to an evaluator.

The failure mode is the same in both directions: a bid assembled from copies rather than from controlled sources produces the wrong client’s name in a methodology and an expired certificate in an attachment.

What clients ask, and what a good answer looks like

• Document control procedure as a quality returnable, which is part of the quality system in our guide to quality management plans and ITPs.
• How will you manage design changes during construction? The answer is the register, the reissue process and the confirmation of receipt — including the machine control model.
• Records and handover, where the format and completeness are specified.
• Platform requirements, where the client mandates a system and expects you to use it competently.
• Evidence. A sample register from a previous job, appropriately redacted, is worth more than a procedure document.

The strongest answer names who does it. Document control fails when it is everybody’s job, and a response that identifies the role responsible reads as a real system rather than a policy.

Checklist

• Is one person nominated to control documents on each bid and each job?
• Is there a document register with revision, date issued, date received, source, status and distribution?
• Do you check the tender portal for addenda rather than relying on notification emails?
• Do you check for addenda on the closing day?
• Are all addenda acknowledged in the submission in the required form?
• Is the price re-checked against what each addendum changed?
• Do filenames keep the issuer’s document number and revision?
• Is there a current folder and a superseded folder, with nothing deleted?
• Is there a returnables checklist ticked against the conditions of tender?
• Does one person assemble the final submission?
• Are certificates, licences and CVs checked for currency before attaching?
• Has the submission been searched for other clients’ names?
• Is a complete copy of exactly what was submitted kept, with the receipt?
• On site, is there one current set and are superseded prints removed?
• Is receipt of revisions confirmed with the people who will build from them?
• Is there a defined process for updating machine control models when drawings are revised?
• Is there an RFI register recording question, dates and what the answer changed?
• Are verbal instructions confirmed in writing the same day?
• Are sketches dated, numbered and registered?
• Are documents issued formally to subcontractors, with revisions reissued and receipt confirmed?
• Do subcontractor and supplier quotes state the revision they were priced against?
• Where the client mandates a platform, do you export and keep your own copy at handover?
• Is your reusable content library controlled at the source rather than fixed inside bids?

Sources and further reading

This guide is general information for Australian civil construction businesses and is not legal or contractual advice. Document control requirements, including the form and timing of addendum acknowledgement, the status of documents issued for construction, requirements for written confirmation of verbal instructions, and record retention periods, are set by the conditions of tender and the executed contract for each project, and differ between them. Whether a failure to acknowledge an addendum renders a submission non-conforming is determined by the conditions of tender and the client’s evaluation process. Whether a document constitutes a direction or a variation, and what notice is required in response, are matters for advice on the specific contract. Retention periods for project records may extend well beyond practical completion under the contract, under limitation periods, and for taxation purposes; confirm the applicable periods rather than relying on a general rule.

• The document control practices described throughout — registers, revision status, transmittal records, superseded document control and the issued-for-construction status — are established construction industry conventions and are commonly required by quality management systems and by contract conditions. The specific requirements for any project are in its conditions of tender and executed contract; none are reproduced here.
• Addendum acknowledgement requirements referenced in §03 are set by the conditions of tender for each procurement. The tender platforms through which addenda are issued are covered in our guide to where to find civil construction tenders.
• The evidentiary role of the document register and the contemporaneous file, referenced in §01, §08 and §10, reflects the general position that entitlement to variations and extensions of time is established by contemporaneous records; the applicable notice and record requirements are in the contract and are covered in our guides to variations and extension of time and delay claims.
• Related TenderBuilt guides carrying the primary-source detail referenced above: contract administration for civil SMEs, quality management plans and ITPs, building a tender content library, common tender mistakes, addressing selection criteria, tender clarifications and the RFI window, machine control and GNSS, digital engineering and BIM, tickets, VOCs and competency records, materials supply agreements and asset management plans and whole-of-life cost.