CIP · Construction Intelligence Platform

From tender to final account.

CIP runs the daily work of a construction project and keeps the record that work produces. It is built in conjunction with construction and dispute domain expertise, so the record is kept the way a tribunal will read it.

Adaptable to your organisation

Set up the way you work.

CIP adapts to the organisation using it. Each organisation is set up for its role, its contracts, its calendars and the region its data must stay in, and it opens on the view that matters to that role.

Opens on: your projects

Contractors and subcontractors

Project first. Tender, plan and build in one place, with each module a click away beside the job.

Opens on: the portfolio

Employers, owners and EPCMs

Oversight of several contractors on one project, choosing what you receive from each: programmes, progress, notices and claims.

Opens on: your matters

Law firms and experts

Matter first. Dispute Intelligence licensed on its own, with matter walls, conflict attestation and privilege controls.

M1
Tender

Tender Intelligence

Win the right work at the right price. M1 reads the tender documents, finds where the contract departs from the standard form and shows what each change does to your risk and your price.

  • Amendment review against standard FIDIC, NEC, GCC and JBCC wording
  • Tender risk register generated from the contract, with contingency priced per risk
  • Rate build up and quantity surveyor review
  • Submission pack assembled from the work above
M1 · Tender Intelligence · Risk registerFIDIC 2017 Red Book
RefClauseChange from standardConsequenceRatingContingency
R-0320.2.1Notice period cut to 14 daysTime bar exposure doublesHighR 1.2m
R-078.8Delay damages cap deletedUnlimited delay damagesHighR 3.4m
R-114.12Unforeseeable conditions deletedGround risk moves to contractorMediumR 2.1m
R-1514.7Payment period extended to 56 daysCash flow strainMediumR 0.6m
4 of 23 amendments shownContingency total R 11.8mExample tender
M2
Plan

Programme Builder

A baseline you can defend. M2 imports Primavera P6 programmes and builds the baseline the way a delay expert would sign it off.

  • Durations from quantities and production rates, with judgement only where no quantities exist
  • Contract calendars, sectional completion and third party milestones at the top of the programme
  • DCMA 14-point assessment, with a separate CIP verdict on logic, structure, contract and build
  • A written reason required for every failed check before the programme can be issued
  • A Basis of Schedule document produced with each baseline
  • Each update compared with the baseline, and near critical work flagged below 10 days of float
  • Reads Primavera P6 XER files
M2 · Programme Builder · Baseline qualityRev 00 · 1,284 activities
DCMA-1412 / 14
CIP verdict3 open
Near critical41
Data date02 Feb
CheckThresholdResult against thresholdValue
Missing logic≤ 5%
2.1%Pass
Leads0
0Pass
Lags≤ 5%
7.8%Review
Hard constraints≤ 5%
1.4%Pass
High float≤ 5%
9.6%Fail
Negative float0
0Pass
High duration≤ 5%
3.0%Pass
Critical path testpass
passPass
Marker shows the thresholdExample programme
M3
Build

Progress and Commercial

Capture the job as it happens. M3 turns the programme into daily work for the foreman, then feeds what was achieved into the next programme update.

  • Daily sheets issued from the programme for a day, a week, or a three or six week lookahead
  • Progress by quantity or percentage, with plant, equipment and labour picked from set lists
  • A separate management diary for time related preliminaries
  • Early warnings and notices previewed, issued from your own mailbox and filed against the project
  • Recipients checked against the contract's named parties, and every send recorded
  • Fourteen contract administration registers in one place
M3 · Progress and Commercial · Daily sheetSynced 17:04
Thu 05 Mar 2026 · Area B
Foreman T. Ndlovu · Weather: clear, 31°C · Lookahead: 1 week
ActivityPlannedAchievedUnitResources
A1010 Bulk earthworks, zone 31,2001,150m³Excavator 30 t ×2, ADT ×3
A1020 Piling, Area B120pilesPiling rig ×1, standing
A1035 Stormwater, line S24852mTLB ×1, general labour ×6
EW-014Area B access not given. Raised from this sheet. Sent 08:12 to the Engineer · named party verified
Feeds Update 07Example project
M4
Cost

Costing

Know where the money stands at every cut off. M4 sets actual cost against value, period by period, on the same record as the programme and the commitments.

  • Actual cost by cost code, linked to its work package and commitment, with a documented import layout
  • A reconciliation ledger of cost against value at each cut off, over and under valuation carried forward
  • A closed period cannot be changed
  • Three estimate at completion methods, with the estimate class read from the tender
  • A cash flow curve built from the programme and the procurement commitments
  • Payment certificates from Progress and Commercial read at the cut off
  • A closed period exported into a Dispute Intelligence case as it stood
M4 · Costing · Reconciliation · Period 07Period 06 closed
Cost against value · cut off 28 Feb 2026
Estimate class from the tender · Estimate at completion: three methods
Cost codeCost to dateValue to dateOver / (under)Carried
1100 Earthworks4,210,5004,480,000269,500from P06
1300 Piling2,975,0002,640,000(335,000)new
1500 Structural steel1,120,3001,180,00059,700from P06
P06Period 06 closed 31 January. Nothing in it changes.Cash flow curve updated
Exports to M8 as it stoodExample project
M5
Procure

Procurement

Buy against the bill, not beside it. M5 groups bill lines and WBS nodes into work packages, takes each to award and keeps every commitment and payment against it.

  • Work packages from bill lines and WBS nodes, and a register of suppliers and subcontractors
  • Requests for quotation issued from a package as house documents, with a record of issue
  • Quotations recorded as they arrive and levelled to one scope, gaps and plug figures shown as such
  • Award to a purchase order or subcontract, fixed at award, with the contract regime and retention
  • Change orders, each citing the variation in Progress and Commercial where one exists
  • Invoices and payments against each commitment, and the direct payment advice where the regime allows it
M5 · Procurement · Package P-014 Structural steel3 quotations
Levelled to one scope
Request for quotation issued 12 Feb 2026 · closed 26 Feb
SupplierQuotedLevelledGapsStatus
Fabricator A1,180,0001,215,0002 plugsLevelled
Fabricator B1,240,5001,240,500noneAwarded
Fabricator C1,095,0001,310,0004 plugsLevelled
PO-0231Awarded to Fabricator B. Fixed at award. Retention 10%.Regime from the contract form
Change orders cite M3 variationsExample project
M6
Assure

Safety, Quality and Environment

One register for safety, quality and environment. M6 keeps incidents, inspections, audits and nonconformances on the project record, each tagged to the clause it answers.

  • One register for incidents, hazards and environmental aspects, tagged by clause number across the three management system standards
  • Inspections, and audits with findings tagged to their clauses, and the indicators that follow from them
  • An inspection and test plan with hold, witness and review points
  • Nonconformance reports that cannot be altered from the moment they are raised, with corrective action and reinspection before close
  • The South African health and safety file, the mandatary agreement and the permit and notification gate
  • Nonconformance reports and findings into a Dispute Intelligence case
M6 · SHEQ · Register · Week 232 open
Nonconformances and findings
Clause tags across the three standards · Inspection and test plan: 14 points
RefTypeClauseRaisedStatus
NCR-012 Rebar cover, Area B slabNonconformance8.704 MarCorrective action due 11 Mar
INC-031 Hand injury, pilingIncident10.202 MarInvestigated
AUD-07-3 Calibration recordsAudit finding9.227 FebClosed · reinspected
NCR-012Fixed when raised. Closes only after reinspection.Hold point H-04 pending
Findings into M8 when neededExample project
M7
Hand over

Testing, Commissioning and Handover

Finish the way the contract says finished. M7 plans commissioning by stage, keeps the snags and the registers, and issues the handover with the dates that follow from it.

  • A commissioning plan by stage, with a seasonal and an aftercare phase
  • Witnessed tests run on the same engine as the inspection and test plan
  • Snags with status, owner and photographs
  • The operation and maintenance register and the as built register
  • The handover certificate
  • Completion and defects dates read from the contract form and fed to Dispute Intelligence
M7 · Commissioning · Stage 2 · Area B4 snags open
Witnessed tests · Stage 2
Handover certificate: not yet issued · Defects period read from the contract
TestWitnessDateResult
HVAC balancing, Level 2Engineer03 MarPassed
Fire alarm cause and effectEngineer, fire consultant05 MarPassed
Standby generator load testEngineer09 MarRetest
SN-118Snag: generator exhaust bracket. Owner: electrical subcontractor. Photo attached.Aftercare phase follows
Defects dates to M8Example project
M8
Resolve

Dispute Intelligence

Prove it. M8 runs forensic delay analysis on the record CIP has kept, and every result traces back to the entries behind it.

  • Delay analysis aligned with the SCL Delay and Disruption Protocol
  • As at reconstruction of the record for any date in the project
  • A chain of custody certificate with every export
  • Matter walls, conflict attestation and privilege barriers for law firms
  • Licensable on its own for legal teams and independent experts
M8 · Dispute Intelligence · Windows analysisMatter walled
Employer delay31 d
Concurrent7 d
Contractor delay10 d
WindowPeriodCritical delay by causeEmpConcCon
W1Jan to Feb
003
W2Mar
1400
W3Apr
642
W4May
005
W5Jun to Jul
1130
W6Aug
000
Certificate CIP-CoC-2026-0418 · SHA-256 9f3a…c21e
As at 31 Aug 2026 17:00 · 214 source entries · export sealed
EmployerConcurrentContractorExample matter
M9
Relief

Relief Determination

Determine relief the way the contract says, and show the working. M9 takes a relief event from the occurrence report to a determination, each stage dated and each document filed against it.

  • A matter for each relief event, with the people acting in it as its members
  • Occurrence report, requests for supplementary information, submissions and further submissions, each against its time limit
  • Points and checks recorded against the submissions before the finding is made
  • An impact determination, previewed before anything is issued
  • Determinations issued as Word documents, superseded only by a later one that says why
  • Referral and deemed acceptance steps when the parties do not agree
  • Every step traceable: the matter's record verifies end to end
M9 · Relief Determination · Matter RD-003Verified
Delayed access to Area B · Relief event
Opened 09 Mar 2026 · Determination issued 09 Apr 2026
StageDateLimitStatus
Occurrence report09 MarReceived
Supplementary information12 Mar7 dReceived 16 Mar
Submission23 Mar14 dReceived
Finding02 AprMade
Determination09 Apr28 dIssued · sealed
Export RD-003-D1.docx · SHA-256 4c1e…b9076 documents filed
Supersede only with a reasonExample project
M10
Claim

Claims Intelligence

Know what the contract expects of you this week. M10 keeps the events, the clocks they start and the claims register, on the record M3 has been keeping.

  • Events logged with the date you became aware, the clause they fall under and the day their effects ended
  • Notice and claim clocks run from the contract's own time limits, tracked to the day, late flagged
  • Notices and claim submissions drafted, approved and issued from the event, every send recorded
  • A time impact analysis and a windows run against the programme series for any event
  • A weekly report, reminders and a radar of what is due across the project
  • Evidence bundles sealed with a verification hash and handed to Dispute Intelligence as they are
  • A portfolio view across the organisation's projects
M10 · Claims Intelligence · Clocks3 running
Clocks · week of 09 Mar 2026
Contract: FIDIC 2017 Yellow · Calendar: contract days
EventClauseNotice dueDaysStatus
EV-021 Access to Area B not given20.2.119 Mar 20266Running
EV-019 Rock encountered, zone 34.1211 Mar 20260Due today
EV-017 Instruction to vary, line S213.3.128 Feb 2026Issued 26 Feb
EV-019Notice drafted from the event. Awaiting approval. Clock started 11 Feb · awareness recorded
Bundle to M8 when neededExample project
Contract forms

Built around the contracts you sign

  • FIDIC 1999 and 2017
  • NEC3 and NEC4
  • GCC 2015
  • JBCC PBA
  • Amended and bespoke forms
Security and data

Your data, where you need it.

Project records are commercially sensitive and often privileged. CIP was designed around that from the first line of code.

Data residency

Each organisation has an explicit data region, and any cross border transfer is recorded with its legal basis.

POPIA and GDPR

Designed to meet both, with a data protection impact assessment behind the platform.

Organisation isolation

Row level security separates every organisation's data inside the database itself.

Audit and retention

Audit records that cannot be altered and a seven year retention clock on project data.

Matter walls

Inside an organisation, access to a dispute matter is granted person by person and attested for conflicts.

See CIP on your own programme.

Bring a Primavera P6 file from a live or finished project. We will take it through the programme checks and the delay analysis with you, in under an hour.