Program snapshot: a quick tour of how you run school meals

• Tell me about the number of meals your district serves on an average school day, and how that changes over the month. Options: Under 1,000 meals/day, 1,000–5,000 meals/day, 5,001–15,000 meals/day, More than 15,000 meals/day
• Describe your current point-of-sale setup across sites, including terminals, cloud services, and any offline modes you use. Options: Legacy countertop terminals, Cloud-based POS with tablets, Mobile or handheld POS devices, Mixed setup across sites, Not sure, I need to check
• Who on your team is responsible for eligibility decisions and who files the monthly reimbursement claim? Options: Child nutrition director, Food service manager, Business office / fiscal, IT, Third-party eligibility processor, Other
• Walk me through the most recent state audit or claim review you experienced, what triggered it, and the result.
• How frequently do you finalize menus and update production forecasts each month? Options: Weekly, Biweekly, Monthly, Quarterly, Ad hoc
• Is there an unresolved audit finding or outstanding corrective action that would prevent you from moving forward with a new vendor? Options: Yes, No, Unsure

Where the process is most fragile, and what that costs you

• If a single compliance or claiming failure this year could put reimbursements at risk, which one would it be and why?
• When claiming errors happen, which downstream task suffers first, for example reimbursements, financial reconciliation, or state audit preparation? Options: Claiming and reimbursement, Financial reconciliation, State audit preparation, Staff scheduling, Menu planning
• How many audit findings or corrective actions has your program had in the last three years? Options: None, 1–2, 3–5, More than 5
• What operational step breaks most often when point-of-sale slows or goes offline during peak meals?
• Which element of menu planning creates the largest forecast uncertainty, recipes and yields, student participation, or special diets and allergies? Options: Recipes and standardization, Yield and waste rates, Predicting participation, Special diets and allergies, Other

Alternatives on the table and reasons to stay or switch

• Who else are you actively considering to address these issues, and what draws you to them?
• List the categories of alternatives you have evaluated so far, for example your incumbent vendor, an internal build, or a different software provider. Options: Incumbent vendor, Another software provider, Internal development, State-provided solution, No change / existing process
• What would have to be true about your current process for you to keep it in place for another school year?
• Has anyone on your team proposed solving these problems by building or extending internal tools rather than buying? Options: Yes, a formal proposal exists, Yes, discussed but no formal proposal, No one has proposed an internal build
• Which vendor deliverables or guarantees would prompt you to switch vendors immediately? Options: Guaranteed claiming accuracy or remediation, SLA for POS uptime, Clear data migration plan, Price or payment flexibility, Local support and training, Other
• Name the shortcoming in a vendor response that would cause you to rule them out today.

People who will approve, influence, or block progress

• Identify any person or group who could block the project if their concerns are not addressed, and explain why.
• List the functions that will need to approve the project, such as child nutrition, finance, IT, procurement, or school leadership. Options: Child nutrition, Finance / business office, IT, Procurement, School principals / site leadership, Other
• Walk me through who manages student data sharing agreements and who can authorize data extracts.
• Tell me which budget owner controls funds for software and hardware purchases and how they prefer to be engaged. Options: Child nutrition budget, District business office, Grant-funded, Site-level budgets, Other
• If the pilot proves the expected results, what final approval or contract signature will be required to expand district wide?

Readiness risks that could derail implementation

• Point to the integrations or data handoffs you expect to be the highest risk during implementation and explain why.
• Select the category that best describes your student information system across most sites. Options: Hosted SIS with API, Export-only SIS, State-managed SIS, Highly customized SIS, Multiple SIS across sites
• Do you have a current inventory of POS terminals and models for each site available to share? Options: Yes, inventory complete, Partially documented, No inventory available, Unsure
• Rate how clean your eligibility data is and list the most common issues, for example duplicates, missing case numbers, or inconsistent fields. Options: Very clean, Some cleanup needed, Significant cleanup required, Not usable without major work
• Identify who on your side will provide API credentials or scheduled file extracts and whether they are typically available on request.
• Would a critical integration being unavailable for more than 30 days stop the project? Options: Yes, No, we can work around it, Depends on which integration

What success looks like in measurable terms

• Point to the single measurable outcome that must improve first for this project to be a clear win for your program.
• Select the KPIs you will use to judge success. Options: Claiming accuracy, Participation rate, Time per transaction, Food cost variance, Forecast accuracy, Staff training completion
• Provide the specific targets you would set for those KPIs in the first six months.
• Name the roles today that track these KPIs and the role that will own them after deployment. Options: Child nutrition director, Food service manager, Business office analyst, District operations, Other
• In the event the pilot fails to meet targets, is there a remediation budget or extension authority to address gaps? Options: Yes, budget set aside, No, not currently, Possible with reallocation, Unsure

Site-level logistics and calendar constraints

• Describe any site-level constraint that would stop a go-live on day one, for example restricted access, union rules, or unsupported hardware.
• Provide the number of school sites in the initial pilot and the grades they serve. Options: 1 site, 2–5 sites, 6–15 sites, More than 15 sites
• Do you have on-site contacts at pilot schools who can approve hardware installs and schedule trainings? Options: Yes, named contacts and schedules, Partially, some sites, No, contacts need to be assigned
• Characterize the state of existing POS hardware at pilot sites, recent, aging, or unsupported, and note any warranty coverage.
• Are there regular windows when kitchens, dining halls, or vendors are unavailable for installs or training? Options: Yes, daytime windows available, Only after school hours, Weekend windows only, Limited availability, variable by site
• Can you reschedule a missed install or training within two weeks without disrupting meal service? Options: Yes, within 2 weeks, Yes, within 4 weeks, No, longer delay expected, Depends on site

Timeline, procurement signals, and next steps

• Assuming everything aligns, how quickly are you prepared to commit to a pilot and who must sign the paperwork?
• Choose your target pilot go-live window, for example within 4 weeks, 5–8 weeks, 9–12 weeks, or the next school term. Options: Within 4 weeks, 5–8 weeks, 9–12 weeks, Next school term, Unclear
• Explain the budget cycle or procurement milestones that could delay contracting, and the dates you must work within.
• Indicate which commercial terms are non-negotiable for moving forward, such as payment schedule, liability limits, or data use agreements. Options: Payment schedule, Liability limits, Data access and use, Implementation timelines, Termination terms, Other
• Share the name and title of the person authorized to approve the pilot contract, and their preferred procurement process.
• When the pilot demonstrates the expected ROI, what is the fastest path to district-wide contracting and the single critical blocker that would remain?

• Solution Experience: Claiming Risk, Transaction Speed, Forecast Accuracy

• Confirm the current state and its cost to your operations
• You confirm the demonstrated transaction flow meets your busiest lunch period throughput needs.
• Run a sample claiming reconciliation using one month of your POS transactions and deliver the discrepancy and audit-trail report before the follow-up review.
• You confirm the claiming reconciliation eliminates the main reconciliation gaps you described and materially reduces audit risk.
• Proof: Replay a busiest-period transaction flow using your sample data
• Provide one month of raw POS transaction exports, the last three months of submitted claim summaries, and production spreadsheets for two representative sites.
• Agreement on the remaining evidence and acceptance criteria required to finalize scope and move toward mutual commit.
• Proof: Run a claiming reconciliation on a sample month
• Prepare a proposed acceptance criteria checklist that ties transaction latency, claiming accuracy thresholds, and forecast variance targets to the go/no-go decision.
• Proof: Demonstrate menu planning into production forecasting with your menus and counts
• Identify the decision-makers who must confirm the acceptance criteria and share their availability for the follow-up evidence review.
• Validate the outcomes and acceptance criteria

• Solution Experience: Claiming Risk, Transaction Speed, Forecast Accuracy
• Solution Experience Deck
• Solution Brief

• meeting
• slides
• document

• Deploy POS terminals and peripheral hardware
• Configure POS transaction workflows and meal-type capture
• Provision student meal accounts and cashless payments
• Load menu database with USDA meal-pattern templates
• Run nutrient analysis and meal-pattern validation
• Configure production forecasting and daily prep sheets
• Implement inventory management and purchasing workflows
• Migrate free and reduced eligibility records
• Set up monthly claiming and reimbursement filing
• Integrate with student information system rosters
• Integrate with district financial/ERP for food cost
• Configure allergen and special-diet tracking
• Train cafeteria staff on POS and production tools
• Activate participation, food-cost, and labor dashboards

Deploy POS terminals and peripheral hardware

• How many POS terminals do you plan to deploy per school site (include teacher/staff kiosks)? Options: 1-2, 3-5, 6+
• Which POS terminal models and receipt/printer/scanner brands are currently in your cafeteria fleet? Options: Modern Windows-based, Android-based, Aging legacy serial terminals, Mix / Unsure
• Do existing kitchen network drops and power circuits support the new terminals and peripherals or will electrical/network work be required? Options: All sites ready, Some sites need work, Most sites need work
• Provide the target go-live window for the earliest and latest sites and any fixed blackout dates (e.g., state audits, school vacations).
• List any peripheral requirements tied to meal service flow (PIN pads, kitchen display, weight scale, barcode scanner). Options: PIN pads, Kitchen display, Weight scale, Barcode scanner, None / Other
• Identify any acceptance criteria for hardware deployment (e.g., terminal boot-to-transact time under X seconds, network bandwidth per POS). Options: Terminal boots and transacts within 30s, All devices reachable on network, Device inventory and serials uploaded, Custom (describe)

Configure POS transaction workflows and meal-type capture

• When capturing meals at the POS which meal-type codes do you use today for reimbursable differentiation (e.g., NSLP lunch, SBP breakfast, a la carte)? Options: NSLP Lunch, SBP Breakfast, After-school snack, A la carte, Other
• Which student identifier(s) will you use at the POS (student ID barcode, PIN, last name lookup, account number)? Options: Student ID barcode, PIN, Last name, Account number, Other
• Do you require transaction splits for second entrees, reduced-price vs free verification prompts, or reimbursable meal hold rules per USDA guidance? Options: Yes - splits and prompts, Yes - hold rules only, No
• Specify the maximum acceptable transaction time per student at peak service you expect (seconds) to measure POS performance. Options: <3s, 3-6s, 6-10s, >10s
• Describe how meal modifications (e.g., vegetarian, allergen substitutions) should be captured on the POS receipt and claimable meal record.
• Confirm the acceptance criteria for POS workflow configuration (example: all meal-types map to claim codes and reconcile to daily meal counts). Options: Map verified for all meal types, Daily POS-to-claim reconciliation within 1%

Provision student meal accounts and cashless payments

• How will students be identified for accounts at POS: district student ID, state ID, or locally issued numbers? Options: District student ID, State ID, Locally issued, Hybrid/Unsure
• Which payment methods do you plan to accept for meal accounts (cash acceptance point, online card payments, third-party wallets)? Options: Cash at POS, Online card payments, Third-party wallets, Direct deposit, Other
• Do you have an existing parent/guardian portal for payments and low-balance alerts or will one be provisioned? Options: Existing portal, Require provisioning, Not needed
• Provide the format and sample of your current student account balance export (fields: student ID, balance, last payment date).
• Are there confidentiality or FERPA-linked restrictions on which staff can view student account balances at point of sale? Options: Yes, No
• Which reconciliation cadence do you require for meal account receipts to district bank deposits (daily, weekly, monthly)? Options: Daily, Weekly, Monthly, Custom

Load menu database with USDA meal-pattern templates

• How many unique rotating menus or menu cycles do you operate (e.g., 4-week cycle, seasonal menus)? Options: Single daily menu, 2-4 week cycle, Monthly/Seasonal cycles, Custom
• Which meal pattern templates must be active for validation (NSLP lunch, SBP breakfast, after-school snack)? Options: NSLP Lunch, SBP Breakfast, After-school snack, Smooth Summer
• Do you have standard recipes with portion sizes and CN (Child Nutrition) labels or will recipes need to be standardized/imported? Options: Recipes and CN labels available, Recipes need standardization, Unknown
• Provide how you currently track menu substitutions and seasonal ingredient changes (spreadsheet, paper, recipe cards).
• List any state agency menu review constraints or pre-approval documents required for your district menus.
• Which sites require menu variations for breakfast-in-the-classroom or alternate service models that affect menu loading? Options: All sites, Select sites, None

Run nutrient analysis and meal-pattern validation

• Are nutrition labels or ingredient-level data available for purchased products to support nutrient analysis? Options: Yes - full dataset, Partial, No
• Which nutrient thresholds are monitored for compliance (calories, sodium, saturated fat) against USDA meal pattern limits? Options: Calories, Sodium, Sat fat, All
• Describe the approval workflow for menu items that fail automated validation (who reviews and signs off on exceptions).
• Provide the list of recipes or items that require CN label cross-check during validation.
• Are there sites with special grade spans (K-5, 6-8, 9-12) that need differentiated nutrient targets? Options: Yes - specify by site, No
• Confirm the acceptance criterion for nutrient analysis accuracy (example: 98% match between recipe nutrient totals and validated USDA-coded targets). Options: 98% match, 95% match, Custom

Configure production forecasting and daily prep sheets

• How do you currently forecast daily meal counts (historical POS counts, teacher pre-orders, SIS schedules)? Options: Historical POS counts, Teacher pre-orders, SIS schedules, Manual estimates
• Which look-ahead window do you require for forecasts (same-day, 3-day, 7-day)? Options: Same-day, 3-day, 7-day, 14-day
• Provide the required fields on daily prep sheets (planned servings, prep quantity, portion size, production time).
• Are there production minimums or par-level constraints for scratch or commodity-reliant recipes that must be enforced? Options: Yes, No
• Identify any receivers or site prep leads who must approve final prep sheets each service day.
• Which variance threshold between forecast and actual counts should trigger an operational alert (percentage or absolute count)? Options: 5%, 10%, 20%, Custom

Implement inventory management and purchasing workflows

• Do you track inventory at site-level kitchens, district central warehouse, or both? Options: Site-level only, Central warehouse only, Both
• Which units of measure do you use for inventory (cases, pounds, each) and do you need automated conversion rules? Options: Cases, Pounds, Each, Mixed
• Describe your purchasing workflow: district PO to vendors, blanket orders, or manual requisitions per site.
• Identify any mandated USDA commodity tracking or inventory tagging requirements your district follows.
• Are there preferred vendor catalogs or EDI ordering endpoints we must integrate for automated ordering? Options: Yes - provide list, No
• Indicate the stocking par levels for top 10 high-turn items or whether par will be set after initial baseline period. Options: Provide pars, Set after baseline

Migrate free and reduced eligibility records

• Do you have a current eligibility export of free/reduced/paid student statuses in CSV or SIS feed format ready for migration? Options: CSV export, SIS feed, Paper records, Not ready
• Which data fields are included in your eligibility extract (student ID, certification date, benefit type, household case number)?
• Are direct certification lists used in your district and how often are they refreshed (monthly, quarterly)? Options: Yes - monthly, Yes - quarterly, No
• Describe the owner and process for verifying eligibility appeals or overrides post-migration.
• List any security or FERPA handling requirements for eligibility records during transfer and storage.
• How will you verify migration completeness (example: reconciliation of migrated counts by school against prior month certified counts)? Options: Reconcile by student counts, Sample verification, Full audit report

Set up monthly claiming and reimbursement filing

• Which state agency claim format do you file (standard CSV, direct web portal, or XML upload)? Options: CSV, Web portal, XML, Other
• Provide the current month-close schedule and submission deadlines for your state claim filing.
• Do you require automated reconciliation between POS daily meal counts and the monthly claim worksheet? Options: Yes - automated, No - manual
• Identify the finance contacts who must sign or approve the monthly claim and the document type used for approvals (email, e-signature, paper).
• Are there historical claim adjustments or prior-year audit findings we should account for when configuring claiming rules? Options: Yes - provide details, No
• What evidence will validate successful claiming setup (example: test claim file accepted by state portal or green-status in claim preview)? Options: State portal acceptance, District sign-off, Test files reconciled

Integrate with student information system rosters

• Which SIS (student information system) export format will you provide (CSV roster, OneRoster API, SIF)? Options: CSV roster, OneRoster, SIF, Other
• How often must rosters sync to the platform (near real-time, daily, weekly)? Options: Near real-time, Daily, Weekly, Manual
• Are there student populations to exclude from feeding rosters (pre-K pilots, alternative programs)? Options: Exclude pre-K, Exclude pilots, Include all
• Who owns roster corrections in your district: nutrition staff, school admin, or SIS team? Options: Nutrition staff, School admin, SIS team, Hybrid
• Provide the field mapping requirements for student records (student ID, grade, free/reduced status, homeroom).
• Are student photo lookups required at POS for verification and do you have consent to use images? Options: Yes - photos available, No photos, Consent pending

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Subscription Agreement / Order Form
• Data Processing Agreement (DPA)
• Education Data Addendum (FERPA)
• Hardware Order Confirmation
• Service Level Agreement (SLA)
• Change Order Agreement
• Governance & Escalation Plan

• Go-live Health Check (weeks 1-4)
• First Outcomes Measurement (weeks 4-10)
• Acceptance Gate Review (around day 90)
• Quarterly Success Review

• Run a targeted review of food cost inputs and recipe yields to improve food cost per meal reporting.
• Run targeted training for meal counting procedures at sites showing low participation capture.
• Prepare a clean data extract and field-mapping verification to be used for the acceptance gate analysis.
• Restate acceptance criteria and numeric targets
• Produce a documented acceptance decision for each acceptance criterion recorded in Solution Scope, noting pass or fail.
• If any criterion failed, agree remediation items with deadlines sufficient to close the loop before final acceptance.
• Confirm the incumbent system is set to decommission or read-only and that data migration/archival tasks are scheduled or completed.
• Publish the acceptance decision and the remediation plan with dates and verification steps.
• Execute legacy system wind-down tasks: finalize archival, set read-only mode if applicable, and confirm contract/renewal disposition.
• Create the post-acceptance support and enhancement request channel and circulate access instructions.
• Trend review for key metrics
• Confirm whether claiming accuracy rate and food cost per meal are on track against targets recorded in Solution Scope and identify any corrective priorities.
• Agree the prioritized enhancement requests to be scoped for the next quarter and confirm the triage outcomes.
• Ensure the shared issue and enhancement channel is up to date and that high-priority tickets have clear resolution timelines.
• Publish the prioritized enhancement list and expected delivery windows for the next quarter.
• Close or update all high-priority support tickets with target resolution dates and verification steps.
• Re-confirm success criteria and owners
• Confirm deployment components (POS, integrations, data migration) are operational or document required fixes.
• Verify training completion status and identify any user groups needing follow-on training.
• Capture all high-priority blockers with owners and target resolution dates.
• Publish a short deployment health summary with open issues and owners within 24 hours.
• Collect missing access credentials and environment details required to remediate open integrations.
• Schedule targeted follow-up training sessions for any user group with <80% training completion.
• Present first-data dashboard
• Determine whether claiming accuracy rate and student participation rate are moving toward the targets recorded in Solution Scope.
• Identify the top 2 root causes for each metric gap and agree remediation workstreams and completion dates.
• Confirm ownership and timeline for data quality fixes required to ensure reliable reporting at the acceptance gate.
• Implement claiming rule adjustments and publish the change log for the next reporting window.
• Present outcome data against each criterion
• Open ticket and SLA burn-down
• Deployment and migration validation
• Compare results to targets recorded in Solution Scope
• Document acceptance decision and next steps
• Early adoption signals and usage patterns
• Enhancement request triage and prioritization
• Root-cause diagnosis for gaps
• Operational blockers and continuous improvement items
• Incumbent system wind-down confirmation
• Blockers, defects, and escalation list
• Agree corrective actions and timeline to acceptance gate
• Data quality and reporting fixes
• Operational handover and support plan
• Confirm next quarter targets and cadence
• Immediate remediation plan and next steps