A public operational guide to platform modules, controlled workflows, security rules, validation, approval boundaries, and current release behaviour.
A control or module may be connected, guided, preview-only, or planned. Confirm its release status before treating it as a production system of record or an authorised write action.
The ThinQ Travel Platform is a governed workspace for travel product, contract, mapping, rate, distribution, policy, and operational-intelligence workflows.
Access is browser-based and identity-controlled. Use an authorised individual work account and a current browser.
The main navigation groups operational work by module. Mobile navigation exposes the same destinations in a compact menu.
Each module is labelled as connected, guided, preview, or planned. That status determines what can be relied on operationally.
Use Properties to review portfolio master data, completeness, mapping quality, operational exceptions, and readiness signals.
The guided builder structures product-definition work, validates required inputs, and prepares controlled output for review.
Contracts provides a structured view of agreement lifecycle, worksheet inputs, validation state, versions, and publication readiness.
Contract dates must represent the commercial agreement accurately and must not overlap in ways that create ambiguous operational output.
The worksheet organises rooms, occupancies, rates, supplements, restrictions, and validation into a controlled working view.
Rates and seasons define the commercial price periods and the conditions under which they apply.
Occupancy rules define permitted adult and child combinations and any additional-person pricing logic.
Use structured supplements and reductions for mandatory or conditional price adjustments.
Saving preserves work. Validation checks structure. Approval confirms accountability. Publishing releases an authorised version.
The audit trail records meaningful state changes, ownership, decisions, and supporting material.
Mapping reconciles internal, reference, and supplier identifiers and surfaces confidence, conflicts, and unresolved exceptions.
The ARI view supports date-level inspection of availability, rates, inventory, restrictions, and stop-sale state.
Distribution controls define channel access, market scope, sales windows, and operational restrictions.
Policies centralise cancellation, payment, billing, legal, and operational terms with review status and audit context.
Governance covers users, roles, secure sources, permission boundaries, approvals, and audit events.
Insights surfaces operational patterns, anomalies, comparison views, and diagnostic evidence to support decisions.
These areas may appear as roadmap or preview modules. Their presence does not mean that operational workflows are enabled.
Use tooltips for field-level guidance and this manual for broader operational rules and workflow boundaries.
ThinQ Desk is a persistent enterprise support agent accessible from every screen. It responds to operational questions with text and optional voice output, and can be dragged, resized, or minimised freely.
The Help Center provides structured access to the platform user manual, keyboard shortcuts, investor documentation, and live support status from the header and profile menus.
The platform adapts its layout across mobile (below 767px), tablet (768px to 1199px), and desktop (1200px and above) breakpoints.
Start with identity, source freshness, validation state, and release status before escalating a platform issue.