Urgency buckets: Planning, Ready, Overdue, Today, Tomorrow, Later

What Action Plans tracks

Action Plans is the franchisor's live view of network initiatives already in motion: decision plans you've activated, at-risk franchisee interventions you're running, consent requests franchisees have approved, and program violations you've escalated. Where Decisions is the full inbox, every network-level item awaiting your judgment, Action Plans is narrower on purpose: it only shows work that has actually started (or finished). Nothing sitting in draft, queued, or pending stays here; it lives on Decisions until you act on it.

Every initiative on this page is really a short internal checklist with dated milestones, Detected, Escalated, Resolved; Sent, Approved, Closed; and so on. The urgency buckets described below sort every initiative by the due date of its next unfinished milestone, so a two-week-old intervention with a stalled step surfaces the same way a two-day-old one would if its own step is running late.

Open it from the sidebar at hq.verinode.ai/actions. The page header reads "Action Plans" with the subtitle: "Network initiatives in flight, plans you've activated, interventions in progress, consent requests approved. The work running across the network."

Where the urgency dropdown sits

The toolbar at the top of the page runs, left to right: a search box (placeholder "Search decisions…", matching on title and entity name), the urgency dropdown, a sort dropdown ("Newest first" / "Biggest impact"), a Select button for choosing multiple in-flight plans to cancel at once, and a Gantt/Calendar view toggle. Action Plans opens by default in Gantt view.

There is no business-area dropdown on this page, that filter belongs to Decisions, where initiatives span enough domains (governance, compliance, operations, risk) to need one. Action Plans has its own single axis: urgency.

The urgency dropdown, bucket by bucket

The dropdown replaces the status filter you'd see on Decisions. Each option shows a live count in parentheses, computed only from initiatives that are already in flight or finished, drafts, queued items, and pending requests aren't counted anywhere in this dropdown because they aren't in this data set at all.

• All (N): every in-flight or completed initiative, the full base count behind every other row in the dropdown.
• Planning (N): an initiative whose plan is actively being generated right now, before it has any dated steps at all.
• Ready to start (N): a plan whose steps exist but hasn't been given a start date yet.
• Overdue (N): the next unfinished step's due date has already passed.
• Due today (N): the next unfinished step is due today.
• Due tomorrow (N): the next unfinished step is due tomorrow.
• Later (N): the next unfinished step is due further out than tomorrow (or the initiative has no plan or no start date yet and doesn't qualify for Planning or Ready).
• Completed (N): every step on the initiative's checklist is marked done.

How the bucketing actually works

Every initiative carries an ordered list of dated milestones. Verinode walks that list, finds the first step that isn't marked complete, and buckets the whole initiative by how that one step's due date compares to today. Steps further down the list don't matter yet, if the second step is still open, a third step due next month doesn't pull the initiative into Later early.

A concrete example: an escalated program violation carries the checklist Detected (already done) → Escalated (due 3 days after detection) → Resolved (due roughly two weeks out by default, sooner if you close it earlier). While Escalated is still unfinished, the violation is bucketed by Escalated's due date, Overdue, Due today, Due tomorrow, or Later, even though Resolved's due date is much further away. The moment you mark Escalated done, Verinode re-evaluates against Resolved instead.

The four initiative kinds each run their own checklist:

• Decision plans (playbooks you've activated): Drafted → Activated → Adoption check → Completed.
• Interventions (at-risk franchisee outreach): Flagged → Contacted → In progress → Resolved.
• Consent requests (data-sharing asks you've sent): Sent → Approved → Closed.
• Program violations (escalated compliance flags): Detected → Escalated → Resolved.

Dates on these checklists come from your own recorded timestamps, when a plan was activated, when a violation was escalated, when a request was approved, not something you type in separately. Once an initiative shows up as actioned (Active, Contacted/In progress, Approved, or Escalated) or resolved, it's already carrying a real start date, so it's already eligible to land in a due-date bucket the moment it appears on this page.

Where the buckets show up beyond the dropdown

The bucketing isn't only a dropdown filter, it's also how Gantt and Calendar view lay initiatives out.

In Gantt view, most rows render as a normal timeline bar, a horizontal track with a checkpoint marker for each dated step, filled in copper up to however far the initiative has progressed. Planning and Ready rows are the exception: since they have no start date, there's nothing to draw a timeline against, so they render as a label with a colored pill instead, a copper "Planning" pill or a green "Ready to start" pill, with no track underneath.

In Calendar view, the same logic shows up as a "Pending plans" strip above the month grid, listing every Ready or Planning initiative that has no due date to place on a calendar day, each with a small dot (copper for Planning, green for Ready) and its title. Everything else appears as a colored pill on the calendar day its next step is due: red for overdue, copper for due today, steel blue for due tomorrow, green for further out or completed.

Empty states

Each urgency bucket has its own empty-state copy in Gantt view, rather than one generic "nothing here" message:

• Overdue: "Nothing overdue. Steps past their due date land here so they don't slip."
• Due today: "Nothing due today. Steps scheduled for today land here as soon as a plan crosses their day_offset."
• Due tomorrow: "Nothing due tomorrow yet. Tomorrow's step list builds as the day rolls over."
• Later: "Nothing parked for later. Plans you don't act on today land here so you can pick them up next week."
• Planning: "No plans in the planning beat. New decisions you've accepted but not yet started will land here."
• Ready to start: "Nothing ready to start. Plans whose first step has come due will land here."
• Completed: "No completed plans yet. Plans you resolve land here so you can run a retrospective."

If the underlying data set is empty outright (nothing has been actioned or resolved on the network yet), Gantt view instead reads: "Nothing matches this filter."

Calendar view has its own single empty state, shown when there is nothing in flight anywhere on the network: "No plans on the calendar yet. Action plans appear here as soon as you click Act on a decision. Each plan step lands on the day it is due."

Working the buckets

Start with Overdue, it's the clearest signal that an initiative is stalling: an escalated violation whose resolution deadline has passed, an intervention that's gone quiet past its check-in date. Due today and Due tomorrow are your short-range worklist, the initiatives that need a status update or a nudge in the next 24-48 hours. Later is everything else in flight but not urgent yet, useful for a weekly review rather than a daily one. Completed is your retrospective pile, initiatives that finished their checklist end to end.

Clicking any card opens the same workspace slider used on Decisions, with the initiative's title, plain-language framing, and a Discuss button that hands it to the agent panel for follow-up questions. Depending on the initiative kind and its current state, the card may also show Act, Park, or Ignore, each mapped to that initiative's own lifecycle (activating a paused decision plan, advancing an intervention, approving a disputed audit, and so on). Those per-kind actions are covered in hq-programs and hq-compliance.