OpsCore // CACFP

Every site, every meal, every month.
Claim-ready.

For sponsors running the Child and Adult Care Food Program across many sites. The claim assembles itself from records you already keep.

Claims — assembled from the records
The OpsCore CACFP claims screen for August 2026, showing supported and claimed meals agreeing at 700 with nothing disallowed, and a reconciliation table tracing one line back to the forty meals over fifteen services it was counted from.

August 2026 · Bluebonnet Child Nutrition

Supported by records

700 meals

counted at the point of service

Claimed for reimbursement

700 meals

assembled from those same counts

Disallowed on review

None

nothing to write off, nothing to repay

Traced to fifteen services across four sites, menus checked against 7 CFR 226.20 and receipts that add up to their own lines. Demonstration record, against this site’s invented sponsor.

The whole program, site by site.

From the route that delivers the meal to the claim that reimburses it.

Sites and routes
Every site you sponsor, the routes that serve them and the delivery schedule behind each one. Bulk import when you are onboarding a lot of them at once.
Participants and enrollment
Who is enrolled where, kept against the site that claims them.
Meal counts
Counts taken at the point of service and totalled against the meals the site is approved to serve.
Menus and cycle menus
Build a cycle menu once, run it across sites, and print it when a monitor asks for the week you served.
Receipts, rates and costs
Reimbursement rates, receipts and cost records held against the claim they support.
Monitoring and reviews
Your own review forms, the visits carried out against them, and what each one found.
Claims
The month assembled from the counts and records already in the system, rather than re-keyed from a spreadsheet at the deadline.
Documents and records
The document set each site has to hold, and whether it actually holds it.

This is the actual product.

Every screen below is the running application against its demonstration sponsor. Nothing here is a mockup.

The roster, with eligibility in force

Every participant, their current site and the eligibility determination that applies today — with how it was determined, because a household application and a direct certification are not the same evidence.

Participants
The OpsCore CACFP participants roster listing each child with a local identifier, date of birth, current site, program type and eligibility category, showing free, reduced and area-eligible determinations and the source of each, above counts for participants, currently enrolled and annual updates overdue.

Meal counts at the point of service

A site and a service date, and the counts recorded as meals are served — against the attendance recorded for that day, which is the ceiling they are checked against.

Meal counts
The OpsCore CACFP meal counts screen with a site, service date and meal service picker, above a table of recent meal services across every site showing the date, site, meal, number of meals and whether the record is draft or certified.

Menus checked against the meal pattern

The kitchen’s cycle menu, and the dated per-site record that supports a claim. Each one is checked against 7 CFR 226.20 — a menu short of a component is told which one.

Menus · 7 CFR 226.20
The OpsCore CACFP menus screen showing the published cycle menu with its last-updated date, counts for menus recorded, menus short of the meal pattern and menus without a production record all reading zero, and a table of daily menus by date, site, meal and age group each marked complete against the meal pattern.

Receipts that have to add up

Cost by site, and every receipt against the sum of its own lines. A difference is reported as a transcription error to find rather than a total quietly adjusted to match.

Receipts
The OpsCore CACFP receipts screen showing total spend, food and milk cost, receipt count and how many do not reconcile, above a cost-by-site breakdown separating cost charged to no site from cost no line accounts for.

Built for many sites

Sponsors carry the claim for every site they serve. Routes, schedules and bulk site import exist because the unit of work is a network, not a building.

The claim is a by-product

Counts, menus and receipts are recorded where they happen. The month is assembled from them rather than rebuilt in a spreadsheet the week it is due.

Monitoring on your forms

Review forms are yours to build. Visits are recorded against the form you actually use, and what they found stays with the site.

Licences assigned through enquiry.

Licences are assigned through enquiry, with certificates issued alongside them. Tell us how many sites you sponsor and we will size it with you. Current per-site figures sit with the rest of OpsCore pricing.

Straight answers.

Who is this for?

Sponsors of the Child and Adult Care Food Program running multiple sites: the organisation that carries the claim and the monitoring obligation, not a single centre keeping its own paperwork.

How does a claim come together?

Out of what is already recorded. Counts are taken at the point of service, menus and receipts sit against the sites that served them, and the month is assembled from those records rather than re-entered at the deadline.

Can we use our own review forms?

Yes. Review forms are yours to build, and the visits your monitors carry out are recorded against the form you actually use, not a generic checklist.

How are licences and certificates handled?

Licences are assigned through enquiry, with certificates issued alongside them. Tell us the sites you sponsor and we will size it with you rather than making you guess from a table.

Bring us one month of your program.

We will walk a real site from meal count to claim and show you what is left to do at the deadline.

Enquire about CACFP
Multi-site sponsors Per site Term licence