Client-safe charter proposals that do not leak the supply chain

A client-safe proposal shows the aircraft category or the presentation the broker chooses, the itinerary, the commercial terms, the price the client will pay, and what is still conditional. It does not show the operator's internal identity when that relationship is protected, the net cost, the margin, or the names of suppliers who were asked and declined.

Jet Intelligence builds the client payload from an allowlist. Fields that belong to the broker's supply relationships stay in the workspace. The released proposal is a snapshot, so a later edit to the draft does not silently change what the client already opened.

Broker pricing changes. An operator revises a conditional item, the desk adjusts margin, or the client asks for a different aircraft. Each of those is a revision. The previous client price should remain readable. A proposal link that always shows 'the latest' without a version makes it impossible to know which number was accepted.

PDF export should come from the same released snapshot as the private link. A PDF rebuilt from the live draft is how two versions of the same proposal end up in the same email thread.

A private link can record a view, a question, a rejection or an acceptance. Acceptance should create the booking handoff: passenger details, permits, handling, catering, transport, insurance evidence, payment evidence and the final briefing. Those tasks belong to the accepted option, not to a new spreadsheet that retypes the route.

Questions and rejections are commercial events too. They should stay on the proposal so the next revision answers the actual objection instead of guessing which email it came from.