Skip to main content

Record a meal count

Denise has just finished serving breakfast at Claymont and has her paper count in hand. This page is how to get that count into PTRS, correctly attributed to her, for one site, one date and one meal period.

Use the header's + → Meal Count dialog. The three CACFP screens do not work

CACFP Meal Service, Meal Records and Point of Service Entry each offer a meal-count form, and all three fail on every save. The reason is the same in all three: the field that records who took the count.

A meal record must name a real staff member. The header's + → Meal Count dialog is the only surface with a staff picker, so it is the only one that sends a real staff member.

Full detail in What the other three screens do instead.

Before you start​

  • Know the site, the date, the meal period, the counts by age band and the staff member who took the count.
  • Have the menu items to hand. The dialog requires at least one.
  • One meal record per site, per date, per meal period. A second attempt is refused with a message naming the existing record and telling you to edit it instead.
  • If the meal was served more than 60 days ago you can still create the record, the 60-day window applies to corrections and deletions, not to creation.

Steps​

1. Open the dialog​

From anywhere in PTRS, press the + button in the header, then Meal Count in the menu that opens. The keyboard shortcut shown beside it is C.

The dialog is headed Log Meal Count, subtitled "Record a CACFP meal service. Counts are broken down by age group for federal reimbursement."

Every signed-in user sees this entry, whatever their role.

2. Location​

A dropdown of every site in your organisation, defaulting to the one selected in the header. Required.

Changing it clears the staff selection, because the staff list is scoped to the site.

3. Date, Meal Type and Recorded By​

FieldRequiredNotes
DateYesDefaults to today. Any date is accepted, past or future
Meal TypeYesBreakfast · AM Snack · Lunch · PM Snack · Supper. These five are the whole set
Recorded ByYesA dropdown of active staff at the selected site. This is the field that makes this dialog the only working path

If Recorded By is empty, the site has no active staff records, pick a different site or add the staff member in Staff first. Typing is not an option; it is a dropdown.

4. Counts by Age Group​

Three number boxes, each accepting 0 to 999:

  • Ages 5–8
  • Ages 9–12
  • Ages 13–18

A running Total: N meals appears beneath them. Saving with a total of zero shows a message asking you to enter at least one meal count, and nothing is sent.

These three bands are not the federal bands, and three other screens use three other sets

This dialog stores the three bands above by name. The federal meal pattern rules are keyed on four different, younger bands, 1 to 2, 3 to 5, 6 to 12 and 13 to 18, and PTRS's own programme age groups (which cover 5 to 7, 8 to 10, 11 to 13 and 14 to 18) map onto those, not onto this dialog's bands.

Nothing reconciles these different sets of bands. The total is correct, PTRS adds up every count it is given regardless of the label, but a breakdown by age band taken from these records will not line up with a federal meal pattern, and records created on different screens will not line up with each other. See the four age-group conventions.

Record the total accurately. Treat the band split as an internal note, and keep your paper point-of-service record.

5. Items Served​

A required box, placeholder "e.g., whole wheat bread, milk 1%, apple slices, chicken strips", with the note "Separate items with commas. Must meet USDA meal pattern requirements."

Items are split on commas, trimmed, and blank entries dropped. Saving with nothing left after that shows a message asking you to enter at least one menu item.

Nothing checks these items against the meal pattern, on this path

The note says the items must meet the federal meal pattern. This dialog never runs that check. The real meal pattern check exists, and only the two CACFP Meal Service and Meal Records composer forms call it, the ones that cannot save.

Even there, the verdict is shown once and thrown away: no meal record is ever marked valid by any path, and nothing stores the check's result against the record afterwards.

6. Save​

Press Save. The button reads "Logging…" while it works.

What the record is worth​

Worth being precise about, because this is a federal record:

What is stored correctly and durably. The organisation, the site, the date, the meal period, the counts, the menu items, the summed total, the staff member who took the count, and when it was entered. The action is written into PTRS's tamper-evident audit log. PTRS will not accept a second record for the same site, date and meal period.

What is not. The record is never marked valid, never priced, never carried into a claim, and never checked against a child's daily limit. Nothing in PTRS turns this record into money.

What happens after the save that reaches nobody. PTRS announces the new record on a CACFP notification channel that is never switched on, so the announcement reaches nobody watching a screen. It also quietly counts the save for its own internal statistics. See the module landing page.

What the other three screens do instead​

All three send their save to the same place PTRS keeps meal counts. All three fail. Knowing which failure you are looking at saves the time otherwise spent retrying.

Point of Service Entry​

The Record Meal Count form, subtitled "Point-of-service meal count entry." Six age bands: Infant, 1-2, 3-5, 6-12, 13-18, Adult.

It sends your sign-in email address in the field that PTRS expects to hold a staff record's id. PTRS refuses the request before it even looks at the rest of the form.

What you see: a red box reading "Failed to log meal count. Please try again." Retrying produces the same result every time.

The rest of the page is honest: the Daily Limits panel shows the site's real configured limits, and the Daily Meal Roster below it shows meal types and totals for today, despite its name, it is not a per-child roster and never lists a child.

The Log Meal Count composer on CACFP Meal Service​

Four age bands: 5-7, 8-10, 11-13, 14-18. It has a Validate button that runs the real meal pattern check and shows the verdict, the one place in PTRS where that check's result is put in front of a person.

It sends your organisation's own id in the field meant for the staff member, a placeholder the people who built this screen left in, by their own comment, until real staff identity was wired up. That value is well-formed, so PTRS accepts it as far as checking it against the staff list, and then refuses, because it does not match any staff member.

What you see: a toast reading "Failed to save meal record."

The Log Meal sheet on Meal Records​

Opened by the Log Meal button, or by a meal-period card. Same four age bands, same Validate button, same organisation id sent where a staff member is required, the same failure.

What you see: a toast reading "Failed to save meal record."

Checked against PTRS on 7 September 2026.