Temperature log: the record an inspector asks for first
A temperature log evidences that food was held safely. What to record, how often, what to do when a reading is out of range, and why gaps are worse than bad readings.
HVAC dispatch software has to cope with maintenance contracts, refrigerant certifications and the weeks when every call is an emergency. What to look for, and what an HVAC operation needs before buying anything.
HVAC dispatch software assigns heating, ventilation and cooling jobs to engineers and keeps the day moving when half the calls are urgent. The trade has three complications most generic scheduling tools handle badly: planned maintenance contracts that must be honoured alongside breakdowns, certifications that legally restrict who may touch refrigerant or gas, and demand that triples in the first cold week and the first hot week of the year.
Every HVAC business knows the first freeze fills the board. The useful response is structural: move planned maintenance out of the peak months when the contract allows, keep a daily reserve of unallocated slots rather than filling the diary in advance, and agree in advance which jobs get deferred when the queue exceeds capacity. Dispatch software helps by making the queue visible; the decisions about what gets dropped still have to be made by someone before the day starts, not during it.
Check how the tool handles refrigerant records. In many jurisdictions logging quantities added and recovered is a legal obligation, and a system that stores it as a free-text note will not survive an inspection.
Ettex Records covers that groundwork: sites with equipment details, engineers with certifications and expiry dates, and a jobs table separating contract visits from reactive calls. Operations running this way arrive at a software decision knowing which features they need, and the wider mechanics of intake and routing are the same as in any service dispatch software.
Certification constraints, refrigerant record-keeping, planned maintenance contracts running alongside emergencies, and strong seasonality. Generic tools handle the scheduling but often not the compliance side.
Schedule contract visits outside peak months where terms allow, hold a reserve of daily capacity for reactive work, and decide deferral rules before the peak rather than improvising.
Often not immediately. A shared jobs table with certifications and equipment history solves most of the pain; buy software when dispatching itself consumes a person's day.
A temperature log evidences that food was held safely. What to record, how often, what to do when a reading is out of range, and why gaps are worse than bad readings.
A clinical audit compares what was done with what should have been done, then changes something. How to pick a topic, set the standard, and close the loop.
A reseller agreement sets who owns the customer, who sets the price, and what happens when it ends. The clauses that matter and the ones that cause disputes.