Does Spruce work with the food code we actually adopted?

The FDA Food Code is built into PH360, and a jurisdiction's local adoption and amendments sit alongside it. Findings are drafted against what the jurisdiction enforces, with the code section and source shown so the inspector can verify before citing.

Environmental health permitting and inspection software

PH360™ Spruce: environmental health, permit to inspection.

One place for the whole permit. The business owner applies, uploads, and pays without calling you. The health agent opens a review file that is already prepared. The inspector arrives briefed and works offline. Spruce drafts the groundwork at every step, and a person makes the call.

Schedule a walkthrough Back to PH360 overview

Configured to your code, forms, and fees Office, field, and offline A person confirms every AI action

Local public health

Environmental health has never had a system of its own.

You permit restaurants, pools, septic, and housing. You inspect them on a schedule set by risk, you cite against a code your jurisdiction adopted and amended, and you carry the enforcement that follows. The tools on offer are generic permitting platforms that know nothing about a food code, so the knowledge lives in binders and in the inspector who has been there twenty years. We started from that inspector instead.

The operating idea

The inspector makes the call. Spruce does the paperwork around it.

Grounded, or it abstains

Spruce works from your adopted code and your own records, not the open web. With no grounded source it says so instead of guessing.

Deterministic where it must be

Fees, deadlines, and inspection frequencies are computed by rule, not inferred. The same inputs give the same answer every time.

The human owns the consequence

A citation goes on the record when the inspector cites it. A permit issues when the agent approves it. Every action carries a name and a rationale.

Your jurisdiction's own form

Categories, required documents, fees, priority levels, and correction deadlines are settings, not code changes. Nobody files a ticket with us.

One permit, end to end

See Spruce in action.

One food service permit, in the order it happens. A new restaurant applies and pays, the health agent opens a review file that is already prepared and decides, the inspector visits and cites, the permit issues, and a year later it renews. Anything in purple is drafted by AI and waits on a person.

Business portal home showing open notices, the owner's establishment, an application in progress, and issued permits. — The business owner gets their own portal. Notices, establishments, applications in progress, and permits already issued all sit on one screen, so nobody calls the health department to ask where their application stands.

Application step showing establishment category, seating capacity, food handling checkboxes, and a purple panel explaining that the fields shown adapt to the selection. — The form asks only what the answers call for. Pick a category and the required fields change with it, and the purple panel says why those fields appeared. Nothing already entered is lost if the applicant switches back.

Documents step listing the required documents for this application with five of five attached and an optional slot still open. — Which documents are required follows from what the applicant told you, and the list is yours to set. The owner drags them in and can see what is still missing before submitting instead of after a rejection.

Fee review panel showing an itemized fee and a confirmed card payment with a receipt number. — Fees are computed from what was submitted, using your fee schedule, and paid by card in the portal. The receipt lands on the application record, so the money and the paperwork never travel separately.

The health agent's Today screen: the day's route, applications awaiting first review, follow-ups, renewals arriving, and a purple proposed day plan. — The health agent opens on one screen: the route, what is awaiting first review, follow-ups due, and renewals arriving. Spruce proposes an order for the stops and explains the reasoning. Accepting it changes nothing on the record. It is still your day.

Application record with a purple reviewer file: documents read, completeness scored, document findings, risk classification, and a suggested next step. — The moment the owner submits, the review file is prepared. Every uploaded document is read and cross-checked against the application, completeness is scored, a risk classification is proposed, and the header says it plainly: drafted for review, not a decision.

Decision panel offering Approve, Return for Additional Info, Request Pre-Operational Inspection, and Deny, with a note that every action is recorded by name. — The decision is the agent's. Approve, return for more information, request a pre-opening inspection, or deny. Every action is recorded under a name, and returning or denying requires a rationale that goes on the record.

Field view before an inspection showing the establishment, the last two inspections, and the items cited before. — The inspector arrives briefed. Before walking in they see the last inspections, what was cited before and is worth checking first, and who the person in charge is. It is stored on the device, so a basement with no signal changes nothing.

Temperature logging in the field with area, equipment, product, and reading fields. — Logging a temperature takes a tap. Spruce offers the equipment and the products it has seen at this establishment before, so the inspector picks from a short list instead of typing the walk-in cooler's name again.

A drafted finding marked out of compliance with the rule applied, the code section, the source, a confidence level, and the code text quoted. — A reading out of range comes back as a drafted finding: the rule applied, the code section, the source it came from, a confidence level, and the code text in plain language. Spruce drafts it. The inspector is the one who cites it.

Inspection record showing a follow-up inspection scheduled on the correction clock. — Findings above the priority you set put a follow-up on the calendar automatically, on the correction clock your jurisdiction uses. Nothing depends on somebody remembering to schedule the recheck.

The issued permit certificate, ready to print or save as a PDF. — Once the agent approves, the certificate is ready to print or save. It goes in the department file and on the wall of the establishment, and the owner can pull their own copy from the portal.

Renewal application pre-populated from the prior permit with a banner showing what changed since last year. — A renewal starts from last year's permit rather than a blank form. What changed is called out at the top, along with why it matters, so neither the owner nor the agent rereads a file to find the one line that moved.

Scope

What Spruce covers.

Applications the public can finish

A portal where owners apply, upload, and pay, with the required fields and documents following from their own answers. The review file is prepared for your staff the moment it is submitted.

By role

What changes, and for whom.

The field inspector

Arrives briefed instead of blind, logs the visit offline, and confirms a drafted finding with the code section already attached rather than writing it up back at the office.

The health agent

Opens a review file that is already prepared, sees which documents disagree with the application before reading them, and spends the time on the decision instead of assembling the packet.

Department leadership

Changes categories, fees, and deadlines by configuration instead of a change request, and can answer a records request from a trail that records who did what and why.

The business owner

Applies, uploads, and pays without a phone call, sees where the application stands at any hour, and renews from last year instead of starting over.

Part of the platform

Spruce runs on the same engine as the rest of PH360.

Spruce runs on our public health reasoning engine, the same one behind the rest of PH360. The FDA Food Code is built in, and your own adopted rules, forms, and fee schedule sit alongside it. That is also why you change your own categories, documents, and deadlines instead of filing a change request with us.

Common questions

Spruce FAQ.

How do we get started?

We configure Spruce with you: your establishment categories, required documents, fee schedule, inspection frequencies, priority levels, and correction deadlines, plus the forms and certificates your jurisdiction issues. Schedule a walkthrough and we will scope it against your own permits.

Does it work with the code we actually adopted?

Yes, and that is the point. The FDA Food Code is built in, and your local adoption and amendments sit alongside it. Findings are drafted against what your jurisdiction enforces, with the section and the source shown so the inspector can verify it before citing.

What happens in the field with no signal?

The inspector keeps working. The establishment history, prior citations, and the checklist are stored on the device, and the visit syncs when there is a connection again. How long a device may stay offline before it must sync is a setting you control.

How do we know an AI-drafted citation is right?

You check it, and Spruce is built to make that quick. Every drafted finding shows the code section, the source it came from, a confidence level, and the code text in plain language. It only proposes findings it has a grounded source for, and when it does not it abstains rather than guessing.

Is there a human in the loop on the AI?

Always. Anything AI-generated is marked in purple and cannot complete on its own. The agent accepts or changes the proposed day plan, AI-drafted findings must be marked reviewed, the inspector is the one who cites, and returning or denying an application requires a rationale recorded under a name.

What happens to our current permitting system?

Most departments start with one permit type in Spruce and leave the rest where it is until they are ready. Single sign-on, directory integration, and access to your data through an API get settled in that scoping conversation, and we will tell you plainly what is in place and what we would build.

Are those real records in the screenshots?

No. Every screen is the actual product, and the people, businesses, and permits in them are sample data. Nothing on this page came out of a live department.

See it against your own permits.

Thirty minutes. Bring your establishment categories, your fee schedule, and the code you adopted, and we will run Spruce against them.