The workload view

What the workload view is

Every decision you act on in Verinode becomes a plan, and every plan is broken into steps (a subtask), things like sending an email, running a call script, or filling in a tracker. Open five or six decisions at once and you have five or six separate step lists to check. The workload view collapses all of that into one queue: every step, from every plan you currently have open, sorted by how urgent it is. It answers one question: what do I actually owe right now, across everything.

This is different from the decision workspace, which is where you work one decision's plan in full. The workload view is the flat, cross-decision list that sits on top of all of them. It is also different from the feed, which is where new signals arrive for you to triage into a decision in the first place. Feed is intake, the decision workspace is depth on one decision, workload is breadth across everything you have already started.

Verinode does not decide what you should do first. It reads the due dates and statuses on the steps you already committed to and lays them out by urgency, oldest and most overdue at the top. You choose what to clear.

Where to find it

On the web app, open Decisions from the sidebar (/decisions). In the page header, next to Triage Log, click Workload. This opens the workload queue as an overlay card on top of the Decisions page, no navigation away from your decision list.

You can also load it as its own page at /decisions/workload. The standalone page shows the same content with a Back to decisions link in its header instead of a close button, useful if you want to bookmark it or keep it open in its own tab.

On mobile, open Decisions, then tap Workload → in the sub-route row at the top (next to Triage Log). The mobile top bar reads Workload while you are in it.

The stat strip

At the top of the view is a row of six numbers, largest first:

• Open · all: every step across Overdue, Due today, Due this week, and Waiting on others, added together. This is your total open workload. Recently done steps are not counted here, they are finished, not open.
• Overdue: steps whose due time has already passed.
• Due today: steps due within the next 24 hours.
• Due this week: steps due within the next 7 days (after today).
• Waiting on others: steps where you are waiting on a counterparty (a carrier, a vendor, a client) to respond, regardless of any follow-up date attached.
• Recently done: steps you completed, marked not needed, or skipped in the last 7 days.

Each number matches the count of rows in the bucket below it. Overdue reads in the same red used for an Analyse signal elsewhere in the product; Recently done reads in the same green used for an Expand signal. Due today, Due this week, and Waiting on others read in more neutral tones. The color is a visual shortcut, not a separate piece of data.

How a step lands in a bucket

Every non-finished step in every plan you have open gets checked against the same rules, in this order, and lands in exactly one bucket (never two):

1. 1If the step's status is "waiting on the other side" (waiting on a carrier, vendor, or client to respond), it goes to Waiting on others. This is checked first and overrides everything else, including any follow-up date, because your attention there is on the counterparty, not the calendar.
2. 2If the step is already finished (done, marked not needed, or skipped) and that happened within the last 7 days, it goes to Recently done.
3. 3If the step is finished but that happened more than 7 days ago, it is dropped from the workload view entirely. Older finished work belongs in the decision's own history, not in a live queue.
4. 4If the step belongs to a plan you have not started yet (you have not pressed Start plan on that decision), it is dropped from the workload view. Verinode will not clutter your queue with work you have not committed to starting.
5. 5From here, Verinode computes a due time: your explicit follow-up date if you set one, otherwise the plan's start date plus that step's planned day offset. If that due time is already in the past, the step goes to Overdue.
6. 6If the due time falls within the next 24 hours, the step goes to Due today.
7. 7If the due time falls within the next 7 days, the step goes to Due this week.
8. 8If the due time is further out than that, the step is dropped from the workload view for now. It will appear once it moves inside the 7-day window.

Within each bucket, the order is also deliberate:

• Overdue, Due today, and Due this week sort soonest-due first, so the most overdue step in Overdue sits at the very top.
• Waiting on others sorts by the oldest follow-up date first, so the follow-up that has gone stalest is at the top.
• Recently done sorts by most recently completed first, so you see what you just cleared, not what you cleared last week.

Reading a row

Each row in a bucket shows:

• A step number (for example #1, #2), the step's position within its own plan. Steps from different decisions can both show #1, the number is relative to that plan, not to the workload list as a whole.
• The step title, exactly as written in that decision's plan (for example "Send the kickoff email").
• The topic, the client, vendor, or entity the underlying decision is about, or the decision's own title if there is no specific entity attached. In the rare case a step has lost its parent decision link, it reads "Unattached."
• A due label, which reads differently by bucket:

- In Overdue, Due today, and Due this week, it shows the relative due date ("today," "tomorrow," "in 3 days," or, for an overdue step, "3 days ago"). - In Waiting on others, it reads "Following up [date]" if you set a specific follow-up date, or "Waiting on counterparty" if you have not. - In Recently done, it reads "Done [date]" ("Done yesterday," "Done 3 days ago").

• A kind label, what type of step it is: Email, Call script, Survey, Tracker, Comparison, IQ lookup, IQ research, Vault, Calendar, External, Linked decision, Note, or another label if the step is a newer kind not yet in this list.
• An Open link on the right, when the step's parent decision is still identifiable. Click it to jump straight into that decision at /decisions/[id], where you can act on that exact step.

Using it day to day

Work the buckets top to bottom. Overdue first, because that is where cost of delay is actively accruing. Due today next, so nothing slips into Overdue by tonight. Due this week when you have room to plan ahead. Waiting on others is a different kind of work, it is a nudge list: scan it for follow-ups that have gone quiet longer than they should have, and chase the ones that matter. Recently done is there so you can see what you already cleared before you go looking for more to do, not a to-do list itself.

Because the step number and title come straight from the decision's own plan, and the topic tells you which client, vendor, or matter it belongs to, you should have everything you need to decide whether to act from the workload view itself, or to click Open and go handle it inside that decision. See acting on decisions for what happens once you open a specific step.

Empty states

If you have no open steps in Overdue, Due today, Due this week, or Waiting on others, and nothing has been completed in the last 7 days either, the entire view collapses to one line:

"Nothing on your plate. Open a decision to start a plan, or wait for IQ to surface a new signal."

If you have no open steps but you do have something completed in the last 7 days, the "nothing on your plate" message does not show. Instead you see only the Recently done section, so you can confirm what you just finished even when your active queue is clear.

Sections for buckets with zero rows simply do not render, you will never see an empty "Due this week (0)" heading taking up space. Only buckets that actually have something in them appear, in the fixed order Overdue, Due today, Due this week, Waiting on others, Recently done.

Data sources