Shared actions & workflow · Suite 1.9
See what needs attention.
Keep responsibility clear.
Bring outstanding work into one assessment view. Follow due dates, open the source record and keep delivery, verification and effectiveness connected.
A shared work queue
Open Shared work queue from module navigation. Outstanding supported records and actions are ordered by due date, with overdue counts and direct links back to the work. Use Everyone or My next steps, responsibility and date filters, and export the current queue to CSV.
Actions with a source
Keep the action linked to the finding or NCR it addresses. Record delivery responsibility and due dates; use Action allocations for named delivery and review.
Review beyond completion
Record the evidence that work was delivered, then assess whether it achieved the intended outcome. NCR brings the corrective actions together for independent review.
Follow one issue across the response
- Identify: record an audit finding, observation or obligation gap in the assessment.
- Connect: raise an NCR and retain its source link. Describe containment and the requirement that was not met.
- Allocate: add corrective actions and named allocations. Set the expected outcome, due dates and evidence needed.
- Deliver: use the queue to find outstanding work. Save completion evidence in the appropriate record.
- Verify: the independent reviewer evaluates the completed work. Linked actions and allocations must be complete before NCR verification.
- Check effectiveness: review results after the planned observation period. Close an effective NCR or return the work with a reason.
The queue is scoped to the current assessment. It is not a company-wide personnel register or an automatic reminder service. Approved and terminal records remain available in their own registers.
Plan work and follow it through
RAMS plans and steps can carry linked preparatory actions. Their actions and allocations must be Closed before plan approval or use. Use the shared queue to open the source, follow named responsibility and find work due next.
Follow a fictional action from allocation to verification → · See the RAMS revision example →
Dates reflect the next decision
Delivery due date
Actions use their delivery due date, helping teams locate overdue work without losing its source.
Effectiveness review date
NCRs awaiting effectiveness use the planned effectiveness date. A completion tick does not bypass the observation period.
Keep the agreed evidence intact
Corrective actions and allocations relied on by an NCR under review or already closed cannot be silently edited, detached or deleted. Return or reopen the NCR through the permitted workflow before changing that work.
Explore Sentinel NCR → · Read the operating guide →
Practise before using real records
Start with a separate fictional training assessment. Give the owner and independent reviewer their own accounts and appropriate existing access. The public example below explains the decisions without loading or saving client information.
Connect contractor work to the suite
Review contractor evidence, link engagement plans and check every compulsory worker qualification. Keep follow-up actions connected to their source.
Explore Contractor management → · Follow the fictional contractor example →