The specifications are not the entire scope

By Cotney Consulting Group. 

Roofing contractors are often told to follow the specifications, and they should. But the specifications are not the entire scope. 

Drawings, specifications, addenda, contracts, supplementary conditions, manufacturer requirements, referenced standards and actual site conditions may govern a roofing project. Each document may contain part of the contractor’s responsibility, and the risk begins when those documents do not align. 

The drawings may show one assembly while the specifications describe another. The contract may transfer risks that are not mentioned in the technical sections. The manufacturer may require details that were not included in the tender documents. Existing conditions may make the proposed design difficult or impossible to install as drawn. 

A contractor that prices only the roofing specification may miss obligations located elsewhere in the project documents. A contractor that relies only on the drawings may miss performance, testing, warranty, documentation and closeout requirements. 

The estimate must account for the full contract package, not only the pages that appear to describe the roof. 

The scope is spread across several documents 

Construction documents are organized for different purposes. The drawings communicate dimensions, locations, assemblies and details. The specifications describe materials, performance requirements, execution standards, testing, submittals and closeout obligations. The contract establishes legal and commercial responsibilities. Addenda modify the tender documents before award, while supplementary conditions may change the meaning of the general conditions. 

The roofing contractor must determine how those documents work together. That requires more than searching for the word “roof.” 

Temporary protection may be addressed in one section, demolition in another and coordination with mechanical or electrical work elsewhere. Safety requirements may appear in the owner’s project manual. Waste handling, access, hoisting, noise restrictions, working hours and site security may be addressed outside the roofing division. 

The scope may also include responsibilities created by reference. A specification may require compliance with a manufacturer’s published installation instructions, a referenced standard or an owner guideline that is not reproduced in the tender package. 

The contractor must identify those references and determine what they add to the work. 

Document priority must be understood 

Project documents do not always agree. When they conflict, the contract may establish an order of precedence. One document may govern over another, or the contractor may be required to request clarification before proceeding. 

The estimator should identify that hierarchy before tender. It is dangerous to assume that the most detailed drawing automatically controls or that the specification always overrides the plan. 

The answer depends on the contract. If the drawings show two layers of insulation and the specification describes three, the contractor should not quietly choose the less expensive interpretation. If the detail shows a standard flashing height but the specification calls for a higher minimum, the discrepancy should be clarified. 

Pricing one interpretation while the owner expects another creates avoidable dispute. A clear request for information before tender is stronger than an argument after award. 

Tender questions should be logged with the date submitted, the response received and the effect on scope or price. A clarification has little value if the answer never reaches the estimator, supplier or project team. 

Addenda can change more than the price 

Addenda are often reviewed quickly as the tender deadline approaches. That is a mistake. 

An addendum may change materials, quantities, details, schedule, access, warranty requirements or contract language. It may answer one bidder’s question in a way that affects every contractor.  

The change may appear small while creating a major operational effect. A revised insulation thickness can affect material costs, labour, fastening, perimeter heights and equipment curbs. A new completion date can alter weather exposure and crew availability. A modified testing requirement can add time, coordination and repair responsibility.  

Every addendum should be logged, distributed and reviewed by the people responsible for estimating, operations and contract risk. The company should confirm that every tender revision is reflected in the final estimate. An addendum acknowledged but not priced is still a missed scope item. 

Document control must be deliberate 

The company should maintain one controlled project-document set that identifies the current drawings, specifications, addenda, approved substitutions and issued revisions. 

Superseded documents should be marked clearly and removed from active use. Estimating, purchasing, project management and the field should all be working from the same information. A revised detail does not protect the contractor when the crew is still building from an earlier drawing. Document control should identify who receives revisions, who reviews them and how the effects on scope, price, schedule and procurement will be communicated. An update to a drawing may require more than just replacing one file. It may affect purchase orders, shop drawings, field instructions, subcontractor scope and completed work.  

Revision control is not an administrative formality. It is part of project risk management. 

The contract can expand the technical scope 

Roofing contractors sometimes focus heavily on technical requirements while giving less attention to the contract. The contract can change the real cost of the work. 

It may require the contractor to verify dimensions, coordinate trades, protect completed work, provide temporary facilities, attend meetings, submit detailed schedules, maintain specific insurance, perform testing, absorb certain delays or return repeatedly for closeout. 

The technical specification may accurately describe the roof assembly, while the contract shifts significant operational risk to the contractor. 

The estimator should understand who is responsible for site access, weather protection, hoisting, temporary heating, material storage, security, damage from other trades, permits, inspections and disposal. 

Payment terms also matter. Holdback, invoice requirements, change-order procedures and closeout conditions may affect cash flow even when the technical work is straightforward. The roofing scope is not fully understood until both the technical and commercial obligations have been reviewed. 

Site conditions can override tender assumptions 

The documents describe the intended work. The site reveals whether those assumptions are realistic. 

Existing roof assemblies may differ from available records. Deck conditions may be concealed. Drainage may not match the drawings. Access may be more restricted than expected. Mechanical equipment may have been added after the original construction documents were prepared. 

The contractor should complete a site review whenever the tender process allows. The review should confirm access, staging, loading, hoisting, storage, interior protection, operating hours, occupied conditions, electrical hazards, roof elevations and visible existing conditions. 

A site visit does not eliminate concealed risk. It does help the contractor identify conditions that should have been visible before tender. When access is limited or destructive investigation is not permitted, the estimate and tender should state the assumptions used. Silence does not protect the contractor when the site later proves more difficult than expected. 

Existing conditions must be distinguished from design responsibility 

Roofing contractors are expected to draw on their experience and identify obvious concerns. That does not mean they should casually accept design responsibility for the entire building envelope. 

The contractor should identify when the proposed work conflicts with observed conditions, manufacturer requirements or sound roofing practice. It should raise those concerns promptly and document the response. 

At the same time, the contractor should avoid redesigning the project without clear authority, appropriate qualifications and compensation. A contractor that notices inadequate flashing height, poor drainage, questionable attachment conditions or incompatible materials should not simply proceed because the detail appears on the drawings. 

The issue should be referred to the appropriate design professional or consultant. Constructability review is part of responsible contracting. Uncontrolled redesign is not. 

Delegated design must be recognized and priced 

Some project documents assign limited design responsibilities to the contractor or its specialists. That may include engineered attachment, wind-uplift design, tapered insulation layouts, support details, shop drawings, calculations or professional seals.  

Those obligations should not be treated as routine submittals when they require design judgment, engineering review or specialist involvement. 

The contractor should determine who will perform the delegated design, what information must be provided, which professional qualifications are required and who carries responsibility for coordination. 

The cost and schedule effect should be included before tender. A requirement for sealed calculations or professional design can affect consultant fees, submittal timing, procurement and field installation. Delegated design is still design responsibility. It must be recognized, assigned and controlled. 

Manufacturer requirements must be confirmed 

A project may require a specific roof-system warranty. That requirement can create responsibilities beyond the tender drawings and specifications. 

The manufacturer may require approved products, attachment patterns, insulation arrangements, details, inspections, testing or contractor qualifications. It may also impose limitations on installation in cold weather or on certain substrates. 

The estimator should confirm that the specified assembly is eligible for the required warranty. Substitutions should not be priced merely because they appear technically similar. 

The manufacturer must confirm whether the proposed materials and details are acceptable within the warranty system. The contractor should also understand who pays for corrections identified during manufacturer inspections. A warranty requirement without confirmed system compatibility can create expensive changes after award. 

Referenced standards carry real obligations 

Specifications frequently reference building codes, test methods, industry standards and technical publications. Those references may establish performance requirements that are not repeated in the specification.The contractor should identify which standards apply and whether the tendered system satisfies them. 

In Canada, applicable requirements may also depend on the code edition adopted by the province, territory or municipality. National model codes provide an important framework, but the governing jurisdictiondetermines what applies to the project. 

The contractor should not make engineering decisions outside its qualifications. It should understand when wind resistance, snow loading, fire classification, energy performance, vapour control or structural attachment requires design input. 

A reference to a standard is not decorative language. It may define the performance the contractor is expected to deliver. 

Division of responsibility must be clear 

Many roofing problems occur where one contractor’s work meets another’s. The project documents may show the completed condition without identifying who installs equipment curbs, provides wood blocking, flashes mechanical penetrations, raises existing units when insulation thickness increases, protects temporary openings or repairs damage caused by another trade. 

Those responsibilities should be defined before the work begins. The specifications may assign related work to different divisions, while the general contractor may assume that the roofer will complete any work that touches the membrane. 

The roofing contractor should not rely on assumptions. Scope interfaces should be reviewed during estimating and clarified during project handoff. Undefined interfaces lead to change-order disputes, schedule delaysand warranty problems. 

Temporary work is still part of the scope 

Temporary protection is often underestimated because it does not remain in the finished building. It still requires labour, materials, supervision and risk. 

The contractor may need to protect open roof areas, interior spaces, stored materials, completed work and adjacent surfaces. Temporary drainage may be required, and work may need to be phased around occupied operations or in response to changing weather. 

The documents should be reviewed to determine the required level of protection and who is responsible if water enters during construction. A general instruction to maintain the building's watertightness can create significant obligations if the phasing and temporary systems are not understood.  

Temporary work should be estimated with the same discipline as permanent work. It may be removed later, but its cost and risk are real. 

Testing and inspection requirements must be priced 

Testing can include moisture surveys, adhesion tests, pull tests, flood testing, electronic leak detection, quality inspections and manufacturer reviews. These activities may require coordination, access, temporary repairs, return visits and written reports. The contractor should determine who arranges the testing, who pays for it and who is responsible for repairs or retesting when results are not accepted. 

Testing schedules can also affect production. A roof area may need to remain exposed until inspection is complete. Overburden may not be installed until waterproofing is tested, and adhesion results may be requiredbefore materials are ordered. 

Testing is not simply a closeout item. It can change the sequence and duration of the work. 

Submittals control procurement and installation 

Shop drawings, product data, samples, safety information, warranty forms and project schedules are sometimes treated as administrative paperwork. They are part of production planning. 

Materials may not be released until submittals are approved. Work may not begin until details are reviewed, and substitutions may require additional technical information and consultant response. 

The contractor should identify every required submittal, who will prepare it and how long approval may take. Late submittals create late purchasing. Incomplete submittals create repeated review cycles. The estimate should include the administrative effort required to prepare, track and revise them. 

A project delayed in the office can lose production time in the field. 

Closeout requirements should be identified early 

The contract may require warranties, maintenance manuals, as-built drawings, photographs, test reports, inspection records, training, statutory declarations, clearance certificates and completion of deficiencies before final payment. 

These items should not be discovered after the crew has left. The project team should create a closeout register during handoff and update it throughout the work. Required photographs should be taken while details remain visible. Product records should be retained, warranty applications submitted on time and deficiencies closed promptly. 

The contractor should also understand which closeout items affect substantial performance, final billing or the release of the holdback. Completing the installation does not automatically complete the contract. 

Assumptions must be written into the tender 

No estimator can eliminate every unknown condition. The company can make its assumptions visible. If the estimate assumes normal working hours, clear access, one mobilization, dry-deck conditions, available power, owner-provided structural support or uninterrupted staging, those assumptions should be stated. 

Exclusions should be specific enough to identify responsibility without becoming an attempt to avoid every reasonable obligation. Clarifications should address genuine gaps or conflicts in the documents. 

The tender should not depend on internal assumptions that the customer never sees. A number supported by written assumptions is easier to defend than a low price built on silent interpretation. 

The handoff must include the document history 

When a project is awarded, operations should receive the same controlled document set used to price it. That includes final drawings, specifications, addenda, tender clarifications, accepted alternatives, contracts, correspondence and supplier quotations. 

The project manager should understand which assumptions were included, which risks were accepted and which revisions changed the original tender.  

A final contract may differ from the tender package. Those differences must be identified before the project begins. The handoff should also confirm unresolved questions, submittal deadlines, long-lead materials, testing, temporary protection and closeout requirements. 

The project team cannot properly execute the estimate when it does not know which documents informed the price. 

The lowest price often contains the most assumptions 

Two roofing contractors can review the same project and arrive at very different prices. The difference may not be material cost or labour efficiency. One contractor may have included temporary protection, testing, coordination, hoisting, remobilization, detailed closeout and realistic weather exposure. The other may have priced only the visible roof assembly. 

The lower number may appear more competitive. It may also contain more unspoken assumptions. The objective is not to add unnecessary cost to every tender. It is to understand the full obligation before committing to the price. 

A roofing contractor should know exactly what it has included, what it has excluded and what remains unresolved. 

Read the project, not just the specification 

Specifications are essential. They describe materials, performance, execution and quality expectations that the roofing contractor must understand. 

But they are only one part of the project. The complete scope is set out across the drawings, contract, addenda, referenced standards, manufacturer requirements, site conditions and coordination obligations. 

Strong contractors do not review those documents independently. They reconcile them. They control revisions, track clarifications, identify delegated design, confirm interfaces and carry the real cost of execution into the estimate.  

The specifications may describe the roof. The complete project documents define the responsibility.