A 45-Point YMCA Job Posting and the Architecture of a Swim Pipeline

Across forty-five information points in a job description for an assistant director of competitive swimming, not one line mentions stroke rate, underwater kick distance, or how to pace the final two laps. I read it twice, underlined every clause, and did what I always do: two columns, one for what the text says, one for what it leaves empty. By the second page I realised I had asked the wrong question. This document does not describe a swimmer. It describes a training system.

My trade is reading footprints in data, and most footprints I have read came from GPS units, expected-goals tables, training-load logs. This time the footprint sat inside an administrative document. A small GPS deviation was enough to teach me that verification is everything. With a job posting, the thing to verify is not a wrong number but the boundary between what was written and what was left out.

The role is assistant director of competitive swim at a YMCA site. The holder reports directly to the Association Director of Competitive Swimming and takes dotted-line direction from the Head Age Group Coach. Below them sit the coaches from the Age Group Select level upward, under direct supervision. The pathway is spelled out: from the age-group select squad up toward national-team readiness. Two tiers are named, Silver and National Team.

The document does not stop at an org chart. It lists responsibility for tracking swimmer results, reviewing meet and practice data, building and standardising testing protocols, rolling out a unified coaching philosophy across sites, developing athletes over the long term, training successor coaches, overseeing a budget, and leading a recruitment and retention strategy that runs from YMCA swim lessons, summer and recreational leagues, through to outside community pipelines.

One detail made me slow down more than the rest: the coaching staff includes both full-time and part-time positions. Another line stopped me longer still: succession planning. When an organisation writes the word "succession" into the duties of an assistant role, it is admitting that turnover is a permanent variable, not an accident.

What holds my attention is how the document defines the cause of performance. When an organisation states that the role must track swimmer results and periodically review meet and practice data, it is saying something I can translate into my own language: coaching decisions will rest on a record, not on memory. That is a methodological claim, and it deserves to be read more seriously than the soft-skills section.

Eight years ago, when the domestic league was suspended by the pandemic, I spent seven months building a recovery-index model on GPS data from three hundred and sixty-five players across three seasons. Step one was not choosing an algorithm; it was persuading people that high-intensity distance had to be logged every session, that accelerations had to be counted, that injury history had to be stored in codes. Without a record, a model is an empty spreadsheet decorated in colour. The pandemic taught me to measure a league by recovery indices rather than by points. It also taught me that data infrastructure always runs at least one season ahead of data analysis.

Read through that lens, this posting shows a programme that has moved past the stage where most youth swim centres in our region remain stuck. Testing protocols appear as a standalone duty, not as an ad-hoc measurement session before a meet. The coaching philosophy is required to be standardised across sites, meaning a swimmer's results must be readable on the same ruler wherever they train. Individualised plans and progress tracking appear together, and that pairing is the valuable part: individualisation without tracking is only a feeling, tracking without individualisation is only a scoreboard.

I trust numbers, but only after they clear three rounds of checks. The first round is what the document says. The second is what it does not say. The third is who is accountable if my assumption is wrong. Here, the first round gives me a two-line reporting structure: directly to the association director, indirectly through the head age group coach. That arrangement spreads technical authority across two ends. In my own risk table, a national-team pathway dependent on a single coach always sits at medium probability and high impact. A shared-responsibility structure does not remove the risk; it only slows it down and makes it visible.

The second round made me lower my voice. Nowhere in the document is there a line on anti-doping, competition rules, eligibility, or equipment. That silence is easily read as a gap, and I once made exactly that mistake in a transfer analysis. In 2026 I advised a club against signing a foreign striker because his eighteen goals came from just eleven point two expected goals, a conversion rate nearly double the league baseline. The lesson stands: a document missing a section does not mean the organisation is missing a process. It only means the document's scope is narrower than my question.

The closest thing to technical content in the whole text is the phrase "testing protocols". A properly built testing protocol in competitive swimming usually measures underwater kick distance after starts and after each turn, stroke rate at threshold speed, strokes per length, and the stability of stroke rhythm in the closing laps. That is my inference, not the text, and I have logged it in the low-confidence column. I do not build a model on a phrase. This caution is not there to look tidy; it is the discipline that keeps me reading data correctly ten years from now.

The strongest temptation when holding a job posting is to turn it into a statement about the future. A new title does not prove a programme is expanding. It only proves that a block of duties has not been fully allocated to whoever currently holds them. Correlation is not causation, and a posted role is not a guaranteed performance cycle.

I set my own falsification conditions. If no similar roles appear at other sites in the same network within six to twelve months, my whole-network professionalisation hypothesis collapses and the posting is just a single staffing gap. If sites do post but publish no shared testing index, the "data infrastructure leads" hypothesis weakens considerably. I wrote both conditions down before drafting, so that memory could not later talk me into my own conclusion.

The recruitment and retention duties run from swim lessons, through summer and recreational leagues, to outside community pipelines. A programme that has to spell out retention strategy at both ends – athletes and part-time coaches – is usually one that has already felt attrition. I read that as a neutral signal on performance and a very notable one on organisation.

Data does not tell stories; it records everything so that I can tell them myself. This job description promises no medal. It leaves three footprints for anyone patient enough: how many similar roles appear in the next half year, whether a shared testing index surfaces, and how many part-time coaches stay through two seasons. Whoever reads all three will know whether the system is growing or merely changing its shirt.