Head Start Programme Management Software: Why Eligibility, Screenings and the Non Federal Match Become Audit Findings

Why a federal review is the moment agencies discover their data is not one system

An agency gets notice of a federal monitoring review. The director calls the data manager, and over the next three weeks a team assembles evidence: eligibility determinations with the verification documents that supported them, proof that developmental and sensory screenings happened inside the required window after entry, attendance records with documented follow up for children with poor attendance, family partnership agreements with goals and updates, and the non federal share ledger with valuations that a reviewer will test. Every one of those exists. None of them exists in one place.

The eligibility files are paper in a locked cabinet at each centre. Screening results are in a health binder plus an email folder from the contracted screener. Attendance is in the child care system and the follow up calls are in a family advocate's notebook. In kind is a spreadsheet the finance director maintains from volunteer sign in sheets that arrive late and sometimes not at all. The Programme Information Report was assembled last year by exporting from three systems and reconciling in Excel over four evenings.

None of this is negligence. It is what happens when a programme is governed by detailed performance standards and the software available was built to a generic model of childcare. In the early childhood agencies we have worked with, the recurring cost is a data manager spending a third of the year on reporting assembly, plus the tail risk that a single missed deadline becomes a finding with a corrective action plan attached to it. The finding is the expensive part. A corrective action plan consumes leadership attention for months and, in the worst case, affects your standing at the next competitive cycle.

Problem 1: eligibility and selection is a scoring model, not an application form

Head Start does not simply enrol whoever applies. Applicants are ranked against selection criteria your governing body and policy council approved, weighting factors such as income relative to the poverty guidelines, homelessness, foster status, disability, and locally chosen priorities. Categorical eligibility applies to certain families regardless of income. There are limits on how much of your enrolment can be over income, and a required share of slots for children with disabilities. Each of those is a rule that has to be applied consistently and evidenced.

Generic childcare software has an application record and a waitlist ordered by date. That is not a selection process, it is a queue, and the difference is exactly what a reviewer tests. Agencies bridge the gap with a spreadsheet where somebody types points, which means the scoring logic lives in a formula that changes when the policy council revises criteria and nobody versions it.

A build treats selection criteria as configured, versioned rules. An application produces a score with a visible breakdown showing which criterion contributed what, the verification documents attach to the specific criterion they support, and the ranked list regenerates automatically when a slot opens. When criteria change, the new version applies from a date and the old determinations remain explainable under the rules that were in force. That last part is what turns a reviewer conversation from a discussion into a printout.

Problem 2: the screening clock starts the day a child walks in

The performance standards require developmental, sensory and behavioural screening within a defined window after a child starts, along with a schedule of health determinations, immunisation status and follow up when a screening indicates a concern. The window is short, the children arrive continuously through the year, and the people who do the screening are often contracted or shared across centres.

What goes wrong is not that staff ignore deadlines. It is that the deadline lives in a person's memory and the child's start date lives in a different system from the screening result. A build computes every due date from the enrolment date the moment a child is enrolled, shows a centre level view of what is due this week, escalates before the deadline rather than reporting after it, and requires the follow up loop to be closed when a screening flags a concern, because an unclosed referral is one of the most common findings we see agencies carry.

The same engine handles immunisations against the schedule your state requires, physical and dental determinations, and the exceptions that legitimately exist. The value is not the dashboard. It is that a family advocate walks in on Monday and sees six names rather than reconstructing the picture from a binder.

Problem 3: attendance triggers a required intervention, not a report

Head Start treats attendance as a programme obligation. When a child's attendance drops, staff are expected to contact the family, understand the barrier, and support a return, and when average daily attendance across the programme falls below the threshold in the standards, the agency has to analyse causes and act. That is a workflow with evidence, not a percentage on a dashboard.

Most systems record attendance and stop. The follow up happens by phone and gets written in a notebook or an email, which means at review time the agency can show the attendance rate but not the intervention. A build makes the contact a record: triggered by the absence pattern you define, assigned to the family advocate, capturing the barrier from a coded list plus free text, linking to transportation or health issues already known about the family, and rolling up so the director can see whether the programme's attendance problem is transport in one centre or illness across three.

Problem 4: non federal share is accounting that nobody owns

The required non federal share, commonly satisfied through volunteer time, donated space and in kind goods and services, is one of the most reliably painful parts of running a Head Start programme. Volunteer sign in sheets arrive on paper, weeks late, sometimes illegible. Valuation rates have to be defensible and donated space needs a basis. The shortfall becomes visible late in the budget period, which is exactly when it is hardest to close.

This is a straightforward build problem that packaged systems handle only partly. Volunteers and parents record hours on a tablet or phone at the centre with the activity coded, rates apply automatically from a rate table you can evidence, donated goods and space capture with the supporting documentation attached, and a running total against the requirement is visible to the finance director every week rather than every quarter. Agencies that implement this typically discover they were undercounting rather than short, because parent hours that were always eligible were never captured.

Problem 5: blended funding is where packaged systems actually break

Very few agencies run only Head Start now. A single classroom might hold children funded by Head Start, Early Head Start child care partnership, state pre kindergarten, and child care subsidy, plus a small number of privately paying families. Each funding source has its own eligibility rules, its own attendance and billing basis, its own reporting cycle and its own monitoring body. The child is one child. The funding is four rule sets.

ChildPlus is a mature product built specifically to the Head Start standards and it is the sensible choice for a single stream grantee. COPA has served agencies in this space for a long time as well. The limitation both share, and it is a design consequence rather than a flaw, is that they model the programme they were built for. When a child carries two funding sources with different attendance definitions, when state pre kindergarten requires a different assessment instrument on a different cycle, or when subsidy billing has to reconcile against attendance recorded for a different purpose, agencies end up running the packaged system plus a second system plus the reconciliation spreadsheet that quietly becomes the real source of truth.

A custom build starts from the child and attaches funding sources as time bounded enrolments, each with its own rules, its own required documentation and its own reporting outputs. That single modelling decision is usually the reason an agency calls us, and it is the one thing that cannot be configured into a product built around one funding stream.

What this costs and how long it takes

A first release covering eligibility and selection scoring, enrolment, attendance with follow up workflow and screening deadline tracking runs $60,000 to $130,000 and ships in 12 to 18 weeks. A full platform adding health and immunisation records, family partnership agreements and goal tracking, non federal share capture and valuation, classroom ratio and staffing, transportation, and Programme Information Report assembly runs $150,000 to $350,000 phased over 6 to 12 months.

What drives cost up here: the number of funding streams, since each is its own rule set and its own reporting output. State specific requirements, because a state pre kindergarten programme brings its own assessment and data submission format. Integration with an assessment tool your teachers already use, with your accounting system for the match ledger, and with a state subsidy portal if you submit attendance electronically. Number of centres and their connectivity, since offline capable attendance changes the app architecture.

What keeps it down: starting with eligibility, enrolment, attendance and screenings for the Head Start stream only, then adding the blended funding logic once the core is live. Also, be realistic that federal procurement standards under the Uniform Guidance apply to this purchase, so build the competition and documentation into your timeline rather than discovering it after you have chosen a partner.

Build versus buy, and when buying is the right call

Buy if you are a single funding stream Head Start or Early Head Start grantee under roughly 400 slots with stable operations. ChildPlus is built to the standards, is widely used, and will cost a fraction of a build. Spend the difference on family advocates. Buy if your leadership team is mid transition or your data practices are not yet consistent, because custom software will faithfully reproduce whatever process you actually have, including the broken parts.

Build when two or more of these are true. You blend Head Start with state pre kindergarten, subsidy or partnership funding and are running two systems plus a reconciliation spreadsheet. You operate across multiple counties or states with different requirements. Your data manager spends more than a third of the year on report assembly. You are carrying a corrective action plan from a review, which is the moment the cost of the current process becomes concrete. Or you deliver services beyond the standard model, for example home based programming, migrant and seasonal services or an early intervention partnership, where the packaged model needs constant workarounds.

How to choose a developer for Head Start software

Ask whether they have read the performance standards, and then ask them how they would version selection criteria. The right answer involves configured rules with effective dates so that a determination made last year remains explainable under last year's rules. A developer who proposes hard coding your current criteria has not understood that your policy council will change them.

Ask how they model a child with two funding sources. If the answer is a field on the enrolment record, they will rebuild it in month six. Funding needs to be a time bounded relationship carrying its own rules.

Ask what they have integrated by name and how they would produce the Programme Information Report. Assessment tools, immunisation registries, accounting systems and state subsidy portals are all specific problems.

Ask who owns the code and settle it in writing before kickoff, and check that the arrangement satisfies your federal award terms. You should hold the repository, the cloud accounts and the right to hire another firm. At Digital Heroes the client owns everything from the first commit. Given that this system holds children's health data and family income documentation, also ask specifically about encryption, role based access down to the centre level, and retention policy, and expect them to raise it before you do.