Replace the Paper Daybook With Digital Log Books
Command Established gives your department real log books — not a spreadsheet, not a Slack channel, and not a binder of half-legible handwriting. Capture daily activity, shift pass-on reports, drills, maintenance notes, and notable events in the right book for the right scope: department-wide, by station, by apparatus, or by shift. Every entry is timestamped, attributed, searchable by the members allowed to see it, and stays in the record forever.
Log Books for Every Scope of the Department
Create as many log books as your department needs and scope each one where it belongs. A station daily log lives at the station scope. A shift pass-on book lives at the platoon scope. The Tower 1 daily check log is scoped to that apparatus. A department-wide "Chief's Notices" book is available across the department.
Scope is set when you create the book and stays locked, so the entries that pile up over the years never lose context. Visibility is separate: keep an operational book open to the whole department, or mark a sensitive book Restricted. Filter the books list by scope badge to find the right one fast.
The log books index for an authorized chief — books stay tagged by scope, and restricted books carry a clear lock badge.
Keep Command-Staff Notes Restricted to the People Who Need Them
Some running logs should not be department-wide: command handoffs, personnel administration, labor matters, and other leadership-only notes. Mark a book Restricted and only owners, admins, its named editors, and the viewer users or groups you choose can see the book or any of its entries. Editors automatically count as viewers, so a person never receives write access to a book they cannot open.
For everyone else, the book does not merely look locked — it does not appear. Unauthorized members cannot discover it in the books list, search, dashboards, recently viewed items, mention back-references, or notifications, and a direct link reveals no more than a nonexistent book would. Department-wide log permissions do not bypass that visibility boundary. Restricted announcements also stay off shared station-board displays, where there is no individual viewer to authorize.
Book-level access stays understandable: choose Restricted, then grant view or editor access to specific people and groups.
A Real Editor Built for Station Life
Each log entry opens in a familiar rich-text editor with the formatting tools crews actually use: headings, lists, tables, bold and italics, links, block quotes, and inline images. Drag a photo from a tablet straight into an entry to document a visitor, a vehicle in the bay, or a piece of broken gear.
Per-book entry templates pre-fill the editor when crews start a new entry — "Apparatus checks", "Shift change summary", "Public visit report", whatever your department needs as the starting point. Crews fill in the blanks instead of reinventing the wheel every shift.
A real entry, not an empty form — rich text and @-mentions rendered exactly as the crew wrote them, with the entry type, author, timestamp, and the oncoming officer's acknowledgement all in view.
Categorize Entries by Type — Notes, Pass-Ons, Drills, Maintenance, and More
Every entry gets a type so books stay useful as they grow. Drop-down picker covers the categories fire stations actually log:
- Note — general entries and observations
- Pass-On — end-of-shift turnover and oncoming-shift briefings
- Drill — in-station training, evolutions, and skill practice
- Maintenance — apparatus and equipment notes that aren't yet a work order
- Incident Follow-Up — debriefs and post-incident notes that didn't fit on the run report
- Announcement — department-wide notices, schedule changes, and visitors
Filter the entry feed by type to pull every pass-on from B-shift this quarter, every drill on Engine 3 last year, or every incident follow-up tied to a member.
Pass-On Reports That Actually Get Read — and Acknowledged
The Pass-On entry type is purpose-built for shift turnover, and it closes the loop. When a captain writes a hand-off, drill order, or safety notice the next crew has to see, they flip on Request acknowledgement before posting. The entry then carries a clear "Awaiting acknowledgement" badge until someone signs off.
The oncoming officer opens the book, reads the latest pass-on, and taps Acknowledge — one tap, and the entry records who acknowledged it and exactly when. No more sticky notes on the watch desk, no more "did anyone tell C-shift about…?" The hand-off is in the log, attributed and timestamped, and it stays in the record.
- Request it when it matters — turn acknowledgement on for any entry, not just pass-ons: a policy change in the Notices book, an out-of-service note on an apparatus log, a safety stand-down.
- One-tap sign-off — readers acknowledge in place; a green "Acknowledged by [name] · [time]" stamp is then visible to everyone who can see the book.
- Proof it was seen — the acknowledgement is part of the permanent, auditable record, so "I never saw that" stops being an excuse.
- Undo a mistake — the person who acknowledged (or an admin) can clear an accidental sign-off, and the change is tracked like any other edit.
A station log book — chronological entries grouped by date, with type badges, author avatars, and lead-text previews.
@-Mention People, Apparatus, Incidents, SOPs, and More
Type @ in any entry to mention a person, an apparatus, a station, an incident, an SOP, a work order, a permit — or any other tracked record. Mentions link both ways: tap a name in the log to jump to that person's record, or pull up a personnel record and see every log entry that mentioned them. Same for apparatus, work orders, and everything else.
Mentions of personnel can trigger in-app notifications too. Turn on "notify mentioned personnel" for a book and anyone tagged by name gets a ping with a snippet of context — provided they can see that book. Captains can leave a note for the oncoming shift and trust it'll be seen without a restricted entry leaking to someone outside its audience.
Filter, Search, and Find Old Entries in Seconds
Scroll back through years of entries with filters layered on top. Filter by:
- Date range
- Entry type
- Author
- Station / apparatus / platoon (auto-applied when you're inside a scoped book)
Need to find the last time Engine 2 went out of service for a brake issue? Filter Engine 2's apparatus book by "Maintenance" and search the snippets. Need every pass-on from the night the storm hit? Filter by date and type.
All dates and times show in your department's local timezone, so the "Today / Yesterday / specific date" headers always match what crews actually worked.
Built for Audits, FOIA Requests, and ISO
Log books are an audit artifact. Command Established treats them like one:
- Permanent history — entries are never silently overwritten. Every edit is tracked with who changed what and when.
- Archive, don't delete — archived books and entries stay readable to their authorized audience for legal, ISO, and FOIA purposes, but no new entries can be added.
- Clear attribution — entries posted automatically (CAD imports, scheduled reminders) are clearly marked as system-generated, never attributed to a person.
- Book-level access when needed — control which people and groups can discover a restricted book, alongside who can create books, write entries, and archive records.
When ISO asks for evidence of station-level activity over the rating period, you have a single, searchable, attributed record to print or export.
Ready to Retire the Paper Daybook?
Command Established log books are included with every fire department subscription. Start a free trial — no credit card required — and your crews can be writing in their first digital log book within minutes.