← All features

Front-of-house · Meals

Meals served, who served them, and who got fed.

Congregate meals at the front desk, age eligibility verified at scan, dietary flags carried into the kitchen, contribution suggestions handled with dignity. The daily count is on your cook's screen by 11; the quarterly funder roll-up is already done.

What it does

The capabilities that earn this module's place.

Meal sign-up

RSVP at the front desk or the day before.

Members RSVP for tomorrow's lunch at the front desk on their way out today, or from the member portal anytime before the kitchen cutoff. The cook sees the live count throughout the morning; cutoff time is configurable per meal.

  • Same-day or next-day RSVP
  • Live count visible to the kitchen
  • Configurable cutoff per meal

Dietary flags

Allergies in the kitchen view.

Dietary restrictions live on the member record — gluten-free, lactose-intolerant, vegetarian, nut allergy, kosher, halal, custom. When a member RSVPs, the flag carries into the kitchen view automatically. The cook sees "two GF, one nut allergy" before service.

  • Per-member dietary flags
  • Custom dietary categories
  • Kitchen view aggregates flags by meal

Age eligibility

Title III at scan, not at audit.

For congregate meal programs with age-eligibility requirements (Title III is 60+), the system checks at sign-up and at scan-in. Members under the threshold get a clear path (paid guest, family member, drop-in non-eligible) — no awkward conversation at the door.

  • Age verified at sign-up and scan
  • Guest, family, and non-eligible paths configurable
  • Funder-required age breakdowns in reports

Contributions, handled with dignity

Suggested contribution, never required.

Congregate meals are donation-supported in most senior-center programs. The system handles suggested contributions without putting members on the spot — anonymous drop boxes, kiosk contributions, or recurring monthly gifts. Contribution rates roll into the funder report without identifying individual donors.

  • Anonymous and identified contribution paths
  • Suggested-amount messaging without demand
  • Aggregate reporting without donor identification

A workflow walkthrough

Tuesday's lunch service, from RSVP to roll-up.

The morning of a congregate-meal service at a senior center. The kitchen, the front desk, and the AAA report — all on the same data.

  1. Monday, 4:00 PM — RSVPs roll in. Patricia signs up for Tuesday's lunch as she heads out from Bridge. Karen RSVPs from the portal at home. By 5 PM, 47 members are signed up; the cook can see the live count on her kitchen tablet.

  2. Tuesday, 7:00 AM — Cook gets her view. Total count: 52 (five more added overnight). Dietary breakdown: 4 gluten-free, 1 nut allergy, 2 kosher, 3 vegetarian. The cook prints the kitchen sheet; menu adjustments locked.

  3. Tuesday, 11:45 AM — Service line moves. Members tap in at the meal kiosk on their way through the line. Each tap logs the meal as served and credits the suggested contribution if the member dropped it in the box. Age eligibility checked at scan — three guests pay non-eligible rates without holding up the line.

  4. Tuesday, 1:30 PM — Service complete. Total served: 50. Two RSVPs no-showed (logged for follow-up). Three guests served at guest pricing. Contribution box: $73. All in the day's record.

  5. October 1 — Quarterly report runs. The AAA Q3 congregate meal participation roll-up generates: total meals served, age-eligible meals, dietary breakdown, average daily attendance, contribution totals. The director hits send Friday afternoon.

Questions, answered

What we hear before customers sign up.

See meals run for your kitchen.

Set up your workspace this morning. Configure your meal program this afternoon. Run tomorrow's lunch with live counts on the kitchen tablet — and watch the Q3 packet write itself.

14 days free · Card required · Cancel anytime