Connected execution systemRun the work.
Run the work.
Keep the proof.
Root connects systems, people, plans, controlled decisions and delivery evidence—so teams can move work forward without losing the thread.
01 Configurable by customer02 Permission-aware03 Audit-trailed
Execution overviewCapital Programme · Project North
ALGOOD MORNING, ALEXAssigned185 due this week Awaiting decision72 require signature At risk4Open constraints My WorkView all 6-week pulse84%
What needs attention
Approve permit PTW-1042Safety · Utilities
Review turnover dossierVendor · SYS-014
Accept Tier 2 hand-offTier Boards · Delivery
W32 — W37
One execution thread
The record stays connected as the work moves.
Root is organised into modules, but the operating model is joined by systems, people, assignments, decisions, evidence and a shared audit trail.
01
Define the system
Create the approved asset and information structure the project can use.
02
Plan and assign
Sequence work, make ownership explicit and account for availability.
03
Review and decide
Collaborate where comments belong, then capture controlled approvals.
04
Deliver and evidence
Connect submissions, construction, safety, change and completion proof.
Designed around the workSixteen modules.
Sixteen modules.
One operating layer.
Enable what each customer needs and keep the links between them.
01
Explore every moduleMy Work
One place to see what needs your attention.
02Systems
The asset register everything else can trust.
03Documentation & Drawings
Collaborate in review. Decide with control.
04Tier Boards
Escalation with acceptance, ownership and a shared answer.
05Pull Plans
Make the sequence visible before the constraint becomes a delay.
06Meetings
Turn discussion into owned, visible follow-through.
07Vendor
A clear route from supplier submission to accepted deliverable.
08Construction
Configure the stage. Prove the work. Sign the handover.
Control without friction
Designed for work that must be trusted later.
Password-backed signatures remain bound to the record, revision, stage, meaning and signer.
Users, records, files, projects and configuration stay within the authorised deployment context.
Roles, terminology, catalogues, stages, workflows and environments can reflect the customer's operation.
Audit trails, historical revisions, source links and exports preserve the route from action to proof.