RFP Management

Status Workflow

3 min read
Updated November 2026

RFP Status Workflow

Understanding each status helps you manage your pipeline effectively.

Status Definitions

Draft

  • A request captured from an e-mail that is still missing details
  • Stays out of the calendar, the availability check and your KPIs until you complete it
Received
  • A new request
  • A request from your form lands here when a room is free and nothing clashes
Review & Send
  • The request needs your review; its contract is never sent automatically
  • The booking page says why: no rooms configured, no room free, a clash with a booking whose contract has been sent or signed, the availability check could not run, or a venue rule (guest count outside the event type's or form's limits, a closing period, a closed weekday)
Contract Sent
  • The contract is out, awaiting the client's signature
Deal To Sign
  • The client has signed, awaiting your countersignature
New Event
  • Both parties have signed: the booking is confirmed
  • The deposit link is sent to the client at this stage
Deposit Received
  • The deposit has been paid
Event Done
  • The event has taken place (a New Event whose date has passed moves here overnight)
Lost, On Hold, Cancelled
  • Lost or cancelled bookings, and bookings paused for now
Superseded
  • Replaced by a newer offer through Create New Offer, and kept as history
  • Leaves the pipeline, the KPIs and the calendar; it is never chosen in the status menu

Allowed Status Changes

The status menu offers only the changes allowed from the current status:

  • Draft → Lost, Cancelled (a draft enters the pipeline only through Complete draft on its booking page)
  • Received → Review & Send, Contract Sent, Deal To Sign, Lost, On Hold, Cancelled
  • Review & Send → Received, Contract Sent, Deal To Sign, Lost, On Hold, Cancelled
  • Contract Sent → Review & Send, Deal To Sign, New Event (with auto-sign), Lost, On Hold, Cancelled
  • Deal To Sign → Review & Send, New Event, Lost, On Hold, Cancelled
  • New Event → Deposit Received, Event Done, Lost, On Hold, Cancelled
  • Deposit Received → Event Done, Lost, On Hold, Cancelled
  • On Hold → Received, Review & Send, Contract Sent, Deal To Sign, New Event, Deposit Received, Lost, Cancelled
  • Event Done, Lost, Cancelled, Superseded → final, no further change

Conflict Detection

The system checks each new request:

  • Against your own bookings whose time overlaps it, on every day of a multi-day booking: the same room at an overlapping time, setup and teardown included (a room combination, each of its own rooms and every other combination that shares one of its rooms count as the same room)
  • Against your rooms' capacity and your venue rules (guest limits; closing periods and closed weekdays on the day the event starts)

With Apaleo connected (in certification, switched on per venue on request), Airplate also checks what Apaleo has free: a room combination needs a free unit for each of its rooms, and a combination Apaleo cannot hold (its rooms in different unit groups, or a room not mapped to Apaleo) is not offered.

Best Practices

  • Respond to new RFPs within 24 hours
  • Always check the review reason on the booking before sending a contract
  • Follow up on "Contract Sent" bookings that are still unsigned

See also: Creating RFPs, how a request arrives and how you answer it.

Was this page helpful?

Let us know if you found what you were looking for