Module: Operations
Actions
Every corrective, preventive and follow up action in one place, whoever raised it and wherever it came from, with an owner, a due date and a check that the fix actually worked.
What it does
One register, whatever raised it
Actions raised on an incident, an inspection, an audit, a risk review, a permit, a document or a contractor all land in the same register, each still linked to the record it came from. Nobody has to remember where a commitment was made.
An owner and a date that holds
Every action has one accountable owner, a priority and a due date, and appears in their own work list. Overdue work is escalated to the person accountable for it rather than waiting for someone to notice.
Closed when it worked, not when it was done
An action moves to verification when the work is finished and closes when it is confirmed effective, or goes back for rework when it is not. Whether the fix worked is recorded on the action, so a repeat problem can be traced to the action that was meant to prevent it.
Extensions asked for, not taken
A due date can be extended, but through a request with a reason that somebody else approves or rejects. The original date, the request and the decision all stay on the record.
Templates and recurring work
Actions that recur, such as a monthly check or an annual review, are set up once and raised on schedule. Action templates carry the wording, the priority and the default owner so the same work is described the same way each time.
Many at once
Assign, reassign, reprioritise or close actions in bulk from the register, on the rows you have selected, with the change recorded against each one.
See where work is stuck
The register shows how many closed actions met their date, with the numbers behind that figure, how long open actions have been open, and where actions come from. Each of those is clickable, so the figure and the list of records behind it always agree.
A calendar as well as a list
Switch the register to a calendar to see what falls due this week or this month, and who is carrying it.
How it fits with the rest
Actions is the module every other module leans on. An incident investigation, an inspection finding, an audit non-conformance, a risk control review, a permit condition, a document review and a contractor assessment all raise their follow up work here, and each action keeps a link back to the record that created it. The panel that shows an action on those records is the same register underneath, so a count on a dashboard and a list in a register cannot disagree.
Owners are people already in the platform, with their own notification settings, so an action reaches them the way they actually work. Due dates respect your working hours and your timezone. And because the source is kept, you can answer the question an auditor asks, which is not how many actions you have open but whether the ones that mattered were done and whether they worked.
Ready-made content
A corrective action pack installs the raise-to-verify workflow, the action form, a corrective action notice you can print or send, and the lists behind the fields, including action type, priority, where the action came from and where the control sits in the hierarchy of controls. Recurring actions and action templates are set up in the register itself, with no separate tool.
Change it if you need to
Every module comes ready to use. If your organisation records something differently, your own team can adjust the forms, fields and workflow, or ask us to do it with you. Nothing here requires a development project.
Works alongside
See actions running on your own processes.
Bring one of your own forms or procedures to the demonstration. We set the module up the way you work and show it end to end.