Technology under a declared emergency: authority and documentation

Reference article · 5 min read

An emergency declaration changes the rules an agency operates under, though not as broadly or as permanently as people assume in the first days of an incident. For technology staff, the practical effect is a set of temporary permissions: buy faster, buy without the usual competition, grant access to people who would normally wait in a queue, and meet in ways your open meetings law would otherwise prohibit. Every one of those permissions is bounded, by the terms of the declaration itself, by state statute and local charter, and by the rules of whatever funding source eventually pays the bill.

The part that gets skipped is the paperwork. Reimbursement reviews and audits arrive long after the incident closes, when the people who made the decisions have moved on and the reasoning survives only in memory. The most useful thing an IT or procurement lead can do during an emergency is write short, contemporaneous records of what was bought, why it could not wait, and who approved it.

What a declaration typically unlocks

Declarations stack. A local governing body declares, a governor may declare, and a federal declaration may follow. Each layer carries its own authorities, and a local declaration does not by itself open federal reimbursement. On the technology side, the common grants of authority include:

• Emergency purchase authority. Raised spending limits, delegated signature authority, or the ability to issue a purchase order outside the normal requisition path.
• Relief from competitive solicitation. Authority to award without advertising or sealed bids when delay would threaten public health, safety, or property.
• Expedited execution. Shortened legal and finance review, or verbal authorization confirmed in writing shortly after.
• Staffing and access flexibility. Emergency hires, mutual aid personnel, overtime, and faster provisioning of accounts for staff working outside their normal role.
• Remote meeting provisions. Temporary modification of in person quorum, notice, or location requirements under state open meetings law, usually for a fixed period and often with substitute public access conditions.

The specifics differ by state and by charter, and emergency statutes are amended often. Confirm your own thresholds and delegations with counsel and your purchasing authority before an incident, not during one.

Emergency procurement is narrower than it sounds

Waived competition is not waived process. Federal grant rules generally permit noncompetitive procurement when a public exigency or emergency will not permit delay, but the recipient still has to justify the sole source, perform a cost or price analysis, and keep the purchase proportionate to the emergency need. Where you can get two or three quotes by phone without losing time, get them and write them down. Partial competition documented beats full competition claimed.

Two failure patterns recur in review. The first is using emergency authority to buy the enterprise platform the agency already wanted, on a multi year term, under an incident that justified a few weeks of capacity. The second is relying on a vendor's claim that its product is reimbursable. Eligibility is determined by the funding agency against its own rules, not by the seller, and a marketing assertion is not a determination.

The controls that do not bend

An emergency suspends procurement steps, not data protection obligations. Criminal justice information, protected health information, federal tax information, and cardholder data carry the same handling rules on day three of an incident as they did the week before. The exposure during a response is predictable: temporary accounts created in a hurry, elevated privileges granted verbally, personal devices used for official work, and files shared through whatever tool was at hand.

Manage it with time limits rather than prohibitions. Give emergency accounts an expiration date at creation. Route access requests through a ticket even when approval is verbal. Log the grant, the approver, and the justification. Schedule the access review for a date certain after demobilization, and actually hold it.

The record that decides reimbursement

Build a single incident file as you go, not afterward. For each technology action, capture the date and time, the person who authorized it, the operational need or failure that drove it, the alternatives considered, the quotes or price basis, and the scope and duration tied to the emergency period. Keep invoices, delivery records, labor and overtime records, and equipment usage logs in the same place, and note where purchased assets ended up.

A memo of a paragraph or two written the same day is worth more than a reconstruction written a year later. Note also that incident communications in email, chat, and text are likely public records in your jurisdiction and subject to retention.

What to require in an emergency contract

• A term tied to the emergency. Scope and duration that end with the declaration, with any continuation handled through a normal competitive action.
• Termination for convenience. With a clear wind down and no penalty tied to early exit.
• Transparent rates. Labor categories, unit prices, and travel stated in writing, even when the award is verbal at first.
• No automatic renewal. Emergency awards that quietly convert to subscriptions are a common audit finding.
• Data return and deletion. Format, timeline, and confirmation of deletion after export.
• Records access and retention. The vendor agrees to retain supporting records and make them available for audit for the period your funding source requires.

Prepare before the next declaration

Do the work while nothing is on fire. Maintain standby contracts and pre negotiated rates for the capabilities you predictably need, such as connectivity, devices, hosting, and surge support. Write a one page delegation matrix showing who may commit funds at what level once a declaration is in effect. Keep a fill in the blank justification memo template in the same folder. Brief finance, IT, and the clerk together, since the open meetings and records pieces usually land on staff who were not in the procurement conversation.

HQT works with state and local agencies on technology planning and systems engineering, including readiness work that makes emergency response decisions easier to document.

Frequently asked questions