The Coach’s Time Audit

Why

Pain quantification with maths is a locked copy technique (“90 minutes building a session plan every week” beats “planning takes too long”). A calculator that turns a coach’s own answers into their personal number (“you will spend X hours this season planning sessions”) makes the drowning concrete and personal, and FootballGPT is the direct fix. Lane = The Agentic Coach; funnel product = FootballGPT. Cheapest build in the family.

What

Static page at 360tft.co.uk/time-audit/:

• Inputs: sessions per week, minutes planning each, matches per month, admin minutes per week, weeks in season.
• Output: honest arithmetic only — total hours per season, split by category, plus one true comparison anchored in the user’s own numbers (e.g. hours vs full working weeks). No invented benchmarks, no fake averages.
• Shareable result: a clean stat line the coach can copy or screenshot (self-attributing with the 360tft.co.uk URL on the card).
• CTA: FootballGPT, framed on the planning line item only (the part it genuinely reduces). UTM params per quiz-family convention.
• Free Gumroad companion: “The Coach’s Time Audit worksheet” (printable version of the same audit for club coach groups). Listing copy drafted; KEVIN creates the listing; claims tagged for a hub sequence (follow-up).

Scope

In: page, calculator, share card, Gumroad listing copy draft, free-resources entry, router-quiz destination addition. Out: Gumroad listing creation (Kevin), hub sequence seed (follow-up), analytics loader changes (site-wide gap tracked separately).

Never-list

No fabricated averages or “coaches like you” statistics; the only numbers on screen are ones derived from the user’s inputs. Standard voice rules apply.

Proof before Shipped

Live 200; the arithmetic spot-checked by hand for 3 input sets; grep sweeps clean.

Note (mirrored into this repo 2026-07-25): this PRD is owned and tracked canonically in 360tft-hub/docs/prd/, per the Hub_ prefix and the PRD Naming & Per-Product Queues convention in that repo’s CLAUDE.md. It is copied here only so this repo’s pre-commit Gate 1-3 PRD check has a local artefact to point at, since the implementation (time-audit/index.html) lives in this repo (360tft/360tft) while the PRD process lives in the hub. Treat the hub copy as the source of truth for status changes.

Expected Experience

• Job: a coach answers six honest numbers and sees a real hours-per-season total, split by category, in under a minute.
• Peak moment: the total-hours card and the “X full 8-hour working days” comparison, the first time the coach sees their own planning time added up.
• Visual bar: matches the site’s established layout: null quiz pattern (which-product/, coaches-compass/day-1/) — purple/red brand palette, card-based results section, no new design system.
• Copy bar: helpful peer voice, no hype, no fabricated benchmarks; the only numbers shown are the user’s own arithmetic plus two disclosed constants (52/12 weeks-per-month, 8-hour working day).
• Never-list: no invented averages or “coaches like you” statistics; standard British English / no em dash / no emoji rules.
• Proof required: live 200 on /time-audit/; arithmetic hand-traced for 3+ input sets; grep sweeps for emoji/em dash/banned words/off-list URLs clean.
• Shareable test: the copy-result stat line is genuinely something a coach would post (specific numbers, not a generic claim) — pass.
• Embarrassment test: no claim on the page is unverifiable or invented — pass (every figure traces to a user input or a disclosed constant).

Honesty artifact

Stated assumptions (decided during implementation, not spelled out in the PRD body above):

• The PRD lists five inputs but “matches per month” has no paired time figure, and inventing a per-match minutes average would break the Never-list. Added a sixth input, “how long does a matchday take you, start to finish (minutes)”, so matchday hours are still arithmetic from the user’s own numbers, not an assumed constant. Documented inline in the page’s own copy so it doesn’t read as an unexplained extra question.
• Converting “matches per month” and “weeks in season” into a single season total needs a months-per-season figure, which the PRD doesn’t collect. Used the calendar constant 52/12 (weeks per month) to derive it. This is a calendar fact, not a coaching benchmark or invented average about coaches, so it doesn’t trip the Never-list.
• The “one true comparison anchored in the user’s own numbers” is total hours divided by a standard 8-hour working day. The PRD’s own example text (“hours vs full working weeks”) pointed at exactly this kind of comparison; 8 hours is a defined, universal unit, not a claim about what coaches typically do.
• CTA is framed on the planning line only, per PRD: the button text reads “Try FootballGPT for planning” and the paragraph immediately above it names the planning figure specifically, not the season total.
• Router-quiz destination addition (PRD’s “in scope” list) was NOT done. The parent task explicitly instructed: never touch which-product/ (owned by a sibling PR), and that instruction overrides the PRD’s own scope where the two conflict. Flagging for whichever PR currently owns which-product/ to add /time-audit/ as a routing destination.
• Added a free-resources.md entry (in scope, not excluded by the parent task’s do-not-touch list) linking to the new page.

Known gaps (explicitly out of scope for this PR):

• No Gumroad listing created (Kevin’s action, per PRD scope). Listing copy drafted at docs/gumroad-listings/time-audit.md.
• No hub nurture sequence for gumroad:time-audit-worksheet claims (follow-up once the listing exists, per PRD scope).
• No analytics event firing: this site has no working gtag loader anywhere (checked every _include and _layout; none load a gtag script even though google_analytics is set in _config.yml). Same pre-existing, site-wide gap noted in the which-product/ and coaches-compass/ PRDs. UTM params on the outbound FootballGPT link are the only campaign-attribution signal available.
• No local Jekyll build run (no ruby/bundle/jekyll on this machine). Verified instead with node scripts/manual-html-validator.js and manual front-matter/permalink comparison against working layout: null pages (which-product/index.html, coaches-compass/day-1/index.html).