For buyers
Turn approved Plan facts into a structured request, select only relevant supplier properties, and keep the final recipient and send decisions under human control.
5 min readUpdated
Something missing from this page? Email help@tap.co
An RFP turns a decision-ready Plan into a clear request that Supplier Properties can answer with Avails. Tap keeps one shared request at the Plan level, then creates a separate RFP Exchange for each property you choose. That gives every supplier its own conversation and response history without making you rebuild the same request.
Your RFP will be easier to complete if the Plan already has a clear objective, market, flight, and audience. A complete Client Product Estimate reference can also carry forward from the Plan, but it is optional and does not block the RFP.
Plan details
Confirm the objective, market, flight, and any optional Client, Product, and Ref Number context.
Delivery goal
Decide the primary demographic, daypart, spot length, goal CPM, and any weekly impression targets.
Supplier context
Prepare programming preferences, exclusions, advanced audience context, or other details that belong in your notes.
Open the Request stage
Open Campaigns, choose the Plan you want to transact, and select Request. Choose New RFP. If the Plan already has an RFP, open it from Your RFPs instead.
Set the request scope
Choose one market and media type for the RFP. Set the flight dates and a response deadline in the market's local time zone. The deadline must be in the future.
The current form supports TV and radio requests. If Tap cannot resolve the market time zone automatically, enter a valid local time zone before continuing.
Define the delivery goal
Choose one primary demographic, a daypart, an allowed spot length, and a goal CPM. You can also add an impression goal for each active week in the flight.
CPM and impression goals apply to the primary demographic. Put secondary audiences, advanced audience definitions, programming preferences, and exclusions in Additional notes so suppliers can interpret the request correctly.
Create the private draft
Review the form and choose Create RFP draft. Tap checks that the request has an objective, active flight weeks, a primary demographic, delivery goals, and a valid response deadline. No supplier is contacted at this point.
The supplier selector starts with properties eligible for the RFP's market and media type. Eligibility defines the directory pool. It does not mean every property belongs on the recipient list.
Tap evaluates each property against the complete brief, including the objective, request notes, flight, audiences, dayparts, and available property facts. A positive match can come from audience, format, programming, affiliation, rights, or performance evidence.
Tap leaves a property off when it has no station-specific evidence of relevance. It does not add every eligible property merely for broad distribution. This is especially important for a narrow sports, event, program, genre, or format request. For example, a sports format alone does not prove that a radio station holds the requested play-by-play rights, and general local reach does not prove that a TV affiliate carries the relevant event window.
The recommendation and reason remain inspectable. Review the evidence, add a property when you know it belongs, or leave an unconfirmed match off. The buyer owns the final recipient decision.
Add recommended properties individually, add another eligible property when you have a grounded reason, or remove a property before sending.
Open a property to review its identity, format, listing owner, legal owner, requested contact, and any available recommendation context. A recommendation is context for your decision, not permission to send.
Tap enables sending only when the draft is complete, the deadline is still in the future, and at least one recipient is selected. The final confirmation shows the number of Supplier Properties that will receive the request.
Resolve completion issues
Review any missing-field messages on the RFP. Confirm that the objective, flight, primary demographic, delivery goals, deadline, and recipient list express the decision you want suppliers to answer.
Approve the exact send
Choose Send RFP, read the confirmation, and approve Send RFP to the displayed number of stations. Tap freezes the sent revision and creates a separate Exchange for every selected property.
After sending, open a Supplier Property's correspondence to see the Exchange status, the response state, and when the request was sent. Common response states include Awaiting Avails, Draft in progress, Avails submitted, and Response withdrawn. When Avails arrive, choose Review submitted Avails to inspect that supplier's response.
Use the Exchange conversation for questions and clarifications. Keeping communication attached to the property preserves the context behind its response.
A sent revision does not change silently. If you edit material details after sending, Tap stages a new revision while suppliers continue to see the previous sent copy. Review the changes and explicitly resend when the updated request is ready.
Changing only the response deadline is a separate amendment. Approving the new deadline updates the open Exchanges immediately without creating a new RFP revision. You can also add another recipient while the deadline remains open. Revision and deadline history stay available so the sequence remains clear.
Once suppliers submit responses, compare their independent Avails and turn the options you choose into Orders.