From Supplier Documents to a Client-Ready Proposal

A supplier sends a rate by email. Another sends a PDF. The transfer company attaches a spreadsheet and asks the agency to confirm the dates.

The client is waiting for a proposal.

Before an advisor can present the trip, somebody has to read the documents, compare the details, and decide what is still valid. That work rarely happens inside the proposal tool. It happens in inboxes, downloads folders, spreadsheets, and the advisor's own memory.

What is a travel agency proposal workflow?

A travel agency proposal workflow is the path from supplier information and a client brief to a reviewed, priced proposal. It includes document import, data checks, option selection, and client-facing delivery. The document is the last step, not the whole process.

The proposal starts before the document

Consider a ten-day itinerary with two hotels, a private transfer, a guide, and a flight connection. The supplier information will probably arrive in different formats and at different times.

One hotel sends room types and cancellation terms in a PDF. Another replies with a net rate. The transfer company sends a spreadsheet. Then the client changes the dates before the first draft is ready.

Now the advisor has to check the details that decide whether an option can go into the proposal:

• Do the dates match the client's request?
• Is the price per person, per room, or for the whole service?
• What is included?
• Which cancellation and payment terms apply?
• Was the option available for these dates, or was it only available when the supplier replied?

These are sales questions as much as operational ones. A proposal that gets them wrong creates work later, usually at the worst possible time.

Copying creates a second problem

Most teams have a sensible workaround. Copy the useful details into a template and keep moving.

It works for a simple trip. Add several suppliers, a few revisions, and a colleague taking over the file, and the workaround starts to show its limits.

A rate gets copied without its currency. A room name loses its occupancy rules. A cancellation deadline stays in the email but not in the proposal. Someone updates the price in one version and sends another.

The missing piece is context. A number on its own is not a rate. A hotel name on its own is not an option. Each detail needs the conditions that make it usable.

That is why the agency has to keep the source close to the decision.

A review that catches the boring mistakes

The review before sending a proposal does not need a complicated scoring system. It needs a consistent habit.

Start with the dates. Check arrival, departure, number of nights, and the date of every service between them. A transfer booked for the wrong day can disrupt an itinerary that otherwise looks correct.

Then check the service itself. For a hotel, that usually means the property, room type, occupancy, board basis, and conditions. For a transfer or activity, it means the service date, duration, meeting point, group or vehicle details, and inclusions.

Price needs its own pass. Confirm the currency, whether the rate is net or marked up, which taxes are included, and whether the amount applies per person, per room, or per service. Keep the cancellation deadline beside the option it governs.

Availability needs care too. A supplier reply tells the agency what was available at that moment. It does not guarantee that the same room or rate will still be available when the client accepts the proposal.

Finally, look at the client. The cheapest valid option can still be the wrong option. A proposal has to fit the dates and the preferences behind the request, not just the fields in a supplier document.

That last check is where advisor judgement matters most.

What Ghloria does today

Ghloria's current proposal workflow starts with supplier documents. It extracts the relevant trip information and turns it into a proposal the agency can review.

The advisor stays in the loop. They can inspect an option, correct it, decide what belongs in the proposal, and adapt the result to the client. The software takes care of repeated reading and retyping. It does not pretend that every travel decision can be reduced to a rule.

The information also stays connected to the client and the trip. That matters when an advisor needs to check an option later or hand the work to someone else.

The current design-partner workflow produces PPTX proposals through Ghloria's delivery flow. A standard PDF template is still in development for broader onboarding. A custom workflow proves that the job is useful. A repeatable template makes the same job easier to adopt elsewhere.

Trace one proposal backwards

Pick a proposal your team sent last week. Follow each hotel, flight, transfer, and activity back to its source.

How many times was each detail copied? Where are the terms that did not make it into the final document? If the client changes one date tomorrow, can someone find every place that needs updating?

The answers tell you whether the agency has a proposal process or a document-making habit.

The proposal is what the client sees. The real product of the work is the reliable trip information underneath it.