Issue tracking

An audit issue tracking app is only as honest as its operating rules.

Software stores fields. Teams decide whether those fields mean anything. This page outlines the model we teach across Smartdevframework programmes.

Four stages, one record

We treat intake, remediation, evidence, and closure as chapters of the same finding — not separate inboxes. When status lives in email and proof lives in a drive, your tracker becomes theatre.

See courses Ask about a cohort
Dashboard charts on a computer screen

  • Intake

    Capture the control, observation, and risk once. Resist optional fields that nobody maintains. Require a human owner before the finding can save.

  • Remediation

    Plan work with dates the owner can defend. Escalate to people, not shared aliases. Record hand-offs when roles change.

  • Evidence

    Narrative first, artefacts second. Name files for strangers. Keep drafts out of the evidence shelf.

  • Closure

    Write acceptance criteria early. Verify with a different person. Stamp reporting exports so board packs cannot drift.

Ready to practise on your register?

Bring a redacted export to Finding to Closure or talk through your current audit issue tracking app setup with our team. We will tell you honestly if you need implementation help beyond training.

Flagship course Read the blog