- Elec Luminaire schedule 24 h
- Mech Plant sizing 62 h
- Fire Alarm schematic 18 h
- P&H Drainage layouts 28 h
The five-minute test
What a project lead can answer five minutes after opening a live job.
Same register, four ways of reading it. Pick a question and the sheet answers it, at the fidelity you would actually see it.
| Deliverable | Owner | Due | Progress | Plan | Burn |
|---|---|---|---|---|---|
| Elec Luminaire schedule at risk | YH | 12 Sep · 4d over | 10% | 24 h | 31 h |
| Elec LV schematic | CW | 26 Sep | 65% | 40 h | 28 h |
| Mech Mechanical schematics & plant sizing | DK | 3 Oct · in 6d | 45% | 62 h | 24 h |
| Mech IES overheating assessment (TM52) burn ahead | SM | 17 Oct | 80% | 34 h | 36 h |
| Fire Fire alarm schematic waiting | JL | 10 Oct | 20% | 18 h | 4 h |
| P&H Above-ground drainage layouts | AC | 24 Oct | 30% | 28 h | 9 h |
Every cell edits in place, and the row records who changed it and when.
Overdue
- Luminaire schedule Electrical · YH · 4d over · 10%
Due inside a week
- Mechanical schematics & plant sizing Mechanical · DK · 45%
- Site-wide diversity assessment Electrical · CW · 70%
Burn ahead of progress
- IES overheating assessment (TM52) 36 h burned of 34 h planned · 80% done
- Luminaire schedule 31 h burned of 24 h planned · 10% done
Blocked, waiting on someone else
- Fire alarm schematic waiting on architect's compartmentation
Nobody sets these. They fall out of the dates, the progress and the hours.
Deliverable
SepOctNovDec
Luminaire schedule
LV schematic
Mech schematics
TM52 assessment
Fire alarm schematic
Drainage layouts
Drag a bar and the date moves on the register. It is one set of rows, drawn twice.
| Person | Sep | Oct | Nov |
|---|---|---|---|
| David Kerr Mechanical | 132 h | 118 h | 46 h |
| Callum Wright Electrical | 148 h | 140 h | 96 h |
| Sean Murphy Mechanical | 126 h | 130 h | 58 h |
| Yusuf Haddad Electrical | 96 h | 112 h | 120 h |
| Committed | 502 h | 500 h | 320 h |
November is thin and Callum is over in September. Both are visible now, not in November.
Monday · 08:47
The information exists. Reassembling it is the job nobody costed.
programme_v7_FINAL(2).xlsx — and two others
- Open last week's programme, hope it is the current one.
- Scroll the inbox for what was issued on Friday.
- Message three people to ask where they got to.
- Hear about the overrun when the timesheets clear.
Riverside · RIBA 4 · live
- Every deliverable, its owner, its date, its last change.
- What slipped this week, on the stage it slipped in.
- Hours burned against hours planned, per deliverable.
- Next month's committed hours, per person.
The problem was never that the information doesn't exist. It is scattered, so it takes half a morning to reassemble — and by the time it is legible, the thing it was warning about has happened.
Why this is not another financial tool
Your practice has already planned this job. It did it last year, under a different name.
Timesheets tell you what a project cost after it happened. The thing no system holds is the shape of the work — which deliverables a depot job owes, in which disciplines, roughly how many hours each one takes, and what has to land before what. That knowledge exists in your practice already. It just lives in the heads of the four people who have done it before, and in a folder of superseded spreadsheets.
Saved as a template
The definition crosses. The burn stays with the job that earned it.
- Elec Luminaire schedule 24 h
- Mech Plant sizing 62 h
- Fire Alarm schematic 18 h
- P&H Drainage layouts 28 h
4 deliverables · 132 h · 0 % burned
That is the difference between a fee you defend and a fee you guessed. The estimate on a new job stops being one person's recollection and becomes the record of what the practice has actually done — which means the person who sets a project up no longer has to be the person who has seen twenty of them. And every job you close makes that record better than it was.
How it works
A stage's worth of deliverables, set up once.
Start the stage from a framework, not a blank sheet
Pick the deliverables the stage owes from a BG6-shaped list, by discipline, then cut what does not apply. What you keep becomes the register.
Put hours and an owner on each row
Planned hours and a name. That is the whole input. Progress and burn land on the row as the work happens, so the register is the record rather than a second copy of one.
Advance the stage when it closes
The stage's set carries forward, burn resets, and the closed stage stays as it was — so what you promised at RIBA 3 is still readable at RIBA 4.
Scope
It reads the work, not the ledger.
The boundary with your finance system is drawn on purpose, and it is not moving soon. Here is exactly where it sits.
Korscope
- Deliverables, by discipline
- Owners and dates
- Hours planned against burned
- RIBA stages and what each owes
- Committed hours, months out
Your finance system
- Timesheets
- Invoicing and payment
- Payroll
- The ledger
- Rates of record
So, plainly, it is not:
- an ERP
- a Maconomy replacement
- a timesheet
- a live ERP integration — that is parked, not promised
- an AI writing your programme
The risk flags are plain rules on dates, progress and hours. You can check them by hand, and during the pilot you should.
Data & access
Your project data, in a region you choose.
- Residency
- UK-hosted by default. Self-host inside your own estate from the same build — it is not a different product.
- Sign-in
- A one-time code to a work address. There is no password store to breach.
- Roles
- Admin actions are refused at the API, not hidden in the interface. One workspace cannot read another's.
- Sharing
- Freeze a project into a read-only snapshot at its own URL. Later edits do not change what the client saw.
Straight answers
Before you ask.
Is this another system for my team to keep up to date?
It replaces the spreadsheet the deliverables already live in, and the register and the programme are the same rows drawn twice — so there is no second place to update. If your team keeps two records instead of one, it has failed.
How much does it cost?
Nothing is for sale yet. This is a private pilot while the commercial and IP questions are settled properly, so pilot practices pay nothing and are told plainly what is unfinished.
Will it save us money?
The honest answer is that we have modelled it and not proved it. What it does do is surface an overrun at least one reporting cycle earlier than the timesheet lag, which is the point at which a fee is still recoverable.
Is this only for MEP?
No. The model is deliverables, disciplines, hours and stages, so any discipline that plans work that way fits — structures, architecture, civils. The vocabulary and RIBA stages come from building services first, because that is who it is being tested with.
What happens to our data if we stop?
You export it, or you keep running the same build yourself. There is one container and two deployment modes; self-host is not a different product.
How finished is it?
Pilot-grade. Projects, the deliverables register, the programme, financials, people, the month-ahead forecast and saving a delivered project as a template are live and in daily use. Tender support is being built. Anything not built is not on this page.
Pilot
If setting up a project still lands on your desk, we should talk.
Most of what a director does on a new job is remembering how the last one went — which is exactly the part a senior engineer could own if the practice's own record were sitting in front of them. A pilot is a handful of real projects for a stage, with someone on hand while your team uses it. No fee, no contract, and you tell us where it fails.