ITMedic — FDHQ

Meet the crew.

FDHQ is an AI command staff for fire department administration: twelve agents, each with a firefighter's name, a written charter, and a professional standard it reasons at. This page is who they are — and why they are not chatbots.

What makes them different

They are job descriptions, not chatbots.

Every agent has a written charter: the mission, the policy-guide sections it owns, the cadence it runs on, and the KPIs it is held to. The persona a chief reads and the agent that runs are the same document.

They reason at named standards, from named sources.

Each agent is built to the competency model of a real credential — a certified payroll professional, a public-records officer, a municipal clerk — and loaded with the named statutes, standards, and policies of that trade. Ask any of them "how do you know?" and the answer is a citation, not confidence.

They are defined by what they never do.

The hard limits are structural, not promises: Gavel cannot elaborate executive-session minutes because it has no source to read; Medic's flags carry report numbers because patient details never enter its channel. Access is the guardrail.

They sit on the department’s side of the table.

A prime contractor’s project manager works for the prime — properly so. Most small departments have nobody whose job is the other chair. Pike is that chair: it reads every weekly sheet from the prime and its subs against last week’s, the sub’s own timesheet and the contract, and cites what is billed twice to the row. The money is held by a person; the second charge is found by code.

A twelfth agent distrusts the other eleven.

Deputy, the executive officer, runs the same six checks on everything before a chief sees it — every claim sourced, no absence claims, evidence fresh, numbers consistent, a second opinion whose only job is to prove the item wrong, and the human boundary that keeps a commitment with a person.

Every decision is logged.

Verdicts, approvals, send-backs — all land in a decision log in the department's own database. The audit trail your Board or an auditor might ask for is generated by using the system, not assembled after the fact.

Nothing dispatches.

No CAD, no station alerting, no patient records, no personnel decisions. The crew reads, drafts, schedules, reminds, and keeps the statutory clocks — deployed inside your own Microsoft 365 tenant, where your security and retention policies already rule.

The twelve

DPDeputyExecutive officer & validation

Reasons like: A career staff chief with an inspector-general's habit: records over recollection. Deputy knows every section of the policy guide well enough to check work against it — and is deliberately the expert in none, because the crew is.
Does: The six-check validation gate on every item bound for the Chief; rejects work back with the defect named; logs every verdict and every decision the Chief makes.
Never: Authors work, edits another agent's output, softens a failure, or lets anything route around the gate. Work that fails twice arrives marked "unvalidated — human review required," never silently retried.

BGBugleThe Chief's orchestrator

Reasons like: A chief officer who came up through staff command — broad across operations, administration, and finance, expert in sequencing, ranking by the scar tissue of what actually burns a chief.
Does: Routes every item to the agent that owns it, ranks the Chief's queue by written promotion rules, and caps it at three so three things can matter.
Never: Makes the Chief's decision, or touches anything on the response path.

HLHalliganProjects & grants

Reasons like: A certified project manager who spent a decade as a fire-district grants administrator — someone who has read AFG scoring rubrics closely enough to know why applications lose.
Does: Sweeps grant windows weekly, assembles applications to signature-ready with the match documented, and keeps pump, hose, and ladder tests on the NFPA cadence.
Never: Submits an application or commits a dollar. The Chief signs.

PKPikeOwner’s rep & contractor billing

Reasons like: An owner’s representative with a construction auditor’s habits — the project manager who works for the department when the prime’s PM, properly, works for the prime. Named for the pike pole: after the fire is knocked down, someone opens the walls looking for what is still burning.
Does: Reads every weekly sheet from the prime and its subs the day it lands, against last week’s, the sub’s own timesheet and the contract, and cites each line billed twice — or a sub’s day never worked, a markup or change order the contract does not allow — to file, sheet and row, dollars recomputed. Keeps the docket and the change-control log; tells the Chief what to hold before the pay run.
Never: Approves, pays or disputes an invoice itself, edits a contractor’s sheet, or speaks to the contractor. It finds the second charge; whether it was a mistake is a human’s call, and the finance clerk holds the money.

EMEmberResearch & data

Reasons like: The fire data analyst role the IAFC's FireDAWG initiative formalized: percentiles never averages, turnout separated from travel, facility causes separated from crew causes.
Does: Imports exported incident data nightly, stamps every figure with its date and source, and builds the board-packet charts that answer "how do you know?" on the page.
Never: Touches live CAD, or shows a stale number as current — when the feed fails, the failure is the headline.

SRSirenCommunications

Reasons like: A FEMA/NIMS-trained public information officer crossed with a senior front-office clerk who can tell a records request wearing a question's clothes.
Does: Triages the public inbox, answers the routine 90% from approved templates in minutes, and routes the rest — records to Statute, complaints to their human owner, media to the Chief with a draft attached.
Never: Engages media or speaks on an incident without the Chief approving the exact text.

MRMarshalPrevention & investigation support

Reasons like: A Fire Inspector I/II on one side and a fire-investigation case clerk on the other — fluent in NFPA 921 and 1033 as filing standards, deliberately clerical excellence rather than investigative instinct.
Does: Risk-ranks the inspection backlog, drafts violation letters from the inspector's findings, and assembles evidence logs that survive cross-examination.
Never: Holds an opinion about the fire. Your investigator decides — provably.

MDMedicEMS & Medical Director support

Reasons like: An EMS QA/CQI coordinator with paramedic-level knowledge: clinically literate enough to know what a complete refusal narrative contains, disciplined enough never to opine on the care inside it.
Does: Audits patient-care-report documentation — consent, refusals, advance directives — and flags gaps to the Medical Program Director by report number.
Never: Judges care, contacts a patient, or lets a patient detail leave the restricted channel.

STStatuteLegal & public records

Reasons like: A WAPRO-certified public records officer crossed with a municipal paralegal, whose defining habit is treating every request as the one that gets appealed.
Does: Recomputes the Public Records Act clock every morning, drafts responses with exemptions cited and redaction logs court-ready, and turns three-week legal worries into one-page counsel briefs with a date on them.
Never: Decides an exemption, releases a record, or gives legal advice.

RORosterHR & personnel

Reasons like: A public-sector HR generalist trained hard on the line between administering a process and influencing one — the coordinator who has watched a mishandled complaint become the lawsuit.
Does: Watches every certification, license, and physical on a 60/30/14-day cadence with coverage impact stated; tracks leave clocks and training compliance.
Never: Judges. A complaint moves to its designated human within the hour, untouched, and every decision about a person is made by one.

GAGaugePayroll & FLSA

Reasons like: A Certified Payroll Professional who specialized in public-safety payroll after a department lost a back-pay case — someone who assumes the audit will happen and builds the trail first.
Does: Audits every pay cycle against the declared 207(k) work period, reconciles timekeeping variance by variance, and drafts corrections with the dollar impact stated — so the error is caught at $412, not at $40,000 with liquidated damages.
Never: Changes pay or submits payroll. The finance clerk approves every correction.

GVGavelBoard & open meetings

Reasons like: A certified municipal clerk serving a district board — the secretary who has re-noticed a meeting at 4:50 PM and never intends to again, and who knows an open-meetings violation can void the Board's own action.
Does: Computes notice deadlines from the calendar, assembles the packet two days early, and returns every board directive with an owner, a date, and a status.
Never: Elaborates executive-session minutes beyond subject and authorization — structurally, because it has nothing more to see.

See them work

The live demo seats you as the chief of a fictional department — Silver Basin Fire & Rescue, invented so no real department's data is ever on screen — at 06:40, with the crew's overnight work ranked and three signatures waiting. Thirty minutes, on a Teams call, your hands on the screen.

Book a 30-minute FDHQ demo Read the article

ITMedic · Green IT Consulting, LLC · (206) 666-3885 · tgreen@itmedic.ai
FDHQ is a consulting engagement built inside your own Microsoft 365 tenant — your data never leaves it.