Action Hub
A to-do list that actually gets finished
Finding gaps is the easy part. The Action Hub turns every gap, risk and incident finding into a task with an owner and a date, and keeps it visible until it is done.
Fix what matters first
Fixes get agreed and then forgotten.
Nobody owns the work
A report lists forty things to fix. Without names and dates, most stay on the list.
The context gets lost
A task that says "enable MFA" does not say why it matters, which risk it closes or who asked.
No record of what was done
When an auditor or insurer asks what you did about a gap, the answer is buried in emails.
What changes
From a list to finished work.
First
Gaps, risks and incident findings become tasks, each with an owner and a priority.
Then
Work moves across a board or calendar. Owners attach files and comments as they finish.
Ongoing
Overdue and blocked items stand out, and the history shows what was done and when.
How it works
How it works.
Every task knows where it came fromIt is linked to the gap, risk, incident or policy behind it.How this works underneath
Tasks are created from compliance gaps, risk treatments, incident findings and policy workflows. The source travels with the task, so the reason is never lost.Work is prioritised and ownedMust, should or could, with a named person and a date.How this works underneath
Priority uses must, should and could. Tasks can be moved on a board or viewed on a calendar, and status, owner and date can be updated across several tasks at once. Tasks sync with Microsoft Planner where you use it.Finishing leaves proofFiles, comments and history stay with the task.How this works underneath
Files and comments attach to each task. An append-only activity log records status changes, reassignments and comments, and completed work becomes for your proof pack.
A small example
What this can look like.
- Situation
- A gap is found: shared mailbox logins have no extra sign-in check.
- What the Action Hub does
- A task is created, linked to the gap, assigned to the IT manager and marked as a must, with a due date.
- What happens next
- The manager completes it and attaches a screenshot of the setting. The task moves to done.
- What is kept
- The task, the screenshot and the dates are kept as evidence.
This is an invented example to show how the module works. The names and figures are not a real customer's.
What is in it
What is in the Action Hub.
Tasks linked to their source
Each task is linked to the risk, gap, incident finding or policy it came from.
Board and calendar views
Move work across a board or see it by due date, and update several tasks at once.
Must, should, could priorities
Priorities that match how teams talk about work.
Files and comments
Attach proof of what was done to each task.
Workload summaries
See what is open, blocked or overdue across the whole programme.
Activity history
An append-only record of status changes, reassignments and comments.
Microsoft Planner sync
Keep tasks in step with Planner for teams that already work there.
Questions
Common questions.
No. The Action Hub works on its own. If your team uses Planner, tasks can sync so work sits where people already look.
From compliance gaps, risk treatments, incident findings and policy workflows. You can also add tasks yourself.
Yes. Each task keeps its files, comments and an activity history, which can be shared as evidence.
Related
Works with.
Get your fixes finished.
The free readiness assessment shows you where you stand and what to fix first. If we are not the right fit, we will tell you that too.