Can this job start on Thursday?
Is the material here, is a crew free, may the stage move, and what happened on site today. Four questions the board answers before anybody drives out.
Ordered and received against this project
Read from the purchase orders and goods receipts you already raised — free warehouse stock is shown beside it as context, never counted as coverage.
A pipeline that matches how you actually build.
Solar EPC work does not fit a generic task app, and it does not fit one vendor's idea of a solar pipeline either. Define the stages once and everything downstream follows them.
Your stages, not ours
Name the stages your business actually runs — between two and eight of them — and every board, funnel and report re-reads them. Changing the list never rewrites a project behind your back; it shows you how many would move before you save.
Gates that warn, not block
Drag a job forward with checklist tasks still open and it names them and asks. "Move anyway" is right there, because on site the reason is usually a good one.
And it remembers the move
Each transition is stamped, which is what makes time-in-stage and bottlenecks real numbers later instead of an impression.
Ask before the crew arrives, not after.
Procurement knew what had been ordered. Operations knew what each job needed. Nothing joined the two, so the steel being on a truck was discovered on site.
Readiness against this project
What its bill of materials needs, what has been ordered for it, and what has actually been received — per line, so one over-delivered item cannot hide another that never arrived.
Free stock is shown beside it, never inside it
Warehouse stock is a shared pool. Counting it as coverage would let two projects both look ready on the strength of the same forty modules, so it is context and labelled as context.
Three-way matched before it is paid
The vendor bill is checked against the order and the goods receipt, and price, quantity and unexpected-item differences are named rather than quietly accepted.
Booked, or double-booked.
Before this existed, a project carried a manager's name and nothing else — so the question of who was physically on site on a given day had no answer in the system at all.
Who is free on Thursday
A week of crews against days, so the answer is a glance rather than three phone calls.
Who is double-booked
A crew is in one place at a time unless you raise its capacity. Two jobs on one day is flagged the moment you make it.
And it still lets you
A clash is a warning, never a refusal — sometimes a split crew is exactly what you meant, and refusing would only make somebody delete the other booking.
Week of 14 October
3 crews · 12 booked crew-days
The update arrives on the record.
Not in a group chat that scrolls away by Friday. Whoever asks in year nine finds the same photographs the supervisor took on the day.
The survey
Measurements, shadow notes and photographs recorded at the site from a phone browser, against the project they belong to.
The daily update
What was done, how many were on site, what is blocking tomorrow, and photographs — one short form, filled in before the crew leaves.
Progress that cannot be talked up
The percentage comes from the tasks actually completed. Nobody types a number into it, so "90% done" means ninety per cent of the work is closed.
Net metering
India · DISCOM applications
Waiting 36 days on the application — 6 over. Chase it.
How long has it been sitting there?
A register tells you which stage a DISCOM application is in. A worklist tells you how long it has been stuck — and puts the ones that are late at the top, where somebody will ring about them.
The application reference lives on the project, the date it entered each stage is stamped when you advance it, and the waiting count is derived from that — so the number on the screen and the number in the chase-up email cannot disagree.
A project with no recorded start date shows no clock at all rather than a fabricated one, and it is offered a start date instead of being quietly sorted to the bottom.
The job ends. The record does not.
A rooftop is a twenty-five-year relationship. What the site team recorded during the install is what the service engineer opens in year nine.
The commissioning pack
A close-out checklist suited to the work, and the certificate only generates once every item on it is ticked. A handover document a customer signs should mean something.
Maintenance that books itself
A schedule raises its own service visits on time — cleaning, an inverter check, the annual review — so year three does not depend on somebody remembering year one.
And where the time goes
Average time in each stage, the stage that holds jobs up most, and anything that has not moved in a fortnight.
What operations teams ask first
Including the one we answer with a plain no, because finding it out after switching is worse.
Explore more of the platform
Every job, with one honest status.
Stop chasing updates across three group chats and a spreadsheet. Put the next installation on a record the whole team reads the same way.