Project Operations
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.
- Starter
- plan site surveys and field reports start on
- Professional
- plan projects, crews and material readiness start on
- Growth
- plan multiple warehouses start on
- 4
- net-metering stages tracked per project (India)
A pipeline that matches how you build. And who is on which roof.
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 — then see, by the day, which crew is where.
The board
Stages you define, gates that warn
Booked, or double-booked
Week of 14 October · 3 crews · 12 booked crew-days
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.
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.
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 update arrives on the record. The record outlives the job.
Not in a group chat that scrolls away by Friday. 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.
From the site
A phone browser, not a group chat
Handover and after
The job ends; the record does not
Explore more of the platform
What operations teams ask first
Including the one we answer with a plain no, because finding it out after switching is worse.
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.
