A door schedule names one hardware set. The specification describes another. The drawing says “fire-rated,” but the product section leaves the rating unresolved. A tenderer prices the least demanding interpretation, and the team discovers the difference after bids arrive. A specification review is not a line-by-line proofreading exercise. It is a deliberate search for contradictions between the design intent, drawings, schedules and written requirements.
Architects often focus on visual drawings while written specifications are assembled late or copied forward from a previous project. The AIA’s guidance on drawings and specifications treats the two as coordinated project information. This article gives a practical review method for young architects and project leads. The contract and local practice determine which documents govern if a discrepancy survives; the aim is to remove avoidable discrepancies before tender.
Start with the project’s decision list
Before reviewing text, list the design choices that matter most to the price and performance: envelope assembly, glazing, doors, fire and acoustic ratings, waterproofing, finishes, equipment, accessibility and any unusual existing condition. If you have limited time, begin where an inconsistency would change a bid or create site rework. Do not assume every section carries equal risk.
For each item, find the drawing reference, schedule entry, relevant specification section and any consultant input. Make a row with those references. The row should answer a simple question: can a competent tenderer identify one intended requirement from the package? If two documents point to different answers, record a conflict. If a requirement is missing, record an omission. If an option remains open, label the decision owner and deadline.
Do not resolve technical criteria by picking the sentence that sounds more precise. Ask the responsible architect and specialist to confirm the design. A spec can be beautifully written and still describe the wrong assembly. The reviewer’s job is to expose the discrepancy and route it to the person with authority to decide.
Check names, numbers and status
Compare product and system names across all documents. Does “Type W4” mean the same wall in the plan, detail, schedule and specification? Is the drawing calling for one glass type while the spec lists another? Do finish codes in the room schedule map to actual sections? Check dimensions, ratings, materials, tests, installation requirements and performance criteria that materially affect procurement.
Pay attention to placeholders. “TBC,” “by others” and bracketed template choices can survive into a tender issue. A reviewer should either obtain a decision, state a clearly managed allowance or remove the placeholder if it does not apply. Avoid deleting it silently when it represents a real missing scope. The project lead may need to discuss the unresolved item with the client or cost consultant.
Check revision status. A late drawing change may not have reached the spec writer. Note the current issue date of each source. A comparison between a revised façade detail and an old specification can produce false alarms unless the versions are clear. Conversely, a spec imported from a prior project may mention a system the current design never uses.
Review one assembly from plan to procurement
Choose a representative assembly such as an external wall. Trace it from the plan tag to the section, enlarged detail, finish schedule, specification and consultant requirements. Ask whether the components, interfaces and performance claims align. Does the detail show a cavity barrier, waterproofing transition or thermal line whose written scope is unclear? Who provides the component? Who coordinates installation at the adjacent system?
This is more valuable than merely reading every specification section in order. A contractor prices assemblies, not isolated pages. A conflict often sits at a boundary between trades. Your review should follow that boundary. Write the question in terms a decision maker can answer: “The detail shows continuous membrane across the slab edge; the spec appears to assign waterproofing only within the roof zone. Which trade owns the transition?”
Do not solve specialist fire, acoustic or structural questions from generic internet advice. Mark the interface, ask the relevant consultant and document the approved answer. The final text and drawing should express the same decision.
Use a conflict log that can close
Each issue needs an ID, references, consequence, proposed decision owner, response and final revision. “Check doors” is too vague. “D-07 is 45-minute rated on A-602; section 08 71 00 lists no rating. Fire consultant and project architect to confirm by 12 October; update schedule and section before issue” can be acted upon. Keep the log separate from casual comments in a PDF so decisions do not disappear when markups are consolidated.
Rank issues by impact: safety and regulatory questions first, then bid scope and cost, then clarity and editorial consistency. A typo may matter, but it should not hide a missing fire-rated assembly. Assign realistic due dates and escalate unresolved high-impact issues before the tender package is locked.
Close each item by checking the revised PDF set and specification, not by marking “answered” after a meeting. If a consultant’s response changes the design, confirm all affected documents. A late correction in one file can create a new conflict elsewhere.
Watch for copy-paste language
Master specifications and past projects can speed work, but they may carry irrelevant products, climate assumptions, codes or warranty language. Search for names of old clients, cities, standards and alternate materials. A text search is useful, but it cannot tell you whether a requirement is appropriate. A reviewer still has to compare the written section with the current design and location.
Remove options that are not part of the project, with the responsible writer’s review. Keep options only when the tender is intentionally asking bidders to price alternatives and the documents explain the basis. An unlabelled “or equal” or a choice between incompatible systems can produce bids that cannot be compared fairly.
If the project uses proprietary products, confirm that the description matches what the design intends and what local procurement rules allow. Do not insert brand names because they appeared in a template. Ask what performance or interface requirement actually matters.
Make the review a learning task
A junior architect can take one door, wall or finish system and build the comparison row under supervision. Ask a senior to explain why a specification clause exists and which drawing shows its effect. This teaches how design intent travels into procurement. Keep the reviewed example as a private learning record, without taking confidential project documents outside the firm.
In a job interview, describe the method rather than sharing a client spec you cannot disclose: “I traced door hardware sets across the schedule and specification, found two inconsistent ratings, logged the decision and verified the corrected issue.” That is useful evidence of coordination and quality control. Do not claim you authored the whole specification if you only reviewed a section.
For a project lead, build a recurring review point before each major issue, not only before final tender. A small check at design development can prevent a large late correction. Assign each discipline the sections and interfaces it must review, and confirm who owns the final cross-document check.
A six-question pre-tender pass
Keep a copy of the final review log with the issue set so the team knows which assumptions were resolved and which were explicitly carried forward. A future construction question should be checked against that record before someone invents a new answer.
Are the document versions aligned? Do drawing tags map to schedules and written sections? Are performance criteria consistent? Are interfaces and trade responsibilities clear? Are template options and placeholders resolved? Has every high-impact conflict been closed in the issued files? If one answer is no, record the specific item, owner and decision date.
The review is finished when a tenderer can price the intended work from a coherent package. A good specification check does not merely polish prose; it finds where two project documents tell different stories and forces the team to choose one.
Browse current architecture jobs on Jobs.archi and compare your next step with our guide to the gap between architecture school and practice.
The post The Specification Review That Catches Conflicts Before a Tender first appeared on jobs.archi.