About the name
PoppaGPT, your guide to the PAPPG, is named for my late uncle Glen, a lifelong public servant.
Jeremy Floyd, creator of Incident Response LedgerOperations, Planning and Logistics live inside that rhythm. Finance usually doesn't: crew time sits on paper in truck cabs, equipment hours get rebuilt from memory, and the FEMA paperwork is reconstructed months later. Incident Response Ledger puts finance on the same rhythm as the rest of the incident.
Each beat lines up with a moment the incident already has. Tap a slide number to see it.
Crew bosses record crew time (SF-261) and equipment shift tickets (OF-297) on their phones and sign them there, even with no signal.
Finance reviews each day's report and approves it, with overtime figured by the agency's own rules, or sends it back.
Totals by category, the burn rate for the whole event, and what was spent each work day against the average, ready before the briefing starts.
"What is this incident costing us, and what's driving it?" Ask Poppa for a status email to leadership, ready to send. Or say what happened and Poppa drafts the paperwork for the crew boss to sign.
Signed SF-261s and OF-297s as one reimbursement packet, plus FEMA's LEMO workbook in one click, with a checklist of anything not ready.
When finance runs on the same battle rhythm as operations, reimbursement stops being a recovery project and becomes part of the response.
Click any slide to enlarge it, or use the arrow keys to move through them. The screens show sample data for a fictional agency.
PoppaGPT, your guide to the PAPPG, is named for my late uncle Glen, a lifelong public servant.
Jeremy Floyd, creator of Incident Response LedgerA walkthrough takes about 30 minutes. We'll use a sample incident or one of yours.