Contact Form Demo (#7)

Book Free 10 Min Demo

Fill the form to see the product live
Trusted by 10,000+ Construction companies ⭐⭐⭐⭐⭐


Contact Form Demo (#7)

Book Free 10 Min Demo

Fill the form to see the product live
Trusted by 10,000+ Construction companies ⭐⭐⭐⭐⭐


BOQ Management

Onsite BOQ Software
for Construction

Connect Scope, Progress, Costs, and Billing in One System

BOQ items linked to activities, progress, and client bills
Daily site quantities feed directly into RA bill generation
Budget vs actual tracked at BOQ item level in real time
★★★★★

10,000+ construction companies across India and the Middle East trust Onsite

Onsite BOQ software for construction — BOQ linked to progress, budget, and billing in one system
Who Needs This

Who Onsite BOQ Software
is built for

Whether you generate RA bills from site quantities, track BOQ-linked costs across trades, or certify executed scope for clients — Onsite keeps the BOQ connected to the work that actually happened.

Industry Challenges

Why BOQ Management crumbles on construcion projects

The BOQ failure in construction is not a technology problem. It is a workflow problem. The BOQ was never connected to the daily records that execution produces, so it could never control what happens on site.

01

BOQ Becomes a Filed Document After the Tender

Construction companies prepare the BOQ to price the tender, win the project, and then never open it again during execution. Progress is tracked through site engineer phone calls and WhatsApp messages from the field. The accounts team reconciles costs against a budget number that nobody can trace back to a specific BOQ item. By the time anyone sits down to check how the project spent its money, the BOQ and the execution records exist in completely separate systems with no connection between them. The BOQ that should have controlled the project simply never did.

02

Progress Recorded as Percentages With No Measurement Behind Them

When a site engineer sends “RCC slab 65 percent done” on WhatsApp, that message is not a progress record. It has no BOQ item reference, no quantity measurement, no date-stamped verification, and no way to be traced into an RA bill or a budget comparison. When the billing team needs to generate an invoice for the period, they call the site engineer and ask them to reconstruct what was completed. The number that ends up on the invoice is a judgment call, not a measurement, and a client quantity surveyor can reject it on first submission.

03

RA Bills Assembled from Memory, Not Verified Records

Generating a running account bill at the end of a billing period should involve three steps: verify executed quantities, apply contract rates, and produce the invoice. In practice, billing teams call the site engineer, search through WhatsApp messages, pull the BOQ from a different file, and enter quantities that nobody has formally measured or recorded. This process takes days instead of hours and produces an invoice that the client quantity surveyor can question at every line item. Disputes over quantities are the single most common reason construction invoices get rejected on first submission.

04

Budget Overruns Surface at Project Completion, Not During Execution

Comparing actual cost against the BOQ at total project level shows whether the project made or lost money. It does not show which specific BOQ items are overrunning, whether the overrun is in material quantities or labour rates, or what the remaining work will cost at the current rate of spending. By the time the project manager sees a report showing that the project has spent 80 percent of its budget at 60 percent completion, there is no practical response left. The margin has already been consumed and the outstanding work will compound the damage.

How Onsite Solves This

How Onsite Connects the BOQ to every decision on your project

The four BOQ problems in construction share one root cause. The BOQ exists in a different system from the work. Onsite removes that separation by making the BOQ the active record that drives every stage of project execution.

See It in Action
Project Setup

Upload Your BOQ and Set It as the Project Control Layer

Before the first day of work begins on site, the project team uploads the BOQ into Onsite from the same Excel or CSV file used during tendering, or builds it from the rate library. Each BOQ item carries its section, cost code, planned quantity, unit, and rate. The moment the BOQ is saved, it becomes the active financial and scope record for the project. Every subsequent decision (material purchase, subcontractor work order, activity schedule, billing cycle) links back to a BOQ item. The BOQ stops being a tender document and starts doing what it was always supposed to do.

Planning

Link Every BOQ Item to Activities, Tasks, and Budget

Each BOQ line item connects to the activity it produces completed scope for. Activities carry planned start and end dates, responsible teams, and predecessor dependencies. The budget baseline calculates from BOQ quantities and rates automatically. Once activity linkage is set up, material purchase requests, subcontractor work orders, and expense claims must reference a BOQ item before they are approved. Scope additions require a new BOQ item and budget entry before resources are committed to the work. The system prevents unlinked spending from accumulating while execution is underway.

Daily Execution

Record Executed Quantities Daily From the Field

Site engineers open the Onsite mobile app at the end of each working day and record quantities executed against each active BOQ item. The entry captures the BOQ item, the unit, the day’s quantity, and attaches geo-tagged photographs and site measurements. Executed quantities accumulate against each BOQ item automatically. The project team always knows the running total of completed work versus planned quantities for every item. Nobody calls the site to reconstruct what happened last week. The daily records that site engineers already produce become the verified basis for every subsequent billing and cost comparison.

Billing and Control

Generate Bills, Track Costs, and Close Projects With Verified Data

When a billing period ends, the accounts team opens the billing module, selects the period, and reviews the executed quantities for each BOQ item. The RA bill generates from those verified quantities, with no phone calls and no reconstruction from WhatsApp messages. Subcontractor running bills are matched against work order scope and the same DPR-verified quantity records. The budget versus actual dashboard shows every BOQ item’s cost position against the budget baseline. Project owners see at a glance which items are on track, which are overrunning, and what the project’s final cost will look like at current rates.

Core Features

Core features of Onsite BOQ software
for construction

Three capabilities make the BOQ an active control layer rather than a filed document: item-level cost tracking, subcontractor bill verification, and rate library-driven margin visibility before the project starts.

Feature 01

BOQ Item-Level Budget vs Actual Tracking

Onsite compares actual cost against the BOQ at line item level, not at total project level. Every material purchase, subcontractor bill, and direct expense posts against the relevant BOQ item automatically as it is recorded elsewhere in Onsite. The budget baseline is the BOQ rate multiplied by the BOQ quantity. The actual figure is the total cost incurred for that specific item during execution. Project managers can see the full variance at item level: which items are running over, what the cause is, and what the remaining scope will cost if current spending rates continue without correction.

Actual cost posts against BOQ items from procurement, billing, and expense records
Budget variance visible at item level showing which scope areas are overrunning
Remaining scope cost projected based on current actual vs budgeted unit rates
Feature 02

BOQ-Linked Subcontractor Work Orders and Running Bills

Subcontractor scope in Onsite is defined as a work order linked to specific BOQ items and agreed rates. When the subcontractor submits a running bill for the period, the quantities claimed in the bill are verified against the executed quantities recorded in the DPR for the same BOQ items during the same period. The contractor does not pay based on what the subcontractor claims. Payment releases only when three records align: the work order scope, the contractor’s DPR-verified quantity records, and the subcontractor’s submitted bill. Discrepancies are visible before payment is approved, not discovered after the fact.

Subcontractor work orders created from BOQ items with agreed rates and scope quantities
Running bill quantities verified against DPR execution records for the billing period
Payment released only after three-way match: work order, DPR quantity, and running bill
Feature 03

Rate Library and Margin Analysis at BOQ Level

BOQ creation in Onsite starts from a rate library maintained at company level. The rate library carries material rates, labour rates, and work item rates that can be reused across all projects. When building a quotation or setting up a project BOQ, the team selects items from the rate library and enters planned quantities. Onsite calculates the cost estimate and project margin at item level. Rates can be adjusted for a specific project without changing the company rate library. BOQ revisions are tracked with version history so changes to quantities, rates, or scope items are always documented.

Rate library with material, labour, and work item rates shared across all projects
Margin visible at BOQ item level during quotation and project setup
BOQ revision history tracking all changes to quantities, rates, and scope items
Feature 04

BOQ-Linked Daily Progress Tracking From Site

Onsite connects the daily progress report to the BOQ rather than treating it as a separate document. Site engineers open the mobile app at the end of each working day and record the quantity executed against each active BOQ item, selecting the item from the project BOQ list, entering the unit quantity completed for the day, and attaching geo-tagged photographs and site measurements. Executed quantities accumulate against each BOQ item automatically. The project team can see planned quantity, executed quantity, and remaining quantity for every item in the project without calling the site engineer for an update.

DPR entries recorded against BOQ items daily from the Onsite mobile app
Geo-tagged photos and site measurements attached to every BOQ quantity entry
Cumulative executed vs planned visible at BOQ item level in real time
Why Manual BOQ Fails

Spreadsheets and WhatsApp
cannot manage your BOQ

The problem is not that contractors use Excel badly. The problem is that Excel was never designed to connect a scope document to daily execution, real-time costs, and verifiable billing at the same time.

No connection

Excel Cannot Link BOQ Items to Daily Site Execution

Excel is a static document. It receives no data from the site automatically and has no mechanism to connect a BOQ line item to a DPR entry, a material issue record, or a subcontractor work order. Every update requires a phone call to the site team, a WhatsApp message, and a manual cell edit that nobody can verify. The BOQ in the spreadsheet and the work happening on site exist in permanently separate systems with no way to synchronise them.

Not a record

WhatsApp Messages Are Not Quantity Records

A site engineer sending “slab 70 percent done” on WhatsApp is not producing a progress record. That message has no BOQ item reference, no date-stamped quantity, no measurement, and no way to be traced into an RA bill or a budget comparison six weeks later. When the billing team asks for quantities to generate an invoice, the answer comes from memory rather than from a record the client can independently verify, which is why first-submission rejections are common on Indian and Middle East construction projects.

No audit trail

Excel Cannot Generate RA Bills From Site-Recorded Data

Preparing a running account bill in Excel requires the accounts team to manually pull the BOQ file, locate executed quantities from a separate source such as a phone call or WhatsApp thread, calculate the billing amounts, and type them into the invoice format. This process takes days instead of hours and produces an invoice with no measurement audit trail. When the client’s quantity surveyor questions a specific line item, the only available evidence is the accounts team’s reconstruction of what the site team reported verbally.

Too late

Neither Tool Tracks Budget Against the BOQ at Item Level

Excel shows whether the total project spend is within budget. It cannot show which specific BOQ items are overrunning, whether the overrun is in material quantities or labour rates, or what the remaining scope will cost at the current rate of spending. By the time a project manager notices that total costs are running ahead of the budget figure in the spreadsheet, the overrun has already compounded across multiple billing cycles with no practical corrective action remaining before project completion.

FAQs

Common questions about
Onsite BOQ software

Questions construction companies ask before they connect their BOQ to execution, billing, and budget control in Onsite.

What is Onsite BOQ software for construction?

Onsite BOQ software for construction is a platform that keeps the bill of quantities active as a live execution record from project start to project close. Most construction companies prepare the BOQ for the tender and store it in a spreadsheet where it sits unused while the project runs on phone calls and WhatsApp messages. Onsite connects the BOQ to daily progress entries, procurement records, subcontractor work orders, and client billing so every quantity executed on site and every cost incurred during execution traces directly back to a specific BOQ line item.

How does BOQ link to progress tracking in Onsite?

Site engineers record daily progress against BOQ line items through the Onsite mobile app. Each DPR entry references the specific BOQ item being worked on, the unit of measurement, and the quantity executed that day. Geo-tagged photographs and site measurements attach to the entry. Executed quantities accumulate against each BOQ item automatically, so the project team always has a running total of completed work versus planned quantities for every item in the BOQ. This data feeds directly into billing and budget reporting without any additional manual entry or reconciliation from the site team.

Can I generate RA bills directly from BOQ executed quantities?

Yes. When a billing period ends, the accounts team opens the billing module in Onsite, selects the billing period, and reviews the executed quantities recorded against each BOQ item for that period. The running account bill generates from those verified quantities, with each line item in the invoice tracing back to the BOQ item and the DPR records that support it. No manual assembly, no phone calls to the site team, and no reconstruction from WhatsApp messages are required. The invoice reaches the client with a full measurement trail attached.

How does the BOQ connect to budget control in Onsite?

The budget in Onsite is built directly from the BOQ. The BOQ rate multiplied by the BOQ quantity for each item gives the budget baseline for that item. Every material purchase, subcontractor bill, and direct expense recorded in Onsite posts against the relevant BOQ item automatically. Project managers see the actual cost incurred for each BOQ item versus the budget allocated to it, updated in real time as transactions are recorded. This gives the project team visibility into which specific items are overrunning and what the project’s final cost will be at current spending rates.

Can I link subcontractor work orders to BOQ items in Onsite?

Yes. Subcontractor work orders in Onsite are created by selecting the relevant BOQ items and entering the agreed rates and scope quantities for the subcontractor. When the subcontractor submits a running bill, the quantities claimed are automatically compared against the DPR-verified quantities recorded by the contractor for the same BOQ items during the same period. Payment can only be released after the work order scope, the DPR quantity records, and the subcontractor’s claimed quantities align. Discrepancies are flagged before approval, preventing overbilling from going undetected until after payment is made.

Does Onsite support BOQ upload from Excel or CSV?

Yes. Onsite accepts BOQ uploads from Excel and CSV files using a standard template format. The upload file includes columns for item name, item code, unit, planned quantity, unit rate, HSN code, GST rate, and cost code. Once uploaded, each row in the Excel file becomes a live BOQ item in the system, connected to the project’s activity schedule, budget, and procurement records. Companies that already maintain their BOQ in Excel during the tender stage can upload the same file into Onsite at project kick-off without rebuilding the BOQ from scratch.

How does BOQ link to material planning in Onsite?

Each BOQ item in Onsite can be linked to the material quantities required to complete it. When site engineers raise a material purchase request, they reference the BOQ item the material serves. The system checks whether the requested material quantity is within the planned scope for that BOQ item before the request is forwarded for approval. Material costs post against the relevant BOQ item automatically when the purchase is recorded. This means the budget vs actual comparison for each BOQ item includes material costs as they are committed, not just when invoices arrive from vendors.

Can I manage BOQs across multiple projects in Onsite?

Yes. Each project in Onsite has its own BOQ, budget baseline, and execution records. Company owners and project directors can view BOQ status and cost position across all active projects from a single account without switching between separate files or calling project managers for updates. The rate library used for BOQ creation is shared at company level, so rates set up for one project are available when building the BOQ for the next. BOQ item costs and executed quantities stay project-specific, while the rate library and reporting structure remain consistent across the portfolio.

How does Onsite handle BOQ revisions and scope changes?

BOQ revisions in Onsite are tracked with version numbers, revision dates, and a record of which quantities, rates, or scope items changed in each revision. The current approved version of the BOQ is always the active record for billing, cost comparison, and subcontractor scope references. Earlier versions remain accessible so the project team can trace the full revision history if a dispute ever arises over what the original agreed scope covered. Scope additions require a new BOQ item and budget entry before the work can be scheduled, procured, or billed.

How quickly can a construction company start using Onsite BOQ software?

Most construction companies using Onsite are set up and running within five to seven working days of account creation. The onboarding process includes uploading the BOQ from the existing Excel or CSV file, setting up the rate library, configuring cost codes, and creating the project’s activity schedule. The Onsite onboarding team handles the setup alongside the company’s project managers and accounts team. Once the BOQ is live in the system and the first DPR entries are recorded, the billing module, budget tracker, and subcontractor work order features are ready to use immediately.

Get Started Today

Stop Running Your BOQ in Excel.
Connect It to Your Project With Onsite.

Join 10,000+ construction companies across India and the Middle East running their projects on Onsite. Go live in under 7 days with a dedicated onboarding manager.

No credit card required  ·  Go live in under 7 days  ·  Dedicated onboarding manager