Skip to main content
The Daily Brief is the read on today. The Weekly Watch is the read on the week. Where the daily lives in detail, the weekly steps back: where are you trending, what breached or didn’t, what to focus on for the next five days. The Weekly Watch lands two ways: as a Monday-morning email/Slack digest, and as a live in-app view at /watch in the dashboard. Both read from the same snapshots; the email is a snapshot of Monday’s prose, the in-app view is always live data with the most recent commentary attached.

​
In-app view

Open it from the Briefings entry in the sidebar (under Reads) and click the Weekly Watch tab at the top of the page; the same destination also holds the Daily Brief, so you can flip cadence without leaving the surface. Direct URL /watch still works. Four blocks, top to bottom:
  1. Capacity runway card. Same breach math as the email — Stable, Watch Nw, or Breach Nw — plus the headline number (“4 weeks” / “Stable”) and the cap detail (“178 weekly tickets vs 240 cap”).
  2. Per-metric trajectory cards. Four cards (CSAT, First reply, AI deflection, Weekly volume). Each shows current value, WoW delta, a real 4-week sparkline from your snapshots, and the shape label (“sustained rising across 4 weeks”, “step change in week 2”, “choppy, 1 reversal”, “flat within 1-unit band”).
  3. Per-agent shape table. One row per agent that has at least two weekly snapshots — CSAT shape, tickets shape, and the combined trajectory line shown beneath their name on the Team view.
  4. Last commentary block. The prose from your most recent Monday digest, with the send timestamp. We deliberately don’t re-generate prose on every page load — that would be expensive and inconsistent. To refresh, fire a digest from Settings → Delivery → Send digest now; the new commentary will appear here on next reload.
If your workspace is below the completeness threshold, the in-app view shows a holding state pointing to Settings instead, same threshold the Monday email uses to decide whether to send.

​
When the email sends

Monday morning, in your local timezone, at the hour you set in Settings → Delivery → Daily Brief by email (the same hour drives both). Each user gets exactly one Weekly Watch per week. If your workspace is below the completeness threshold on Monday morning, no email goes out. Forepost would rather skip than guess.

​
What’s in the email

Three blocks:
  1. Capacity status pill. Top-right of the header. Stable (green), Watch Nw (amber, if breach is 9-16 weeks out), or Breach Nw (red, if breach is ≤8 weeks).
  2. Week-over-week movement table. Four rows:
    • Volume: this week’s count + % change vs last week.
    • CSAT: now + pp change.
    • First response: now + % change.
    • AI deflection: now + pp change.
    Green for movements you’d want, red for the opposite, neutral for flat. If this is the baseline week (no prior snapshot to compare), the table is replaced with “First week, no prior snapshot to compare yet.”
  3. AI commentary. Two paragraphs of plain prose. Lead sentence gives the read on the week, then what to focus on, then a forward-looking observation. Same Forepost voice as the Daily Brief.

​
How the deltas are computed

Forepost stores a metrics snapshot every time you save Settings. The Weekly Watch picks the most recent snapshot at least six days before the latest one and computes the delta between them. That’s the closest approximation of “this week vs last week” without a strict cron-aligned schedule. If you only saved Settings once (this is your first week), there’s nothing to compare. The table reads “First week” and the commentary leans on absolute values rather than direction.

​
Trajectory (multi-week shape)

As of Phase 3C, each metric row in the digest carries a small trajectory line beneath the WoW delta — the SHAPE of the last four weeks, not just the latest point compare. Examples of what you’ll see:
  • “sustained falling across 4 weeks” — monotonic decline week after week
  • “step change in week 3 (out of 4)” — one big jump, the rest flat-ish
  • “choppy, 2 reversals” — sign flipped between adjacent weeks
  • “flat within 1-unit band” — no real movement to read into
The AI commentary above the table is told to lead with the SHAPE wherever multi-week data exists (“three weeks of CSAT decline that accelerated this week”) rather than the WoW point compare. Single-week reads get framed as such — the digest doesn’t pretend a one-week dip is a trend. The trajectory needs at least two weeks of snapshots per metric to render. For a fresh workspace, the row stays trajectory-free until enough snapshots accumulate.

​
Action follow-through in the Weekly Watch

The Weekly Watch also receives a summary of the actions queued across the week’s Daily Briefs (“5 queued, 3 taken, 1 dismissed, 1 still pending”) and references them in the prose. If a metric moved in line with what was taken, the commentary names the connection (“Sarah’s coaching landed, her CSAT moved from 78 to 82”). If actions were dismissed and the underlying issue is still live in the data, it’s flagged without re-litigating the dismissal. The Weekly Watch itself doesn’t queue new actions — that’s a daily affordance. The week is for closing the loop.

​
Subscribing & unsubscribing

Subscriptions live in Settings → Delivery → Weekly Watch. The on/off switch is independent of the Daily Brief, you can have one without the other. To unsubscribe from a single email: every Weekly Watch carries a List-Unsubscribe header for one-click opt-out, plus a footer link. Both flip the same setting in Settings.

​
Why no AI commentary the first week

The data is too thin. You’ve made one snapshot; there’s no week-over-week direction yet. Forepost reads the breach status and current values, but skips the trend interpretation rather than fabricating one.