FT
Follow-Through
concept prototype
Friday, August 14

Good morning, Maya

7 commitments have not moved. This is your one digest for the day. Nothing here has been sent.

Interruptions today
1 digest, 0 pings
Nothing was urgent enough to break in.
7 of 7 leftApprove level. Every action waits for your click.
Jump toYou owe 3Owed to you 2Unowned 2
Show

You owe

3

Promises you made. You are the one who has to move.

Overdue

You told Priya in Tuesday's QBR you'd send revised pricing by Thu.

Deadline passed yesterday. No pricing sent, no reply on the thread.

Evidence
  • Meeting transcript / Meridian Freight QBR, Tue Aug 11"I'll get you revised pricing by Thursday." 00:41:22
  • Email thread / Re: Meridian renewal terms, 6 messagesLast message Aug 11. No attachment sent since.
  • Doc / Meridian pricing v3 (draft)Last edited by you Aug 12. Never shared externally.
ProposedDraft nudge Goes outside the companyHigh confidence 94%

Send Priya the revised pricing with a one line status.

Explicit commitment, named owner, named date.

To priya.raghavan@meridianfreight.com
Subject Revised pricing for the renewal

Hi Priya, Following up on Tuesday. Revised pricing is attached, with the volume tier we discussed applied from month one. Two things changed from the version you saw: the tier break moves from 500 to 400 seats, and onboarding is folded into year one instead of billed separately. Happy to walk through it Thursday if that is easier than reading it cold. Maya

Written from mail you have already sent. Nothing goes out until you click the button below.

Overdue

You promised Elena the security review summary after Monday's call.

3 days late. Review doc exists but was never sent.

Evidence
  • Meeting transcript / Security review, Mon Aug 10"I'll write this up and send it over." 00:52:10
  • Doc / Security review notes, Aug 10Created by you Aug 10. Not shared with Elena.
ProposedDraft recapGood confidence 83%

Send the recap you already wrote, trimmed to what she asked for.

Commitment is clear. 'After the call' has no hard date.

Coming up

You told Rosa you'd send the Cobalt go/no-go summary before Monday's launch review.

Due Monday Aug 17, two working days out counting today. Nothing drafted yet.

Evidence
  • Meeting transcript / Cobalt launch checkpoint, Wed Aug 12"I'll have the go/no-go summary to you before Monday." 00:18:47
  • Doc / Cobalt launch checklist6 of 9 items closed. No summary doc exists yet.
  • Jira ticket / COB-214, Webhook retries drop eventsStill open. This is the one item the summary has to cover.
ProposedDraft ahead Goes outside the companyHigh confidence 91%

Write the summary now, while the standup notes are fresh, and hold it for your Monday send.

Explicit commitment with a named date. Nothing written yet.

Owed to you

2

Promises made to you. Chasing these is the whole job here.

Overdue

Marcus said he'd open the integration escalation for Bellwether by Friday.

End of week passed. No ticket exists in the Bellwether project.

Evidence
  • Meeting transcript / Bellwether sync, Thu Aug 6"I'll open the escalation before end of week." 00:12:04
  • Jira ticket / BWH project, escalation query0 tickets created since Aug 6. Expected 1.
ProposedDraft nudgeGood confidence 88%

Nudge Marcus with the two lines he needs to file it.

Clear owner. Deadline inferred from 'end of week'.

How wide should the mute go?

You can turn any of these back on in settings.

This commitment stops showing up. Nothing else changes.

Context closes the commitment in the ledger, so nothing else chases it. Without context the ledger row stays open.

Quiet

Bellwether Health has not replied to your Aug 6 renewal thread.

9 days quiet. Renewal date Aug 28.

Evidence
  • Email thread / Renewal paperwork, Bellwether HealthYour message Aug 6. No reply since.
  • Doc / Account record, Bellwether HealthRenewal date Aug 28. Owner: you.
ProposedDraft nudge Goes outside the companyFair confidence 79%

Short check in that gives them an easy way to answer.

Quiet thread plus a dated renewal. No explicit promise.

Unowned

2

Nobody picked these up. Take one or leave it.

Overdue

Cobalt Systems integration blocker was raised twice with no owner.

Raised Aug 5 and Aug 13. Ships Aug 21. Still unassigned.

Evidence
  • Meeting transcript / Integrations standup, Thu Aug 13"Cobalt is still blocked on the webhook retry." 00:07:33
  • Jira ticket / COB-214, Webhook retries drop eventsUnassigned. Priority not set. Opened Aug 5.
  • Email thread / Cobalt launch checklistShip date Aug 21 confirmed by Cobalt on Aug 11.
ProposedEscalation flagGood confidence 86%

Flag to Nadia with both mentions and the ship date.

Repeat mention plus a fixed date is a high risk pattern.

Quiet

Roadmap review produced an action item with no owner and no ticket.

7 days since the meeting. No ticket, no thread, no owner.

Evidence
  • Meeting transcript / Q4 roadmap review, Fri Aug 7"Someone needs to scope the audit log export before we commit." 00:28:51
  • Jira ticket / ARC backlog, keyword scanNo ticket mentions audit log export.
ProposedCreate ticketGood confidence 81%

Open a ticket in ARC and assign it to the review owner.

Action item is explicit. Owner is inferred from context.

2 detections scored under 60% confidence, so they were left out.Move the bar in settings.

Concept prototype. Fictional people, companies, and evidence. Not a Glean product and not affiliated with Glean.