Disconnected action sources
Actions originated from risk assessments, audits, meetings, incidents, complaints, safety observations and pre-startup checks, with no common place to track them.
Safety actions, tracked to closure.
We customised a Task Management and Issue Tracking System on SharePoint Online for Descon Oxychem Limited, bringing seven safety and operational workflows into one action-item lifecycle inside the client's existing Microsoft 365 environment.

What stood in the way.
Action items at Descon came from many sources, each with its own owners, approvals and deadlines. The project needed one system that could link every action to its originating record, its responsible department and its status
Actions originated from risk assessments, audits, meetings, incidents, complaints, safety observations and pre-startup checks, with no common place to track them.
HSE, relevant departments, line managers and the Works Manager were all involved. Extensions, reassignment
Risk-rated follow-up dates, pre- and post-commissioning actions, and short- versus long-term safety-critical defeats each called for structured capture and different…
Without a common process structure, monitoring pending work and spotting ownership bottlenecks across workflows was difficult.
How we answered it.
We translated Descon's own workflow diagrams into a SharePoint-centred task and issue management environment. Rather than treating each process as a separate application, the design brings specialised source modules into a shared action-item lifecycle
The parts that made the difference.
Assessments route through HSE to the relevant department, which raises risk-rated action items with target dates set by the risk rating.
Saving a meeting emails attendees and creates a Microsoft Teams invitation in their Outlook calendars. Minutes generate action items, and the meeting can close once all its actions are closed.
Observations logged by authorised managers are routed by HSE to the concerned department, giving every observation a defined path to corrective action.
Incidents are risk-classified: high-risk events go to individual or team investigation and root-cause analysis, while lower-risk issues go to the responsible department. Incident reports can be requested and delivered by email.
What changed for the client.
The system gives Descon a structured, documented way to manage safety-related actions from capture to validated closure. The outcomes are functional rather than quantified
What it was built with.
Part of our RPA and workflow automation work.
Related projects.
The next big thing starts with a conversation.
An idea, a challenge, a “what if”. Tell us what you have in mind, and we’ll figure out the next step together.
What happens next
Find us on