The operating record for developers, main contractors, and subcontractors in Ghana
Construction margin leaks every day site truth reaches head office too late.
Three roles. Three versions of the same gap.
Darikoda is the operating record that closes the time gap between site reality and head office. Per-project profitability, materials variance, subcontractor performance, per-cubic-metre cost. Captured at source.
Darikoda gives Ghana developers, main contractors, and construction subcontractors structured operating evidence for per-project profitability, materials variance, approval cycles, and IPC defence. Captured at source.
Read the view that fits your seat
Which describes you?
Site truth versus financial truth.
Two versions of reality. What the project is actually doing: operators on machines, materials in stockyards, subcontractors on sections, approvals waiting on phones. What head office sees: a finance report Monday morning, a WhatsApp update Wednesday, a Friday review of last week.
The developer is too late to protect delivery date and buyer trust. The main contractor is too late to protect IPC and margin. The subcontractor is too late to defend work done and deductions. Same gap. Three positions. The role decides which margin you lose first.
Real-time site truth, before the consequence arrives.
What the report says, and what the site shows.
What surfaces
Monday morning finance report shows Project A profitable, Project B middling, Project C bleeding.
What doesn't
Project A is profitable because two operators carry it. Project B is bleeding the same way Project A would be if either of them left.
What surfaces
BoQ records 1,800 tonnes of aggregate delivered to Block A.
What doesn't
540 tonnes became Block A structure. 1,260 tonnes are unaccounted at month-end. Three weeks too late to intervene.
What surfaces
Off-plan buyer's delivery date moves from 30 September to 15 December.
What doesn't
The operational evidence said September wasn't survivable in June. The buyer found out in August. The refund clause activates in October.
What surfaces
Cert submitted to consultant for Phase 1 Block C, GHS 4.2M claimed.
What doesn't
The consultant cuts GHS 380,000 because three weeks of cube tests are missing from the evidence pack. You absorb it.
What surfaces
Site dashboard shows 8% margin on the development overall.
What doesn't
Block B alone is at -3%. Aggregate margin hides it for another quarter.
By the time the numbers reach finance, the work has already moved on.
The gap shows up differently depending on which seat you sit in. The main contractor produces an IPC submission three weeks after the work was done. The developer sees a profitability number that already absorbed the variance. The subcontractor receives a deduction at month-end with no evidence to dispute it. Same underlying gap. Three different commercial consequences.
ARCHETYPE 1 · MAIN CONTRACTOR (LEAD)
If you're the main contractor.
You win the contract from the developer or the government. You own the fleet. You run the site. You subcontract specific labour or specialised work. 100 to 2,000 assets across multiple projects. Contract structure usually FIDIC red book, some yellow book, some lump-sum.
What you care about
- Per-machine operating cost across all projects
- Per-project profitability comparison, which project is healthy, which is bleeding, surfaced before quarterly review
- Cost per cubic metre, per tonne, per linear metre of output, live and project-specific. Drives bid pricing, margin protection, and capital allocation decisions
- Material consumption truth at section level, aggregate delivered vs aggregate consumed against BoQ, surfaced the day variance appears, not the month after
- Cross-project fleet visibility
- Cert preparation speed
- Subcontractor independent measurement
- Approval velocity
- Idle machine detection
- Fuel and material integrity at scale
- Authorised dealer account funding cycles
- Audit trail that survives legal disputes, with the consultant on cert measurement, with subcontractors on tally hours and deductions, with off-plan buyers on missed delivery
Role-routed by design.
Mid-market operators distrust dashboards that show everything to everyone. The discipline is role-routing: workshop sees workshop, finance sees finance, GM sees the exception roll-up, director sees the briefing. Darikoda routes only the necessary intelligence to each role.
The approval bottleneck.
At main contractor scale (50+ assets, multiple projects), the truth gap compounds through approval friction. The GM processes hundreds of daily decisions on parts, machine moves, fuel orders, exceptions, through phone calls and WhatsApp. Machines sit idle for weeks because no one at head office had visibility on what was free where.
Darikoda surfaces the cost of an approval delay in real time, on the GM's phone, prioritised by financial impact. The decision still happens. It happens with the data.
Many main contractors are also internal plant hire firms.
On road and civils projects, the main contractor owns the equipment but rents it to specialist subcontractors. The contractor charges by machine hours, supplies the fuel, deducts both from the subcontractor's monthly payment.
When the paper tally is challenged at month-end, the contractor loses revenue or absorbs cost. Operators work for the subcontractor, but the fleet owner stays close to them: poor care of the machine shows up in the fleet owner's costs later. You can remove a bad operator from your machine, but not from the subcontractor's payroll. The leverage is real but partial.
Buyer language we hear: "internal cross-hire", "deductions from the sub's IPC", "supplied fuel against payment", "the tally guys", "we supply the machine, they dispute the hours".
Proof point
Role-routed dashboards plus cert preparation that takes 2 people 1 week instead of 10 people 1 month.
ARCHETYPE 2 · REAL ESTATE DEVELOPER
If you're the developer.
You own the project. You hire the contractors. You sell off-plan or completed homes. Mid-market in Ghana, 50 to 500 unit projects. Single-project or portfolio.
Published buyer guidance in Ghana increasingly emphasises legal certainty, financial resilience, execution track record, quality assurance, and post-acquisition support. Buyers verify GREDA membership, REAC registration, AMA permits, EPA compliance, material certifications as standard due diligence. The developer's operational record is now part of how the buyer evaluates the developer.
Real estate developers want to see everything in real time. They want efficiency, planning, coordination, and detailed transparency across every department on every project. They normally cannot see what is happening until it is already too late.
Till it's too late.
Late is not "slightly behind schedule". Late is the buyer ringing about the delivery date you promised and your operations team scrambling for an answer. Late is the budget already overspent before head office sees the variance. Late is the subcontractor's tally clerk having already pocketed three weeks of disputed fuel. Late is the consultant's cert cuts already arriving while your evidence is still in three WhatsApp threads.
By the time most developers see the operational truth, the consequence has already arrived.
The eight specific pains developers carry
- 01
Different performance on different projects.
Cost and time efficiency vary site to site. The developer with five active projects usually has two healthy, two middling, one bleeding. The aggregate makes the portfolio look balanced. The bleeder hides until quarterly review.
Darikoda surfaces per-project profitability side by side, so the bleeder shows up the moment it diverges, not three months later.
- 02
Performance tied to individuals, not the team.
A site might be hitting numbers because two of five operators carry the rest. The team average hides this.
Darikoda's attribution layer shows where performance is really coming from, per operator, supervisor, machine, shift, project. Fairer basis for coaching and recognition than team averages.
- 03
Legal disputes.
With the consultant on cert measurement. With subcontractors on tally hours and deductions. With off-plan buyers on missed delivery. The party with weaker evidence loses.
Darikoda's immutable, time-stamped, attributed audit trail is the record that survives in dispute.
- 04
Customer refunds triggered by missed delivery.
The off-plan buyer signed a contract with a delivery date. The date slips. The developer's defence is operational evidence, was the slip foreseeable, was it managed.
Darikoda surfaces earlier warning when operating evidence no longer supports the delivery date. Time to intervene before the buyer relationship breaks.
- 05
Stolen materials.
100 tonnes delivered. 70 tonnes became structure. 30 tonnes vanished. Currently the variance shows up only at month-end.
Darikoda's material consumption truth at section level surfaces variance the day it appears, not the month after.
- 06
Materials shortfall.
Wrong amount ordered. BoQ assumptions off. Supplier under-delivered. Work stops. Crew sits idle. Schedule slips.
Darikoda links material consumption to BoQ and work front. Shortfall surfaces before the crew arrives at an empty stockpile.
- 07
Many stakeholders, no real-time visibility.
Architects, engineers, contractors, subs, suppliers, finance, sales, regulators. Each gets a different version filtered through different people.
Darikoda's role-routed dashboards give each stakeholder their slice from the same record. Same source, different cuts.
- 08
Cost per cubic metre to manage sales and margins.
Without it, sales pricing is guesswork and margin protection is reactive.
Darikoda's cost-per-output attribution (per cubic metre, tonne, linear metre, home unit) is live, project-specific, updated as work happens.
Their language
Phase 1, phase 2, block A, block B, off-plan buyers, completion date, snagging, contractor variation order, BoQ overrun, GREDA, Lands Commission registration, AMA permit, EPA compliance, escrow account, "see what's happening before it's too late", "every department in real time", "cost per cubic metre", "the buyer is asking", "we have a refund clause", "different sites different stories".
Proof point
A live dashboard the developer's finance director or COO can open at any moment and see: budget vs actual on every active section, material consumption variance, subcontractor performance, projected delivery dates with operational evidence beneath each one, and per-cubic-metre cost across every project side by side. Not a Monday-morning report. A real-time record that closes the time gap between site reality and decision-making, before the news becomes bad news.
ARCHETYPE 3 · SUBCONTRACTOR
If you're a subcontractor.
Earthworks, concrete, finishing, MEP, mechanical, labour-only. 5 to 30 assets if equipped, or no fleet if labour-only. Paid per measurement, per day, or lump sum.
The proof point is simple: a defendable log of work done you can hand to the main's QS at month-end. Time-stamped. Attributed. No reconstruction. The hours you worked, the metres you laid, the tonnes you placed are the hours, metres, and tonnes that get billed.
02 / The platform · applied to construction
Three engines, applied to construction.
The same operating-record logic that runs underneath every Darikoda deployment, surfaced in construction's native vocabulary.
Materials variance at section level
The variance shows up the day it appears, not the month after.
100 tonnes delivered. 70 tonnes became structure. 30 tonnes vanished. The variance shows up the day it appears, not the month after.
Phase 2 of the next development gets a defensible BoQ because phase 1 evidence is already in the record. 20 to 30 day reduction in detection latency vs month-end reconciliation.
Subcontractor coordination
Independent measurement of each subcontractor's work. Fuel and material attribution where you supply them. A defendable trail when the deduction is challenged. Same source: main contractor sees the aggregate, each sub sees their own slice.
Approval cycle visibility
The GM processes hundreds of daily approvals through phone and WhatsApp. Each carries a cost only visible when the consequence arrives: an idle machine, an unstarted section, a fuel order that didn't ship. Darikoda surfaces the cost of an approval delay in real time, prioritised by financial impact. Median approval time of 47 seconds across pilot operators. The decision still happens. It happens with the data.
Where the margin gap closes.
Per-project profitability vs portfolio average
Old way
Quarterly review shows 8% portfolio margin. Comfortable. Three months later, Block B's reconciliation arrives at -3%. The portfolio average had been hiding it for a full quarter.
On Darikoda
Per-project profitability surfaces live. Block B diverges from the portfolio average in week three of the quarter, not at quarterly review. The intervention window opens 10 weeks earlier.
10 weeks earlier
variance detection on average across pilot operators.
Materials variance
Old way
1,800 tonnes aggregate delivered to Block A. The variance shows up at month-end reconciliation. 1,260 tonnes unaccounted. The supplier dispute begins. The site is already on the next phase.
On Darikoda
Material consumption captured at the section. Variance against BoQ flags the day it crosses the threshold. The intervention happens before the next delivery is ordered, not three weeks after the fact.
Same-day
variance surfaces vs month-end. 20 to 30 day reduction in detection latency.
Approval cycle under WhatsApp
Old way
GM gets the part-order approval request at 11:47am via WhatsApp. Responds at 3:14pm because of an unrelated meeting. Machine sits idle for the rest of the day. Cost is invisible.
On Darikoda
Approval lands on the GM's phone with the financial impact attached. GM sees that the delay costs GHS 47K in idle-machine time. The decision happens with the data.
47 seconds
median approval time across pilot operators. The cost of delay becomes visible before it's incurred.
Contract environment
Built for the contracts you actually sign.
FIDIC red book. Joint measurement. BoQ-aligned cost tracking. Variation orders documented at the moment, not three months later. Cert prep with 2 people for 1 week instead of 10 people for 1 month. The contract environment shaped the operating record, not the other way around.
Built so the record survives the site.
- Every field write saves locally first, syncs when signal returns. Your operators don't wait for 4G.
- Every transaction has a sync state, saved, queued, synced, failed. No more "did it go through?"
- Every action is attributed to a person, role, device, and time. No silent edits to history.
- Shared tablets use PIN-level worker attribution. No one is logged in as someone else.
- Failed syncs create visible issues, not silent gaps.
- Finance and operations see the same record. Your existing accounting or ERP gets fed the per-project truth it cannot produce on its own.
Built so the record survives the site
Cross-vertical reach
Many main contractors operate as internal hire firms.
The internal cross-hire dynamic, where you own the equipment, supply fuel, and deduct both from the subcontractor's payment, is a substantial part of how Ghana road and civils projects actually run. If that's part of your operating model, the deduction-game framing on the Plant Hire & Fleet Owners page applies directly.
Construction-specific FAQ.
Common questions from developers, main contractors, and subcontractors.
Do you integrate with ERP systems like Sage, NetSuite, or Yardi?
Yes. Darikoda is the operating record layer above the ERP. Sage, NetSuite, Yardi, QuickBooks Enterprise, Microsoft Dynamics handle finance, GL, AR, AP, asset depreciation: what the invoice says. Darikoda handles what happened on site. We feed structured operational data into the ERP on whatever cadence the finance team needs.
What if our fleet is 200+ machines across 5+ projects?
That's the sweet spot for main contractor scale. The operating record is per-machine, per-project, per-shift: the multi-project layer is built in. Head office sees cross-project plant utilisation, redeployment opportunities, per-project profitability side by side. The bleeding project shows up the moment it diverges, not in quarterly review.
How does Darikoda handle subcontractor relationships?
Three things. Independent measurement of each sub's work, captured at source with PIN-level attribution. Attribution of any supplied resources (fuel, materials, equipment hours) where you supply against deduction. Role-routed access: the sub sees their own slice, you see the aggregate. Same source, different cuts.
Can you produce IPC submissions automatically?
Cert preparation moves from ten people for a month to two people for a week. Structured field evidence (section quantities, materials consumed, plant hours, manpower attendance) feeds directly into the IPC submission format. Configurable to FIDIC red, FIDIC yellow, lump-sum measurement, or your specific client's template.
What's the minimum project size where this makes sense?
Around 50 active assets or a single development of 50+ units, or any multi-project portfolio. Smaller projects can still benefit on specific use cases (IPC defence, subcontractor measurement, materials variance), but the full operational record value scales with operational complexity. The Operational Audit produces the specific number for your portfolio.
How fast does material variance show up?
Same day. Material delivery is captured at the gate. Material consumption is captured at the section. The variance between aggregate delivered and aggregate consumed against BoQ is live, updated as material moves. If the day's variance crosses a threshold, the alert reaches the relevant role the same day, not at month-end reconciliation.
Can the developer have read-only visibility into the contractor's data?
Yes, by design. Role-routed dashboards give the developer their own view: projected delivery dates with operational evidence beneath each, per-cubic-metre cost across the portfolio, material variance flags, subcontractor performance. The contractor controls what's shared. The developer gets the slice they're entitled to under the contract, in real time, from the same source.
We rent equipment internally to our own subcontractors, what changes?
That model has a dedicated page. The internal cross-hire dynamic is distinct enough that we built a separate buyer brief for it. Deduction game, working / faulty / not needed pattern, leverage nuance: see the Plant Hire & Fleet Owners page.
Are you compatible with the Ghana Building Code requirements?
Darikoda captures the operational record. Compliance with the Ghana Building Code, AMA permits, EPA conditions, GREDA standards is on the contractor and developer. What we provide is the time-stamped, attributed, immutable evidence chain that supports regulatory audit, buyer due diligence, and dispute defence.
What does it cost?
Fixed-fee Build & Activation phase (four weeks, configures the operating record to your operation), then per-environment monthly tier once the pilot proves value. The Operational Audit produces the specific number for your portfolio. Book it through the audit page above.
See where your construction margin leaks.
The Operational Audit takes 30 minutes. You get a one-page leakage report, construction-specific, that you keep regardless of next steps.
Patterns described here are drawn from extensive field audits and industry research across Ghana's mining, construction, roadworks, and quarry sectors. No specific operator is named or identifiable.