Skip to content
GarnetOS

Action Centre

Every decision waiting on you. One list.

The reason work goes missing in a growing company is not that people are careless. It is that the thing needing a decision lives in whichever system produced it, and nobody checks six systems on a Tuesday.

The GarnetOS Action Centre, listing work waiting on one person

Home

My actions

5 open

  • Approve Ahmed Siddiqui’s leave

    Leave

    Five days requested from 14 April. Two others in Operations are already off that week.

    Due 9 AprWith You
  • Verify Sarah Donnelly’s passport

    Documents

    A new document was uploaded on Tuesday and nobody has checked it against the original.

    Due 11 Apr
  • Resolve an attendance exception — Tomas Novak

    Attendance

    Recorded as working on 2 April, which is a closure day for his working pattern.

    Overdue — was due 4 Apr
  • Review a change to Priya Nair’s salary

    People

    Her pay was changed on 1 April, effective from 1 May. A second person has to look.

    Due 15 Apr
  • Provide missing evidence — right-to-work check

    Compliance

    The record names a check on 3 March but no document is attached to it.

    Due 18 Apr

The rule

No module gets its own inbox.

It would be easier to build a notifications tab inside leave, another inside documents, another inside compliance. It is also how you end up with six places to check instead of one — which is the problem the product exists to solve.

So there is exactly one Action model, and every module raises into it. A leave request awaiting approval, a document nobody has verified, an attendance day that contradicts the working pattern, a salary change needing a second pair of eyes, a compliance requirement with evidence missing — the same shape, the same queue, the same way of closing.

Actions are raised by the system from what actually changed. Nothing here depends on somebody remembering to create a task, which is the step that fails first in every company that tries to run this on a to-do list.

Anatomy

Three facts on every action, in the same order.

Most notification systems give you a title and a link, which means opening each one to find out whether it matters. Every action here answers the question before you click.

  1. 01

    What happened

    The title states the event in plain words, with the person’s name in it. “Verify Sarah Donnelly’s passport”, not “Document pending review”.

  2. 02

    Why it matters

    A required field on every action — not a subtitle somebody might fill in. “A new document was uploaded on Tuesday and nobody has checked it against the original.”

  3. 03

    What happens next

    Where the decision is made, and what recording it does. Some actions close from the queue; the ones that represent a judgement open the record where that judgement belongs.

Owned by a person

Every action has a named owner, not a role or a shared queue. A thing everybody can do is a thing nobody does.

Due, and overdue

Dates where a date exists. Overdue is stated in words and coloured, never colour alone.

Escalation

An action that sits too long moves up, and says that it has. Silence is not an acceptable outcome.

Closed with a trace

What was decided, by whom, and when — in the same audit record as everything else.

Stop checking five places.

We will show you the Action Centre with the kinds of work your company actually generates.

Request a demo