“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
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.
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: CO-004 was approved on March 12 by the role assigned to final approval in routing version 3.
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.
Not established. The record contains discussion, but no executed waiver by an authorized person. TRACE will not infer waiver from silence or informal correspondence.
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.
Create an account, sign in, or accept an invitation.
Select delivery method and jurisdiction, then create the project with explicit working-day or calendar-day basis.
Configure organizations, team, authority, templates, and executable routing.
Run schedule, field, technical, commercial, quality, and compliance workflows.
Complete handover, obtain accountable closure, archive, and export evidence.
The thirteen areas below share the same customer, project, authority, routing, evidence, and audit boundaries. They are not disconnected feature tiles.
Design-Bid-Build, Traditional or Progressive Design-Build profiles; jurisdiction; duration basis; teams; permissions; templates; routing; and separately verified construction-release evidence gates.
Baseline and update versions, CPM analysis, constraints, look-aheads, quantities, progress, and cited contract clocks.
Versioned sheets, specifications, markups, model links, viewpoints, issues, and locations connected to accountable workflows.
Daily reports, timecards, crews, equipment, production, weather, photos, observations, receipts, and T&M records.
Registers, packages, review steps, ball-in-court, responses, transmittals, distribution, and complete decision history.
Potential changes, directives, notices, pricing, time impact, approval, incorporation, billing, and claim chronology.
Budget, commitments, approved SOV, pay applications, stored materials, retention, releases, forecast, and accounting exchange.
Certified payroll review, DIR/DAS, apprenticeship, PLA/CWA, classifications, exceptions, and linked evidence.
Jurisdiction-aware permit and agency-approval screening, ITPs, inspections, observations, deficiencies, NCRs, punch, job walks, safety, corrective action, closure, and reopening.
Agendas, attendance, minutes, action items, due dates, distribution, notifications, reminders, and escalations.
Controlled files, versions, O&M manuals, warranties, as-builts, training, closeout register, archive, and portable export.
Project position from accepted-schedule progress, billing position, missing work, cited answers, explicit refusals, reviewed knowledge, OCR provenance, hashes, custody, search, and evidence export.
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.
TRACE Management System records provider, project, mapping, authorization, dry-run, idempotency key, exchange result, reconciliation, and retry history. A logo never means Connected.
Link model elements, viewpoints, issues, documents, and project evidence through provider-backed Autodesk Platform Services and open exchange formats.
Ingest and export governed XER/XML schedule versions, preserve source hashes, compare updates, and connect contemporaneous evidence to delay analysis.
Map systems of record, validate in a sandbox, dry-run changes, post idempotently, reconcile variances, and require human approval for financial actions.
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.
Complete browser access on current desktop and tablet browsers, with account control, project operations, administration, TRACE, and hosted checkout.
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.
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.
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.
TRACE Management System exposes the boundaries a reviewer needs to evaluate: identity, isolation, authority, retention, evidence, portability, AI scope, integrations, operations, and incident handling.
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.
Procore offers broad construction execution and a large data ecosystem. Validate fit, evidence portability, and public-owner controls for your program.
Autodesk leads deep BIM/model workflows. TRACE Management System connects through APS and IFC/BCF instead of imitating the geometry engine.
Oracle Primavera brings mature CPM depth; Aconex brings multi-organization collaboration. TRACE Management System preserves interchange and forensic project evidence.
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.
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.
Current web workspace. Customer and project records shown in demonstrations must be synthetic or expressly authorized.
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.
A seeded public-works project with guided access to core workflows. Demo records cannot be represented as production evidence.
Field and project administration for contractors, with scope confirmed before payment or activation.
A controlled pilot for public owners and program teams, including security, retention, integration, and authority review.
A real limited account—daily reports, RFIs, submittals, photos, and evidence—clearly marked and automatically expiring after 14 days.
Walk through authority, routing, contract clocks, changes, pay applications, labor, evidence, TRACE, integrations, and export with your stakeholders.