Per-person logging
Served, refused, or partial recorded for every individual on the unit — a true record, not a single tally for the whole housing area.
Meal Checks
Document every meal served — and every one refused.
A meal refusal is more than an empty tray. It can be the first sign of a hunger strike, a medical decline, or an unmet dietary or religious need. Sentry Inview turns meal service into a clean, per-person record your medical staff, supervisors, and counsel can rely on.
Why it matters
A refused tray is a data point — one that matters for medical monitoring, for spotting a hunger strike early, for honoring dietary and religious needs, and for showing exactly how your facility cared.
Three meals a day, every individual, on the record
3×/day
meals documented per person — served, refused, or partial, every service
Per-unit meal logging
0
paper tally sheets to transcribe, lose, or reconcile after the fact
Captured at point of service
1
unique officer ID, location, and tamper-evident timestamp behind every entry
Defensible record
100%
of refusals carry a reason — turning a blank into clinically useful context
Reason required at log
Built for the tray line
Per-person logging that fits the pace of meal service
The unit roster loads on the officer's device with the right diet flags already attached. As trays go out, each individual is marked in a tap — and refusals capture the reason while it's fresh.
- Served, refused, or partial logged for every individual on the unit — not a single line item for the whole housing area.
- Refusal reasons at the point of service — not hungry, religious or dietary issue, protest, medical, asleep, and more.
- Special & religious diet flags surface on the device so the right tray reaches the right person, every time.
- Medication-with-food cues prompt officers when a meal coordinates with a scheduled dose.
Lunch service · Unit B
B-114 · Tray servedStandard diet · Ofc. Reyes #447111:32Served
B-115 · Tray servedHalal · diet flag verified11:33Served
B-117 · RefusedReason: not hungry · 2nd in a row11:34Refused
B-120 · RefusedReason: protest · 3rd in a row11:35Flagged
Capabilities
A meal record that does more than count trays
Every tap during service builds an accurate, individual history — and the system watches for the patterns that need a human response.
Refusal reasons
Captured at the point of service while the context is fresh — not hungry, religious or dietary issue, protest, medical, asleep, and more.
Consecutive-refusal detection
Automatically flags when someone refuses a configurable number of meals in a row, routing a hunger-strike or medical referral to the right staff.
Special & religious diet flags
Surfaced right on the officer's device so the correct tray — medical, kosher, halal, allergy-aware — reaches the right person.
Medication-with-food cues
Prompts coordinate meals with scheduled doses so medication that must be taken with food isn't missed at the tray line.
Tray counts & reconciliation
Trays served are reconciled against the live housing roster, so over- and under-counts surface before service ends.
Defensible by default
Tamper-evident, audit-ready
Every meal entry is bound to a unique officer ID, a verified location, and a timestamp that can't be back-filled — a record that holds up in audits and grievances.
Our compliance approachFrom tray to record
Four steps, every meal service
The roster pulls the meal list and diet flags
Sentry Inview loads the current housing roster onto the officer's device, with special and religious diet flags already attached to the right individuals.
Officers log served or refused, person by person
As trays go out, each individual is marked served, refused, or partial in a single tap — keeping pace with the line without slowing it down.
Refusals capture a reason and flag patterns
Every refusal records why — not hungry, religious, protest, medical, asleep — and the system tracks how many meals each person has missed in a row.
Consecutive-refusal alerts trigger a referral and reports
When refusals cross your configured threshold, a hunger-strike or medical referral routes to the right staff, and meal-service reports export on demand.
Where it earns its keep
One workflow, several jobs done well
Hunger-strike monitoring
Consecutive-refusal detection catches a developing hunger strike early and notifies medical and supervisors before it becomes a crisis.
Special & religious diets
Diet flags on the officer's device protect medical and religious accommodations — a compliance-sensitive area that paper sheets handle poorly.
Medical & medication-with-food
Refusal records are clinically relevant, and meal cues keep doses that require food on schedule — closing a gap between the kitchen and medical.
Liability & grievance defense
Clear, timestamped records of meals served and refused rebut grievances and claims — and document exactly how your facility met its duty of care.
Accountability
A record that supports care and rebuts claims
Meal documentation does double duty. The same per-person history that helps medical staff monitor a refusing individual is the record that answers a grievance or a discovery request.
- Refusal documentation supports medical and hunger-strike monitoring with a clinically useful timeline.
- Diet-flag handling shows accommodations were offered and honored, not overlooked.
- Tamper-evident entries rebut grievances and protect the facility with proof rather than recollection.
NCCHCACA StandardsState Jail Standards
On-demand reporting
Exports your staff actually use
- Meal-service compliance by unit and shift
- Refusal trends across days and individuals
- Individual meal histories for medical or counsel
Questions
Meal checks, answered
How does the consecutive-refusal alert work?
You set the threshold — for example, three refused meals in a row. When an individual crosses it, Sentry Inview automatically routes a hunger-strike or medical referral to the staff you designate, with the full refusal history attached so the right people can respond quickly.
Will logging slow down the meal line?
No. The roster loads in advance with diet flags already attached, and each person is marked served, refused, or partial in a single tap. Refusal reasons are chosen from a short list, so documentation keeps pace with service instead of holding it up.
How does this hold up in a grievance or audit?
Every meal entry is bound to a unique officer ID, a verified location, and a tamper-evident timestamp that can't be back-filled. Individual meal histories and compliance reports export on demand, so you can show exactly what was offered, what was refused, and when — with proof rather than recollection.
Ready when you are
See meal checks running on your units
Book a walkthrough and we'll map your meal schedule, diet flags, and refusal thresholds to a live demo — using your housing layout.