Get started

TraceUnified is one connected system for the regulated engineering lifecycle. Requirements, architecture, tests, risk, and SBOM live as native records in a single database, joined by governed traceability and an audit trail that is a by-product of the work — not a scramble before a submission.

This section gets you from first sign-in to a working project. You’ll learn how the workspace is organized, what an item is and how the thread connects everything, and how to stand up your first project.

What makes TraceUnified different

Most regulated teams run a stack: one tool for requirements, another for tests, a modeling tool for architecture, a spreadsheet for risk, and a separate system for the audit trail. The seams between those tools are where evidence drifts and where audit preparation becomes a scramble. TraceUnified is built the opposite way — requirements, architecture, tests, risk, and SBOM are native records in a single database, joined by governed traceability. The audit trail isn’t a report you assemble; it’s a by-product of doing the work.

The two ideas that make everything else make sense

Two concepts carry the whole platform. An item is any controlled record — a requirement, a test case, a risk, a model element — with its own identity, lifecycle, and history. The thread is the web of deterministic links between items: the connections that let a test verify a requirement, a risk reference the requirement it threatens, and a change flag everything downstream as suspect. Once those two ideas click, the rest of the product — modules, states, coverage, impact — follows naturally.

From sign-in to your first project

This section takes you from first sign-in to a working project. You’ll get oriented in the workspace — how modules, tabs, the project selector, and search fit together — learn the core concepts above in a little more depth, and then stand up your first project with its first real records. From there, the day-to-day actions in Working with items carry across every module, so what you learn once you use everywhere.

What’s in this section

• Welcome to TraceUnified — what the platform is and who it’s for
• Signing in — reaching your workspace and your account
• The workspace — modules, tabs, the project selector, and search
• Core concepts — items, the thread, lifecycle states, and projects
• Your first project — creating a project and adding your first records

Common tasks

Once you’re set up, Working with items collects the day-to-day actions you’ll use in every module — creating and reusing items, organizing the tree, editing under change control, linking, attaching files, and exporting. Learn them once and they carry across Requirements, Architecture, Tests, Risks, and SBOM.