Dashboards & Analytics · Workload

Follow-Up Workload View by Owner

A workload view that shows how many open follow-ups each owner is carrying and how many are overdue, so work can be balanced before anyone drowns.

Start a ProjectAll Case Studies
4 to 7 days
build time
4
outcomes
5
stack tools
6
build steps

Built with real HMX dashboard tool paths

Supabase PostgresSQL view (per-owner aggregation)Next.js 16 server componentsMetabase (read-only BI)Vercel hostingSupabase PostgresSQL view (per-owner aggregation)Next.js 16 server componentsMetabase (read-only BI)Vercel hosting

01 // Outcomes

Outcome signals

Per-owner
open and overdue follow-up counts
Overdue
work surfaced against an agreed threshold
Balance
signal between most- and least-loaded owners
Drill
into each owner's oldest untouched leads

Case architecture

Follow-Up Workload View by Owner Architecture

6 nodes
the owner field plus the
the overdue threshold with
Supabase Postgres
SQL view
Review Queue
Owner Review
  1. 01the owner field plus the

    A workload view that shows how many open follow-ups each owner is carrying and how many are overdue, so work can be balanced before anyone drowns.

  2. 02the overdue threshold with

    Set the overdue threshold with the operator so it matches the real follow-up cadence.

  3. 03Supabase Postgres

    Supabase Postgres contributes the trusted model for Follow-Up Workload View by Owner so metrics are defined before they are visualized.

  4. 04SQL view

    Build a view returning open count, overdue count, and oldest-untouched age per owner.

  5. 05Review Queue

    When automation confidence is low, route the record to a manual owner with the source, stage, and last action attached.

  6. 06Owner Review

    Per-owner open and overdue follow-up counts; Overdue work surfaced against an agreed threshold; Balance signal between most- and least-loaded owner...

Problem

The operating gap

Follow-up load is invisible until someone is buried: one owner has forty open leads and another has six, but without a view nobody knows the imbalance until calls start getting dropped.

Build

What gets built

A read-only view that counts open and overdue follow-ups per owner using existing owner assignment and next-action / last-touched fields, with an overdue threshold and a simple oldest-untouched list per owner. It reports the distribution of work; it does not reassign anything automatically.

Build steps

How it ships

Follow-Up Workload View by Owner uses a reporting model and review layer for Dashboards. A workload view that shows how many open follow-ups each owner is carrying and how many are overdue, so work can be balanced before anyone drowns. The architecture connects the owner field plus the, supabase postgres, sql view, and owner review with an explicit control path.

  1. 01Confirm the owner field plus the timestamps that define 'open' and 'overdue' follow-ups.
  2. 02Set the overdue threshold with the operator so it matches the real follow-up cadence.
  3. 03Build a view returning open count, overdue count, and oldest-untouched age per owner.
  4. 04Render a per-owner workload table sorted by overdue count, with a drill into each owner's oldest items.
  5. 05Add a team total and a simple balance indicator (most-loaded vs least-loaded owner).
  6. 06Document the thresholds and clarify the view is for balancing, not automatic reassignment.

Stack

Tools and layers

  • Supabase Postgres
  • SQL view (per-owner aggregation)
  • Next.js 16 server components
  • Metabase (read-only BI)
  • Vercel hosting
  • Inputs layer: Confirm the owner field plus the timestamps that define 'open' and 'overdue' follow-ups.
  • Transform layer: Set the overdue threshold with the operator so it matches the real follow-up cadence.
  • Metrics layer: Supabase Postgres contributes the trusted model for Follow-Up Workload View by Owner so metrics are defined before they are visualized.
  • Visualization layer: SQL view (per-owner aggregation) handles refresh, review, or reporting delivery while a read-only view that counts open and overdue follow-ups per owner using existing owner assignment and next-action / last-touched fields, with an o...
  • Action layer: Per-owner open and overdue follow-up counts; Overdue work surfaced against an agreed threshold; Balance signal between most- and least-loaded owner...

Data flow

  1. 01Confirm the owner field plus the timestamps that define 'open' and 'overdue' follow-ups.
  2. 02Set the overdue threshold with the operator so it matches the real follow-up cadence.
  3. 03Build a view returning open count, overdue count, and oldest-untouched age per owner.
  4. 04Render a per-owner workload table sorted by overdue count, with a drill into each owner's oldest items.
  5. 05Add a team total and a simple balance indicator (most-loaded vs least-loaded owner).
  6. 06Document the thresholds and clarify the view is for balancing, not automatic reassignment.

Controls

  • Follow-up load is invisible until someone is buried: one owner has forty open leads and another has six, but without a view nobody knows the imbala...
  • A read-only view that counts open and overdue follow-ups per owner using existing owner assignment and next-action / last-touched fields, with an o...
  • When automation confidence is low, route the record to a manual owner with the source, stage, and last action attached.

Research basis