Illustrative use case: how a mid-size contractor could run BOQ, measurements and RA bills on Woxox

An illustrative (fictional) example of how a mid-size contractor could run BOQ, measurements and RA bills on one project record in Woxox Construction OS.

In this article
  1. The scenario
  2. How Contractor A could set it up in Construction OS
  3. What an RA bill cycle could look like
  4. See it on your own projects

This is an illustrative scenario, not a customer story. The company, people and project below are invented to show a workflow. There are no real results, numbers or quotes.

The scenario

A fictional general contractor, "Contractor A", runs four or five building projects at a time: a mix of commercial blocks and housing. Each project has a contract BOQ, a site team of engineers and supervisors, and a client-side engineer who certifies running account (RA) bills each month.

Today (in this scenario) the BOQ lives in a spreadsheet, measurements are written in the site MB and typed up later, and the billing engineer builds each RA bill by copying quantities across files. Typical pain points:

  • Quantities in the bill can't always be traced to an MB page.
  • Nobody can easily see which measured work has already been billed.
  • Purchase orders and GRNs aren't tied to BOQ items, so cost overruns show up late.

How Contractor A could set it up in Construction OS

  1. Project, WBS and BOQ. Create the project, set up the WBS (blocks, floors, trades) and load the contract BOQ, with each item linked to the WBS and a cost code.
  2. Work packages and measurements. Site engineers record measurements against BOQ items and work packages as the work is done, with the location and dimensions, instead of retyping MB pages at month end.
  3. Budget and cost codes. Budgets sit on the same cost codes, so measured quantities and committed costs can be compared item by item.
  4. Requisitions, RFQs, POs and GRNs. Site requisitions turn into RFQs and POs; GRNs record what arrived. Each is tied to the project and cost code.
  5. Site records, RFIs, quality and defects. Daily site records, RFIs and defect lists stay on the same project, so the context for a disputed quantity is in one place.
  6. Construction AI, with approval. Construction AI can suggest actions, and a person approves them before anything changes.

What an RA bill cycle could look like

  • At the cut-off date, the billing engineer reviews measurements recorded since the last bill, item by item.
  • Quantities for "this bill" come from those measurements; "previous" and "up to date" columns are built from earlier bills.
  • The client-side engineer test-checks a sample against the site and the recorded measurements.
  • Once the bill is certified, the billing engineer marks the measured entries with the bill reference, so the team can see what has already been billed (a process step; confirm with the product team how Construction OS records it before saying so publicly).

Your organisation's own MB rules, approvals and contract terms still apply. Construction OS is an add-on to the Woxox Professional or Business plan.

See it on your own projects

If your BOQ, measurements and RA bills live in separate spreadsheets, see how they could sit on one project record in Woxox Construction OS. Talk to Woxox.


By WOXOX Editorial Team

ShareLinkedInX