Client journey

How UnifyOS enters a live project — and what changes.

UnifyOS does not arrive as a replacement platform. It attaches to the project you are already running, takes over the parts that depend on documents and evidence, and gives every decision a traceable record.

Below: what happens at each stage, what we need from you, and what you get back.

Who this is for

Three starting points, one operating record.

Where a client enters depends on what they are accountable for.

Developer

Delivering a new asset or a major expansion, accountable for an opening date and a capital budget, working through consultants and contractors.

Usually enters at design review and programme intelligence, before the first tenant package arrives.

Landlord / asset owner

Running trading assets with continuous tenant churn, fit-outs and reinstatements, accountable for compliance and rental performance.

Usually enters at tenant fit-out review, then extends across the portfolio.

Consultant / project manager

Acting for the client across multiple projects, accountable for advice, controls and reporting rather than for the asset.

Usually enters at programme intelligence and reporting, then adds compliance review per project.

The journey

Seven stages, from first conversation to portfolio.

01

Scoping the operating picture

We start from what already exists: which systems hold the documents, which standards apply, who signs what, and where the current delays actually occur. Nothing is migrated at this point.

What you do

  • Nominate the pilot asset, project or portfolio slice
  • Provide design criteria, tenant handbook and statutory references
  • Identify the decision-makers who validate findings

What you get back

  • Baseline of current cycle times and failure points
  • Map of standards to be enforced
  • Defined scope for the pilot
02

Connecting your existing systems

IntelliBridge connects UnifyOS to the platforms you already run, so your teams keep working where they work today. Submissions travel to UnifyOS and findings travel back with the record intact.

What you do

  • Nominate the source system and a technical contact
  • Approve the connector scope and event triggers
  • Confirm document access and retention rules

What you get back

  • Connector configured for RealCube, Aconex, Procore or a generic API
  • Webhook events verified end to end
  • Traceability from source document to returned finding
03

Structuring obligations and standards

Lease obligations, works splits, key dates and the applicable design criteria are turned into testable requirements bound to each unit or package — so review tests the right standard at the right revision.

What you do

  • Confirm landlord and tenant works splits
  • Confirm the governing revision of each standard
  • Agree the tenant-specific conditions that must be enforced

What you get back

  • Structured obligation register per unit or package
  • Version-controlled criteria set
  • Conditions carried into every later review
04

Running compliance review

Submissions are assessed against the bound standards. Every finding is linked to the drawing, clause or specification that raised it, and presented for a named person to accept, amend or reject.

What you do

  • Validate findings and issue the comment sheet
  • Record overrides with reasons
  • Own the approval decision

What you get back

  • Evidence-linked findings per submission
  • Revision-by-revision comparison of resubmissions
  • Complete audit trail of decisions and overrides
05

Watching programme and cost risk

Alongside compliance, the programme and controls data is analysed for emerging delay, sequencing, procurement and approval risk, with forecast financial exposure attached and assumptions recorded.

What you do

  • Provide baseline and current programmes
  • Validate the forecast assumptions
  • Select the mitigation to pursue

What you get back

  • Prioritised early-warning register
  • Critical-path movement and milestone confidence
  • Forecast exposure, separated from confirmed cost
06

Handover and opening on evidence

Inspections, snags, testing records and readiness criteria accumulate on the same record, so opening or handover is signed off on documented evidence and the pack is assembled rather than reconstructed.

What you do

  • Sign off readiness with recorded accountability
  • Close outstanding conditions
  • Accept the handover evidence pack

What you get back

  • Opening-readiness assessment
  • Outstanding conditions register
  • Complete handover evidence pack
07

Scaling to the portfolio

Once one asset or project runs on the record, the same structure repeats. Unit and project records roll up into portfolio intelligence: where risk concentrates, which standards keep failing, which parties perform.

What you do

  • Extend to further assets or projects
  • Use recurring findings to correct your own standards
  • Set the governance reporting cadence

What you get back

  • Portfolio stage and risk dashboards
  • Cross-asset delivery benchmarking
  • Recurring non-compliance analysis

Indicative shape

What a first engagement typically looks like.

Indicative only — the sequence is fixed, the pace depends on your asset, systems and approval cycles.

  1. Weeks 1–2

    Scoping, baseline and standards captured. Pilot scope agreed with named decision-makers.

  2. Weeks 3–6

    Connector configured through IntelliBridge, obligations and criteria structured, first submissions reviewed in parallel with your existing process.

  3. Weeks 7–12

    Review becomes the working process for the pilot, programme early warnings running, reporting cadence established.

  4. Beyond

    Rollout to further assets or projects, portfolio intelligence in use, roadmap modules shaped around what the pilot exposed.

How we work

What holds true at every stage.

  • Your teams keep working in the systems they already use.
  • Every finding is traceable to a source document.
  • A named person validates every decision — nothing is approved autonomously.
  • Financial outputs are forecasts and decision support, not certified determinations.
  • Your standards and documents remain yours, with access and retention under your control.

Walk the journey against your own project.

Bring one asset, one programme or one tenant package and we will show you exactly where UnifyOS attaches.