Restaurant case study (DRAFT - placeholder)

Status: DRAFT. This page is a template for a working restaurant case study. Replace the bracketed sections with a real customer story (with the customer's permission and preferred level of attribution) before promoting this URL externally. The structure below is the one ChillSense uses for restaurant / pub case studies.

The customer

Name: [Restaurant name, or "A Melbourne neighbourhood restaurant" if anonymised]
Location: [Suburb, state]
Format: [Independent restaurant / gastropub / neighbourhood diner]
Cold-chain assets: [Walk-in cool room, 3 line prep fridges, 1 bar fridge, 1 upright freezer]
Service: [Lunch + dinner, six days a week, ~80 covers per service]
Food safety regime: [State environmental health, with semi-annual inspections; insurance audit annually]

The problem

[Open with a concrete operational pain. Examples:]

The walk-in cool room had no monitoring at all; nobody knew it was failing until the chef arrived at 5am and the floor was wet.
The previous system was a temperature data logger in the walk-in that nobody downloaded for months; an audit request triggered a panicked CSV export and Excel cleanup.
Multiple food safety incidents in the previous year had no contemporaneous corrective-action records, because the staff who handled them at 2am had nobody to report to until the next morning.

The ChillSense deployment

Hardware: Restaurant Pack - 1 hub + 6 sensors.
Subscription: 6-sensor monitoring - [monthly or yearly] (5% volume discount).
Sensor placement: 1. Walk-in cool room - door-side. 2. Walk-in cool room - deep inside. 3. Line prep fridge - cold-side. 4. Line prep fridge - garde-manger side. 5. Bar fridge. 6. Upright freezer.
Hub placement: [Single hub on the back-of-house wall; clear line of sight to all six sensors. Coverage check confirmed in the dashboard before going live.]
Install time: [Two hours, including staff briefing and threshold tuning per asset.]

The first month

[Describe what happened in the first month. Common patterns:]

The two walk-in sensors immediately showed the door-side cycling much wider than the deep sensor during service, confirming the door seal was already weak.
The owner tuned thresholds per asset over the first fortnight based on real readings rather than manufacturer specs.
Alert contacts were set up with the head chef as primary and the owner as backup; sous chef received SMS for line-fridge incidents only.

The outcome that mattered

[The heart of the story - a concrete incident the platform handled.]

Example structure:

At 2:15am on [date], the walk-in cool-room sensors started drifting up; by 2:25am the deep sensor had crossed the actionable threshold and an SMS landed on the sous chef's phone. The sous chef (off-duty, but on the after-hours roster) opened the mobile action page from bed, drove in, found the compressor had failed, moved the high-value protein stock to the spare freezer in the next building, and logged the corrective action - all before 4am.

"We saved the stock because somebody knew within 10 minutes that the walk-in had gone, not 6 hours later when the chef arrived for prep," said [Owner name]. "The audit trail on the dashboard turned the warranty claim against the cool-room supplier from a wrestling match into a five-minute conversation."

The compliance side

[Describe how the HACCP reports changed the audit experience.]

"Before ChillSense, an audit meant a full day of compiling records and explaining gaps. Now I export the previous 12 months of PDFs in five clicks. The auditor said it was the cleanest pack he'd seen all year."

What the customer says about ChillSense day to day

[2-3 short quotes about specific behaviours.]

"Head chef checks the dashboard at the start of service. He's done in 30 seconds. Before, he was checking each thermometer by hand. Now he trusts the system."

"We had two SMS alerts last month. One was a door left open after a delivery; the other was a real sensor signal-strength issue we fixed with a second hub. Last year, neither of those would've shown up as anything until something broke."

"I forwarded last month's PDF to the insurance auditor without even opening it. He came back and said 'this is fine'."

Configuration details (for technical readers)

Per-asset thresholds:
Walk-in cool room: [range]
Line prep fridges: [range]
Bar fridge: [range]
Upright freezer: [range]
Alert contacts: Head chef + sous chef + owner; mixed SMS and email.
Escalation: Sous chef as overnight primary; owner escalation if no acknowledgement within 15 minutes.
Reporting cadence: Auto monthly PDF; ad-hoc per-asset reports during the walk-in incident investigation.
Subsequent additions: Second hub added to extend coverage into a separate prep room six months in; no change to subscription.