Is the roofing package clear enough to price and sequence?

Compare repair, replacement or new-roof proposals on clear zones, interfaces, design responsibility, logistics and handover so the package can be priced, sequenced and built without hidden gaps.

Commercial roof package viewed within an active construction project.

Package boundaries come before price comparison

Deck, vapour control, insulation, waterproofing membranes, slate, lead flashings, rooflights, outlets, parapets, edge protection and temporary weathering may sit across several trades. On a Scottish school extension, listed building refurbishment or commercial project, the tender should allocate openings, supports, drainage connections and protection of completed areas.

Supply, installation, design input, testing and maintenance information may also have different owners. Clear exclusions and builder's-work interfaces reduce the risk of gaps becoming delay, disputed change or incomplete handover.

Design responsibility must follow the actual information

Check the revision status of current drawings, roof build-up, details, specification and schedules. Unresolved falls, drainage, fire, thermal, wind, acoustic or plant interfaces should stay with the appropriate design party rather than transferring silently through an ambiguous package. The project team should also settle any building warrant or planning authority question before a dependent roof detail is released.

Technical queries, substitutions, samples and revised details need a clear decision route. Any manufacturer, warranty or third-party requirement should be verified for the project instead of being assumed from a generic roof system or service description.

The master programme needs roof-zone dependencies

A single roofing start date is not enough when structure, deck, upstands, drainage and zones become ready at different times. Design decisions, procurement, access, lifting, inspection and follow-on trades all affect when weather resistance can be achieved.

Temporary weathering needs clear ownership while outlets, penetrations or interfaces remain incomplete. Allocate inspection, forecast response, damage and removal by roof zone, then set duration and weather-tight milestones against the agreed dependencies.

Late penetrations can undo completed waterproofing

Every penetration needs a location, size, support detail, responsible trade and required date. Late services, plant supports or edge changes can damage completed work or alter a tested junction, so the change and making-good responsibilities should be agreed first.

Zone handovers between deck, roofing and later trades should make the condition and outstanding items clear. Where access continues, walkways, protection and permitted routes help prevent a completed roof becoming general construction access.

Hold points and handover protect concealed work

The project team and specification should set which substrates, vapour-control layers, insulation, outlets, upstands, edges and penetrations need inspection before covering. A percentage-complete figure cannot show whether a critical junction is accepted or waiting for another trade.

State handover requirements at tender stage and tie them to roof zones. List the required as-built information, product data, photographs, maintenance guidance, outstanding-defect position and project-specific warranty documents, then verify each item before award.

Settle the roofing scope before award

Set out the project stage, roof zones or quantities, current drawings, specification, programme, interfaces, logistics, design duties, hold points and handover needs. Unresolved information should be visible so proposals do not price different assumptions as if they were comparable.

Before award, verify technical responsibility, named people, insurance and health-and-safety arrangements. Accept design assumptions, price and construction dates only when the written scope and responsibility schedule support them.

Frequently asked questions

What makes roofing tender returns comparable?

Current information, consistent roof zones, clear package boundaries, design duties, logistics, programme dependencies, hold points and handover requirements give bidders a common basis.

How should design responsibility be allocated?

Use a responsibility schedule that distinguishes design, coordination, decision and installation. Unresolved project design should not move through vague package wording.

What happens when another trade adds a late penetration?

Use the agreed change route and settle the support detail, programme effect, opening and making-good responsibility before the completed roof is altered.

Who is responsible for temporary weathering?

The contract and package documents should allocate installation, inspection, response, maintenance and removal for each stage.

Which roof details need hold points?

The specification and project team should choose details that will be concealed or difficult to revisit, with the required inspection party and release route agreed before covering.

Can warranty or handover documents be assumed?

No. List project-specific requirements during procurement, verify what each bidder can supply and tie accepted documents to the written roof scope.

Need help planning roofing work?

Set the roof zones, interfaces, design duties, dependencies and handover requirements before comparing price, sequence and construction dates.

Request an assessment

Tell us what you have noticed

Six short steps collect the details needed to route your enquiry. Stay at ground level and never climb onto a roof to gather information.

Step 1 of 6