Request Builder · EM Field Guide

This is where requests succeed or stall out. The reviewer has your form, a ringing phone, and no picture of your incident except the one you paint. Vague requests stall. Specific requests get filled. Answer the six questions so a stranger who has never seen your incident could fill the request without calling you back -- then copy the assembled request into your EOC platform, a STAR, a 213RR, or an email.

Why Requests Stall

The problem	The fix
No justification, or “needed for response”	Five-line formula, every time
A quantity with no math	Show the calculation in line 3
An item with no specs -- “generators,” “pumps,” “buses”	Size, power, connections, capacity, terrain -- or request the mission instead
Brand-locked -- “3 Honda EU7000is”	State the capability; accept equivalents unless there's a real compatibility reason (say what it is)
No needed-by time, or “ASAP”	A date and an hour. Urgency lives in the consequence line, not in capital letters
No site POC, or a site that can't receive	Name, phone, hours on site; note the forklift, the dock, the locked gate
No proof you exhausted your level	Vendor emails, screenshots, mutual aid answers -- attach them
Bundled needs in one request	One need, one request -- requests are tracked, filled, and closed one at a time
Submitted and abandoned	Confirm receipt, track every period, answer returns same-day
Nobody authorized it	Signature from the person who can commit funds, routed through the ordering point

Sample Requests -- Weak vs. Strong

emrevolution.net/solutions/resource-request/builder EM Field Guide · Resource Request System