What August Setup Really Costs a School-Age Program

The August nobody puts in the budget

Picture a program office in the first week of August. The school year is close. Registration forms are stacked on the desk. Somebody reads a form, types a child's days into the schedule, then opens a second spreadsheet and types the same days again so the bill will come out right. Then a third file, so the site coordinator has a roster. Then the next form.

It is quiet work, and it is necessary work. It is also expensive, in a way that almost never shows up as a line in anyone's budget. It just looks like the office being busy in August.

The question worth asking is not whether August is busy. It is how much of that busy is setting up the year, and how much is telling your own software something it should already know.

The numbers from a program we built alongside

At a YMCA school-age program we built alongside, August setup had a real cost. You can read how we built it on our process page. Every August, it took 3 people 3–4 weeks to set up the school year. That is 360–480 hours of staff time, spent before the first child walked in on the first day.

Now 1 person does the August setup in 3 weeks. That is 120 hours, and up to 75% less setup time.

Those hours did not come back because anyone learned to type faster. They came back because so much of what filled August was never really setup. It was re-entry: the same facts, typed again, into another place.

The fastest data entry is the entry nobody has to make twice.

Where the August hours actually go

When you listen to how an office spends its setup weeks, the work sorts into a handful of jobs. You will probably recognise them:

• Typing a child's days, again. A parent writes the weekly schedule on a form, and the office types it in.
• Keeping the bill in step with the schedule. When billing lives in its own place, every schedule has to be entered a second time wherever the bill is figured.
• Building site rosters by hand. Coordinators need a current list of who is coming, with allergies and contact numbers, and someone has to assemble it.
• Answering the phone. Families call to change days they have just chosen, and each call means another round of edits in more than one place.
• Checking it all. Because the same fact lives in several files, someone has to compare them to find where they disagree.

Only a small part of that list is real setup: deciding the year's calendar, the sites, the days offered and the rates. The rest is the program repeating what it already knows.

Notice that none of those jobs is a mistake. Each one exists because the tools asked for the same information in more than one place, and a careful office gave the tools what they asked for. The cost is not carelessness. It is the shape of the software.

One fact, several homes

The pain point is August. The root cause is that a child's schedule lived in more than one place. Every place it lived had to be filled in, and every change had to be made in every place.

So the fix was never a faster way to type. It was fewer places to type into. In what we built for that program:

• Parents choose and change their own days online, so the office is not copying days from a paper form.
• A child's weekly days are set once and repeat. Nobody re-enters the same Tuesday and Thursday every week.
• The bill is built from the schedule, so the two match. There is no second sheet to keep in step.
• Days the program is closed are not charged, so the closed-day calendar does not need its own correction pass on every bill.
• A child who starts mid-week is billed that day for the days left in the week, with no hand calculation.
• Printable rosters for each site carry allergies and contact numbers.

The office still does August. Someone still sets up the year. But that person is setting up the year, not retyping it.

That is what we mean by software that echoes you. The program says a child's days once, and the bill is built from that same schedule.

How to count your own August

You can put a number on your own setup without any new software at all. At your next staff meeting, list every task your team does to get ready for the school year. For each task, write down three things:

• How many people work on it.
• How many weeks it takes.
• Roughly how many hours a week each of those people spends on it.

Multiply people by weeks by hours for each task, then add the tasks together. That total is what your August really costs.

Now go back down the list and mark every task where someone is typing information that already exists somewhere else: on a paper form, in another spreadsheet, in a binder at the front desk, in a parent's email. Those marked hours are not setup. They are re-entry, and re-entry is the part software built around your program should be absorbing for you.

Finally, ask your site coordinators how they get their rosters for the first day. If the answer involves someone retyping a list, count that too. And ask the person who answers the phone in August how many of those calls are about changing days. That is re-entry as well. It just arrives by phone.

Bring us your August

We would like to hear how your day really runs, starting with how your YMCA, park district or rec center gets ready for the school year. Walk us through your August, task by task, including the parts that live in spreadsheets and binders. We will show you what setup looks like when the program only has to say something once.

Request a demo