Create an operational request
One request can contain multiple independently matched personnel, transport, resource, module, and service needs.
For Company staffing manager, Incident operationsHelp Center
Search 75 guides covering every major Wildland Exchange workflow.
Operational needs and matching
One request can contain multiple independently matched personnel, transport, resource, module, and service needs.
For Company staffing manager, Incident operationsA match requires compatible type or role, dates, status, location, availability, and any hard requirements.
For EveryoneEvery missing component should create an independently configurable item.
For EveryoneInvitations are scoped, time-limited, and may already have a response.
For EveryoneAvailability must be active, within its time window, visible to the intended audience, and owned by the correct provider.
For EveryoneOffer comparison preserves component coverage, provider terms, documents, and partial acceptance.
For EveryoneFuel type and minimum tank capacity should appear only for fuel support or a swamper bringing fuel support.
For EveryoneEach accepted request item creates a fulfillment record that tracks the committed component.
For EveryoneRanking considers structured compatibility, distance, availability, pay, and provider constraints.
For EveryonePublishing is blocked until every selected need item has its required structured fields.
For Company staffing manager, Incident operationsRecurring schedules create occurrences only while active and within their configured window.
For EveryoneRoles are filtered by the selected company resource and operational capability catalog.
For EveryoneRequest options come from the canonical catalog and the company's supported resources and templates.
For EveryonePersonnel responses and provider offers are structured separately and can cover one or several request items.
For Everyone