Administration, Budgeting, and Resource Allocation
This domain tests whether a captain can run a command as an organization: staffing against a table of organization, controlling overtime, procuring within the rules, and defending resource decisions with data.
Staffing and the table of organization
The table of organization sets authorized headcount by rank and title. A captain tracks assigned versus authorized strength, sick and leave rates, and detail obligations that strip the command of patrol coverage. Vacancies are requested through the chain with justification, not by complaint.
Overtime
Overtime is the most scrutinized line in a command budget. Drivers include court appearances, details, arrest processing, and backfill for absences. Control means forecasting, pre-approval thresholds, daily tracking against plan, and a variance explanation when the command exceeds projection.
Procurement and assets
Purchases follow City procurement rules, including required approvals, competitive thresholds, and minority- and women-owned business participation goals. Equipment is inventoried and accounted for; a command that cannot produce an asset on request has a fiscal and an integrity problem.
The budget cycle
The City fiscal year runs July 1 through June 30. Commands submit needs during budget development, then manage against the adopted plan, with quarterly variance review.
Worked example
Overtime is projected to exceed allocation by 12 percent in the third quarter. Rather than cutting all overtime, the captain disaggregates the drivers, finds that court appearances and detail backfill account for most of the variance, adjusts scheduling to reduce backfill, and requests an allocation adjustment with documentation. The variance explanation is the deliverable.
Traps
Treating overtime as one number instead of its drivers; requesting staff without workload justification; ignoring procurement thresholds; failing to reconcile inventory; presenting a variance without a corrective plan.