How does version control work in Ausmed Competency™?

When you edit a competency, Ausmed Competency™ uses version numbers to keep assessments accurate and auditable — without disrupting work already underway.

In-progress assessments aren't affected

Editing a competency — whether Trivial, Minor, or Major — never disrupts an assessment that's already underway:

• Active sessions: if an assessor has already started an assessment on their device, they finish and submit it using the version they started with (e.g. v1.0.0). They're not forced to restart.
• Saved attempts: assessments saved before the update stay locked to the version they were started on. The assessor can resume and submit without interruption.
• New assessments: anything started after you publish the update automatically uses the latest version.

Why this matters for clinical governance

Version control is a safety and accountability mechanism, not just document management. It ensures every assessment is evidence-based, every record is defensible, and every change is transparent.

• Chain of evidence: historical records are never overwritten. If an audit happens years later, the system retrieves the exact criteria (e.g. v1.1.2) used on the day of the assessment — an indisputable snapshot of competence at that point in time.
• Current standards: once a newer version is live (e.g. v2.0.0), staff can't be assessed against an outdated one — you can't start a new assessment using a prior version (e.g. v1.0.0).
• Accountability: categorising updates (Trivial, Minor, Major) and adding notes builds a clear record of how your competencies have evolved, helping auditors understand when and why a standard changed.