Fathom Review Policy: Mike's Team Underprep Flagging
Owner: Mike Hwang Created: 2026-06-16
Applies on top of the standard Fathom call review policy. Adds a new flag category (underpreparation by Konstruct reps) for a specific group of team members, with split routing.
Mike’s team
Section titled “Mike’s team”The following Konstruct reps are in scope for the underprep flag:
| Name | Slack ID | |
|---|---|---|
| Trevor Heaver | U0ATM7R9UKZ | trevor.heaver@konstructdigital.com |
| Courtney Krauss | U08PLS9QGH5 | courtney.krauss@konstructdigital.com |
| Thomas Jacobs | U0944FALR2A | thomas.jacobs@konstructdigital.com |
| Dakota Marx | U06ASHGHZA8 | dakota.marx@konstructdigital.com |
| Jason Tran | U082G14ETB9 | jason.tran@konstructdigital.com |
Mike Hwang’s Slack ID for DM routing: resolve at flag time via slack_find_user(name_query="Mike Hwang").
Call scope
Section titled “Call scope”- Client-facing calls only. Skip pure-internal team syncs, 1:1s, sprint planning.
- A “client-facing” call means at least one external (non-Konstruct) attendee.
- The flagged rep must be one of the five people listed above. If a different Konstruct rep is on the call, this policy does not apply to them (the standard policy still does).
Underprep flag criteria
Section titled “Underprep flag criteria”Flag if the Konstruct rep shows clear signs of underpreparation or low-quality information:
- Vague or non-committal answers to expected questions. “We’ll look into it”, “I think maybe”, “not sure off the top of my head” when asked about their own work or deliverables.
- Heavy hedging or filler / repeated false starts indicating they’re winging it on substance they should know.
- Can’t speak fluently to their own deliverable, scope, or recent work. Asked a direct question about something they own, they fumble or defer.
- No clear agenda, losing control of the meeting, client driving it. The rep isn’t steering.
- Deferring decisions they should own or making vague non-committal promises without a concrete next step.
Threshold: lean toward flagging. Calibration baseline is the Ohana Care call Mike flagged as “textbook bad” (Fathom: https://fathom.video/share/iY1yGzUYRaeidq91jLyRWWs4ijHskrVB). Tighten the threshold later if it gets noisy.
Routing logic
Section titled “Routing logic”Standard criteria (client frustration, lack of trust, weak leadership):
- Flag to
#kt-leadsas usual.
Underprep criteria (this policy) on a Mike’s-team rep:
- DM Mike directly. Do NOT post to
#kt-leads.
Both true on the same call:
- Post the standard-criteria flag to
#kt-leads. - DM Mike a separate flag focused on the underprep angle.
- Each flag is its own message, focused on its own angle. Don’t combine.
If the flagged rep is NOT on Mike’s team:
- This policy does not apply. Fall back to the standard policy.
Format
Section titled “Format”Same casual review format as the standard policy: two to four sentences, Fathom link near the start, one or two specific quoted moments via Slack blockquote when they help, no signoff, no em dashes.
For the DM to Mike, drop the <!channel> mention (not needed in a DM).
Caveats
Section titled “Caveats”- Transcript-only analysis: actual stuttering, nervous pace, mumbling don’t come through cleanly. This policy catches content-level tells (hedging, vagueness, fumbling in text). A smooth-sounding rep giving thin info is easier to catch than a shaky-sounding rep giving correct info.
- DM routing depends on backend webhook wiring. The policy is captured here; surface a wiring question on the first test call if the DM path isn’t configured.