The evidence-governed operating system for public works

Run every workflow.
Defend every decision.

TRACE Management System connects field capture, drawings, contract clocks, routing, changes, payment, labor compliance, permits, and closeout in one provable record. Ask where the project stands: TRACE answers from authorized evidence with citations—or refuses to guess.

Built for public owners, construction managers, contractors, inspectors, designers, and trade partners. Human authority remains required for approval, certification, submission, and payment release.

Field → proofphotos, observations, time, location, and custody
Plan → paymentone governed chain across the whole project
Cited or refusedTRACE never substitutes a nearby answer
DEMONSTRATION PROJECT — SYNTHETIC DATA
SHA-256 · 8f2c…41a0e9 — a correction creates a new event. The original state remains independently traceable.
Web workspace available Desktop clients in implementation Native mobile follows web completion Payments remain on secure hosted web checkout
TRACE proof

A useful answer shows its basis. An unsupported answer stops.

TRACE separates product help, public-reference research, and one authorized project's evidence. It can explain schedule progress, budget position, open work, permit actions, and missing release evidence fairly from the record. It never expands access or converts an AI suggestion into a human approval.

Supported answer · synthetic example

“Was Change Order 4 authorized?”

Supported: CO-004 was approved on March 12 by the role assigned to final approval in routing version 3.

  • CO-004 · signed record · page 2
  • Routing v3 · approval node 5
  • Evidence event · 2026-03-12T16:41Z
Basis: active project only · authorized records · cited passages
Project position · synthetic example

“TRACE, where are we?”

Recorded position: 62.4% duration-weighted progress on the accepted schedule; 59.8% billed; 3 RFIs, 2 submittals, 1 permit action, and 2 construction-release evidence gates remain open.

  • Accepted schedule · current data date
  • Certified billing record · current period
  • Project registers · neutral counts
Boundary: reports what is recorded · assigns no blame, entitlement, acceptance, or permission to build
Evidence refusal · synthetic example

“Did the City waive the notice deadline?”

Not established. The record contains discussion, but no executed waiver by an authorized person. TRACE will not infer waiver from silence or informal correspondence.

  • Missing: executed waiver or cited controlling determination
  • Next step: route the issue to the authorized contract administrator
Safety: no fabricated citation · no hidden cross-project retrieval
Zero-to-100 operating path

Run the project. Preserve the proof.

Every capability opens a working flow. When project facts, accountable people, authority, a template, or provider credentials are required, TRACE Management System routes the user into setup and keeps the state honest until validation is complete.

1

Enter

Create an account, sign in, or accept an invitation.

2

Establish

Select delivery method and jurisdiction, then create the project with explicit working-day or calendar-day basis.

3

Govern

Configure organizations, team, authority, templates, and executable routing.

4

Operate

Run schedule, field, technical, commercial, quality, and compliance workflows.

5

Close

Complete handover, obtain accountable closure, archive, and export evidence.

Complete capability map

One system for the work—and the record of the work.

The thirteen areas below share the same customer, project, authority, routing, evidence, and audit boundaries. They are not disconnected feature tiles.

01
Start & govern

Project setup, people, and authority

Design-Bid-Build, Traditional or Progressive Design-Build profiles; jurisdiction; duration basis; teams; permissions; templates; routing; and separately verified construction-release evidence gates.

Control: delivery method and design percentage never imply permission to build.
02
Plan & control

Schedules, look-aheads, and production

Baseline and update versions, CPM analysis, constraints, look-aheads, quantities, progress, and cited contract clocks.

Boundary: P6 interchange and forensic evidence—not a replacement for Primavera's solver.
03
Coordinate design

BIM, drawings, and specifications

Versioned sheets, specifications, markups, model links, viewpoints, issues, and locations connected to accountable workflows.

Boundary: Autodesk APS and IFC/BCF integration—not CAD authoring or a proprietary geometry engine.
04
Run the field

Daily operations and workforce

Daily reports, timecards, crews, equipment, production, weather, photos, observations, receipts, and T&M records.

Evidence: sealed field facts remain attributable to author, device, project, and time.
05
Ask & deliver

RFIs, submittals, and decisions

Registers, packages, review steps, ball-in-court, responses, transmittals, distribution, and complete decision history.

Truthful state: Submitted and Approved require the supporting action.
06
Protect scope & time

Changes, notices, T&M, and claims

Potential changes, directives, notices, pricing, time impact, approval, incorporation, billing, and claim chronology.

Separation: change approval and contract incorporation remain distinct acts.
07
Control the money

Budget, commitments, and pay applications

Budget, commitments, approved SOV, pay applications, stored materials, retention, releases, forecast, and accounting exchange.

Human gate: certification, posting, and payment release remain accountable actions.
08
Verify compliance

Labor and public-works requirements

Certified payroll review, DIR/DAS, apprenticeship, PLA/CWA, classifications, exceptions, and linked evidence.

Human review: supported findings assist; authorized people resolve conclusions.
09
Assure the work

Quality, safety, and inspections

Jurisdiction-aware permit and agency-approval screening, ITPs, inspections, observations, deficiencies, NCRs, punch, job walks, safety, corrective action, closure, and reopening.

Evidence: permit applicability needs a recorded basis; issued status needs authority proof.
10
Coordinate people

Meetings, actions, and communication

Agendas, attendance, minutes, action items, due dates, distribution, notifications, reminders, and escalations.

Execution: decisions become routed work, not buried notes.
11
Preserve & close

Documents, handover, and closeout

Controlled files, versions, O&M manuals, warranties, as-builts, training, closeout register, archive, and portable export.

Lifecycle: closed projects leave Active Projects but remain authorized and retrievable.
12
Explain with evidence

TRACE, audit, and evidence ledger

Project position from accepted-schedule progress, billing position, missing work, cited answers, explicit refusals, reviewed knowledge, OCR provenance, hashes, custody, search, and evidence export.

Rule: no retrievable support means no claim of knowledge—and a count never becomes blame.
13
Get accountable help

In-app support and safe diagnostics

Open a request from the screen where work stopped, include consent-based redacted diagnostics, keep an append-only conversation, and escalate from guided help to support staff or a System Full Admin.

Truthful state: intake and human escalation are active; 24/7 automated guidance is planned, and automatic repairs remain disabled until individually allowlisted and audited.
Interoperate with the systems cities already trust

Integrate specialist engines. Govern what crosses the boundary.

TRACE Management System records provider, project, mapping, authorization, dry-run, idempotency key, exchange result, reconciliation, and retry history. A logo never means Connected.

Models & coordination

Autodesk APS + IFC/BCF

Link model elements, viewpoints, issues, documents, and project evidence through provider-backed Autodesk Platform Services and open exchange formats.

Scope: TRACE Management System does not recreate Autodesk geometry, authoring, clash, or reality-capture engines.
Schedule intelligence

Primavera P6 interchange

Ingest and export governed XER/XML schedule versions, preserve source hashes, compare updates, and connect contemporaneous evidence to delay analysis.

Scope: TRACE Management System does not recreate Oracle Primavera's mature CPM authoring engine.
Financial & enterprise exchange

ERP, accounting, APIs, and webhooks

Map systems of record, validate in a sandbox, dry-run changes, post idempotently, reconcile variances, and require human approval for financial actions.

State: Listed → Configured → Authorized → Validated → Connected.
One account across platforms

The web is authoritative. Signed clients make field access easier.

Customers register, manage licenses, and complete payment on the secure website. Every client uses the same server-derived tenant, project, role, and capability grants; a local device can never promote itself.

Available now

Web workspace

Complete browser access on current desktop and tablet browsers, with account control, project operations, administration, TRACE, and hosted checkout.

Implementation track

Windows & macOS

Signed desktop clients will open the same workspace, authenticate through the web identity service, use encrypted local storage, sync through versioned APIs, and direct all licensing and payment back to the website.

Sequenced after web completion

iOS & Android

Native field capture will prioritize offline drafts, photos, receipts, OCR, device provenance, conflict review, resumable media, and encrypted sync. Approval, certification, and payment stay server-authoritative.

Hardware integrations in validation

Connected Field Capture

A governed capture envelope is being designed for hands-free photo and voice workflows, plus survey-instrument evidence. Named Meta, Android XR, and Trimble adapters will be announced only after real device, offline, isolation, coordinate-integrity, and human-approval tests pass.

Desktop and native mobile availability will be announced only after signed builds, store/notarization checks, offline conflict tests, security review, and production synchronization evidence pass. No download is represented as available on this page today.

City IT & procurement path

Security claims should be inspectable, not decorative.

TRACE Management System exposes the boundaries a reviewer needs to evaluate: identity, isolation, authority, retention, evidence, portability, AI scope, integrations, operations, and incident handling.

Operating controls

  • Tenant and project isolationScope is derived and checked on the server for routes, APIs, search, files, TRACE, and exports.
  • Human authorityAI and routing can prepare or recommend; accountable people approve, certify, submit, close, and release payment.
  • Evidence historyAppend-only events, sealed states, hashes, versions, provenance, and authorized export support later examination.
  • Safe filesQuarantine, allowlists, non-executable private storage, review gates, OCR provenance, and resumable large-file paths.
  • Infrastructure pathPostgreSQL portability, concurrency controls, health checks, backups, restore rehearsal, and observable queues are launch requirements.
Deliberate product boundaries

Depth where TRACE Management System is accountable. Interoperability where specialists lead.

Established platforms have real strengths. TRACE Management System's focus is governed public-works execution: authority, contract clocks, evidence, compliance, portability, and TRACE answers that remain attributable.

General-purpose CM platforms

Procore offers broad construction execution and a large data ecosystem. Validate fit, evidence portability, and public-owner controls for your program.

Design & model platforms

Autodesk leads deep BIM/model workflows. TRACE Management System connects through APS and IFC/BCF instead of imitating the geometry engine.

Schedule & collaboration platforms

Oracle Primavera brings mature CPM depth; Aconex brings multi-organization collaboration. TRACE Management System preserves interchange and forensic project evidence.

Owner program platforms

Kahua emphasizes configurable capital-program delivery. TRACE Management System differentiates through public-works governance and cited-or-refused TRACE behavior.

Sources and evaluation starting points: Procore products, Autodesk Construction workflows, Oracle Aconex, and Kahua platform. Product packages change; verify every material requirement in a controlled pilot.

Working product

A normal control center for the account—and a governed workspace for each project.

Account administrators manage customers, users, licenses, active projects, archived projects, integrations, and portfolio views. Opening a project changes the scope to that project's operations and settings.

app.tracems.com
TRACE Management System project dashboard showing action items, contract clocks, and project notices

Current web workspace. Customer and project records shown in demonstrations must be synthetic or expressly authorized.

Start with proof

Evaluate the working system before procurement.

Use a clearly identified demonstration workspace or request a structured City pilot. Provider connections, formal certifications, and production data are never implied by a demo.

Demonstration

Free

A seeded public-works project with guided access to core workflows. Demo records cannot be represented as production evidence.

Agency / program

Quoted

A controlled pilot for public owners and program teams, including security, retention, integration, and authority review.

See it live

Choose the safest way to evaluate TRACE Management System.

Instant demonstration

A real limited account—daily reports, RFIs, submittals, photos, and evidence—clearly marked and automatically expiring after 14 days.

Public-agency review

Walk through authority, routing, contract clocks, changes, pay applications, labor, evidence, TRACE, integrations, and export with your stakeholders.