The county emergency management office is reviewing its activation procedures. Two senior staff have been asked to speak to one question: if the office adopts an agent to help with shelter rosters, who owns the roster? The operations chief and the planning chief disagree, and they say so plainly. This is an edited version of what each of them argued.
The operations chief: speed decides everything in the first hours
During an activation, shelters open faster than the paperwork can follow. Sign-in sheets arrive by photograph, by email and sometimes by a runner. The roster I need at the operations table is the one that tells me how many people are in each shelter, who needs a medical referral, who has pets and where the cots are running out. Today a staff member retypes those sheets into a spreadsheet while the numbers change under them. An agent that reads the sheets and builds the roster as they arrive gives me a picture while it still matters.
The planning chief: a roster is a record, not a picture
I do not dispute the speed. But a roster is also the document the recovery team uses months later, and the one that feeds the reimbursement packet. If an agent misreads a handwritten name, or merges two people with the same surname, that error is in the record for good. I have seen a roster double count a household because two volunteers recorded it on different shifts. The person who knows the shelter is the shelter manager, and the roster has to answer to them.
The operations chief: then let the shelter manager verify, not retype
Nobody is proposing to take the manager out. The agent drafts the roster, flags every line it is unsure about, and the manager approves the version that goes into the log. Compare that with today, where the manager is both the source of the sheets and the person typing them up at midnight. Verification is a better use of a tired person than transcription.
The planning chief: verification only works if the flags are honest
That is my concern. A flag that appears on every third line teaches people to stop reading flags. A flag that never appears teaches them to trust a draft they should not. Before I accept your version I want to see how the agent marks uncertainty, what it does with a name it cannot read, and whether it keeps the original sheet linked to each line, so that anyone can look at the source in seconds. I also want the version history kept, so we can show later which entries changed and who changed them.
The operations chief: agreed, and I want one more rule
The agent does not decide anything about people. It does not decide who is eligible for a service, who moves to another shelter, or who is told what. It counts and lists, and a person acts on the list. If it ever drifts toward telling us what to do with a household, it has stepped past its job.
The planning chief: then here is where I land
I will accept an agent that drafts the roster from the submitted sheets, links every line to its source, marks what it cannot read and keeps a full history. The shelter manager verifies and releases each version. The planning section owns the final record. We exercise this in a tabletop before a real activation, with deliberately messy sheets, and we review how it handled them.
The operations chief: and I will take that
The roster belongs to the shelter manager and the planning section. The agent belongs to both of them as a tool. If we write that down, I have my picture during the first hours and you have a record you can defend afterward.
What the office wrote down
The office adopted a single paragraph. The agent drafts and flags. Shelter managers verify and release. Planning owns the record. Operations reads the verified roster, never the raw draft. Everyone agreed it was shorter than the argument that produced it.