Policies

Policies sets a practical governance boundary for passenger transport enquiries and confirmed duties. It applies from the first request through quotation, confirmation, operation, payment and post-service review. The purpose is not to replace the written quotation or contract, but to explain the common process customers should follow before relying on a vehicle, timing, route, inclusion or commercial outcome.

Bookings or Services Covered — Policies

The covered services may include airport transfers, employee and workforce routes, event movements, hotel transport, tours, inter-emirate journeys, temporary projects and recurring contracts. The exact application of the service-policy framework depends on whether the request is only an enquiry, a written offer, a paid confirmation or an active service. Each stage has different operational and commercial consequences.

Application — Policies

The policy is applied together with the latest written quotation, service agreement, approved movement sheet and any confirmed amendment. Where a customer message conflicts with a later accepted document, the most recent authorised written record should be reviewed. Informal conversations, assumptions from an earlier booking and website examples do not automatically change the current duty.

A successful transport arrangement requires a clear division of work. Wadi Swat reviews vehicle suitability, operating feasibility and the scope it is prepared to provide. The customer or authorised organiser supplies accurate requirements, approves the proposal, coordinates passengers and completes the obligations assigned in writing. Neither side should assume that an unrecorded task belongs to the other.

Responsibility framework — Policies

Responsibility is assessed from the confirmed record rather than from a generic service label. The customer remains responsible for the accuracy of passenger numbers, luggage, stops, access information, event instructions and required approvals assigned to the customer. Wadi Swat is responsible for the offered service elements that are expressly accepted, subject to the stated limitations and operational conditions.

Before an exact quotation or policy decision can be made, the request should identify the date, reporting time, finish time, pickup and destination pins, all stops, passenger and luggage totals, vehicle preference, waiting, trip frequency, access restrictions and the authorised contact. Missing information can affect capacity, schedule, price and the ability to reserve resources.

Requests, Approvals and Deadlines — Policies

Requests should arrive early enough for route, capacity and availability checks. Approval means accepting the written scope and commercial conditions through the stated method, including any required payment or purchase order. A deadline shown in an offer protects availability only for the stated period; after that point the vehicle, rate or operating arrangement may need to be checked again.

Procedure — Policies

The normal procedure is to submit the complete duty, receive a written offer, review inclusions and exclusions, confirm through the approved channel and issue the final movement information. Any later change should identify the original booking reference and specify exactly what is being added, removed or moved. The revised instruction becomes operational only after written acceptance.

Documents and Communication — Policies

Useful records include the enquiry, quotation, approved route, passenger estimate, payment evidence, permits or venue instructions, change requests and service correspondence. Keeping one controlled version avoids conflicting instructions between procurement, passengers, the organiser and operations. Sensitive personal details should be limited to what is genuinely needed for safe and accurate coordination.

Evidence — Policies

Evidence allows a fair review when timing, scope, charges or responsibility are questioned. Relevant evidence may include message timestamps, approved documents, map pins, attendance lists, receipts, access notices and operational reports. A claim should describe the specific booking and event rather than relying on a general expectation that was never included in the confirmed service.

Charges, refunds or other consequences under the service-policy framework are not determined by one public percentage. They depend on the accepted commercial terms, notice received, work already completed, resources reserved, supplier or permit commitments, additional distance or time and whether a revised duty can be delivered. The written decision should identify the basis used for the affected booking.

Applicable Commercial Rules — Policies

Applicable commercial rules may cover deposits, advance payment, credit approval, purchase orders, mileage or hour limits, waiting, overtime, tolls, parking, permits, accommodation, additional trips and cancellation or amendment notice. Only the items stated in the current offer apply. A condition from another client, route or earlier booking should not be imported without written agreement.

Financial impact — Policies

The financial effect of a request is reviewed against the actual operational change. A later reporting time may extend driver duty; an extra stop may add distance; reduced passengers may not remove a reserved vehicle; and cancellation after mobilisation may leave committed costs. A clear written breakdown is more reliable than assuming that every change increases or reduces the price proportionally.

Some matters remain outside the ordinary policy because they depend on authorities, airports, venues, road conditions, third-party access, weather, emergencies or other circumstances that the transport provider cannot control. The team may propose a practical alternative, but it should not promise access, timing, permit approval, a specific model or a refund that has not been confirmed.

Boundaries — Policies

The policy does not create a guarantee beyond the accepted service scope, nor does it remove any mandatory right or obligation that may apply under a governing written agreement or applicable law. It should be read as operational guidance. Customers requiring legal interpretation should rely on the signed contract and obtain independent advice where appropriate.

Changes and disputes are easier to resolve when they are raised promptly and in writing. The customer should state the original requirement, the requested revision, the time the issue was identified and the preferred resolution. Wadi Swat then checks availability, cost, evidence and operational effect before accepting, rejecting or proposing an alternative.

Amendments and Review — Policies

Policy wording and operating procedures may be reviewed when services, systems or business requirements change. A revised policy applies prospectively from its stated publication or approval point, unless the parties agree otherwise in writing. A booking already confirmed remains governed by its accepted documents and any valid amendment rather than by an uncommunicated internal change.

Change handling — Policies

When a change is accepted, the updated route, date, time, passenger number, vehicle class, price or responsibility should be recorded in one clear message or revised document. The organiser should distribute only the final version. Drivers and passengers should not be asked to rely on different instructions from separate conversations.

Complaints and Resolution — Policies

A complaint should identify the booking reference, service date, route, people involved, facts, time of occurrence, supporting material and the result requested. Clear information allows the responsible team to compare the complaint with the confirmed scope and operational record. Unsupported allegations or incomplete screenshots may delay a fair review.

Escalation — Policies

If the first response does not resolve the matter, the customer may request escalation through the approved business contact. The escalation should explain why the earlier response is disputed and include any missing evidence. Management review does not automatically reverse a decision; it checks whether the policy, documents and facts were applied consistently.

Policies is intended to guide current and future customer arrangements from the date it is published or formally issued. The applicable version is the one referenced by the current booking documents or made available when the customer confirms the service. The final quotation, contract and accepted amendment remain the primary commercial record.

Policy Version and Updates — Policies

Policy versions may be updated to improve clarity, reflect service changes or align the published guidance with current operating practice. Material changes should be identifiable through the current page or controlled document. Customers should review the latest version when making a new request rather than relying on a saved copy from an earlier transaction.

Governance — Policies

Governance requires authorised approvals, controlled records, clear ownership and consistent communication. Operational staff should not create special terms outside their authority, and customers should not treat a driver or third party as the final commercial decision-maker. Exceptions should be approved by the responsible company representative and recorded against the booking.

Where to Ask Questions — Policies

Questions should be sent through the formal contact route used for the quotation, contract or booking. Include the policy name, customer name, booking or quotation reference, service date and a focused question. This helps the team distinguish a general policy enquiry from a time-sensitive operational change requiring immediate attention.

Approved contact — Policies

The approved contact is the official company channel identified in the quotation, agreement or current website contact information. Customers should avoid sending confidential records to unverified personal accounts. A response is most reliable when it comes from the responsible operations, accounts, customer-service or management representative with access to the complete booking file.