ISO9001
Build an Operational Process Register in SharePoint for ISO 9001
Set up one SharePoint List that records each operational process: what it is, how often it runs, who does it, who is accountable, which document applies and how competence is shown.
An operational process register is one SharePoint List with a row for every process your business runs. It answers four questions for each: what is the process, who does it, which document tells them how, and how do you know they are competent to do it?
It is the backbone of an ISO 9001 system in SharePoint. Objectives, events, audits and management review are separate processes with their own records. This article covers only the register. The ISO 9001 QMS in SharePoint guide shows how the rest connects.
Start with the processes people already run
List the real activities by department, such as order picking, invoice entry or sales team meetings. Do not start from ISO clauses. Start from the work. Each activity becomes one row.
The columns
These columns are a practical starting point, not required ISO fields.
| Column | SharePoint type | What it records |
|---|---|---|
| Process name | Title | A clear, plain-language name |
| Description | Multiple lines of text | What the process achieves, in one or two sentences |
| Frequency | Choice | Daily, weekly, monthly, as required, ongoing |
| Department / function | Choice | Where the process sits |
| Responsible position (R) | Choice or text | The role that performs the work |
| Accountable person (A) | Person | Who answers for how the process runs |
| Formal document | Choice, plus a link | SOP, work instruction, or none yet |
| Training required | Choice | On-the-job instruction, external certification, none |
| Competency evidence | Choice | How competence is shown, for example supervisor verification or a qualification |
| Retraining frequency | Choice | As required, annually, not required |
| Related quality principle | Choice | Optional link to your own quality principles |
Use Choice columns wherever you can. They keep entries consistent and make filtering reliable. Use a Person column for the accountable owner, so ownership changes are visible and searchable.
Make it usable
- Group views by department. Each team sees its own processes first.
- Add a "no formal document" view. This shows where instructions are missing.
- Add an "owner or competency not set" view. This shows gaps in accountability and training.
- Use column formatting for status choices. Colour makes gaps easy to scan.
A filtered view is not a security boundary. Decide separately who can edit the register and who can only read it.
Keep it honest
- "Supervisor verification" says how competence is checked. It is not evidence by itself. Keep the actual assessment record somewhere access-controlled and link to it.
- A document link does not prove the document is current. Point to the controlled library, not a copy.
- Review the register on a schedule. Stale rows are worse than missing ones.
Check it works
Pick one row. Ask the accountable person to use only SharePoint to answer:
- What does this process involve and how often does it run?
- Which document applies today?
- Who performs it and how is their competence shown?
- Who do I go to if it goes wrong?
If they cannot answer, improve the row before adding more rows.
Where it connects
Link events, improvements and audits back to a process by its name or ID. That is how the register becomes useful beyond a list of activities. Each of those is its own process and register. Set them up one at a time.
For help defining your processes, start with the quality process mapping fit questions or contact QikSolve.
Sources and limits
This is general educational guidance, not a complete ISO requirement list, an installable template or evidence of conformity to ISO 9001. Assess applicable requirements against an authorised copy of the standard and your own context.