A Charter Desk Tries One Page per Proposal: A Case Study

A Charter Desk Tries One Page per Proposal: A Case Study

What follows is an invented scenario, built only to show one way of working. A small charter coordination desk, five people with overlapping duties, had a recurring problem. Their trip proposals kept growing. Each client request added another option, another routing idea and another paragraph of caveats, until a proposal ran to several pages. Clients replied slowly or not at all. The desk lead suspected the proposals were too complete to be useful, and decided to test a single creative constraint: every proposal would fit on one page.

The starting point

The desk handled requests of every kind, from simple one-way trips to multi-stop itineraries. Their habit was to be generous. If a client mentioned two possible dates, the proposal covered both. If a client hesitated about airports, the proposal listed several. The intention was service. The effect was a stack of paper that made the client do the choosing the desk was meant to help with.

A review of recent threads showed a pattern the team had not named before. The longer a proposal, the longer the silence that followed it. Nobody could prove cause and effect, but the correlation was strong enough to try something different.

The rule they set

The team wrote the rule on a whiteboard in plain words: one page, one recommended itinerary, one alternative, and a short note on what would change the recommendation. Anything else went into a follow-up conversation if the client asked.

They also added a formatting limit. No more than a handful of short paragraphs, no tables that spilled onto a second sheet, and no technical vocabulary that the client would have to look up. Where a term was unavoidable, the proposal explained it in the same sentence.

What happened in the first week

The first one-page proposals were uncomfortable to write. The team found themselves arguing over which option deserved the recommendation, a conversation they had been avoiding by listing everything. One member described the process as being forced to have an opinion. That was exactly the intended effect.

Clients replied faster. Several answered within the same day with a direct choice or a precise question. The questions were better, too. Instead of “can you send more options?”, clients asked things like whether a particular date allowed an earlier departure. The desk could answer those quickly.

An unexpected benefit: sharper ideas

The page limit changed how the team thought about itineraries. With room for only one alternative, they started asking which alternative was genuinely different from the recommendation, rather than a slight variation. Some of those alternatives were inventive. One proposal suggested an unconventional split of a journey that the desk would never have raised when it was listing every option.

The limit also made the team curious about flexible pricing structures such as repositioning flights. To get the wording right for clients, they revisited their own reference material on how unfilled return sectors come about and why they are sometimes offered, and agreed that a single paragraph was enough to explain it in a proposal if it was written carefully.

Where the rule bent

Not everything fit. Complex multi-leg trips struggled on a single page, and the team had to decide how to handle them honestly. They adopted a compromise: the one-pager stayed as the front sheet, and a clearly labelled appendix held detail that only some clients needed. The rule became “one page for the decision, as many as needed for the reference”.

That compromise worked because the appendix was optional. The client could make a choice from the front page alone. If they wanted more, it was available. The team noted that most clients never opened the appendix.

Borrowing a layout from outside the industry

While redesigning the front sheet, a team member showed colleagues a drone-themed website, Dronesnow, as an example of tidy sectioning. By its own description the site is a connected ecosystem, and each theme has a dedicated area: the people who fly, the craft themselves, schools, film, written articles, a discussion board and a store. The desk had no interest in drones. What they borrowed was the habit of one clear label per block. Their front sheet adopted five small headings: route, timing, recommendation, alternative and open questions.

Measuring the change

After a month, the desk compared two sets of threads, before and after the rule. They did not use elaborate statistics. They simply counted how many proposals received a reply within a day, and how many needed a second round of clarification. Both numbers improved, though the team stayed cautious. A month is short, and the type of requests had varied.

More convincing was the qualitative feedback. Clients said the proposals felt easier to act on. Internally, the team said that writing them felt faster and less anxious, because there was a clear template and a clear stopping point.

Changes the desk would make next time

In hindsight the desk named two adjustments. First, they would have introduced the rule with a short training session on writing a clear recommendation, since the hardest part was committing to one. Second, they would have involved a client or two in advance, asking whether a one-page format would suit them.

They also noted that the constraint needed a gentle reminder every few months. Old habits crept back, and a proposal would stretch to a page and a half. A quick reread of the rule on the whiteboard was enough to bring it back.

Lessons for other teams

  • A limit on length forces a decision, and clients often want the decision more than the options.
  • Keep detail available but optional, so the page stays light.
  • Test the rule on a small scale and measure something simple.
  • Review the rule periodically, because habits drift.

Teams that arrange charter travel will recognise how easily a helpful impulse becomes clutter. For readers who want the background to the pricing concepts the desk reused, our guide for travellers on unfilled-sector jet journeys covers the basics in a clear way.

The desk still uses the one-page rule today in this fictional account, and its lead describes it as the least expensive improvement the team ever made. It required no software and no budget, only the willingness to choose. That is the heart of the method: a limit does not take capability away from the team. It takes away the option to avoid deciding.