This guide provides an operating framework, not legal, financial, safety, medical, licensing, or regulatory advice. Adapt it to your business and local requirements.
Define what counts as an emergency
Publish a plain list of the situations that qualify for an after-hours call: water running, no heat in winter, a dangerous fault. A plain threshold keeps the phone from ringing for a problem that can wait until morning, and it hands the person on call a script instead of a judgment call at 11pm. Define it once and everyone stops arguing about it.
Rotate on-call fairly
Post the on-call schedule somewhere everyone can see it, so the burden is shared and the fairness is visible. People stay willing to answer a call they see rotate around to the pool. The tech who feels stuck on duty forever is the tech who starts missing calls.
Price emergencies to cover the cost
Set a firm after-hours rate and an arrival charge that actually pays for the disruption, and publish both. Transparent pricing does two things at once: it compensates the rotation fairly and it quietly screens out the calls that are not really emergencies. The money ends the resentment, and the sheet ends the frivolous ring.
Give on-call a short protocol
Give the person who answers a single sheet script for those calls: the greeting, the questions, the point at which you wake the field versus log it for the morning. A script means the answer reads identically at 10pm and 10am, and the operator is not improvising on no sleep. Boring, and it pays off.
Review the rotation quarterly
Count up which after-hours calls were genuinely urgent and which were not. Adjust the threshold and the roster to match the real load, and the phantom calls shrink fast. The quarterly look keeps the rotation honest and the crew rested.