For developers
The dates are the product
A developer’s statutory exposure is almost entirely date arithmetic against rules that differ by state: when the periodic filing is due, when the clearance stops being valid, which rate governs a transfer, and whether a disbursement is ahead of the progress it was certified against. None of that is difficult. All of it is easy to miss, and expensive when missed.
Five problems
Every one of them is a date somebody did not own
None of these are difficult. All of them are easy to miss, and the cost of missing one is out of all proportion to the effort of not missing it.
The quarterly filing was late because nobody owned the date
Obligations are generated from the registration date and the project’s end date, against the prescribed schedule for the state the project is actually in, with real due dates rather than reminders. They appear on a calendar somebody is responsible for, which is the only mechanism that has ever worked for this.
A clearance lapsed and we found out from the authority
Every approval carries its validity, its expiry, the authority that issued it and the document that evidences it. Anything lapsing inside ninety days is surfaced without being asked for. An approval that expired is a problem that was visible for a quarter before it became one.
Duty was computed on the consideration, and the notified rate was higher
Both are computed and both are shown, with the governing one identified and the difference visible. The arithmetic is exact decimal and rounds once, and the working stays on the record — so a figure questioned later is answered from the file rather than reconstructed.
A tranche was released ahead of the stage it was certified for
The request is checked against the certified stage percentage and flagged rather than paid. The certified stages and what has already been disbursed are both on the record, so the flag is a number somebody can look at.
The agreement was a template somebody edited last year
Development agreements, deeds, leases and powers of attorney are drafted against a clause schedule, so parties, recitals, consideration, covenants and the schedule of property are structural requirements rather than sections a drafter might remember. Consideration figures come from the record on the same rule the valuation figures follow, and the evidence gate applies here too — an instrument cannot assert a title fact that nothing on file supports.
The first question we will ask
Which states, and which authorities
Everything on this page is downstream of that answer: the authority, the prescribed schedule, the due dates, the duty rate, the notified rate and the factor a local area unit converts by.
- Obligations and due dates resolved per state rather than from a national default.
- Duty rates, and the concessions that vary with the parties to the instrument, per state.
- Local area units — bigha, biswa, katha, vigha — carry factors that differ by state, and one of those wrong moves an area by a multiple.
- Those state-dependent factors are held as unverified against notified schedules and refuse to convert without an explicit instruction. A blocked conversion is recoverable; a silently wrong area is not.
- Where a value is not verified against a notified source, the software says so rather than using it quietly.
Said plainly
This is the statutory half of the product, and that may be all you need
Most of what is written across the rest of this line is about valuation — the grid, the approaches, the evidence gate, the signature. If you are a developer, you may never touch any of it, and we are not going to pretend the valuation engine is what you came for. What is useful to you is the filing calendar, the approvals with their expiry, the duty arithmetic and the disbursement check. Tell us which states you build in and we will tell you plainly whether that is worth your time — including when the answer is that a spreadsheet and a diligent person are already sufficient.
Tell us which states you build inFiling quarterly across more than one state?
That is the case where the calendar stops being something a diligent person can hold in their head, and it is the case this half of the product is for.
Get in touch
Talk to the people building it
No chatbot and no ticket queue. Tell us what your practice actually looks like — how many valuers, which asset classes, who reviews, which banks you are on the panel of — and someone who works on the software will reply.
info@legosphere.com