Revisions lose their history
BOQ quantities change, but teams circulate renamed spreadsheets. Buyers and commercial teams may work from different versions, creating incorrect package limits.
EPC BOQ and project cost control software
Control BOQ, budget, commitments and actual project cost
Built for commercial heads, quantity surveyors and project directors. Keep approved quantities, budget allocations, purchase commitments, subcontract bills and site expenses connected so cost exposure is visible before final accounts.
Role-based accessConfigurable workflowsMobile access
What is epc boq and project cost control software? EPC BOQ and project cost control software organises the Bill of Quantities (BOQ), approved budget, commitments, actual costs and forecasts by project, cost code and work package. BOQ value represents priced scope; budget is the approved spending limit; commitments are contracted amounts; actual cost is recorded expenditure; forecast cost estimates the expected final position.
The operational problem
Why project cost reports arrive after the decision window
Commitments stay hidden
Management reviews posted costs while approved purchase orders and work orders sit elsewhere. The apparent budget headroom disappears when invoices arrive.
Variance has no source
A package is over budget, but the report cannot show which order, bill, expense or quantity caused it. Corrective action becomes slow and disputed.
Connected EPC records
Follow value from BOQ line to final cost
Cost control works when each commercial record retains project, WBS, package and cost-code context. A variance can then be traced from summary to purchase order, subcontract bill or site expense.
01BOQ version
02Approved estimate
03Budget allocation
04Cost code
05Purchase commitment
06Subcontract commitment
07Actual expense
08Forecast and margin
Core capabilities
Controls your team can evaluate in a demo
BOQ revisions
Maintain controlled BOQ versions and revision context. Prevent teams from treating an obsolete quantity schedule as the current commercial baseline.
Approved budgets
Allocate approved budgets by package, cost code or configured dimension. Give approvers the correct control limit before a commitment is made.
Commitment view
Bring approved purchase and subcontract commitments into cost reviews. Show exposure that has not yet become an invoice or paid cost.
Actual cost
Relate recorded invoices, subcontract bills and expenses to their cost context. Reduce manual reconciliation between accounts and project reports.
Package variance
Compare budget, commitment and actual cost at a useful project level. Direct commercial reviews toward exceptions with material impact.
Forecast context
Combine available cost and progress records to support forecast reviews. Authorised teams retain responsibility for estimate-to-complete assumptions.
Source drill-down
Open the orders, bills and expenses behind a number. Give reviewers evidence without distributing parallel spreadsheets.
Product walkthrough
Understand the five cost positions
A controlled cost review separates priced scope, spending authority, contractual exposure, recorded cost and expected final cost.
- 1BOQ defines priced scope
- 2Commitments expose future cost
- 3Drill-down explains variance
Operational takeawayThe view gives authorised teams a shared record for the next decision; it does not replace physical verification or professional judgement.
Feature workflow
Control cost from baseline through forecast
Approve scope
- Trigger
- Contract BOQ or approved revision
- Responsible role
- Quantity surveyor
- Record produced
- Versioned BOQ
- Control point
- Revision approval
- Next handoff
- Estimate and budget preparation
Set cost limits
- Trigger
- Approved estimate
- Responsible role
- Commercial head
- Record produced
- Budget by package and cost code
- Control point
- Management approval
- Next handoff
- Procurement and work-order controls
Capture commitments
- Trigger
- Approved PO or subcontract work order
- Responsible role
- Procurement and commercial teams
- Record produced
- Committed cost
- Control point
- Budget availability and approval
- Next handoff
- Cost exposure reporting
Record actual cost
- Trigger
- Invoice, bill or supported expense
- Responsible role
- Finance team
- Record produced
- Actual cost entry
- Control point
- Validation and financial approval
- Next handoff
- Project cost report
Review forecast
- Trigger
- Progress or cost variance
- Responsible role
- Project director
- Record produced
- Forecast and corrective action
- Control point
- Professional commercial review
- Next handoff
- Management margin outlook
Role-based value
Make cost exposure useful to commercial decisions
Commercial head
See package commitments, actuals, forecasts and margin pressure before closeout.
Quantity surveyor
Keep BOQ revisions, measured quantities and cost codes in controlled context.
Project director
Relate cost variance to progress, procurement and accountable work packages.
Finance team
Trace project reports to the approved transaction or expense behind each value.
Lois AI in this workflow
Ask Lois to explain cost records, not invent forecasts
Lois works with permitted Supista data and does not bypass configured validations, permissions or approvals.
“Why is the civil package above budget?”
- Checks
- Budget allocations, approved orders, bills and expenses
- Prepares
- A variance breakdown with linked source records
- You review
- Commercial owners assess causes and corrective action
“Show commitments not yet billed.”
- Checks
- Approved purchase orders, work orders and recorded invoices
- Prepares
- An open-commitment list by package
- You review
- Finance confirms accounting treatment and status
“Summarise cost exposure for this project.”
- Checks
- Permitted BOQ, budget, commitment, actual and progress data
- Prepares
- A review draft identifying exceptions
- You review
- The project director approves assumptions and interpretation
Connected EPC lifecycle
See where this feature passes work next
Proof and deployment confidence
Keep your cost structure and approval limits
Implementation maps current BOQ structures, cost codes, budget ownership and approval paths before transactions move. Configurable fields and role-based access support control without turning every change into uncontrolled custom development.
- ISO/IEC 27001-certified controls
- Role-based record access
- Configurable forms and workflows
- Mobile-friendly operational access
- Human review for professional decisions
Buyer questions
EPC BOQ and project cost control software FAQs
What is EPC BOQ and project cost control software?
It connects BOQ scope, approved budgets, purchase and subcontract commitments, actual project costs and forecasts by project and work package.
How are BOQ value and budget different?
BOQ value represents priced contractual scope or an estimate basis. Budget is the internally approved amount available for controlled spending against that scope.
What is the difference between committed and actual cost?
Committed cost is covered by an approved order or contract but may not yet be billed. Actual cost is expenditure recorded through accepted invoices, bills or expenses under the configured accounting process.
Can users trace a variance to its source?
Where connected records are available, authorised users can move from a package variance to relevant purchase orders, subcontract bills, invoices or expenses.
Does the system calculate the final forecast without judgement?
No. Available records can support forecast reviews, but authorised commercial and project professionals remain responsible for assumptions, estimate-to-complete and margin judgement.
Can our existing cost codes and approval limits be configured?
Yes. Cost dimensions, fields, roles, validations and approval paths can be mapped during implementation, subject to the agreed design.
Use a real workflow
Review one live project cost structure in Supista
Bring a BOQ, budget and current cost report. We’ll show how commitments, actuals and source records can be controlled without losing your package structure.