The proposal is where most incentive programs live or die, and it is the document most planners spend the least time on.
The common mistake: treating the proposal as a logistics summary. Here is the destination, here is the per-person cost, here is when we would travel. The CFO reads it and asks why this is better than just giving everyone a cash bonus.
A proposal that gets approved is not a logistics summary. It is a business case. It answers the CFO’s question before the CFO asks it. It connects the program to the organization’s specific performance goals, translates the investment into expected return, and makes the objections visible so they can be addressed rather than left to surface in the meeting.
Here is the structure I use and the logic behind each section.
Why the Proposal Matters, and What It Is Really Doing
The proposal is doing three things simultaneously.
It is making the case for incentive travel as a category. For a company that has never run a program before, the leadership team may not have a strong prior belief that incentive travel is worth the investment. The proposal has to make that case from scratch, using evidence rather than assertion.
It is making the case for the specific program you are proposing. Even for a company with an existing program, a new destination or a significant change in program design needs to be justified. What makes this particular program the right investment at this particular time for this particular group?
And it is making the case for you as the person who can execute it. A proposal that is well-constructed, that shows command of the business case and the logistics, that demonstrates that the risks have been considered: this builds the confidence that the person presenting it can run the program effectively.
A proposal that treats approval as a formality will not get approved.
The One-Page Summary: What Leadership Reads First
Most executives read the one-page summary and decide whether to engage with the rest of the document based on what they find there. The summary is not an introduction; it is the complete argument in compressed form.
The summary should answer four questions in four paragraphs.
What is the problem? What performance outcome is the company trying to drive, and why is the current approach not producing it at the level needed? One paragraph, grounded in data if possible.
What is the solution? A brief description of the program: the destination, the qualifying criteria, the approximate group size, and the travel dates. One paragraph.
What is the expected return? A brief statement of the projected ROI: revenue impact, if quantifiable, and the motivational and retention value if not fully quantifiable. One paragraph.
What does it cost? Total program cost and per-person cost for expected qualifier group. One paragraph.
If the summary does the job, leadership will read the rest of the document for validation. If it does not do the job, the rest of the document does not get read.
The Problem Statement
This is the section most proposals skip, and it is the most important one.
The problem statement establishes why the company is considering an incentive travel program in the first place. It is not sufficient to say “we want to motivate the sales team.” That is always true. The proposal should answer: what is the specific performance gap we are trying to close, and why does incentive travel address that gap better than the alternatives?
Examples of effective problem statements:
“Our sales team’s attainment in the 80 to 110 percent range of quota has declined over three years. This cohort, our ‘solid middle performers’, generates approximately 55 percent of total revenue. Neither the current commission structure nor the existing recognition program has produced meaningful movement in this group. An aspirational incentive program is designed specifically to move this cohort.”
“Our top performers have accepted counter-offers from two competitors in the past 18 months. Exit interviews indicate that recognition and experience-based rewards are factors in the departure decisions. The current bonus structure is competitive; the non-monetary recognition program is not.”
Both of these are specific, grounded, and connect the program to a real business problem. A CFO reading either of these understands why the proposal is in front of them.
The Program Design Section
The design section covers the details of the program structure: who qualifies, based on what criteria, over what performance period, traveling to where, when, for how long.
For each element, include the reasoning as well as the decision. Not just “travel to Israel in October” but “Israel was selected for its combination of distinct heritage experience, which no other program on our shortlist provides, and the logistical accessibility from our primary team locations via direct flights.”
The qualification criteria section should be specific about the threshold, the metric, the performance period, and how ties or near-misses will be handled. Leadership will ask about edge cases; having the answers in the proposal is better than navigating them in the meeting.
Include the expected qualifying group size and the logic for that estimate. If the bar is set correctly, 10 to 20 percent of the qualifying pool should earn a spot. Show how you arrived at that range.
The ROI Section
This is the section where most proposals are weakest, and the section that most needs to be strong.
The framework for incentive travel ROI has two components: the direct revenue impact and the cost-per-revenue-dollar comparison.
Direct revenue impact: If a program motivating the top 15 percent of the sales force to maintain or increase attainment produces a 5 to 8 percent average attainment improvement in the qualifying cohort, what is the revenue value of that improvement? For a sales team generating $20 million in annual revenue, a 5 percent improvement in the top 15 percent of performers is a material number. Calculate it specifically for your team.
Cost-per-revenue-dollar: Compare the program’s cost against the revenue it is projected to generate. A program that costs $120,000 total and is projected to produce $400,000 in incremental revenue has a 3.3x return. That number belongs in the proposal.
Include the less-quantifiable elements too, but separately from the revenue math. Retention value, recognition signal, brand impact with external channel partners: these are real, and a sentence on each acknowledges them without asking leadership to accept unquantified numbers as justification.
The comparison to cash bonus should be in this section. An equivalent cash bonus of $3,500 to $4,000 per qualifier is fully taxable, which means the net value to the qualifier is significantly lower than the face amount. An incentive trip valued at $5,000 per person delivers the full value as an experience. This comparison belongs in the proposal.
The Cost Breakdown
Per-person cost and total program cost, fully loaded.
Per-person: flights from primary departure cities, hotel accommodation, ground transport and guide, meals, activities, program management fee. Show the range based on expected group size, since smaller groups have higher per-person fixed costs.
Total program cost at expected qualifier count.
Include the complimentary group leader spot as a budget offset: groups of 15 or more typically receive one complimentary participant, which the company should capture as a budget reduction.
Do not try to make the cost look smaller by leaving out line items. A proposal that omits the program management fee or the pre-trip communication costs will be amended upward after approval, which erodes trust.
The Risk Section
Every proposal that is taken seriously has a risk section. Every proposal without one is missing something.
The risks worth addressing for an incentive travel program in Israel: geopolitical and security considerations, the risk of lower-than-expected qualification rates, and the risk of program under-execution.
For geopolitical risk: acknowledge it, describe how it is monitored, and note the program’s cancellation and postponement policies. Leadership knows this risk exists; a proposal that ignores it looks naive. One that addresses it directly builds confidence.
For qualification rate risk: describe the triggers that would cause the program to be adjusted if the qualifying group is significantly larger or smaller than projected, and what those adjustments would look like.
For execution risk: describe the partner managing the in-destination program and why they are the right choice. A proposal that says “we are planning to figure out the on-the-ground logistics” is weaker than one that says “Heritage Tours has managed programs of this type in Israel for groups of 15 to 35 participants and will be responsible for guide selection, hotel coordination, and day-of logistics.”
Our incentive travel hub has the destination detail for the program design section. Our ROI article has the framework for quantifying the return. Our vs. cash bonus article has the comparison that belongs in the cost section.
FAQ
How long should an incentive travel proposal be?
Five to seven pages for the full proposal, with a one-page summary that can stand on its own. More than ten pages signals that the writer does not know what matters. Less than three pages signals that the business case has not been made rigorously.
Should the proposal include a comparison to other destinations?
Yes, briefly. A one-page appendix or a paragraph in the program design section showing why the chosen destination was selected over two or three alternatives, and the evaluation criteria used, demonstrates that the decision was deliberate. It also preempts the question “why not Italy?” in the meeting.
Who should present the proposal to leadership?
The VP of Sales or the HR Director, depending on who is the primary sponsor. The person who can answer the performance-gap question from firsthand knowledge of the sales team is the right person in the room. The operational planner should be there as a resource, not as the presenter.
What if the budget has not been approved before the proposal is written?
Include a budget range in the proposal with a recommendation, and note that the final budget can be adjusted based on group size and program design decisions made after approval in principle. Asking for approval to spend a specific number before any planning is done is a legitimate ask; asking for a blank check is not.
How do we handle the political dimension of Israel in the proposal?
One to two sentences in the risk section, factual and direct: the geopolitical context of the region requires ongoing monitoring; the program includes cancellation provisions in the event that the security situation changes in a way that makes the travel inadvisable; Heritage Tours monitors conditions and will flag changes relevant to the program. That is all it needs.
What happens if the proposal is rejected?
Ask for the specific objection. Most rejections are about the cost structure or the ROI case, not the destination or the program concept. A proposal that is rejected for a fixable reason is worth resubmitting with that fix. A proposal rejected because leadership does not believe incentive travel works is a longer conversation about the category, not a proposal problem.