Check the feasibility of a circuit before proposing it

A circuit designed by a professional is the fruit of knowledge that no calculation replaces: the ground, the suppliers, knowing the client. This engine does not stand in for any of it. It adds one more look, a systematic one, at what escapes the eye when you have been staring at the circuit for hours.

This page details the use for ground handlers and agencies. For the other professions, see For your profession.

The profession's problem: what shows up late

A circuit is usually read place by place, day by day. The defects that matter appear between the places and between the days, and often too late: when the client has left, or when the client complains.

• A pace that does not hold: a run of full days with no breathing space, or three changes of accommodation in a row.
• A night too many (or a night too few): two nights in a stage that needs only one, a one-night base for a place that deserves a day.
• A season that does not suit the stage: each stage has its own climate and access depending on the month, and the circuit is rarely re-read stage by stage from that angle.
• An underestimated driving time: the sightseeing day that is in reality a driving day.

None of this is a professional failing. It is what is hard to hold in your head over a circuit of several weeks. Read the study A tour is not a list of places.

What the engine checks

Six dimensions, each with its finding:

• Roads and driving time: the real legs, day by day, and the days when the road eats the visit.
• Pace and nights per base: the alternation of full days and days with no plan, one-night bases, stages too short for what they hold.
• Season, climate, closures: the climate of the month at each stage and what it does to the planned activities, seasonal roads and sites.
• Access and gateways: how you get in, how you get out, connections with limited departures.
• Budget: the advertised price against an estimate, with the question to ask when the gap turns on what is or is not included.
• Gaps and repetitions: what is missing, what repeats.

For the detail of each check, read the study How to check a tour itinerary.

An example of a report, described

The example is fictitious: a 12-day circuit between islands and mountains. The report looks like this.

• A grade from A to D, here C, with what it rests on.
• Six dimensions, each with its finding (those of the previous section).
• A gap with the market: for pace, three one-night bases in a row from day 2 to day 4, when comparable circuits in the area have one or two. It is a point of comparison, not a verdict.
• Assumptions, stated plainly: what the engine assumed when the circuit did not say.
• Questions to ask: when a piece of information is missing, the engine does not guess. It writes the question: "the crossing on day 5 depends on a ferry with limited departures: which one, and what timetable?"; "is the international flight included in the advertised price?".

Each alert says what it saw, why it matters and what remains to be checked. The engine flags and explains; you decide, and the decision may well be to change nothing.

When the pace does not hold, the engine can put the circuit back at the right pace and say what it changed (stages added, removed or moved, nights, route of the longest day): this is a corrected variant, to compare with your own; it does not count as a validated circuit.

How to use it without changing the way you work

You design as usual. The check comes afterwards, or alongside.

1. You entrust an existing circuit to us: your own, a correspondent's, the quote a client brings you.
2. You receive a confidential report: it stays between you and us, and we never quote a checked circuit nor the agency that built it.
3. You read what is useful to you. One alert teaches you something, another confirms a choice you made knowingly. No tool to integrate, no interface to adopt, no data to re-enter.

The engine is neither a booking tool nor a competitor: you keep the ground, your contacts, the relationship with the client, the design and the decision. For the work a hand-built circuit represents, read the study How long to build a tour itinerary.

What the engine does not do

• It does not verify visas, ferry timetables, road openings or permit quotas: it detects that a constraint exists, never that it is compatible with your dates, and it writes that down.
• It books nothing and does not sell trips.
• It does not know your ground, your suppliers or your clientele.

Frequently asked questions

Does the engine replace the circuit designer? No. It checks a circuit you designed and flags what will not hold; it does not sign it off. The ground, the contacts, the client relationship and the decision stay with you. Read the study Tour operator, AI assistant or engine.

What happens when a piece of information is missing from my circuit? The engine does not guess it. It writes the question to ask (an accommodation not specified, a flight not indicated) and marks the point "not verified".

Does my circuit stay confidential? Yes. The report stays between you and us. We never quote a checked circuit, nor the agency that built it.

Do I need to change tool or method? No. There is nothing to install or integrate. You entrust a circuit to us, you receive a report. The service is in beta.

Have a circuit checked

The form on the Agencies page opens with "Check an existing circuit" already ticked: leave your address and we will get back to you.