UnifyOS roadmap

Every module, its stage, and what it takes to get there.

UnifyReview, UnifyRetail OS, UnifyProjectVision and IntelliBridge are running today. Four further modules extend the same governed intelligence across leasing, handover, operations and portfolio decisions.

Horizons show sequence and dependency, not calendar dates. Nothing is described as available until it is running for a client.

These modules are roadmap positions within UnifyOS. They are in design or scoping, are not available today, and no delivery dates are committed. They are published so clients can see the direction of the platform and shape it — not to imply released functionality.

How to read this

Four stages, three horizons.

Stage describes how far a module has been built. Horizon describes when it comes in the sequence.

Available

Released and in use. Governed rule packs, evidence-linked findings and audit trail are live.

Extending

Available, with additional capability being built out against live client requirements.

In design

Scope, data model and review logic being defined with landlord, developer and delivery input.

In scoping

Problem validated, direction published, requirements still being gathered before design starts.

Now

Live modules clients can run today, on the current platform.

Next

The modules closest behind: design underway, dependencies largely in place.

Later

Direction set and published, dependent on earlier modules landing first.

Horizon · Now

Live modules clients can run today, on the current platform.

Design and compliance review is live: governed rule packs, evidence-linked findings, severity scoring, revision comparison and audit trail.

Already in place

  • Rule library and version-controlled rule packs
  • Document and drawing intelligence
  • Finding severity and corrective-action logic
  • Human validation and approval controls
  • Portfolio compliance analytics

Needed to reach the next stage

  • Client design criteria loaded and version-controlled as rule packs
  • Broader discipline coverage extended asset by asset
  • Reference reviews from live submissions to tune severity thresholds

Depends on: UnifyOS core · IntelliBridge for connected deployments

The lease-to-operating unit record and portfolio intelligence are live, with UnifyReview performing compliance review inside it.

Already in place

  • Unit record from commercial terms to trading
  • Obligation register and works-split mapping
  • Approval and condition tracking across revisions
  • Opening-readiness evidence and portfolio views

Needed to reach the next stage

  • Leasing data feed to remove manual obligation entry
  • Handover evidence structure for readiness sign-off
  • Benchmark data across more assets to sharpen cycle-time comparison

Depends on: UnifyReview · UnifyOS Leasing (planned) · UnifyOS Handover (planned)

Programme and project intelligence is live: delay, sequencing, procurement and cost-risk analysis with forecast financial impact for project boards.

Already in place

  • Programme and controls data ingestion
  • Early-warning risk pattern detection
  • Financial-impact forecasting, labelled as forecast
  • Board and PMO reporting cadence

Needed to reach the next stage

  • Consistent programme and cost baselines from the client side
  • Historic project data to strengthen forecast confidence
  • Handover data to close the loop at completion

Depends on: UnifyOS core · IntelliBridge for programme and ERP feeds

The integration layer is live: authentication, field mapping, signed webhooks, event delivery, retries and integration traceability.

Already in place

  • Secure REST API and signed webhooks
  • Sandbox and production environments
  • Idempotency, retry and failed-event handling
  • Generic connector pattern

Needed to reach the next stage

  • Named connectors hardened per client instance
  • Client-side API access and a nominated integration owner
  • Field mapping agreed against the client project and asset model

Depends on: Client system API access

Horizon · Next

The modules closest behind: design underway, dependencies largely in place.

Turns agreed lease terms into structured obligations that downstream modules can enforce.

Already in place

  • Problem validated with landlord and developer input
  • Obligation model drafted against UnifyRetail OS unit records

Needed to reach the next stage

  • Representative lease and heads-of-terms sets to train extraction
  • Agreed obligation taxonomy across landlord clients
  • Access to a leasing or property-management platform for the data feed
  • A client partner willing to run the first structured lease intake

Depends on: UnifyRetail OS · UnifyReview · IntelliBridge

Measures completion readiness against verified evidence rather than reported percentages.

Already in place

  • Completion evidence model drafted from live retail and mixed-use handovers
  • Readiness scoring approach defined against UnifyRetail OS records

Needed to reach the next stage

  • Statutory certificate and testing-record templates per jurisdiction
  • Agreed definition of verified rectification with client delivery teams
  • O&M and as-built handover requirements structured per asset type
  • A live handover programme to validate against

Depends on: UnifyRetail OS · UnifyProjectVision

Horizon · Later

Direction set and published, dependent on earlier modules landing first.

Operates the asset from the record the project produced, instead of a fresh survey after occupation.

Already in place

  • Direction published and validated with operators
  • Dependency on structured handover evidence identified

Needed to reach the next stage

  • Handover module delivering verified asset and system records
  • CAFM and BMS integration patterns defined
  • Operating requirement libraries per asset class
  • Operator partner to shape maintenance and compliance cycles

Depends on: UnifyOS Handover · IntelliBridge

Portfolio and investment decisions grounded in delivery and operating evidence rather than periodic reporting.

Already in place

  • Direction published
  • Portfolio analytics foundations already running inside existing modules

Needed to reach the next stage

  • Sustained delivery and operating data across multiple assets
  • Handover and facilities modules producing comparable records
  • Agreed portfolio benchmarking measures with owners
  • Investment reporting requirements defined with asset managers

Depends on: UnifyOS Handover · UnifyOS Facilities Management · UnifyRetail OS · UnifyProjectVision

Planned modules

In design and scoping.

Published so clients can shape them before they are built.

Leasing intelligence

UnifyOS Leasing

Carry leasing obligations into delivery instead of losing them in the deal.

Leasing decides what the delivery team is later held to: fit-out obligations, landlord works, rent-commencement triggers, brand and design conditions. Today that intent lives in lease documents and negotiation email, and reaches delivery as an incomplete summary.

In design — shaped with landlord and developer input

Handover & completion intelligence

UnifyOS Handover

Close projects on evidence, not on assurances.

Handover is where delivery risk concentrates: snag lists, statutory certificates, testing and commissioning records, warranties, O&M documentation and as-built information all land at once, usually against a fixed opening or occupation date.

In design — informed by live retail and mixed-use handovers

Operating & maintenance intelligence

UnifyOS Facilities Management

Operate the asset from the record the project actually produced.

Most operating teams inherit an asset they cannot see clearly: incomplete asset registers, warranties nobody can find, maintenance regimes built from guesswork, and no link back to how the building was designed or delivered.

Planned — scoped after handover

Portfolio & lifecycle intelligence

UnifyOS Asset Intelligence

Judge portfolio decisions on delivery and operating evidence.

Owners and investment committees make lifecycle, capital and reinvestment decisions on financial models that rarely reflect how each asset was designed, delivered, handed over and operated.

Planned — the portfolio layer above the delivery modules

How we sequence

The rules we hold ourselves to.

  • Nothing is published as available until it is running for a client.
  • Sequencing is driven by dependencies, not by marketing convenience.
  • No delivery dates are committed — horizons show order, not calendar.
  • Client requirements shape scope before design closes.
  • Every module inherits the same evidence, audit and human-validation standard.

Shape a module before it is built.

If one of these solves a problem you are living with, we want your requirements in the design.