BranchCheck
Shipped

Audit, on a proof chain

Audit missions run on the same engine — a plan based on risks and history, typed findings with the auditee's response, recommendations tracked until their closure is independently validated. This domain runs end to end today.

In the free trial, this domain's screens start empty: the shared demo pre-fills inspections only.

The business problem

An audit mission produces findings that must stay proven from the field note to the final report: today's observation, the recommendation due next week, the independent closure six months out. Rebuilding the chain for every request for explanation costs more than the mission itself.

What runs today

Shipped and executable end to end on the common engine in v1.5 — every brick below exists in the product, not on a roadmap.

Risk-based plan

The audit plan builds on risks and on mission history.

Equipped missions

Scope, independent team, schedule, work programme — interviews and tests.

Typed findings

Five kinds of findings, with the auditee's formal response.

Sealed report

The audit report is sealed, with its chain of evidence.

Independent closure

Recommendations are tracked until their closure is independently validated.

The requirements specification, requirement by requirement

The specification's requirements for this domain — and, facing each, its real status in the product.

CodeRequirementPriorityStatus
AUD-01Build an audit plan based on risks and history.P2 Covered
AUD-02Manage mission, scope, team, calendar and work program.P2 Covered
AUD-03Document interviews, tests, findings, recommendations and responses.P2 Covered
AUD-04Distinguish observation, recommendation, non-conformity, incident and critical finding.P2 Covered
AUD-05Generate an audit report with a proof chain and validations.P2 Covered
AUD-06Track recommendations to a validation independent of closure.P2 Covered

Codes and priorities: functional and technical requirements specification, §4.3 and §7.