When a field markup becomes an as-built, and what it must carry
In short
An as-built markup is a field annotation recording what was actually installed, and it becomes a record rather than a scribble only when it carries five things: the sheet and the issue it was drawn against, the date of the observation, the person who made it, the reason for the departure, and the instrument that authorised it. Without the issue reference it cannot be promoted at all.
Key takeaways
- A markup without the issue it was made against cannot be promoted, only re-verified in the field.
- The observation date and the upload date are different facts, and only one of them is evidence.
- Reason belongs on a closed list; free text is an addition to it, never a replacement.
- Store a grid reference alongside page coordinates, because flattening on export destroys the anchor.
- As-built, record drawing and conformed set are three different documents made by different parties.
An as-built markup is a field annotation recording what was actually installed, as distinct from what was drawn. It becomes a record rather than a scribble when it carries 5 things: the sheet and the issue it was drawn against, the date the condition was observed, who made it, why the installation departed from the drawing, and the instrument that authorised the departure. A markup missing the issue reference cannot be promoted into an as-built set at all.
The words are used loosely on site and that looseness travels into the software. Pinning them down is not pedantry: the documents below are produced by different parties, carry different liability, and evidence different things.
Four terms that are not synonyms
| Term | What it is | Who makes it | What it evidences |
|---|---|---|---|
| Markup | Any annotation on a drawing, at any stage | Anyone | That somebody had a comment |
| Red line | A field annotation showing a departure from the issued drawing | The installing trade, in the field | That a condition differed on the day it was marked |
| As-built drawings | The contractor's record of what was installed | The contractor | What the contractor states was built |
| Record drawings | The contractor's as-builts compiled back into the issued set | The design team, usually with a disclaimer | What was reported, redrawn |
| Conformed set | Contract drawings updated to incorporate addenda before construction | The design team | What was contracted — not what was built |
The five fields that make a markup promotable
- Sheet identity and the issue it was made against. Sheet number, revision and issue date, captured at the moment of marking rather than inferred later from whatever happens to be current. This is the field most systems omit and the one everything else depends on.
- The observation date, held separately from the upload date. On a site with patchy signal those differ by 3 to 5 days, and only one of them is evidence. A record whose worth is its timestamp is a familiar shape on a job — a delivery slot is only useful if it records the slot rather than when somebody typed it, as running a gate booking board on a tight site works through.
- Author and role, as a person and a trade rather than a device or an account. 'Marked by the tablet in the site office' is not attribution, and attribution is what makes the record usable in a dispute.
- The reason, from a closed list: response to an RFI, change order, design clash, field condition, coordination move, dimensional correction. Free text alongside it, never instead, because 400 markups with free-text reasons cannot be sorted, counted or reported on.
- The authorising instrument: an RFI number, a change order reference, an instruction — or explicitly 'none, field condition', which is a genuine and useful answer. A blank is not the same as none, and the difference matters at closeout.
The failure that kills most sets: marked on a superseded issue
The corollary is a process rule rather than a software one. When a sheet is reissued, every open markup against the previous issue has to be listed and dispositioned — carried forward, superseded or re-verified — before the new issue is distributed. Systems that quietly re-point markups at the latest issue are doing that guessing invisibly, on every sheet at once.
Location has to survive the export
- Store a grid or column reference alongside page coordinates. Coordinates are relative to one page geometry, and a sheet exported at 1:50 and re-exported at a different size moves every one of them.
- Keep the annotation as data, not only as a flattened image. Bluebeam Revu, Procore and Autodesk Construction Cloud all hold markups as objects; flattening on export is the most common way that layer becomes an unqueryable picture of itself.
- A markup on a scanned print has no vector geometry to anchor to — one more consequence of the split in extraction is clean on issued PDFs and useless on scans.
- Where the markup changes a scheduled item, it has to land against the schedule row as well as the plan, and schedule extraction has its own failure mode in the extracted equipment schedule is one column out of alignment.
- Attach the photograph and the measured value, not just the line. A dimensional correction without a measurement is an assertion; with one, it is a record.
A red line says the world disagreed with the drawing. Without a date and an issue, it does not say which drawing, or when the world disagreed.
Where this page stops
How the markups get captured — photograph with annotation, or redline on a tablet — is a separate decision resolved by who consumes the result, argued in photo markup or tablet redline for as-builts. Assembling the closeout package, of which the as-built set is one part alongside test certificates and warranties, belongs to quality, punch lists and handover.
Building capture that records those 5 fields without slowing anyone down — offline, on a phone, one-handed, in a stairwell — is a product problem more than a document problem, and it is the shape of work we scope under MVP and product builds. The rest of this silo sits under drawings, specs and document intelligence, inside our construction and contracting work.
Frequently asked questions
Short answers to the follow-ups this page tends to raise.
What is an as-built markup?
It is a field annotation recording what was actually installed, as distinct from what the issued drawing showed. To be usable later it has to carry the sheet and issue it was made against, the observation date, the author, the reason for the departure and the instrument that authorised it. Without those it is a comment on a drawing rather than a record.
What is the difference between as-built drawings and record drawings?
As-built drawings are the contractor's record of what was installed. Record drawings are the design team's compilation of those as-builts back into the issued set, usually issued with a disclaimer that they rely on contractor-supplied information. Different authors, different liability, not interchangeable in a contract or a handover package.
Who is responsible for as-built drawings?
The contractor produces them from records kept by the trades doing the work, and the design team compiles record drawings from what it receives. The obligation, the required format and the delivery point are contract terms that vary, so read the closeout provisions on this project rather than assuming last job's arrangement.
What does red line mean in construction?
A red line is a field annotation marking where the installation departed from the issued drawing, traditionally drawn in red pen on a printed sheet. It is the raw input to an as-built set, not the as-built itself, and it only becomes one when it has been dated, attributed and tied to the drawing issue it was marked against.
- as-builts
- field capture
- drawings
- document control
The work behind this page
Builds from our portfolio that this page draws on.
GroundUp
A construction project-management command centre for general contractors that keeps schedule, RFIs, budget and the field log in one place — and maps the critical-path recovery the moment a job slips.
Real EstateNotewell
An AI meeting assistant that records and transcribes every meeting, extracts the decisions and action items, assigns owners and due dates, and tracks follow-through until it's done.
Productivity AIRead next
- The drawing comparison marks every sheet as changedWhen a comparison returns differences on every sheet, it is usually telling you it never managed to line the two files up. Three sheets you know did not change will settle it in about ten minutes.diagnostic
- The title block is the metadata layer of a sheet setEvery document system built over a sheet set is really built over the title block. Some of its fields are dependable across consultants and some are not.definition
- Deferred submittals: the items the register has to hold openA deferred item is an obligation with a later trigger and a reviewer outside your contract. A register that files it under 'not started' has already lost it.definition
- Extraction is clean on the issued PDFs and useless on the scanned onesMeasure effective resolution at the smallest annotation, the skew angle across the sheet, and the contrast between linework and background. Those three explain almost every scan that will not read.diagnostic
- Order of precedence when the drawing and the specification conflictPrecedence is a contract term, not an industry constant. Until somebody reads the clause on this project, no conflict-detection tool can rank what it finds.definition
- The extracted equipment schedule is one column out of alignmentValidate three known rows against the sheet by tag number rather than by position, then run the four post-extraction rules that catch a shift before anyone prices the schedule.diagnostic
Working on something in this space?
Tell us where you are in a sentence or two. We'll tell you honestly whether we're the right team, and what a sensible first slice of the work looks like.
Start the conversation