ThinQ Travel | Structured travel execution

01 / Respondent context

Who should ThinQ follow up with?

Respondent name *

Email *

Role / title *

Organisation represented *

Market / country

Phone / WhatsApp

02 / Contract creation and maintenance

How are hotel contracts created, changed and maintained?

Current contract workflow *

Contracts are created manuallyContracts are partly template-basedUpdates are handled by email or spreadsheetSejour is the main contract workspaceTraSo receives contract data downstreamApproval steps are not consistently enforcedVersion history is hard to auditOther

Contract context notes

03 / User experience and workflow

Where do teams lose time or clarity?

Workflow context notes

04 / Validation, data quality and bugs

What needs stronger validation before release?

Validation risks *

Missing mandatory fieldsInconsistent hotel or room namesWrong or incomplete guest policy dataPricing rules entered inconsistentlyUnsupported offers still reach downstream systemsManual checks are needed before releaseBugs are difficult to reproduceOther

Validation context notes

05 / Unsupported offers and guest policies

How are unsupported offers and guest rules handled?

Guest-policy handling *

Child policy varies by hotelGuest age rules are difficult to modelOccupancy rules create booking riskPolicy details are missing from supplier materialPolicy rules are not visible enough to salesManual intervention is commonNo major issue currentlyOther

Guest-policy context notes

06 / Offer combinability and best-price logic

Can teams explain why an offer wins?

Offer logic state *

Best-price logic is manually checkedOffers cannot always be combined correctlySupplier rules conflict with internal rulesSales sees multiple similar offersThe winning offer is not explainableMargins or markups affect the result unexpectedlyNo major issue currentlyOther

Offer logic context notes

07 / Sejour-to-TraSo data flow

Where does data move cleanly, and where does it need help?

Data-flow health *

Data-flow context notes

08 / Governance and versioning

How are approvals, exceptions and versions controlled?

Governance state *

Clear maker-checker workflow existsApprovals are informalVersion control exists but is not easy to auditException approvals are not structuredTeams rely on individual knowledgeSOPs are incomplete or outdatedManagement needs better visibilityOther

Governance context notes

09 / Time to market

What delays product launch or seasonal updates?

Time-to-market impact *

Contract loading takes too longCorrections delay releaseManual validation slows publicationSeasonal updates are hard to coordinateSupplier changes are difficult to apply quicklySales waits for operational confirmationNo major issue currentlyOther

Time-to-market context notes

10 / Price and availability accuracy

Where does confidence break before booking?

Price and availability accuracy *

Prices need manual confirmationAvailability is not trusted enoughStop-sale or closeout handling is riskySupplements or discounts are missedTaxes or fees create discrepancy riskBooking terms are not displayed consistentlyNo major issue currentlyOther

Price / availability context notes

11 / Failed bookings and troubleshooting

How are failures diagnosed and resolved?

Failed-booking pattern *

Failures are investigated manuallyRoot cause is not visible quicklySupplier, Sejour and TraSo evidence is hard to compareSupport tickets lack enough contextResolution owner is unclearRepeat failures are not tracked wellNo major issue currentlyOther

Failed-booking context notes

12 / Invoicing and reconciliation

Where does finance need stronger evidence?

Invoicing and reconciliation state *

Invoice matching is manualContract terms and invoice terms are hard to compareCredit notes are difficult to trackDisputed amounts take too long to resolveFinance lacks contract audit evidenceOperations and finance work from different recordsNo major issue currentlyOther

Reconciliation context notes

13 / Health and safety management

How are compliance documents tracked?

Health and safety state *

Health and safety documents are managed outside the workflowExpiry dates are not tracked reliablyMissing documents are found lateApproval responsibility is unclearDocuments are stored but not linked to contract statusThere is no current structured processNo major issue currentlyOther

Health and safety context notes

14 / Future of Sejour

What should the future operating model support?

Future-state direction *

Keep Sejour as the operational coreImprove Sejour with better validationImprove Sejour and TraSo integrationAdd dashboards and exception reportingReduce manual workflow around SejourAssess whether parts should be replacedNot yet decidedOther

Future-state context notes

Definition of success *

Additional context

Response handling

Responses are securely stored within the ThinQ platform and are only accessible to authorised members of the ThinQ delivery team.

I confirm this response can be routed through the ThinQ operational discovery intake workflow.