The audit record
One audit: its team, surveys, data sample, interviews, findings and report.
The header gives the audit's name and status, its reference, Customer and coverage. All audits goes back to the Audits register.
The life of an audit
Draft (scope, dates and survey being prepared) → Active (survey out, data audit and interviews under way) → Reporting (the report being written) → Closed (the audit locked). The buttons at the top move it on:
- From Draft: Start audit or Close audit. A Draft audit sends no survey.
- From Active: Move to reporting or Close audit. Issuing the report also moves an Active audit to Reporting.
- From Reporting: Start audit (back to Active) or Close audit.
No audit goes back to Draft.
Close audit asks you to confirm. With findings still open it says how many, and how many are red, and you must give a reason; the reason is kept on the audit and in its history. Closing the audit also closes any of its surveys still open, as Close survey does: no more answers are taken, the links say the survey is closed, and reminders stop. The confirmation says so, and the history shows a Survey closed line for each, marked closed with the audit. A survey still in draft stays a draft: a closed audit sends nothing. Once closed, the details, team, surveys and interviews are locked, no finding or action can be added, and no report can be issued or started. The follow-up actions already raised are not locked: they can still be marked done, and each finding closed once they are. The CSV exports still work.
Details and team
Details shows the reference, coverage, lead auditor, dates, who created it and the description. Edit details changes the name, dates and description until the audit is closed.
Audit team lists the auditors. Assign an auditor offers only the Customer's Administrators who can see this audit; turn on Make them the lead auditor to hand them the lead, then Assign. They are emailed. Make lead passes the lead to someone already on the team; Remove takes anyone but the lead off it (make someone else lead first).
The five parts
- Pulse Surveys — one row per survey with invited, responded and status. + New survey: choose the Survey template, name it, choose the Anonymity — Attributed (answers recorded on the Worker profile; the default) or Anonymous (not linked to the Worker; it must go to at least 10 Workers) — and set Closes on, Remind every (days, 0 for none) and a Message to Workers, then Create survey. A survey from Obtempera Wellbeing Survey, or your own copy of it, starts anonymous. Then choose the Workers on the survey page.
- Worker Data Audit — a check of what the system already holds. + Draw a sample from the whole audit scope or from a surveyed group, at random (How many, from one) or by choosing Workers by hand. A random draw is recorded with who was picked, from how many, and its seed, so it can be repeated. Open a sample to see its Workers, with Interview to start an interview with anyone not yet interviewed. The export icons download a CSV of every Worker in scope, or of one sample: identity and compliance status only, one row per Worker and Project with the name, email, Contractor, Project code and compliance status (Green, Amber, Red or Not assessed). No form answers and no evidence files leave the system this way.
- Worker Interviews — pick any Worker in scope and Start interview, or start one from a sample; see the interview page.
- Findings & Follow-ups — + Raise a finding on the Audit Finding form: the Flag (Red: immediate follow-up and action; Amber: follow-up and action; Green: no action), its Source, the Contractor it is against, the Worker it concerns (optional), a Title and Detail, and for red or amber a Follow-up action with a Due on date (left empty: today for red, in 14 days for amber, where the audit is). Your organisation can add its own questions to the form under Fields & Forms (with more than one finding form, choose which when raising), including documents or photographs, which are checked for viruses before anyone can open them; the answers show when you open the finding. A Contractor named on an action is emailed and responds in its Contractor Portal; the response shows under the action. While the audit and the finding are open, Add action adds another. Mark done completes an action, and Close finding closes the finding: a red or amber one only once every action is done. Both ask you to confirm first, with a note of what was done; for a red or amber finding the note is needed. A finding closed by mistake has Reopen finding, and an action marked done by mistake Reopen (while its finding is open): each asks why, and the reopening is kept on the audit trail with the reason and what the closing said. A finding raised in an interview has Interview to go back to it.
- Audit Report — Write the report (later Continue the report or Open the report) on the report page.
Audit History, above the report, records each event, when, and by whom: press Show history. Each follow-up action is there as Follow-up action added, including those sent with the finding when it was raised. On a phone the Findings and History tables scroll sideways to show the flag, status and who did what.
What a Report Viewer sees
A Report Viewer for the whole Customer reads the audit and changes nothing: the buttons that move it on, edit it, manage the team, draw samples, start interviews, raise findings or close them are not shown, and Open the report opens the report to read. Only basic Worker data is shown to them:
- Samples and survey invitations name the Workers without their email addresses.
- The data export has no Email column: name, Contractor, Project code and compliance status.
- Worker interviews are not listed, and a single Worker's interview cannot be opened. The findings and the report stay readable.