ESA for Families · AthlyticZ

For families

A school year that ends with something to show.

The High School Masterclass is what we built for high school students: a live session every week in real data science, taught by working practitioners, in the same professional environment our adult programs use.

The Coaching Room

Practice with somebody on the other side of the table.

AI coaching is built into the practice sessions. The coach takes the stakeholder's part, and your student works the problem in whatever medium the question actually calls for.

What that means literally: AI coaching built into practice sessions, stakeholder simulation where a student presents a plan and defends it when someone pushes back, and no-code visual builds alongside code builds, because plenty of real work is a plan rather than a script.

AI as copilot, not autopilot. Students are taught to direct the machine and defend the output, which is the habit that outlasts whatever tool they end up using.

The year

Three terms, and what exists at the end of each.

Shaped like a school year because that is the rhythm you are already planning against. Every phase names the thing that appears on the screen, not the topic it came from.

Preseason · Weeks 1 to 6

First code, first answers

A student who has never written a line of code opens a notebook in the browser and gets a real answer out of real data in the first session.

In these weeks
  • Python from the beginning, in a browser, nothing to install
  • Reading a real sports dataset and cleaning it
  • Asking a question of the data and answering it
  • Charts that make a point rather than decorate a slide
  • Weekly live session, recorded, so a game or a meet costs nothing
What exists at the end
A first Python notebookA cleaned datasetA first chart
By the end of preseason

Open a dataset nobody has prepared for them and find something in it worth telling you about.

On an application or a resume

Writes and runs Python. Works with real data rather than classroom exercises. This is the line that separates a student who has taken a coding class from one who has used code to answer a question.

Regular season · Weeks 7 to 18

A real project

The stretch where it stops being exercises. One sports data project, carried from a question through to a finding, at their own pace.

In these weeks
  • Statistics that hold up: averages, rates, and what they hide
  • Working with a season of data rather than a teaching sample
  • Version control, so work is never lost and progress is visible
  • Writing up a finding for someone who does not code
  • Monthly group build alongside the weekly session
What exists at the end
A finished sports data projectA written finding
By the end of the regular season

Explain a result to a room, including what it does not prove.

On an application or a resume

An independent research project with a written conclusion. Something concrete to name in an essay, an interview, or a supplemental question, with a link attached rather than a claim.

Playoffs · Weeks 19 to 30

Something to show

The part that outlasts the school year: a page they can send to anyone, with real work on it and their name at the top.

In these weeks
  • Building and deploying a shareable portfolio page
  • Presenting the work out loud and taking questions
  • A second project chosen by the student, not assigned
  • Communicating technical work to a non-technical audience
What exists at the end
A deployed portfolio pageA presented project
By the end of the season

Send a link to a teacher, a coach, or an admissions reader and have it stand on its own.

On an application or a resume

A live portfolio URL with two projects on it. The rare thing a high school student can put on an application that a reader can actually open and check.

Simulated technical questions

The question arrives the way it actually arrives.

Someone walks up and wants an answer. Practice runs on a clock, in the same provisioned environment the sessions use, and the review afterwards is about the thinking rather than the answer.

Practice runs in a timed provisioned environment, the same one the sessions run in. You get a real task and a clock, not a quiz. The session is recorded, and the review afterwards is about the reasoning you showed rather than whether you reached the expected answer.

Scenarios are written the way the question actually arrives
  • Your coach asks: are we actually better this season, or did we just play easier teams? You have twenty minutes and the schedule data.
  • A teammate says the new drill is working. What would you look at to find out whether that is true?
  • Explain your chart to someone who has never seen this data before, in under a minute, without using the word average.
Communication training

Explaining it is half the skill, so we teach it.

Most technical programs stop at the code. This one does not, because the students who go furthest are the ones who can say what they found and why it matters to somebody who does not code.

Technical writing is taught as its own skill: writing up a finding so a reader can follow the reasoning, state what the work shows, and state what it does not. Presenting to a non-technical audience is practised out loud, with questions afterwards, because a result nobody understood is a result nobody used.

These are the parts that transfer to every subject, every application essay, and every job they will ever have, whether or not they end up writing code for a living.

Why this one

The skills schools are still catching up to.

Students work in Python and R, the two languages this field actually runs on, in a provisioned professional environment that opens from a browser. Nothing to install on a school laptop and nothing for a parent to configure. They use version control from early on, which is how professional work is kept and reviewed everywhere, and they practise explaining technical work to people who do not code, which is the skill that survives whatever happens to any particular tool.

Every session is taught live and recorded, so a student who misses one for a game or a meet has not missed the material. What they finish with is showable work built on professional tools, and we describe what they build rather than where it takes them.

The skills a student builds here are the same foundations our Career Programs are built on, taught at a high school level.

The funding

What we can tell you, and what we cannot.

Education savings account programs differ by state and their rules change without notice to vendors. Here is exactly where we stand.

Arizona. We are an approved ClassWallet vendor, which is the platform Arizona's Empowerment Scholarship Account program pays through. We provide an itemized invoice separating live instruction from curriculum, which is the documentation these programs ask for.

Florida is pending. It runs through a different administrator and a different marketplace. We are working through it and it is not live yet. That is the whole of what we can say today.

Whether your account covers it is your program administrator's decision, not ours. We would not want to speak for them, and a vendor who guesses wrong costs a family money. Ask them, and we will provide whatever documentation they need.

We describe what your student builds. We do not promise admission, a scholarship, or a job. The program is a defined pathway to a verifiable digital credential. We provide completion records. We are not a degree-granting or accrediting institution, and we make no claim about admissions, scholarships, or placement.

Every live room, the recordings, the code, and the environment, behind one door.

Join the Masterclass

Talk to us about your student.

A short call: what they are interested in, where they are, and whether this is a fit. Enrolment is handled on that call.