Is your office documentation ready for pricing and construction?

What must the package contain to provide an unambiguous basis for pricing?

A concept can correctly define function, specification and intended outcome. Tendering requires an additional layer: measurable scope, document hierarchy and rules for information that cannot yet be confirmed. The objective is not simply to produce more graphical detail, but to reduce the room for contractors to create their own interpretations.

The pricing package should therefore define partition geometry, wall types, glazing and door parameters, ceiling layouts, floor finishes, joinery and MEP elements resulting from the new room layout. For each discipline it should state not only the final outcome but also strip-out, relocation, supply, integration, commissioning, measurements and handover requirements.

Existing conditions and document hierarchy in the tender package

The second condition is reliable information about the existing state. Landlord base-build drawings may show the original condition rather than alterations made by previous tenants. Before fixing the price, identify what has been verified by survey or opening-up, what relies on as-built information and what remains a risk to be settled after works begin.

The third condition is document hierarchy. Plans, specifications, schedules, bills of quantities, building guidelines and tender clarifications may contain different information. The enquiry should state which document takes precedence and whether the bill of quantities is a binding scope, supporting information or only a basis for bidder verification.

A package requiring interpretation versus one that supports comparable pricing

Before tender issue, the documentation should pass tests for currency, coordination and contractability

Calling a package ‘detailed design’ does not guarantee that every file describes the same version of the project or that it can support a robust contract. Instead of reclassifying design stages, run three practical tests on the package issued to contractors.

A lump-sum price works properly when the parties understand the same outcome and use the same information basis. The more undefined elements there are, the more risk will be priced in, excluded or deferred for later settlement.

How does a general contractor assess the package before detailed pricing begins?

An audit is not simply a check that files have been provided for every discipline. Its primary purpose is to assess whether information is measurable, mutually consistent, buildable in the specific building and assigned to the correct parties.

The output of the audit should be a technical query list, not a general statement that ‘the design needs more work’. A good practice is to create an RFI register in which every question has a number, response owner, deadline and price/programme impact. A tender-assumptions register should also show which items were priced directly from the design, which use an assumed specification and which are carried as allowances.

A separate tool is the scope-interface matrix. Office projects contain many items that sit between disciplines: power to a fan-coil unit, blind controls, AV equipment connections, cable penetrations, access-control lock power or reinstatement of fire stopping after services pass through a partition. If no party owns an interface, the work does not disappear. It returns during construction as a question, delay or variation.

In practice, this is the first step an office general contractor should complete before confirming price, programme and responsibility for turnkey delivery.

Eight areas to check in a package issued for pricing

A tender package becomes useful only when all parts describe the same building, layout and specification. The greatest risk usually does not arise within one discipline, but at the interfaces between architecture, MEP systems, building procedures and party responsibilities.

The following areas do not carry the same weight in every project. In former-tenant space, the survey and scope for reuse of existing systems may be critical. In Shell & Core space, connections, loads and base infrastructure matter more. Building-management procedures, fire safety, BMS and handover documentation are covered separately in our guide to landlord approvals and fit-out procedures.

A high score in one area does not compensate for a critical gap in another. A complete architectural design cannot achieve handover without coordinated fire-safety documentation, while a complete MEP design cannot fix the price if material specification remains undefined. Readiness should therefore be assessed both overall and against the single most serious gap.

If the issue is not only package completeness but also the real sequence of design, approvals, procurement and works, see our guide to how long office fit-out takes.

Not every decision must be closed before pricing, but every open decision must be defined

The purpose of documentation is not to remove the investor’s ability to choose. It is to separate decisions that affect geometry, MEP loads, cost or programme from aesthetic decisions that can safely be made later.

An item can remain open if the offer defines minimum parameters, an assumed budget, selection deadline and mechanism for settling the difference. An allowance assigned to a specific package can work well. A generic phrase such as ‘to be selected by the investor’ is weak because it defines neither the specification nor the consequences of a late decision.

Apparently decorative choices that affect technical systems need particular control. A light fitting may require different power and controls, an acoustic panel a different substrate, a curtain changes to sprinklers, and joinery additional ventilation or access panels. Before leaving a decision open, check its dependencies rather than only the product value.

Missing information does not disappear from a quote: it becomes contingency, an exclusion or an allowance

A contractor cannot price information it does not have. It can make an assumption, add contingency, exclude the scope or carry it as an allowance. Each approach affects offer comparability and later commercial settlement differently.

How does incomplete documentation affect price and a lump-sum contract?

The first effect of incomplete documentation is false precision. A quote may contain detailed line items and unit rates while still relying on assumptions that do not match the intended outcome. Two similar totals may cover different equipment specifications, relocation quantities, tests or as-built documentation.

The second effect is that decisions move into construction. At that point, a change no longer affects design alone. It may require cancelling an order, redesigning routes, remobilising a team, reinstating protection or changing the sequence of works. Change cost therefore includes materials and labour as well as downtime, coordination and impact on other packages.

The third effect is a conflict with lump-sum logic. The investor expects a fixed price, while the contractor does not want to take risk on information it could not verify. The solution is not to pretend the risk does not exist, but to define it: what is included, which parameters are assumed, which items are settled after opening-up and who designs any resulting changes.

The lowest offer may therefore represent not the best price, but the fewest included obligations. A proper comparison needs to align prices, assumptions, exclusions, contingencies, commissioning scope, handover documentation and responsibility for discipline interfaces. Only then can the real price difference be assessed.