The main types of construction documents fall into a few families: contract drawings, written specifications, the agreement and conditions, and the running paper trail a project generates while it is built (RFIs, submittals, change orders, daily reports, and as-builts). Together they define what gets built, how it gets built, who is responsible, and what actually happened on site. Understanding the types of construction documents, and how they relate, is the difference between a coordinated job and a litigated one. In our studio in Vilnius we move between most of these every week, so here is the practical version, not the textbook one.
The core types of construction documents
At a high level, construction documents split into two big buckets: the bidding/contract set (everything that defines the work before a shovel hits the ground) and the project record (everything created while the work is happening). Most disputes come from confusion between the two.
1. Contract drawings
The drawings are the graphic instructions, plans, elevations, sections, details, and schedules. They are usually organized by discipline with a sheet-numbering prefix: A for architectural, S for structural, M/E/P for mechanical, electrical and plumbing, C for civil. Every sheet carries a title block identifying the project, sheet number, revision, and who issued it, the single most important piece of metadata on a drawing.
2. Specifications
If drawings show quantity and location, specifications (the "specs" or project manual) describe quality, the materials, products, standards, and workmanship required. They are written, usually organized into CSI MasterFormat divisions. Where drawings and specs disagree, the contract documents themselves state which governs, so the order of precedence matters.
3. The agreement and conditions
The owner–contractor agreement, the general conditions, and any supplementary conditions set the legal and commercial framework: scope, price, schedule, payment, insurance, and dispute resolution. These are construction documents too, even though no one draws them.
4. Addenda and bulletins
Issued during bidding (addenda) or after award (bulletins/ASIs), these modify the documents before they become final or instruct minor changes during construction. They are dated and numbered so the latest issue always wins.
Project-record documents (the paper trail)
Once construction starts, a second category takes over. These don't define the work, they manage and record it.
- RFIs (Requests for Information): formal questions from the contractor to the design team when a document is unclear or conflicting. The answer becomes part of the record.
- Submittals and shop drawings: the contractor's proof of what they intend to install, product data, samples, and fabrication-level shop drawings, reviewed against the design intent before fabrication.
- Change orders: documented modifications to scope, cost, or time, signed by both parties. The honest backbone of every project's budget story.
- Daily reports and meeting minutes: who was on site, weather, deliveries, and decisions made. Mundane until there's a claim, then priceless.
- Punch list: near completion, the running list of incomplete or defective items to resolve before handover. We've written a full guide on the punch list if you want the detail.
- As-built drawings: the contract drawings marked up to reflect what was actually built, including field changes. These become the owner's reference for the life of the building. Our as-built drawings guide covers how to keep them honest.
How the types relate to each other
Think of it as a flow. The bidding documents become the contract documents when signed. During construction, RFIs and submittals interpret and confirm them; change orders and addenda modify them; daily reports record the build. At the end, the punch list closes out the work and the as-builts capture the final truth. Every type exists because the previous one was either ambiguous or got changed in the field.
A practical hierarchy when documents conflict
On a real job, documents will contradict each other. A typical order of precedence (always confirm it in the agreement) runs roughly:
- Signed modifications and change orders (latest dated)
- The agreement and supplementary conditions
- Addenda (latest first)
- Specifications
- Drawings, with larger-scale details generally governing over smaller-scale, and figured dimensions over scaled ones
When in doubt, you don't guess, you raise an RFI. That is exactly what the record-document layer is for.
FAQ
What is the difference between construction documents and contract documents?
"Construction documents" is the broad term for everything that defines and records a project. "Contract documents" is the specific subset that is legally binding once signed, typically the agreement, conditions, drawings, specifications, and any addenda. All contract documents are construction documents, but not every construction document (a daily report, for example) is contractual.
Do drawings or specifications take priority?
It depends on the contract, which is why every set states an order of precedence. Specifications usually govern on quality and materials; drawings govern on quantity and location. When they conflict, raise an RFI rather than assuming.
Are as-built drawings legally required?
Often yes, most contracts and many jurisdictions require as-builts at handover, and owners need them for future maintenance, renovation, and permitting. Even when not strictly required, skipping them is a decision you'll regret the first time someone needs to know what's behind a wall.
Most of these documents live as large PDF drawing sets exported from AutoCAD, Revit, or ArchiCAD, and they're heavy, often 50–200 MB+. If you spend your day marking up RFIs, redlining as-builts, and flipping through full sheet sets, a fast desktop PDF editor that opens those drawings smoothly and works locally on your machine is worth the switch. That's exactly why we built Ncored, try it free for 14 days at ncored.com.