Use casesApprovals and back office
Compliance and audit checklists
Run recurring checks, capture evidence, and show auditors exactly who did what.
- Scheduled
- In progress
- Submitted
- Reviewed
- ClosedDone
PassedWaits for a personEvery move is kept in the record's history
The problem
What goes wrong today
Today
Checklists are printed, filled in by hand and scanned, or kept in a spreadsheet that anyone can edit. When an auditor asks for last quarter’s evidence and the sign-off, somebody spends days putting it together.
How It Works
How this use case runs, step by step
Amber steps wait for a person's decision; everything else moves on its own.
- Inspections are createdOn the first of the month, a chain of fitness clubs gets its safety inspections created automatically, one per club.
- An inspector walks the siteAt one club, the inspector fills in the checklist. A failed answer on fire exits opens extra questions, and she adds a photo.
- The finding is raisedThe fire-exit finding is marked high severity. The quality team is notified at once and a corrective action is created for the club manager.
- Review and sign-off Site manager, then qualityThe club manager reviews the inspection. Because of the high-severity finding, the quality lead signs off too.
- Audit dayThe auditor asks for the quarter’s evidence. The findings report and each record’s history show who did what, and when.
Product Capabilities
What you configure in this app
Mostly configuration. Rules that configuration cannot express are written in C#.
Records 4
- Inspection5 fields + history, files, comments
- Checklist template4 fields + history, files, comments
- Finding5 fields + history, files, comments
- Corrective action4 fields + history, files, comments
Stages 5
- Scheduled
- In progress
- Submitted
- Reviewed
- Closed
Automatic 3
- ScheduleA scheduled workflow creates next month’s inspections from each template
- NotifyA high-severity finding notifies the quality team by email and in-app straight away
- WorkflowCorrective actions past their due date escalate to the site manager
Screens and reports 5
- Inspection form with layout rules that show follow-up questions only when an answer fails
- Kanban of corrective actions by status
- Pivot table of findings by site and severity
- Inspection report with findings and photos, as a PDF
- Quarterly findings summary in Excel for the audit committee, sent on a schedule
Who approves, in detail
A submitted inspection goes to the site manager named on the record (record field strategy). Inspections with a high-severity finding also need the quality role. Each decision and comment is stored on the record’s history.
When the rules change
See TechAppForce on your own use case
Bring your own version of “Compliance and audit checklists” and we will model its records, stages and approvals with you. A change a few months in is a reviewed release, not a rebuild.
Release: Checklist: site safety
Questions
Added: + First aid kit checked
Removed: - Visitor book signed
Frequency
Removed: - Quarterly
Added: + Monthly
- Developmentmake the change
- QAreview the diff, test it
- Productionpromote the release