For transit police officers

The rotation

Transit schedules are built from service hours backwards. Where a system runs close to twenty-four hours, that usually means twelve-hour Panama or Pitman cycles. Where it shuts overnight, eight-hour watches on a 5-2 5-3 are more common, with heavier coverage stacked onto the morning and evening peaks.

Some agencies add a split or an overlap tour that exists purely to double the officers on the platform between four and seven. Whatever your agency runs, you set it once and the year fills itself in.

Your jurisdiction moves

A district officer answers to one court. A transit officer can make an arrest in one county on Monday and another on Thursday, and be summonsed to both. That is the single biggest reason to keep court dates somewhere other than your head.

Court and jail addresses go in the directory once — every courthouse your line passes through, with the addresses and contacts — and they are there whether or not you have signal underground.

The event calendar is somebody else's

A stadium on your line, a parade route, a festival, New Year's Eve. Transit surges when the city does, and those dates are published well in advance by people who are not your agency.

Put them on the calendar as soon as they are announced. They decide which leave requests are realistic months before the roster comes out.

Details and overtime

Where the agency permits outside work it is often at the same venues that generate the surges. Save each employer once, log the hours and the rate as you work them, and mark what has actually been paid.

Underground, without a signal

Platform level is where the phone stops working. Everything in BlueShifts is on the device — the rotation, the directory, the addresses and codes — and none of it needs a connection to open.