The Zero-Overtime Directive
You are a newly promoted lieutenant commanding Station 3, a single-engine house in a 22-year-old career department with four platoons and a $412,000 overtime line. The fiscal year ends June 30. It is March 1 and 78% of the account is already spent. Two of your six firefighters are on long-term injury leave with no return date, and a third begins 12 weeks of military leave on April 1. Minimum staffing is four per apparatus, and department policy mandates callback of an engine company on every reported structure fire. The deputy chief, under pressure from the city finance office, has directed all station commanders to hold overtime to zero for the remainder of the fiscal year and to "make it work with mutual aid."
1. What analysis and data would you bring to the meeting with the deputy chief before you respond to the directive? Explain why each item matters.
Read the worked answer
Compute the actual run rate first, because the directive is built on a number nobody has checked. 78% of $412,000 spent in 8 months is roughly $40,200 per month. Four months remain and about $90,600 is unspent, so the projected need is roughly $161,000 - a shortfall near $70,000. That reframes the conversation from "spend less" to "which services you are willing to reduce."
Separate controllable from non-controllable overtime. Break the 78% into callbacks, holdovers, sick-leave coverage, training details, inspection and public-education assignments, and special events. Only the discretionary categories can realistically go to zero; callbacks are driven by run volume and the mandatory callback policy.
Verify the legal and contractual floor. Review the CBA for minimum staffing language, callback and holdover provisions, and any comp-time provisions under FLSA §207(o) (which requires an employee agreement, so it is not a unilateral management tool). Confirm USERRA obligations for the military leave and workers' compensation rules for the injury leave.
Quantify the service impact. Pull runs per day, structure fires per month, and the last 12 months of callback events. Model the specific dates when Station 3 will fall below four with the April 1 military leave - that converts an abstraction into a calendar.
Map the mutual-aid assumption. Verify what automatic aid actually delivers and its response time. "Make it work with mutual aid" is only an answer if the neighboring company is closer and available; if it adds six minutes to a first-arriving engine, that is a documented risk decision and the chief should own it in writing.
2. State your substantive recommendation and the trade-offs. What would you actually propose in place of "zero"?
Read the worked answer
Recommend a documented cap with a reporting mechanism rather than an unachievable zero. A number the deputy chief can defend upward is worth more than a directive that everyone quietly ignores.
Proposed package, in order of savings per unit of risk:
- Suspend discretionary overtime immediately - training details, inspection overtime, public-education events, standby for non-emergency community events. Savings are clean and the risk is administrative.
- Tighten the callback policy by incident type. If the policy callback is a blanket rule, propose a documented exception for single-company, non-structure responses where an automatic-aid company is en route. This should go through the labor-management process, not be announced.
- Schedule rather than call back. Pre-schedule a recall list for known high-volume periods at straight time where the CBA allows, converting premium hours into planned hours.
- Seek a documented staffing variance for the April–June military leave period from the deputy chief, with the specific dates and the specific response-time impact stated.
Name the trade-offs out loud: longer response times on the second-due engine, reduced inspection and public-education output, higher injury and liability exposure when apparatus run at three, and morale effects from repeated mandatory holdovers. Offer a weekly two-page burn-rate report so the finance office sees the trend instead of discovering a surprise in July.
The credibility move is to say: I can hold the discretionary categories to near zero; I cannot hold callbacks to zero without either violating staffing policy or degrading response, and here is the calendar showing which days that happens.
3. The deputy chief holds firm and repeats the zero directive. What do you do next, and what do you document?
Read the worked answer
Do not comply silently, and do not comply by breaking a rule to satisfy a budget. The sequence matters.
- Request the directive in writing. Not as a challenge - as a request for clarity on what you are authorized to do when staffing falls below four. If it stays verbal, send a confirmatory email summarizing your understanding.
- Deliver a dated risk projection. A short memo listing the specific shifts in April, May, and June when Station 3 will be at three or fewer without overtime, the response-time consequence, and the mutual-aid assumption it depends on. Attach it to the request for written direction.
- Ask for documented risk acceptance. "If the department directs that no callback be made on these dates, please confirm in writing so the record reflects that this was a command decision." This is not insubordination; it is the officer's duty to make risk decisions visible to the person who owns them.
- Notify labor relations. If the directive conflicts with a CBA staffing or callback article, the department has an obligation to meet and confer. You are not the bargaining agent, but you must flag it before the union files.
- Keep a contemporaneous log. Dates, staffing levels, callback requests denied, incidents affected. Contemporaneous notes are the only documentation that survives a grievance or an injury investigation.
What you must not do: unilaterally ignore the directive, unilaterally rewrite the callback policy, or quietly run apparatus below minimum without telling anyone. Each of those converts a budget problem into a discipline problem - yours.