Food Safety Inspection Router

The Food Safety Inspection Router scores regulated food facilities by risk, using their violation history and current information such as recalls, complaints and laboratory results, and proposes inspection assignments and routes for supervisors to approve. Inspectors work from a mobile app that records findings offline and synchronizes when a connection returns. Every score, assignment and finding keeps its reasons, so the program can show how inspection resources were directed.

The problem it solves

Inspection programs have more facilities to cover than inspectors to cover them, and assignments are often built from fixed rotations, spreadsheets and local knowledge. Facilities with a history of problems can wait as long as those with clean records, while inspectors in rural districts lose time to long drives and to paper forms that are keyed in later because there was no signal on site. When oversight bodies ask why one facility was visited and another was not, the reasoning is hard to reconstruct.

Who it’s for

• 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

1. ScoreFacility 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.
2. PlanThe 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.
3. InspectInspectors 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.
4. Follow upFindings 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.

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.

Field inspector

Carries out assigned inspections on a mobile device and records findings, online or offline

Supervisor

Approves inspection plans, reviews findings and decides on follow-up

Planner

Builds inspection plans from the Router's proposals for a district or circuit

Risk analyst

Maintains and tests the risk model, without approving plans or findings

Enforcement officer

Receives referred findings and records enforcement decisions under agency procedures

Auditor (read-only)

Views scores, plans, findings and the audit trail, with no ability to change them

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.

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.

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.

Data mapping

We map your facility registry, inspection history, laboratory and complaint data to the Router's model and agree the file or API schedule. We need data extracts and a contact from each owning system.

Risk model configuration

Risk factors and weights are set with your program and risk staff, documented, and tested against past inspection outcomes before approval.

Planning rules

Required frequencies, districts, circuits, travel constraints, qualifications and conflict rules are configured to match your procedures.

Checklists and citations

Inspection checklists are built for each facility and product type, with each item linked to your agency's citations.

Mobile rollout

The app is packaged for your mobile device management, and offline use is tested in the districts with the weakest coverage before go-live.

Pilot and training

A pilot district runs the Router alongside current scheduling for a period you choose, and inspectors, planners and supervisors are trained on their own workflows.

• 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.

• Load a sample of your facility and inspection history and compare the Router's ranking with where your inspectors actually found problems
• Check that each risk score's explanation would make sense to a supervisor and an auditor
• Ask a planner to build a period's plan for one district and note what they still need to adjust by hand
• Take the mobile app to a site with no coverage, record an inspection and confirm it synchronizes correctly
• Confirm that required-frequency visits are never dropped from a plan
• Review role separation: who can propose, approve and change plans, findings and the risk model