Examples

Multi-package tender

This worked example is illustrative. Adapt the structure to the actual tender, responsibilities, and review process.

Situation

A tender contains structural frames, stairs, handrails, and cladding. Several drawings apply across packages, while specialist files apply to only one package.

The estimator needs separate working estimates but one commercial response.

1. Keep one RFQ

The customer issued one enquiry with one due date, so the estimator keeps it as one RFQ.

The shared RFQ area holds the customer and requester, common correspondence, due date, priority, full file set, and project-wide notes.

2. Create practical assets

The estimator groups the work into four assets:

  1. Structural frames
  2. Stairs
  3. Handrails
  4. Cladding

An asset represents a practical package that can be reviewed and estimated independently. A drawing may still need to be considered across more than one package.

3. Add deeper structure only where useful

The frame package needs separate engineering, fabrication, coating, and erection sections. The estimator applies a project structure template and removes irrelevant nodes.

The handrail package is simple enough to estimate without a deeper hierarchy.

4. Estimate each package

Each asset receives its own takeoff items and cost rows. The estimator links reusable records, checks quantities, records package assumptions, avoids counting shared mobilisation twice, and keeps exclusions visible.

5. Handle shared costs deliberately

Site mobilisation applies across several assets. The estimator chooses one clear treatment according to the business process.

The important point is that the cost is included once and remains understandable during review.

6. Prepare quote options

The estimator creates options such as:

  • Base: frames, stairs, and handrails
  • Alternative: base scope plus cladding
  • Supply only: selected fabricated packages without installation

Each option is reviewed against the intended asset selection and commercial conditions.

7. Respond to an addendum

A revised stair drawing arrives before submission.

The estimator adds the file to the existing RFQ, updates the Stairs asset, reviews shared consequences, recalculates quote options, and exports a new revision.

The unaffected package estimates remain intact unless the addendum changes them.

What this example demonstrates

  • One customer enquiry does not require one oversized estimate.
  • Assets separate working packages while preserving common RFQ context.
  • Project structure is optional and should clarify rather than inflate the job.
  • Shared costs need an explicit treatment to prevent duplication.
  • Quote options can recombine reviewed packages for different commercial offers.