BuildSuiteBuildSuite
GitHub Book a demo

BuildSuite Sites

Know where every project actually stands.

Stages, work packages and tasks with progress logged from the site — so the number in your client report is the number your PM sees.

BOQStage planningDaily progressClient reports
Book a demoSee the full platform
app.buildsuite.io / project / BTP-P2 / overview
Stages7
Work packages9
Open tasks15
Progress62%
StageProgress%
Substructure100
Superstructure98
Finishing27
Handover0

Daily progress logged from site · approvals routed automatically

Key features

Built around how a site actually runs.

Planning

Stage planning

Break a project into subprojects, work packages and stages with planned dates, then track slippage against the contract programme.

Execution

Daily progress

Supervisors log completed work, delays and reasons from the mobile app. Progress rolls up to the stage automatically.

Estimating

BOQ & rate master

Quantities priced off a controlled rate master, with revisions kept as history rather than overwritten.

Change

Scope changes

Client variations captured as records with a cost and time impact, so they stay billable.

Approvals

Stage sign-off

Multi-level approvals routed to the people who should authorise them, with a full audit trail.

Reporting

Client reports

Daily, weekly and monthly reports with executive summary, progress against programme and delay analysis.

How it is structured

Five levels, and every one of them adds up.

Most tools give you a flat task list and leave you to reconcile it against the contract. Sites models the shape a project actually has, so a percentage at the bottom means something at the top.

How a BuildSuite project is structured: project, subproject, work package, stage, task Project Bangalore Tech Park — Phase 2 BTP-P2 · Prestige Group Subproject Block A (G+8) 9 floors Block B (G+6) 7 floors Work package Civil works ₹1.10 Cr MEP ₹48.00 L Finishes ₹32.00 L Stage Substructure 100% Superstructure 98% Finishing 27% Handover 0% Task Column casting — L4 18 open · 3 overdue Every level rolls its progress and cost up to the one above it. Nothing is entered twice.

Bangalore Tech Park — Phase 2, as modelled in BuildSuite

Subproject
A block, a tower, a phase — anything billed and programmed separatelyEach carries its own BOQ, programme and cost centre
Work package
The unit you actually award and costMaps to a cost code, so budget-versus-actual works without a spreadsheet
Stage
Substructure, superstructure, finishing, handoverWeighted by value, not by task count — so 27% of finishing means 27% of its money
Task
What a supervisor ticks off on siteRolls into the stage, which rolls into the project

One entry, five destinations

What a supervisor logs at 6pm is in the client report.

This is the whole argument for one system. The same entry moves the stage, exposes the variance, posts the cost and prints the report — without anyone opening a spreadsheet in between.

How a day on site becomes a client report 01 Site log Supervisor, mobile 02 Stage rolls up % against plan 03 Variance vs contract programme 04 Cost posts to the project P&L 05 Client report PDF, your letterhead One entry. No export, no nightly sync, no re-typing at any step.

Why it matters at month end

When progress and cost come from two systems, the client report and the P&L disagree — and someone spends three days deciding which one to believe. Here they cannot diverge, because they are the same record read two ways.

One source

What the supervisor actually does

Opens the app, marks the work done against a stage, adds a photo and a delay reason if there is one. No codes to remember, no forms to file. If the site has no signal it queues and syncs later.

Mobile

Scope changes

The work you do for free is usually the work nobody recorded.

Verbal variations are where contractor margin quietly goes. Sites turns each one into a record with a price and a time impact before the work starts, so it is billable when the account closes.

How a scope change stays billable 01 Variation raised from site or client 02 Priced off the rate master 03 Approved cost + time impact 04 BOQ revised v2 → v3, history kept 05 Contract value updated, then billed Unapproved variations never reach the bill; approved ones never get forgotten.
Priced
Off the same rate master as the original BOQNo invented rates, no arguing about them six months later
Versioned
v2 becomes v3; v2 is still thereYou can show a client exactly what changed and when they agreed it
Time impact
Recorded against the programme, not just the valueAn extension of time is a claim; an undocumented delay is a penalty

Client reporting

Stop rebuilding the monthly report by hand.

The report is generated from the same site data your team works in — on your letterhead, client-facing or internal, exportable to PDF.

DailyWeeklyMonthly Client vs internalDelay analysisPDF export
app.buildsuite.io / project / report / monthly
Actual62%
Programme100%
Variance−38%
Position56d late
Executive summary · 09 Jul → 08 Aug 2026
Works are 62% complete against a programme position of 100%.
Superstructure 98% complete; finishing stage 27% complete.
7 labour-days deployed on site during the period.

Generated from site data · exported to PDF on your letterhead

Pairs with

Sites plus accounting is the whole picture.

Sites tells you where the project is. The Platform tells you what it cost. Same install — switch it on when you're ready.

See BuildSuite Platform

Get started

Bring one messy project to the demo.

Thirty minutes on your BOQ, your labour categories, your cost codes — and you’ll know whether it fits.

Book a demo Or self-host it