Start Here: Your Day in the Life of School Nutrition

• What's your role and primary responsibility for school meals today? Options: Child Nutrition Director, Food Service Manager, Cafeteria Lead, Business Official/Finance, IT/Operations, Other
• How many school sites and approximate daily meals are you responsible for? Options: 1–2 sites / <1,000 meals, 3–10 sites / 1,000–10,000 meals, 11–30 sites / 10,000–50,000 meals, 31+ sites / 50,000+ meals
• Tell us what currently works best in your daily operations—what gives you confidence?
• Which parts of the operation consume the most of your time each week? Options: Claiming & reporting, Menu planning & compliance, POS operations/line speed, Eligibility processing, Inventory & purchasing, Staff scheduling/training, Other
• If you had to pick one immediate pain that, if solved, would free up the most time, what would it be? Options: Claiming accuracy, POS speed/reliability, Eligibility backlogs, Forecasting/production planning, Inventory shrink/waste, Staff turnover/training

What's Costing You Sleep Tonight?

• When you think about audits, repayment risk, or state findings—what keeps you awake more: the financial hit, reputational risk, staff stress, or something else? Options: Financial repayment, State audit findings, Loss of community trust/reputation, Staff morale & turnover, Operational disruption, Other
• Have you had a USDA or state audit in the last 3 years that required repayment or corrective action? Please describe what happened and the scale.
• How frequently do you discover claiming or eligibility errors that require manual correction? Options: Weekly, Monthly, Quarterly, Annually, Rarely/never
• Who on your team typically discovers and fixes those errors, and how do they feel about doing it? Options: Nutrition Director, Cafeteria Manager, Administrative Clerk, Business Office, External Consultant, Other
• What would the concrete financial or operational impact be if those errors were reduced by half? Give examples or estimates.

Walk a Tray: Where Our Process Trips Up

• Describe the last time a meal service went off-schedule or produced claiming exceptions—what happened, step by step?
• How do you currently capture meal counts and exceptions at each serving line? Options: POS terminal swipe, Manual tally sheets, Mobile handhelds, Teacher/roster counts, Combination, Other
• How old or reliable are your POS terminals and printers, and how often do they fail during peak service? Options: Brand new / rarely fail, Under 3 years / occasional issues, 3–7 years / intermittent failures, 7+ years / frequent failures, We don't track age
• When a child is eligible but the POS flow marks them as paid (or vice versa), what's the typical correction process and who owns it?
• What are the busiest window(s) during meal service, and how do throughput issues show up (line time, student complaints, lost sales)? Options: Breakfast pre-bell, Breakfast after bell, Lunch first period, Lunch peak (recess/lunch overlap), Multiple peaks, Other

Data That Tells the Truth—or Hides It

• How confident are you that your student eligibility and meal counts match what's recorded in your SIS and financial systems? Options: Very confident, Mostly confident, Some doubts, Not confident at all
• Which systems feed your claiming and reporting today (SIS, POS vendor, finance, eligibility vendor)? Select all that apply. Options: Student Information System (SIS), Current POS vendor, Finance/ERP system, Eligibility processing vendor, Spreadsheet exports, Manual uploads, Other
• How often do you reconcile meals served to claims filed, and what discrepancies are most common? Options: Daily, Weekly, Monthly, Only during audits, Never
• Who is the designated owner of data quality for meals, eligibility, and claiming in your org? Options: Nutrition Director, Business Office, IT, School Site Lead, No clear owner, Other
• Tell us about a data error that changed a claim or cost—what caused it and how long did it take to resolve?

What If Claiming Wasn't Something to Fear?

• Imagine you never had to contest a claiming audit again—what would that free you to focus on instead?
• What measurable outcomes would convince you a new platform is working (time saved, reduction in errors, faster claims, food waste reduction)? Options: % Time saved for director/staff, Reduction in audit findings, Increase in reimbursement accuracy, Lower food waste %, Faster monthly close, Other
• If we set a success target, which of these would be most meaningful in the first 6 months? Options: Reduce claiming errors by X%, Cut staff hours on reporting by X hours/week, Improve POS throughput by X%, Reduce food waste by X%
• How would improved forecasting and menu compliance change relationships with staff, families, or your finance office?
• What concerns would you still have after a successful technical implementation—things that technology alone won't fix?

People & Politics: Who Holds the Keys?

• If you had to name the single biggest internal blocker for change, who or what would it be—budget cycles, decision-makers, unions, or comfort with old tools? Options: Budget/timing, Board/School leadership, Business office/finance, IT/network constraints, Union/staff resistance, Comfort with legacy systems
• Who are the stakeholders that must sign off for new food service technology? List roles and their main concern.
• How does procurement work in your district—open RFP, piggyback contract, cooperative purchasing, or sole source? Options: Open competitive RFP, Cooperative contract, Piggyback/contract extension, Sole source/waiver, Unsure
• What level of ROI or payback period does your district expect for operational technology investments? Options: <6 months, 6–12 months, 1–2 years, 2+ years, No strict ROI requirement
• Describe how you prefer training and change management to be handled—hands-on on-site, train-the-trainer, virtual, or hybrid? Options: On-site hands-on, Train-the-trainer, Virtual instructor-led, Self-paced eLearning, Hybrid

Tech Reality Check: Integrations, Networks, and Hardware

• How much of a surprise would it be to discover your POS, SIS, and finance systems don’t easily talk to each other? Options: No surprise—already fragmented, Somewhat surprised, Very surprised
• Which vendors or systems are critical to connect during implementation? Select all that apply. Options: Current POS vendor, SIS (PowerSchool, Skyward, Infinite Campus, etc.), Finance/ERP (Munis, Oracle, QuickBooks), Eligibility/Community Eligibility software, Inventory/Purchasing system, Payment processor, Other
• Do you have documented APIs, SFTP exports, or flat-file routines available for data exchange today? Options: APIs available, SFTP or scheduled exports, Manual CSV/Excel exports, No automated feeds
• Describe your network reliability and POS connectivity at the busiest sites—any known bandwidth or offline challenges?
• Are your POS terminals, printers, and network hardware owned by the district, leased, or vendor-provided? Options: District-owned, Leased, Vendor-provided, Mixture

Rolling Out Change Without Breaking Lunch

• What would worry you most about implementing a new system during the school year—service interruption, staff confusion, claiming errors, or other risks? Options: Service interruption, Staff confusion, Claiming/reporting errors, Data migration issues, Parent/family communication problems, Other
• Do you prefer a phased pilot (by site/type) or a simultaneous district-wide cutover, and why? Options: Phased pilot, Simultaneous cutover, Hybrid approach, Undecided
• How many sites could you realistically pilot in the first 60–90 days given trainers and resources? Options: 1 site, 2–5 sites, 6–10 sites, 10+ sites, Unsure
• What rollback or contingency measures would you insist on before go-live (parallel claiming, manual fallback, extra staff)?
• Who would be the on-site owner during cutover and who is the escalation contact in the district?

Decision Signals: What Makes a 'Yes' Happen?

• If everything else aligned, what is the single most persuasive factor that would make you choose a new platform? Options: Proven claiming accuracy, Faster POS throughput, Seamless integrations, Clear ROI, Excellent support/training, Other
• Where are you in the decision timeline—exploring, shortlisting, pilots, or ready to procure? Options: Exploring options, Shortlisting vendors, Running pilots, Ready to procure
• Who else needs to be convinced, and what would they need to see (cost models, pilot results, references, SLA)? Options: Board/Leadership, Business Office, IT, Principals/site leads, Union/HR, Other
• What unanswered questions or data would help you move to the next step after discovery?
• Realistically, what procurement or budget window should we target for a pilot or implementation? Options: Immediate / this month, Next 1–3 months, This fiscal quarter, Next fiscal year, Unknown

• Solution Experience Kickoff & Data Validation
• Live POS Flow Replay — Real Meal Counts & Transactions
• Claiming Scenario Validation & Audit Package Walkthrough
• Edge Cases & Exception Handling Workshop
• Outcome Validation, Acceptance Criteria & Sign-off

• Reduce expected manual labor/time-to-fix for each class of exception and quantify where possible.
• Demonstrate the platform prevents known claim errors and reduces repayment risk.
• Show reconciliation paths to finance and quantify variance resolution effort.
• Produce an audit-ready package and confirm it meets the district's audit response needs.
• Identify remaining data gaps that could affect claim accuracy and assign owners.
• Export and deliver the full month’s claim run results and audit package PDF to district reviewers.
• List and prioritize data gaps or mapping errors discovered during the run.
• Assign finance and district approvers for claim sign-off workflow configuration.
• Schedule a mini-audit simulation with district auditors if requested.
• Inventory Top Edge Cases
• Ensure the system handles each high-priority edge case correctly or has an efficient correction workflow.
• Define clear SOPs and owner responsibilities for exception resolution.
• Introductions & Objectives
• Identify any policy/configuration choices requiring district sign-off.
• Document finalized SOPs for each edge case and circulate for sign-off.
• Create quick-reference job aids for cafeteria staff covering the top 5 exceptions.
• Schedule follow-up hands-on tests for any unresolved or complex scenarios.
• If needed, create a short vendor ticket for platform behavior changes where configuration cannot meet need.
• Executive Summary of Findings
• Obtain explicit customer confirmation that the Solution Experience proves the future-state outcome.
• Agree and capture measurable acceptance criteria and any remaining gaps to close.
• Assign owners and timeline for outstanding items required before Mutual Commit.
• Produce a final Solution Experience report that will be attached to the journey template.
• CustomerNode to deliver the final Solution Experience report with metrics, discrepancies, and recommended fixes.
• District to sign or accept the acceptance checklist or list remaining gaps with owners and target dates.
• Schedule the Mutual Commit meeting with commercial and deployment stakeholders.
• Open tickets or tasks for any platform configuration/code changes discovered during runs.
• Document a single-sentence current state that will be referenced in all subsequent sessions.
• Make the consequence explicit and measurable (dollar, time, audit risk).
• Agree on a one-sentence future state as the outcome to validate.
• Obtain committed access to required datasets and assign owners.
• Schedule hands-on scenario sessions with required participants and environments.
• District to deliver redacted sample datasets: 2 weeks of POS logs, one month meal counts, roster, and eligibility file.
• District to provide copies of recent claiming errors/audit findings for consequence analysis.
• Assign an IT/data owner with access credentials and share contact details.
• CustomerNode to provision test environment and confirm readiness date.
• Schedule the Live POS Flow Replay and Claiming Validation sessions.
• One-sentence Recap and Future State Reminder
• Prove that POS flows classify reimbursable meals correctly and block or flag non-reimbursable transactions.
• Measure and agree POS throughput and identify any performance tuning required.
• Validate that common exceptions are handled with minimal manual intervention.
• Create a prioritized list of configuration or data fixes required before deployment.
• Map and correct POS SKU-to-menu mappings for any discrepancies found.
• Create a short list of top POS performance tuning tasks and owners.
• Document each exception workflow and assign owners to close data gaps.
• Prepare short training notes for cashiers covering flagged exception flows.
• Framing: Current Claiming Problem and Target Outcome
• One-sentence Current State (District)
• Map Findings to Problem & Future State
• Load Month Data & Preliminary Sanity Checks
• Pre-run Data Sanity Check
• Simulate & Validate Each Edge Case
• Run Claiming Pipeline & Edit Checks
• Customer Validation (Force Confirmation)
• Quantify Consequence
• Transaction Replay — Typical Day
• Rollback & Correction Workflows
• Meal Pattern Enforcement & Reimbursability Checks
• Policy Choices & Configuration Discussion
• Define One-sentence Future State

• Deploy and Configure POS Terminals
• Migrate Free & Reduced Eligibility Data
• Enable USDA Meal Pattern Compliance Engine
• Configure Menu Database with Nutrient Analysis
• Implement Production Forecasting and Prep Schedules
• Activate Monthly Claiming and Reimbursement Filing
• Install Inventory Management with Barcode Scanning
• Launch Student Meal Account & Cashless Payments
• Integrate with District Financial Systems
• Enable Allergen and Special Diet Tracking
• Train Cafeteria Staff on POS & Meal Counting
• Provide Real-time Participation and Cost Dashboards

Deploy and Configure POS Terminals

• Do you plan to replace existing POS terminals, add new terminals, or both? Options: Replace, Add new, Both, Unsure
• How many school sites will need POS terminals configured? Options: 1, 2-5, 6-20, 21+
• Approximately how many terminals total (all sites combined) need deployment? Options: 1-5, 6-20, 21-50, 51+
• What models/operating systems are your current POS terminals (list models and OS versions)?
• Which POS peripherals are required or expected (select all that apply)? Options: Barcode scanners, Receipt printers, Cash drawers, PIN pads, Scales, Kitchen display/label printers, None, Other
• Is your POS network and power infrastructure ready at each site, or are upgrades required? Options: Network & power ready, Upgrades required, Partial readiness, Unknown - need assessment

Migrate Free & Reduced Eligibility Data

• Do you have an electronic eligibility roster to migrate (SIS export, spreadsheet, state file)? Options: Yes - SIS export, Yes - spreadsheets/CSV, Yes - state file (TIDE/other), No, Partial
• Approximately how many student records will be included in the migration? Options: Less than 1,000, 1,000-5,000, 5,001-20,000, 20,000+
• Are student identifiers (student ID) consistent between your SIS and current meal system? Options: Yes - consistent, No - inconsistent, Partial / some exceptions, Unknown
• Do your eligibility records include household application data, direct certification flags, or both? Options: Household applications, Direct certification, Both, Other / unclear
• Are there known data quality issues (duplicates, missing DOB/IDs, handwritten forms) that require cleaning before migration? Options: Yes - cleaning required, No - data is clean, Some issues, Unknown
• Who will own eligibility data mapping and validation during migration (district staff, SIS vendor, our team)? Options: District staff, SIS vendor, Our implementation team, Shared responsibility

Enable USDA Meal Pattern Compliance Engine

• Do you want automated meal pattern checks enabled for all sites and meal types? Options: Yes - all sites, Yes - pilot sites only, No - not required, Unsure
• Which grade groups should meal pattern checks be configured for? Options: PreK, K-5, 6-8, 9-12, All
• Do you use multiple menus/meal components (e.g., alternate entrees, a la carte) that require separate compliance rules? Options: Yes - multiple menus/components, No - single menu structure, Partial / some variations
• Do you require tailored rules for crediting recipes (e.g., grain/bread equivalents, vegetable subgroups)? Options: Yes - tailored rules, No - standard USDA rules, Unsure - need review
• Is there an existing baseline for acceptance criteria (e.g., 100% automated rejection of non-compliant meals) or should we propose default thresholds? Options: We have baseline criteria, Propose default thresholds, Unsure - need guidance
• Please list any state-specific meal pattern variations or waiver needs that should be considered.

Configure Menu Database with Nutrient Analysis

• Do you already have standardized recipes and ingredient lists that can be imported? Options: Yes - standardized recipes ready, Partial - some recipes, No - need to create
• Approximately how many unique recipes/line items need nutrient analysis? Options: Less than 100, 100-500, 500-1,000, 1,000+
• Do you require USDA nutrient analysis and/or additional micro-nutrient reporting? Options: USDA nutrient analysis, Additional micro-nutrients, Both, No nutrient analysis needed
• Will menus be maintained centrally or by individual sites (who will own updates)? Options: Central (district) maintained, Site-level maintained, Hybrid
• Do you need vendor product catalogs and vendor pack-size/ingredient mappings imported? Options: Yes - vendor catalogs, No, Partial
• Are there special reporting requirements (state nutrient reports, school wellness reports) to include?

Implement Production Forecasting and Prep Schedules

• Do you want forecasted production quantities generated for each site/meal period? Options: Yes - all sites, Yes - pilot sites, No
• Are historical meal counts and participation data available for the previous 1-2 years? Options: Yes - full history, Partial history, No - limited data
• What forecasting granularity do you need (select all that apply)? Options: School-level totals, Meal period (breakfast/lunch), Recipe-level/line-item, Serving line-level
• Should forecasting incorporate special events/field trips/assemblies automatically? Options: Yes - auto incorporate, No - manual adjustments only, Need to configure event calendar
• Do you require integrated prep schedules and printed/visual job lists for kitchen staff? Options: Yes - printed/visual schedules, No, Partial
• What target accuracy or waste reduction goals should forecasts aim for (e.g., % reduction in overproduction)?

Activate Monthly Claiming and Reimbursement Filing

• Do you currently prepare and submit USDA claims electronically, manually, or via a vendor? Options: Electronically (district), Manually (paper/spreadsheet), Vendor-submitted, Not currently submitting
• Which state agency or portal will claims be submitted to (please specify state and system)?
• Do you require automated claim generation, reconciliation, and submission from our system? Options: Yes - full automation, Yes - generate only, district submits, No - manual process prefers
• Do you need claims reconciled to district financials and meal revenue accounts? Options: Yes - reconcile automatically, Yes - reconciliation reports only, No
• Who will be the claim approver(s) in the district (roles/titles)?
• What acceptance criteria define a successful claim (e.g., zero audit exceptions, <1% variance)?

Install Inventory Management with Barcode Scanning

• Do you want a centralized inventory system with site-level counts and transfers? Options: Yes - centralized with site counts, Yes - centralized only, No - site-level only, Unsure
• Approximately how many unique SKUs (ingredients/products) will be tracked? Options: Less than 500, 500-2,000, 2,001-5,000, 5,000+
• Will you use barcode scanning for receipts, issues, and physical counts? Options: Yes - all processes, Yes - select processes, No - manual entry
• Do you need integration between inventory and production forecasting to auto-generate purchase suggestions? Options: Yes - full integration, No, Partial
• Which costing method do you use/require for inventory valuation? Options: FIFO, Average cost, Specific lot, Other
• Who will maintain inventory counts and cycle counts (roles/titles)? Options: Cafeteria staff, Warehouse staff, Third-party, Shared

Launch Student Meal Account & Cashless Payments

• Do you plan to enable cashless payments district-wide, per site, or not at this time? Options: District-wide, Pilot sites, Not at this time, Unsure
• Which payment processors are you currently using or prefer to integrate with? Options: PaySchools, RevTrak, Square, Stripe/custom, None, Other
• Do you want parent/guardian web portals for payments and low-balance notifications? Options: Yes - web portal & notifications, Yes - notifications only, No
• Will cash still be accepted at POS or do you require cashless-only workflows? Options: Cash accepted, Cashless-only, Hybrid - cash accepted at select sites
• Do student accounts need restrictions (allergen alerts, spending limits) or cross-school account linking? Options: Yes - restrictions and linking, Restrictions only, No
• How should free/reduced eligibility be applied at payment (automatic masking, manual override, verification steps)? Options: Automatic application, Manual verification/override, Hybrid

Integrate with District Financial Systems

• Which district financial/ERP systems must we integrate with? Options: Munis, PeopleSoft, Infinite Visions, QuickBooks, Other/Custom, None
• What integration scope do you need (GL mapping, AP/AR posting, purchase order sync, bank reconciliation)? Options: GL mapping, AP/AR posting, Purchase order sync, Bank reconciliation, All of the above, Other
• How frequently should financial data sync to the district system? Options: Real-time, Daily, Weekly, Monthly
• Who owns the chart-of-accounts mapping and validation in the district? Options: Business office, Finance vendor, Our team, Shared
• Are there security or compliance constraints (SFTP, VPN, IP allowlist) for integrations? Options: Yes - constraints exist, No special constraints, Unknown - need details
• Do you require test/sandbox validation and sign-off cycles before production sync? Options: Yes - sandbox & sign-off, No - direct to production, Partial

Enable Allergen and Special Diet Tracking

• Do you require allergen flags to appear at POS and on production/picking lists? Options: Yes - POS & production, POS only, Production only, No
• Which special diet categories need tracking (select all that apply)? Options: Nut-free, Gluten-free, Dairy-free, Vegetarian/vegan, Diabetic-friendly, Other
• Where are medical or accommodation statements currently stored? Options: SIS, Nurse/health office records, Paper files, Other
• Do you require POS prompts/blocks to prevent serving contraindicated items? Options: Yes - prompts, Yes - hard blocks, No prompts/blocks
• Should special diet tracking feed into claiming/meal modification reports? Options: Yes - include in claims, No - separate reporting, Unsure
• Who will manage and approve special diet entries and medical statements? Options: School nurse, Child nutrition director, Site manager, Other

• Statement of Work (SOW)
• Master Services Agreement (MSA)
• Order Form & Pricing Schedule
• Payment & Invoicing Terms
• Implementation Timeline & Go‑Live Schedule
• Roles & Responsibilities (RACI)
• Data Migration & Integration Plan
• Training & Knowledge Transfer Agreement
• Acceptance Criteria & USDA Claiming Certification
• Service Level Agreement (SLA) & Support
• Hardware, POS & Procurement Agreement
• Data Processing Agreement (DPA) & Security
• Change Order Process
• Renewal & Term Extension Terms
• Termination & Exit Plan

• Success Metrics Review
• Post-Implementation Lessons Learned (Retrospective)
• Ongoing Operations & Support Rhythm
• Enhancement Prioritization Workshop
• Compliance & Audit Readiness Review

• Product to add top 3 prioritized enhancements to public roadmap and assign owners.
• Create the shared channel, invite named owners from district and CustomerNode, and post onboarding guidelines.
• Publish the triage runbook with severity definitions and SLA timeframes.
• Schedule recurring weekly triage and monthly ops review meetings on the shared calendar.
• Review Submitted Enhancements & Usage Data
• Agree on a prioritized list of enhancements tied to operational impact.
• Assign product owners and pilot sites with timelines for top-priority items.
• Define measurable acceptance criteria for each selected enhancement.
• Introductions & Objective
• Schedule pilot deployments and define data collection plan to validate impact.
• Communicate roadmap and pilot plan to district stakeholders via the shared channel.
• Claims Reconciliation Walkthrough
• Ensure documentation and reconciliations are complete and auditable for the upcoming audit cycle.
• Assign audit contacts and practice responses for common auditor inquiries.
• Define remediation steps and deadlines for any discovered discrepancies.
• District to provide sampled POS logs, eligibility rosters, and reconciliations for the last three months.
• CSM and finance owner to produce an audit artifacts folder and a one-page audit readiness summary.
• If issues exist, schedule a focused remediation sprint with clear owners and evidence collection plan.
• Validate which success signals are met and which require remediation.
• Assign owners, deadlines, and acceptance checks for each remediation action.
• Ensure consequences of unmet signals are quantified for the district (dollars, compliance risk, labor hours).
• Owner(s) to provide raw data and screenshots for metrics out of tolerance within 3 business days.
• CustomerNode CSM to log remediation tasks and assign product/support teams for software/config issues.
• Schedule follow-up verification meeting within 2 weeks to re-check adjusted metrics.
• Timeline Recap
• Document concrete lessons to reduce risk in future rollouts.
• Identify training/operational gaps and assign owners to update materials.
• Agree on final acceptance/status for formal closeout or continued remediation.
• Draft 'Lessons Learned' summary and updated deployment checklist to be shared with district and internal teams.
• Assign training owner to produce short targeted refresh sessions for cafeteria staff at affected sites.
• Update acceptance criteria documents to reflect any agreed measurement adjustments.
• Confirm Shared Channel & Access
• Establish a primary shared communications channel with clear membership and usage rules.
• Agree on issue severity levels and corresponding SLAs to reduce downtime and audit risk.
• Set a repeatable cadence for operational reviews and data sharing.
• Baseline vs Current Metrics
• Prioritization Framework & Scoring
• Sampling & Documentation
• Issue Triage & SLA Definitions
• Wins — What Worked
• Roadmap Commitments & Pilot Selection
• Enhancement Intake & Prioritization Process
• Mitigation for Known Gaps
• Pain Points & Root Causes
• Gap Analysis & Consequences
• Define Acceptance Criteria for Enhancements
• Decisions: Adjustments & Owners
• Audit Playbook & Point People
• Recurring Cadence & Dashboards
• Actionable Improvements
• Next Steps & Follow-up Cadence
• Finalize Acceptance & Closeout