Approved inbox label, folder, thread export, upload, or manual evidence set.
One-chase proof run
Prove the follow-up loop before wider setup.
Admin Chief starts with one approved chase. The output is a source-grounded tracker, draft pack, and no-send approval log that a team can inspect before committing to fixed setup or a managed rhythm.
An expected-vs-received queue with owner, deadline risk, source excerpt, and next action.
Routine chase, firmer second chase, escalation note, and internal handover wording.
No client-facing messages leave Admin Chief without explicit human approval.
What the proof run includes.
The first run is intentionally narrow. It answers whether the chase is recurring, whether the evidence is clear enough, and whether the prepared draft matches the team’s approval standard.
1
Approve the source
Pick the label, folder, thread, date window, or export that is safe to review. Exclusions are recorded first.
2
Extract expected vs received
Admin Chief separates received evidence from missing items and avoids treating professional judgement as automation.
3
Prepare reviewable output
The team sees the tracker rows, source excerpts, deadline risk, draft wording, and no-send decision log.
Boundaries stay visible.
- Admin Chief handles admin follow-up and record chasing, not legal, financial, HR, insurance, tax, freight, or accounting advice.
- Payment links are used after fit and scope are agreed, not as a blind checkout before context.
- Public API, MCP, webhook, and export access remain roadmap until implemented and verified.
- Private dashboard, setup, review, and API routes stay noindex and no-store.