Every clock watched. Your Friday back.
Our planners keep the programme honest in Primavera P6 or Microsoft Project, while AI drafts the reports, reads the contract and watches every notice period in it. You spend the week managing the job instead of describing it.
-
Weekly progress pack
4×faster
A day of compiling becomes two hours of review, drafted around the programme update.
-
Contract clocks
100%tracked every day
Every notice period in your contract, with the days left, before the time bar.
-
Compensation events
1 dayto flag, with the clause
Lifted out of the minutes within a working day, for you to decide.
The week you know
The week goes on describing the job, not running it.
Monday is a look-ahead nobody believes. Friday is report day. Somewhere in between, a clock in the contract starts running, and the only record of it is a line in the minutes.
-
Monday · 07:00
The look-ahead nobody uses.
The three-week look-ahead is a P6 filter printed this morning. Nobody checked whether the drawings are issued, the steel has landed or the permit is signed, so the foremen plan from memory.
What it costsA crew stood down on Wednesday, and a promise broken at the coordination meeting.
-
Tuesday · 11:30
The eight-week clock nobody started.
Late access was raised at the site meeting in week three. Under NEC4, the contractor has eight weeks from becoming aware to notify a compensation event. In week twelve, someone remembers.
What it costsThe entitlement itself. Miss clause 61.3 and neither the Prices nor the Completion Date move.
-
Wednesday · 15:10
It was in the minutes.
The delay is minuted, so everyone assumes it was notified. Under the JBCC Principal Building Agreement, notice of intention to claim is due within 20 working days, failing which the claim is forfeited. Minutes are not notice.
What it costsA forfeited extension of time, and the penalties that follow it.
-
Thursday · 09:45
The programme everyone stopped believing.
The accepted programme is three revisions behind the site. Under NEC, the Project Manager has two weeks to accept a revised programme, but can't accept one that never arrives. Meanwhile, every compensation event is assessed against dates that stopped being true.
What it costsWeak assessments, harder negotiations, and a dispute waiting at the end.
-
Thursday · 16:20
Variation order archaeology.
The VO was agreed on site, the instruction is an email, the quote is on another revision, and the QS needs all three for the payment certificate. South African research ranks variation orders as the leading cause of cost overruns on public projects.
What it costsA late payment certificate, and an overrun nobody can trace back to its cause.
-
Friday · 14:00
Friday is report day.
Progress from five supervisors in five formats, the P6 update, photos off WhatsApp, cost from finance, stats from the SHE officer. By the time the pack goes out, it's Monday's news.
What it costsThe best part of a day, every week, spent describing the job instead of managing it.
What we take off your plate
The controls kept. The paperwork drafted.
We run the project-controls engine under your contract, whether NEC, JBCC, FIDIC or GCC, and hand you packs you can edit and send. The programme stays in Primavera P6 or Microsoft Project, owned by our planners.
-
Baseline programme
Built or reviewed in Primavera P6 or Microsoft Project, resource- and cost-loaded where you need it, with a basis-of-schedule narrative.
-
Weekly progress pack
Progress against baseline, critical-path movement, look-ahead, constraints, photos, safety and quality headlines, and the decisions waiting on you.
-
Three-week look-ahead with constraint log
Every activity checked for drawings, materials, permits, access and people, and cleared before the Monday meeting.
-
Contract notices register NEC · JBCC · FIDIC · GCC
Every early warning, compensation event, instruction and claim, with the clause that started its clock and the days left to act.
-
Variation order files
Instruction, drawing revision, quote, measured quantities and approval chain for each VO, ready for the quantity surveyor.
-
Delay register and claim support
A delay register kept as events happen, time-impact or windows analysis by our planners, and a drafted narrative with an evidence index.
-
Monthly report and programme submission
Written to what your contract asks for, whether that's a revised programme under NEC or the monthly update GCC 2025 now requires.
-
Steering committee pack
A one-page dashboard, the risk register and the cash-flow S-curve, in Power BI or PDF, drawn from the same data as everything else.
How it gets done
One data date a week. Every record, every day.
Planners own the programme. AI reads everything around it: the contract, the diaries, the minutes and the correspondence. You see what needs a decision, with the clause and the deadline attached.
-
Week 1Set-up
The contract becomes a calendar.
Our planner builds or reviews the baseline with you. Kuumba Work reads the contract, the Contract Data and every amendment, and builds the notice calendar: each clause with a clock, who must act, and how many days they have.
- Planner
- AI reads the contract
- You approve
-
DailySite records
Every record read the day it's made.
Supervisors keep diaries, photos and minutes as they do now. AI reads the day's records and correspondence, and flags anything that may be an early warning, a compensation event or a delay, with the clause and the deadline. Whether to notify is your call.
- Site team
- AI flags
- You decide
-
FridayData date
A planner updates the programme.
Actuals and remaining durations go into P6 or Microsoft Project, and our planner reviews the logic and the critical path. AI never touches your P6: it reads the export, and your planner imports only the changes they accept.
- Planner
-
FridayThe pack
The pack is drafted around the update.
Narrative, variance tables, look-ahead, constraints, photo log and open decisions, drafted from the programme export and the week's records. The planner adds the commentary only a planner can write.
- AI drafts
- Planner
-
FridayIssued
You approve, and it goes out.
You read it, change whatever you'd say differently, and approve. Nothing leaves under your name until you have.
- You approve
-
MondayLook-ahead
Constraints cleared before the meeting.
Each look-ahead activity is checked against drawing status, purchase orders and goods receipts in SAP Business One (read-only), permits and open RFIs. The construction manager runs the meeting from a ready list, not a wish list.
- AI checks
- Construction manager
-
As neededChanges and claims
Every VO and claim, built from the record.
AI assembles each VO file and drafts the quotation or assessment letter. For claims, our planners do the delay analysis and AI builds the evidence index from records made at the time. You and your contracts adviser own the position, and you sign.
- AI assembles
- Planner
- You sign
What the week depends on. Two hours on the weekly pack assumes site records arrive daily, in whatever form your supervisors already use, and a planner who updates the programme on the data date. A clock flagged is not a notice sent: whether an event is truly a compensation event, or worth a claim, stays a judgement for you and your contracts adviser.
The old way, and with Kuumba
Same contract. Nothing left to the minutes.
| Area | The old way | With Kuumba |
|---|---|---|
| Weekly report | The best part of a day, every Friday | Drafted around the update, with about two hours of your review |
| Notice periods | Remembered, or not | Every clock in the contract on one register, checked daily |
| Possible compensation events | Found in the minutes, weeks later | Flagged within a working day of the record, with the clause and deadline |
| Look-ahead | A printed filter, planned from memory | Checked against drawings, orders, permits and RFIs before Monday |
| Variation orders | An email, a quote and a verbal yes | One file per VO: instruction, revision, quote, quantities and approvals |
| Claims | Rebuilt months later from memory | Evidence indexed from records made at the time, as the SCL Protocol prefers |
| The programme | Three revisions behind the site | Updated every data date by a planner, and submitted when your contract asks |
Where AI helps, where people decide
AI watches the clocks. People make the calls.
AI does
The reading, the drafting and the clock-watching.
- Reads the contract, Contract Data and amendments into a calendar of clocks.
- Reads diaries, minutes and correspondence every day for events that may need notice.
- Drafts weekly and monthly packs around the P6 or Microsoft Project export.
- Checks look-ahead activities against drawings, orders, permits and RFIs.
- Assembles VO files and claim evidence, citing every record it uses.
People decide
The programme, the position and every letter.
- The logic and durations in the programme. Our planners own it.
- Whether an event is notifiable, and whether to notify.
- What to claim, and the delay analysis behind it.
- Every instruction, quotation and letter that leaves under your name.
- Running the meetings, and talking to the client.
AI never notifies, instructs or accepts on your behalf. It tells you a clock is running; you decide what happens next.
Contracts we work to
Written to the contract you signed.
The notice calendar is built from your Contract Data and amendments, not the default clauses. These are the clocks we meet most often on South African projects.
- NEC4 ECC · clause 61.38 weeks to notify a compensation event
- NEC4 ECC · clause 62.33 weeks to submit a quotation
- NEC4 ECC · clause 31.32 weeks to accept or reject a programme
- JBCC PBA · clause 2320 working days to give notice; the claim within 40 of quantifying it
- FIDIC 2017 · Sub-Clause 20.228-day notice, 84-day detailed claim
- GCC 2015 · clause 10.128 days to claim or give notice of intention
- GCC 2025Two-stage claims and a monthly programme update
- CIDB Standard for UniformityStandard contract forms for public work
- SCL Delay and Disruption ProtocolSecond edition, 2017: records made at the time
- Construction Regulations 2014Client audits at least every 30 days
Questions project managers ask
The questions we hear first.
Does the AI update my P6 programme?
No. Our planners update Primavera P6 or Microsoft Project. Kuumba Work reads the exported programme and the site records, and drafts the narrative around them.
It has no live connection to your scheduling software and never writes to it. The programme has one owner, and that owner is a person.
Which contracts do you work under?
NEC3 and NEC4, JBCC, FIDIC 2017 (and 1999 where it still governs), and GCC 2015 or the new GCC 2025.
We build the notice calendar from your actual Contract Data, Z clauses and amendments, not the default text, because that's where the clocks usually change.
Will it tell me I've missed a time bar?
It tells you long before: that a clock is running, which clause started it and how many days are left.
Whether a site event really is a compensation event is a judgement for you and your contracts adviser. We make sure you have time to make it.
Can you write the claim?
We draft it, and our planners do the delay analysis. You and your adviser own the position and sign. The SCL Protocol favours records made at the time, which is exactly what the daily capture builds.
We never back-fill a record and present it as contemporaneous.
Our data lives in SAP Business One, Excel and WhatsApp. Is that a problem?
No. SAP Business One we read directly, read-only. Excel, Word and PDF we read and produce. WhatsApp photos and notes are loaded into the project; a direct WhatsApp channel is on our roadmap, not live.
So what does the project manager still do?
Manage. Run the meetings, make the calls, talk to the client. The pack arrives drafted; you edit it, approve it and send it.


