Tracidor links business requirements, functional and configuration specs, integration and UAT tests, defects and change requests — so delivery evidence is never reconstructed from spreadsheets again.
A 30-minute walkthrough, a question on GxP scope, Jira integration, deployment or pricing — write to us directly and you will reach a practitioner, not a queue.
Each artefact carries its own code and status. Tracidor keeps the links live, so coverage gaps and unlinked defects surface the moment they appear — not the week before go-live.
GxP adds a dedicated Installation Qualification step and renames the testing tiers to their regulated equivalents — same live traceability engine underneath, so nothing is reconstructed by hand at audit time.
Every project picks a framework when it is created. The workspace then adapts its artefacts, states and terminology — same traceability engine, two levels of assurance.
Select a framework below to see its dashboard.For business and IT programmes that need clean traceability and a defensible sign-off — without qualification overhead.
For life-sciences and other regulated environments: qualification stages replace generic testing, and deviations are tracked as first-class records.
The standard framework keeps the familiar delivery vocabulary: BRD, FSD and CFG artefacts with approval states, SIT and UAT execution, defects raised automatically from failed tests, and a sign-off percentage that tells you exactly how close the release is.
Best for business and IT programmes that need audit-ready traceability without qualification protocols.
Explore a standard project ↗The dashboard swaps SIT and UAT counters for IQ / OQ / PQ, adds deviations as first-class records, and reports release readiness per requirement — so an inspector sees the full chain in one screen.
Best for life-sciences and other regulated environments where computerised system validation has to be evidenced.
Explore a GxP project ↗Coverage from requirement to result in a single grid — filter by system, owner or release.
Raise defects from a failed step; open, in-progress and resolved counts stay in sync with testing.
Plan a cycle, execute it, and close it with a recorded business approval per test.
Draft specs and UAT cases from a requirement, then review and approve them like any other artefact.
Proposed to implemented, with the requirements each change touches attached.
Who changed what, when — for auditors, regulators and the post-release review.
AI suggests action types and selectors from your UAT steps — reviewed and applied before anything runs unattended.
Formal sign-off captured with signer identity and timestamp — the audit trail GxP release evidence needs.
Map a Tracidor project to a Jira project, push defects and change requests, and pull status back — the traceability chain stays intact on both sides.
Configure in the app ↗Team access controls who can author, approve and sign off. Automation systems and environments are registered per project, and every action lands in the audit log.