Prepare, revise, and submit Avails

Avails are the supplier's structured response to a broadcast RFP. Work begins in a private draft inside the RFP Exchange and becomes buyer-visible only when an authorized person submits it.

You need Edit Avails to create or change a response. You need Submit Avails to send or withdraw one.

Start from the buyer request

Open Pipeline, select the RFP, and open Avails. Read the immutable request revision before entering rates or schedules. Confirm the flight, requested market and Property, dayparts or programming, primary audience, weekly goals, deadline, and buyer notes.

If the buyer has issued a newer request revision, reload and work from that version. Tap prevents a stale request revision from being submitted as though it were current.

Build the private draft

Add each offered Avail and identify whether it is a daypart, program, rotation, or other supported placement. Enter the schedule, spot length, weekly rate, projected impressions, and any relevant notes.

Use weekly entries when price or delivery changes by week. Where the editor offers an apply-across action, use it only after checking that the same value is correct for every week.

Mark a requested placement as not offered when you cannot supply it. If you propose an alternative, explain the difference clearly enough for the buyer to compare it with the request.

Review exclusion or conflict fields before submission. A potential conflict must be acknowledged and explained where required.

Use a source file safely

You can upload a rate card or Avail source to stage response data. Staging creates private working material and does not send the source or the response to the buyer.

Review every staged row, especially dates, overnight schedules, rate units, audience labels, and projected impressions. Fix rejected or conflicting rows before submission. The original source and its provenance remain supplier-private unless another product control explicitly makes a file public.

The supplier Agent can also prepare a private draft from a source. It cannot submit the result.

Understand autosave

Draft changes autosave. Watch the save indicator before leaving the page or submitting.

If autosave fails, keep the page open and retry after checking the invalid field or connection. If Tap reports that the draft changed elsewhere, another tab or teammate saved a newer version. Reload the current draft, compare the latest values, and reapply only the intended changes.

Do not continue editing a stale copy because submission validates against the latest saved draft.

Review and submit

Use the review step to check all Avails, weekly values, totals, alternatives, exclusions, and notes. Tap saves the latest edits before submission.

You can send the complete response or, when the workspace supports it and permissions allow, send one ready Avail from a larger private draft. A submitted response is an immutable revision visible to the buyer.

Later edits stay private until you submit a replacement revision. The revision history preserves what the buyer previously received.

Late, closed, and withdrawn responses

A response submitted after the buyer deadline may be marked late. The buyer decides whether to consider it.

You can withdraw a sent response while the exchange and response state allow it. Withdrawal is buyer-visible and requires Submit Avails. If you need to send corrected terms after withdrawal, prepare the next permitted response from the current exchange state.

A closed, expired, accepted, rejected, or otherwise terminal response may no longer be editable or withdrawable. Read the current status and activity history before asking the buyer to reopen or replace work.

For the larger flow, see Respond to an RFP and Manage the supplier Pipeline.