Run your first audit
Point DataBridge at a source system and surface every data-quality issue against cited rules.
By the end you’ll be able to
- Understand what an audit pack is and what a Quality Rule checks.
- Run an audit over the demo institution and read the findings.
- Recognise how every finding is tied to a cited, published source.
An audit runs a set of Quality Rules over your source data and reports every place the data breaks a rule. DataBridge ships audit packs across the F1–F15 families (see docs/AUDIT_RULE_COVERAGE.md for the live count and breakdown) — HESA Data Futures, source-native conformance (SITS, Banner, Workday…), GDPR/PII, and the AU TCSI packs.
Each rule is cited: it names the published source it enforces (a HESA coding-manual field, an OfS regulatory threshold, a TCSI data-element rule) — or it carries an explicit `[UNVERIFIED:]` marker. That citation is what lets you defend a finding to a registrar or an auditor.
Every finding is appended to a tamper-evident audit log (a SHA-256 hash chain), so the data-quality story is provable end-to-end — not just asserted. You'll meet that audit log in the 'Prove it' lesson.
In this lesson you'll run an audit over the seeded demo institution and read the results. Nothing you do here changes real data — demo mode simulates writes.
Walkthrough
- Open Audits
1.Open the Audit Engine
Go to the Audits screen. This is where you launch audits and review findings for the demo institution.
- Review findings
2.Read a finding
Open any audit and expand a finding. Note the rule id, the severity, and the cited source — that citation is the rule's published basis.
- Open reference
3.See the coverage
Browse the codesets/rules reference to see how many rules ship and which families they belong to.
Your turn
Open the Audit Engine and review at least one finding for the demo institution.
Hint: Use the 'Open Audits' step above — it takes you straight there.