A transport partner or external instructor needs enough information to deliver the agreed service. They do not necessarily need access to the school's other bookings, customer history or financial data.
Agree the responsibility before the access
Describe what the provider delivers, who confirms availability and how changes are handled. Decide which booking details are necessary for that work and who at the school owns the relationship.
TIDEFORCE supports provider accounts and permissions in the relevant school setup. Test the actual provider view before relying on it. A partner name in the Guidebook is a recommendation, not automatic operational access.
Keep the assignment understandable
For a shuttle, for example, the provider needs the agreed date, time, meeting point and relevant passenger information. Staff should be able to distinguish a request from a confirmed arrangement. If the details change, update the authoritative record and make sure the responsible people receive the change.
Do not assume that external systems synchronize simply because a provider has an account. Any integration and its supported data need to be confirmed separately.
Review delivery before settlement
Distinguish settling a service supplier from invoicing a booking intermediary. Recorded bookings from tour operators, hotels and other booking partners can be combined into consolidated invoices; selected partners can join a scheduled monthly billing run. Check an external service supplier’s work, rates and exceptions against your agreement.
Keep exceptions attached to a named owner so the next person can understand what is agreed and what remains open.
The provider page explains the supported access and workflow. For general local recommendations without an operational assignment, use the Guidebook.
How does this work at your school?
Bring an everyday task from your school. We’ll show you how it could work in TIDEFORCE.
Request a demo →