Area
Actions are grouped by the team or system that owns the work, so each area head can read one section and see everything their part of the business owes. One area per action, never two — that is what makes the counts add up.
Operations — call-offs, scheduling, plot status and the day-to-day running of installs, including the Window Designer parts and product data behind a plot.
Customer Care — the post-install contact narrative, SLAs, defects and Site Services.
Warehouse & Fitters — picking and preparation, the field app, sign-off and balances.
Finance — chargeable versus free of charge, invoicing, the finance pack, and everything that crosses into or out of Sage Intacct.
Data & Migration — getting existing records into PivotOS and keeping them aligned.
Reporting — what each team needs out of PivotOS, and the data quality behind it.
Programme — running the project itself: access, comms, glossary, decisions and the parallel run.
Whose
Vindico — we hold it.
GCW — you hold it, and we are waiting on it.
Joint — it needs both of us in the room. Joint actions appear under Vindico’s and GCW’s filters, because neither side can close them alone.
Status
Open — agreed and owned, not started.
In Progress — actively being worked.
On Hold — deliberately paused, waiting on something named in the action.
Review — the work is done and sitting with someone to confirm.
Complete — closed. Kept on the board so the history stays readable.
★ New — added at the 11 August project meeting.
Targets and overdue
An action counts as overdue when it has a real target date, that date has passed, and it is not complete. Actions marked TBC or Ongoing have no date to miss, so they are never counted as overdue — they are tracked by the comment instead.
Notes and comments
The note under an action carries its history: what changed, when, and what was agreed. The comment is the current position, attributed to whoever gave it, and it is the line to read if you only read one.