Every site,one programme
A programme that spans several sites is hard to keep honest in a spreadsheet. Orisynx plans every audit against its site or department and shows, for each one, what is planned, confirmed, complete and overdue.
| Audit | Standard | Date | Status |
|---|---|---|---|
| Purchasing | ISO 9001 | 12 Mar | Confirmed |
| Warehouse, Leeds | ISO 45001 | 3 Apr | Scheduled |
| Kestrel Metals | Supplier | 21 May | Tentative |
| Access control | ISO 27001 | 9 Jun | Scheduled |
7 of 18 audits confirmed
Each site and department in one plan
Every planned audit belongs to a department or site and has a priority, a risk level and a status. One audit plan can cover the whole organisation, so the programme reflects where the risk is rather than where the last audit happened to be.
If the programme already lives in a spreadsheet, import it from .xlsx or .csv. Every row is validated before anything is created, and errors are reported by row and cell.
| Row | Audit | Standard | Result |
|---|---|---|---|
| 2 | Purchasing | ISO 9001 | Ready |
| 3 | Warehouse, Leeds | ISO 45001 | Ready |
| 4 | Boiler house | ISO 5001 | Fix |
Row 4 · Standard: “ISO 5001” is not a recognised standard. Fix the cell and upload again.
See which sites are falling behind
Progress is shown for each department: how many audits are planned, scheduled and confirmed, the percentage complete, and what is overdue.
That makes uneven coverage visible early, while there is still time in the year to rebalance the programme, and gives you a straight answer when someone asks whether every site has been audited.
- Planned, scheduled and confirmed audits
- Percentage complete per department
- Overdue audits per department
Move an audit without losing it
Sites ask to postpone. A planned audit can be tentative, scheduled, confirmed, moved or cancelled, so a postponed audit is marked as moved and given a new date instead of being deleted and re-entered.
The shared calendar shows audits and due dates across every site, including overdue work, so a clash between two sites is easy to spot.
- 3 APRWarehouse, Leeds · ISO 45001Audit · Scheduled
- 17 APRBoiler house · ISO 50001Audit · Moved from 10 Apr
- 30 APRRe-evaluate suppliersTask due · J. Okafor
Workload by person, across sites
Analytics show each person’s open, completed and overdue work for the year, alongside audits by type per month and progress per department.
Groups organize people by site, department or audit team, and everyone receives a daily email digest of their overdue work, work due soon, and work waiting on them.
| Owner | Open | Done | Overdue |
|---|---|---|---|
| J. Okafor | 3 | 17 | 0 |
| R. Patel | 5 | 9 | 2 |
| A. Mensah | 1 | 22 | 0 |
Multi-site audits: questions
Can we bring in our existing multi-site programme?
Yes. Import it from .xlsx or .csv. Every row is checked before anything is created, and any errors are listed by row and cell so you can fix the file and upload it again. Legacy .xls files are not accepted.
How do we decide how often each site is audited?
ISO standards expect the programme to reflect the importance of the processes and the results of earlier audits. Give each planned audit a priority and a risk level, and audit higher-risk sites more often.
What happens when a site postpones its audit?
Mark the planned audit as moved and give it a new date. It stays in the programme and on the calendar, and the change is recorded in the activity log.
Keep reading
See it with your own audits
Bring an audit you have already run. We will walk it through Orisynx with you, from the plan to the last closed corrective action.