Food Safety Inspection Router

Principal workflows

• Score: Facility records, inspection history and current signals are combined into a risk score for each facility, with the factors behind the score shown in plain words.
• Plan: The Router proposes which facilities each inspector should visit in the coming period and in what order, balancing risk, required inspection frequencies, travel time and inspector qualifications. A supervisor reviews and approves the plan.
• Inspect: Inspectors open each assignment on a mobile device, see the facility's history and the reasons it was selected, and record observations, photos and findings, whether or not they have a connection.
• Follow up: Findings feed back into the facility's history and risk score. Noncompliance is routed for supervisory review and, where needed, follow-up inspection or referral for enforcement under the agency's procedures.

Who uses it

• Federal food safety inspection programs and their district offices
• Field inspectors and investigators who visit processing and manufacturing facilities
• Supervisors and schedulers who build inspection assignments
• Risk and data analysts who maintain facility risk models
• Program leadership, inspectors general and auditors who review how inspection resources are used

Reporting

• Inspections completed against plan, by district and inspector
• Facilities by risk band and time since last inspection
• Mandatory-frequency inspections due and overdue
• Findings and follow-up status by facility type and citation
• Risk model changes and the tests behind them
• Records awaiting synchronization or conflict resolution

Features

• Explainable risk scores: Each facility's score lists the factors behind it, such as recent findings, product type, volume and open recalls, so a supervisor can see why it ranks where it does.
• Proposed assignments and routes: Assignments and visit order proposed for each inspector, taking account of risk, required frequencies, travel time and qualifications. A supervisor approves every plan.
• Offline mobile inspection: Checklists, facility history and assignments are available on the device without a connection, and findings synchronize when coverage returns.
• Conflict-aware synchronization: When the same record was changed in two places while a device was offline, both versions are kept and the conflict is shown to a supervisor to resolve.
• Configurable checklists: Inspection checklists by facility and product type, each item linked to the regulatory citation your agency uses.
• Photo and evidence capture: Photos, sample identifiers and notes attached to the finding they support, with the time and the inspector recorded.
• Signal intake: Recalls, complaints, laboratory results and outbreak notices linked to the facilities they concern, so they can raise a facility's priority.
• Mandatory frequency tracking: Facilities that must be inspected at a set frequency are tracked separately, so risk-based planning never displaces a required visit.
• Qualification and conflict checks: Assignments respect inspector qualifications for the facility type and any recorded conflicts of interest.
• Model governance: Risk model versions, factor weights and the tests run before each change are recorded, and changes need approval before they take effect.
• Follow-up and referral: Open findings tracked to follow-up inspection or referral, with the decision and its reason recorded.
• Audit trail: Who scored, planned, approved, inspected and changed what, and when, for every facility and assignment.

Integrations

• Facility registry: Facility identifiers, locations, product types and establishment details from your agency's registry, by scheduled file or API.
• Inspection and enforcement history: Past inspections, findings and enforcement actions from your existing systems, mapped during implementation.
• Laboratory results: Sample results from the laboratory information systems your agency uses, linked to the facility and sample.
• Recalls and complaints: Recall notices and consumer complaint records from the agency's intake systems.
• Mobile device management: The mobile app is deployed and managed through your agency's mobile device management, so device policies and remote wipe stay under your control.
• Single sign-on: Staff sign in through your identity provider (SAML or OpenID Connect), including PIV-backed authentication where your agency uses it.
• Work API: Scores, plans, findings and follow-up status available to your data warehouse and reporting tools through the Moraph Work API.

Deployment

• Moraph cloud, United States: Hosted and operated by Moraph in the United States region, with data kept in the US.
• Dedicated environment: A single-tenant environment for agencies that require isolation, scoped in the proposal.
• With a managed service: Optionally run alongside a Moraph managed service for administration, model monitoring support and integration support.

Security and privacy

• United States hosting: Data is hosted in Moraph's United States region only.
• Cleared support lane: Support tickets from federal clients are handled only by US citizens with active security clearances.
• Protected data on devices: Data held offline on a device is encrypted, limited to the inspector's current assignments, and removed once synchronized and no longer needed.
• Encryption and keys: Client data is encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.
• Complete audit trail: Every view, change, approval and synchronization is logged with the person and time, and cannot be edited.
• Tested releases: Every release passes security testing gates before it ships, and a software bill of materials is maintained for the product. Moraph is SOC 2 Type II and ISO/IEC 27001 audited.

Limitations

• The Router proposes; it does not decide. Inspection plans are approved by a supervisor, and findings and enforcement decisions belong to your agency.
• Risk scores depend on the completeness and quality of the facility, inspection and signal data you provide, and should be reviewed periodically as that data changes.
• It does not replace inspection frequencies set in law or regulation. Required visits are planned alongside risk-driven ones.
• Offline use covers the inspector's downloaded assignments. Facility records not downloaded beforehand are not available without a connection.
• It is not a laboratory information system or a recall management system. It uses results and notices from the systems your agency already has.
• Moraph holds no FedRAMP authorization for this product. We provide control documentation to support your agency's own authorization decision.
• It is not designed for classified information.
• The mobile app requires agency-managed devices that meet the supported operating system versions listed in the proposal.

Next steps

Book a demonstration or a technical briefing at www.moraph.com/solutions/food-safety-inspection-router. Purchasing routes and company information: www.moraph.com/how-to-buy.