Site Management Software for Builders

A builder running four projects is running four different information systems, whether they intended to or not. Tower A's progress lives in a site engineer's diary. The Phase 2 material position lives in a storekeeper's register. The revised structural drawing for Wing C went out on a WhatsApp group that now has 47 members and no record of who opened it. And the quarterly progress report due to the state RERA authority next week needs numbers that nobody has actually measured.

Site management software for builders exists to solve a specific version of this problem: not "how do I run one site better", but "how do I see six sites at once, close the month, keep contractors honest, and file compliance from real data instead of estimates".

That is a different job from the one a contractor's site app does, and it is worth being precise about the difference before you buy anything.

What changed for builders between 2024 and 2026#

Three shifts have moved portfolio visibility from a nice-to-have to a cash-flow issue.

Input costs are moving faster than sales#

Per the Office of the Economic Adviser's wholesale price index release for June 2026 (DPIIT, published 14 July 2026), the basic metals group — the closest official proxy for steel — was up 12.31% year on year, and it has accelerated every month since January 2026 (5.19% in January, 8.57% in March, 12.30% in May). Fuel and power was up 27.41%, which lands directly on your diesel, DG sets, and transport bills. Cement, read through the non-metallic mineral products group, was comparatively flat at 1.84% after several months of mild deflation.

Meanwhile, Knight Frank India's India Real Estate: Office and Residential Market H1 2026 report puts January–June 2026 launches across the top eight cities at 187,350 units (up 4% year on year) against sales of 171,471 units (up 1%). Unsold inventory rose 4% to 525,695 units, and the quarters-to-sell measure moved from 5.8 at the end of 2025 to 6.0 quarters. Supply has outpaced sales in that market continuously since 2022.

Read together: your cost line is climbing and your absorption line is not. The margin you protect is the margin you find inside execution — wastage, rework, idle plant, retention leakage, and interest on capital sitting in slow-moving towers.

Stalled projects are a policy category now, not just a bad quarter#

The Press Information Bureau's March 2026 backgrounder on the SWAMIH fund restates the baseline problem in the Indian residential market: roughly 1,509 stalled projects covering about 4.58 lakh housing units, around 90% of them in the affordable and mid-income segments, needing about Rs 55,000 crore to finish. SWAMIH has completed over 58,596 homes against a portfolio of more than one lakh, and a second fund with a Rs 15,000 crore corpus has been announced to target another lakh of stalled units.

Nobody sets out to stall a project. It happens through an accumulation of small invisibilities: a drawing revision that three subcontractors never saw, a slab that slipped four weeks while the sales pitch still said "possession December", a material advance paid twice.

The regulator reads your site data now#

Quarterly RERA reporting has moved from a filing formality to an enforcement trigger with real consequences, and it consumes exactly the data that site management software produces — covered in detail below.

Builder view versus contractor view#

Most tools marketed as "construction site management software" are built around the contractor's daily loop: attendance, today's work, today's material, today's photos. A builder needs that loop running underneath, but consumes it differently.

A tool that only does the left column leaves you aggregating in Excel every Friday — which is how most builders end up with a portfolio view that is a week stale and quietly wrong.

The builder's weekly review: five numbers, one hour#

The test of any system is whether it can answer a fixed set of questions in an hour, every week, without anyone preparing a deck. Here is the set worth standardising on. A purpose-built builder's workspace should surface all five without a data-collection exercise.

1. Progress against plan, by tower and floor#

Percentage-complete at project level is close to useless — it hides everything. The unit that means something is the activity within a location: slab 7 of Tower B, blockwork on floors 3–5 of Wing A, external plaster on the west elevation.

This is why location breakdown matters more for builders than for anyone else on the project. When progress is recorded against a location structure that mirrors how the building is actually built and sold — tower, wing, floor, unit — the same data serves site review, sales handover forecasting, and statutory reporting without re-keying. A work breakdown structure tied to location is the difference between "we are about 60% done" and "we are 11 days behind on Tower B slabs, and that pushes internal plaster into the monsoon".

What to look at weekly, per tower:

• Activities that should have finished this week and did not, with the reason coded (labour, material, drawing, approval, weather, payment)
• Variance in days against the declared completion date, not against last week

2. Material and cash exposure across sites#

At portfolio level the question is not "do we have stock". It is "how much of my working capital is sitting as material, where, and how much of it is stranded".

Four figures, refreshed weekly:

• Stock value on hand per site, and per site the top five items by value
• Purchase orders raised but not received — your committed-but-undelivered exposure
• Material received but not yet invoiced or reconciled against challans (the gap where leakage lives)
• Advances paid to suppliers against undelivered material

The awkward case, and the common one, is material moving between sites. A builder with three projects in the same city will shuttle scaffolding, shuttering plates, and surplus cement between them, and that movement is almost never documented. It shows up later as a shortage at one site and an unexplained surplus at another. The mechanics of getting this right are covered in more detail in the guide to multi-site inventory tracking, but the short version is that inter-site transfers need to be a first-class transaction type with a challan and a receiving acknowledgement, not a phone call.

3. Drawing revisions in circulation#

This is the most under-monitored number on an Indian residential project, and the most expensive when it goes wrong. A revised beam layout issued on Friday, built to the old revision on Monday, discovered on Thursday — that is a fortnight lost and a structural consultant's opinion to buy.

What a builder should see weekly:

• Revisions issued in the last 14 days, and which of them have been acknowledged by the executing contractor
• Superseded revisions still marked as current at any site
• Requests for information or clarification open beyond seven days with a consultant

The control that actually works is a single current-revision register with acknowledgement tracking, so that "he never sent me the revision" and "I never got it" both become checkable claims. The practical setup for this, including how to handle hold-status and superseded prints, is in the walkthrough on drawing revision control.

4. Open quality issues and their age#

Count is not the metric. Age is. Ten open snags raised yesterday is a healthy site. Three non-conformances open for 60 days is a dispute in gestation and, if any of them touch waterproofing or structural cover, a warranty liability.

Track:

• Open non-conformances by age band (0–7 days, 8–30, 31–60, over 60)
• Open items by responsible contractor, because concentration tells you who to have a conversation with
• Repeat non-conformances of the same type, which point at a process problem rather than a workmanship problem

Repeat items are the ones worth escalating formally; the distinction between a one-off snag and a systemic defect requiring corrective action is handled in the note on non-conformance management.

5. Contractor and subcontractor position#

For each active work order:

• Value ordered, value certified to date, value paid, retention held
• Current running account bill in the certification pipeline and how long it has been sitting
• Advance recovered against advance paid
• Open quality items and back-charges pending adjustment

Two-thirds of the disputes a builder ends up in are versions of the same argument: the contractor's measured quantity does not match the builder's. That argument is winnable in advance if joint measurement is recorded against location with photographs at the time of measurement rather than reconstructed at bill time. The formats and the sequencing are set out in the guide to running account bills.

RERA quarterly progress reports run on measured site data#

This is where portfolio visibility stops being a management preference and becomes a statutory obligation with a bank account attached.

What the law actually requires#

The quarterly duty sits in Section 11(1) of the Real Estate (Regulation and Development) Act, 2016 — specifically clauses (b) through (e), which require a promoter to keep the project webpage on the authority's site updated quarterly with the number and types of apartments or plots booked, the number of garages booked, the list of approvals taken and approvals pending after the commencement certificate, and the status of the project. The full text is on India Code.

Note the framing: this is a continuing disclosure obligation, not an annual return. Missing it is a contravention of Section 11, which is penalised under Section 61 — a penalty extending up to five per cent of the estimated cost of the real estate project as determined by the authority. Separately, defying an authority's order attracts a per-day penalty under Section 63, cumulatively also capped at 5%.

What "status of the project" means in practice#

Each state has built its own reporting form, but most descend from the model architect's certificate — Form 1 in the MahaRERA General Regulations, 2017 — which is prepared separately for each building or wing and asks for percentage of work done against a fixed activity list.

A second table covers internal and external development works for the registered phase — roads and footpaths, water supply, sewerage and STP, storm water drains, landscaping, street lighting, community buildings, solid waste management, rainwater harvesting, fire protection, and the electrical substation.

Some states go further. Tamil Nadu's official quarterly progress report template asks for construction stage per block, tower and floor, splits completion into physical and financial percentages, and requires geotagged, dated colour photographs from at least two angles.

Read that list against how your sites currently report. If your engineer sends you a WhatsApp voice note saying "slab work chalu hai", you cannot produce a defensible percentage for row five of Table A, per tower, four times a year. You will estimate — and the estimate will drift from reality, and the gap will compound quarter over quarter until a revised completion date becomes unavoidable.

The deadlines are tighter than most builders think, and vary by state#

There is no single national deadline. Verified from the primary instruments:

Maharashtra's 20-day window comes from MahaRERA Order No. 33/2022 dated 5 July 2022, which replaced the earlier and much tighter seven-day rule from Order 18/2021. Several consultancy websites still publish the seven-day figure for Maharashtra; it is stale. Uttar Pradesh, by contrast, genuinely is seven days, under Rule 14(1)(d) of its state rules, and UP now requires the reports to be filed through the architect, engineer and chartered accountant with digitally signed certificates.

One more Maharashtra-specific change to note: since MahaRERA's go-live order of May 2025, registrations, corrections, extensions and quarterly updates all run through the MahaCRITI platform, and the old portal was closed with effect from 11 May 2026. If your compliance consultant is still describing the old workflow, that is a signal.

What non-compliance actually costs#

The penalty amount is rarely the painful part. On 28 July 2026, MahaRERA's own non-compliance listing showed 1,632 projects kept in abeyance for failing to file quarterly updates. The consequences attached to abeyance, in the authority's own words, are that the project's bank account is frozen and the promoter is prohibited from executing agreements for sale or sale deeds with buyers until compliance is restored. A separate district-wise list carried a further 212 projects, with Pune, Nashik, Palghar and Thane accounting for the largest shares.

A representative enforcement order from 2023 shows the ladder: notice with 15 days to comply, then a show-cause notice, then an order that keeps the registration in abeyance, directs the bank to freeze the project account, directs the Joint Registrar of Assurances not to register any agreement for sale, and imposes a Rs 50,000 penalty under Section 61. Restoration is available on compliance — but by then you have lost weeks of registrations.

Press reports in early May 2026 put the scale of the latest wave at more than 8,000 under-construction projects receiving show-cause notices for missing the 20 April 2026 deadline, out of roughly 33,000 under construction, with 60 days to respond. Outlets disagree on the district-level splits and MahaRERA has not published the aggregate on its own site, so treat the exact number as press-sourced rather than official. The direction of travel is not in doubt.

For scale: the Ministry of Housing and Urban Affairs stated on 4 September 2025, at the launch of the unified RERA portal, that 1,51,113 projects and 1,06,545 agents had been registered under RERA to date. Every one of those projects carries a quarterly obligation.

If your compliance calendar and your site data currently live in different worlds, the sequencing problem — and how to close the gap without hiring a compliance team — is worked through in the guide to RERA compliance and project management.

Contractor oversight without micromanaging#

Builders who run 3–10 projects almost never do their own execution. They contract it — often to different contractors per project, sometimes per trade. Oversight is therefore an information design problem, not a supervision problem: you need enough visibility to catch drift early, without inserting yourself into decisions the contractor is paid to make.

Three controls do most of the work.

Make the daily record the contractor's obligation, not your engineer's favour. Write the daily progress report into the work order as a deliverable, with a defined format and a submission time. If it is a contract obligation, it gets done; if it is a request, it gets done for three weeks. What belongs in it for an Indian residential site — pour records, cube test references, RMC delays, rain and power stoppages, pending approvals, material shortages — is set out with a usable format in the note on DPR formats.

Tie certification to recorded measurement, not to submitted claims. The rule that removes most arguments: nothing gets certified that was not measured jointly and recorded against a location, with photographs taken at the time. Enforce it once, painfully, on the first bill. It holds after that.

Separate a shortfall from a dispute. When a contractor is behind, the coded reason matters more than the delay. If the reason is "drawing awaited" or "approval pending" or "payment delayed", the problem is on your side of the table and chasing the contractor is theatre. Coded delay reasons, aggregated across a portfolio, will tell you uncomfortable things about your own organisation — most commonly that your decision latency, not your contractor's labour, is the binding constraint.

A rollout path for 3 to 10 projects#

The failure mode is always the same: buy licences for every site, announce it in a meeting, and discover in six weeks that two sites are using it, four are not, and the portfolio view is worse than the spreadsheet it replaced because it is now half-populated.

Sequence it instead.

Month 1 — one site, two workflows#

Pick your second-best site, not your best one. The best site will succeed regardless and teach you nothing; a hopeless site will fail and poison the rollout.

• Set up the location structure first: tower, wing, floor, unit. Get the naming right now, because everything downstream inherits it and renaming later is genuinely painful.
• Turn on exactly two things: daily progress against location, and photographs.
• Set one hard rule with a time: entries closed by 7 pm, and the builder or project head reviews them the next morning. Review is what creates compliance; enforcement from an office nobody visits does not.
• Do not touch materials, billing, or quality yet.

Month 2 — materials and drawings on the same site#

• Start goods receipt for your top items by value only. Cement, steel, and one or two finishing items. Every receipt linked to a challan photograph.
• Load the current drawing revisions and switch drawing issue to the system. Stop issuing revisions on WhatsApp on a stated date; a parallel channel guarantees the register goes stale.
• Run one 30-minute weekly stock review. Reconcile physically at month end.

Month 3 — sites two and three#

Now you have a template: a location naming convention, a working daily rhythm, a materials scope, and one engineer who can train the next one. Onboard two more sites simultaneously, using that engineer rather than the vendor.

Expect the second site to take about half the effort of the first, and the third about a third. If site two takes as long as site one, you did not actually standardise anything in month one — go back rather than pressing on.

Months 4–6 — the portfolio view and the compliance loop#

• Bring the remaining sites on.
• Stand up the weekly one-hour review against the five numbers above, at a fixed time, with the same format every week. Consistency is what makes variance visible.
• Map your reporting fields to your state's quarterly progress report activity list, so that the quarter-end filing is an export and a professional's certification rather than a fortnight of reconstruction. This is the single highest-return configuration step in the whole rollout, and it is the one most builders skip.
• Only now consider expanding into equipment, safety, or CRM.

A note on connectivity, since it derails rollouts more often than any feature gap: basements, stilt levels and peripheral layouts routinely have no usable signal, and a system that needs a live connection to record a pour will not be used at the moment it matters. Offline capture with later sync is not a premium feature for Indian sites; it is a precondition. SiteSetu was built around that constraint, with progress, materials, drawings and quality records captured on mobile and synced when the network returns.

What to ask in a live demo#

Vendor demos are where portfolio claims come apart. Ask for the workflow live, on their system, in your presence.

1. Show me one screen with progress variance for four projects, broken down by tower, against declared completion dates.
2. Produce this quarter's progress report data for one project, per building, mapped to my state's activity list.
3. Transfer 200 shuttering plates from Site A to Site B and show both stock ledgers updating with an acknowledgement trail.
4. Issue a drawing revision, show me who has and has not acknowledged it, and show me the superseded print marked as superseded.
5. Show my total material exposure across the portfolio: stock on hand, ordered-not-received, and advances paid.
6. Show me every non-conformance open more than 30 days, grouped by contractor.
7. Certify a running account bill and show the audit trail from joint measurement through certification to payment.
8. Turn the network off, record a slab pour with photographs, turn it back on, and show it synced.
9. Correct a wrong entry from last week, show me the audit trail of the correction, then export everything to Excel and PDF.

Anything a vendor will not do live in a demo, they will not do in production either.

ROI math a builder can defend#

Skip the vendor spreadsheet. Three lines are enough, and all three are conservative.

Line 1: material leakage. On a Rs 20 crore residential project, material is typically 55–60% of construction cost, so roughly Rs 11–12 crore. Documented receipts, challan-linked inward entries and monthly reconciliation reasonably target one percentage point of that: Rs 11–12 lakh per project. Across four concurrent projects, Rs 44–48 lakh.

Line 2: rework avoided through drawing control. One structural rework event on a residential tower — demolition, re-execution, consultant fees, follow-on trade delay — lands in the Rs 5–15 lakh range before you count the schedule cost. Preventing one per year across the portfolio pays for most systems outright.

Line 3: the compliance line, which is the easiest to quantify and the one builders forget. A project kept in abeyance cannot register agreements for sale. Frozen registrations on a project selling even Rs 3 crore a month, held up for six weeks, is roughly Rs 4.5 crore of deferred collection plus interest on the working capital you were expecting to release. Against that, the Rs 25,000-to-Rs-50,000 penalty is a rounding error. The real cost of a missed quarterly report is the sales freeze, not the fine.

None of these lines capture the compounding benefit: a builder who knows on Monday that Tower B slipped 11 days can re-sequence internal plaster before the monsoon. A builder who finds out at the next quarter end cannot.

FAQs#

How is site management software for builders different from a contractor's site app?#

A contractor's app is optimised for the daily loop on one site: attendance, today's work, today's material. A builder needs that data underneath, but consumes it as a portfolio: variance against declared completion dates across every tower, material and advance exposure across all sites, contractor position by work order, and quarterly compliance data. If a tool cannot show four projects on one screen with location-level variance, it is a contractor tool being sold to a builder.

Does site management software actually help with RERA quarterly progress reports?#

It helps if — and only if — your progress is recorded per building or wing against the activity list your state's reporting form uses. The statutory form asks for percentage of work done against fixed activities like excavation, plinth, number of slabs, internal finishes and external plaster, prepared separately for each building. Software that records a single project-level percentage will not produce a defensible filing. Software that records progress against a tower-and-floor location structure turns the filing into an export plus a professional's certification.

What is the deadline for filing a RERA quarterly progress report?#

It depends on your state, and the range is wide. Maharashtra allows 20 days after each financial quarter ends, under MahaRERA Order 33/2022, so 20 July, 20 October, 20 January and 20 April. Karnataka, Telangana, Bihar, Haryana and Tamil Nadu allow 15 days. Uttar Pradesh and Andhra Pradesh allow only seven. Check your state's rules directly rather than relying on consultancy summaries, several of which still publish Maharashtra's superseded seven-day window.

What happens if a builder misses the quarterly filing?#

The statutory penalty under Section 61 of the RERA Act can extend to five per cent of the estimated project cost, and several states have set fixed rates — Rs 25,000 per quarter in Karnataka, Rs 15,000 in Uttar Pradesh, Rs 500 per day after a month in Telangana. The heavier consequence is administrative: MahaRERA's own non-compliance listing showed 1,632 projects in abeyance on 28 July 2026, with project bank accounts frozen and the promoter barred from executing agreements for sale until compliance is restored. For most builders the lost registration window costs far more than the fine.

How long does it take a builder with five projects to get fully onboarded?#

Realistically four to six months if you sequence it, and it fails at around six weeks if you do not. Run one site for a month on daily progress and photographs only, add materials and drawing control in month two, then onboard two more sites in month three using your own trained engineer rather than the vendor. Expect each additional site to take roughly half the effort of the one before it. If it does not, the first site was never standardised.

Should a builder buy one platform or separate tools for each function?#

Separate best-in-class tools work when the boundaries are clean, and they fail exactly where builders need them most: at the joins. Progress has to reconcile with billing, materials with cost, drawings with quality, and all of it with quarterly compliance. Every join you leave between two systems becomes a manual reconciliation somebody does on a Friday. For a builder running three to ten projects, a single system covering progress, materials, drawings, quality and billing is usually the lower-effort answer even if any individual module is not the best available.