Everything it does, in plain language.

Days hold items: flights, lodging, transfers, meals, activities, tours, cruises, notes. Drag to reorder, or move a whole day and its contents to a different slot. Timed items sort themselves chronologically.

There is no Save-or-lose-it. Close the tab in the middle of a sentence and the work is there when you come back. We test this by actually killing the tab, not by trusting the code.

Type a flight number and the airline, route, terminals and scheduled times fill in from the timetable; sixty-eight carriers are recognised by name, so “Delta 1996” resolves as well as “DL1996”. On the day it flies, the builder shows its status (scheduled, delayed, landed) while the trip is open; best effort, and nothing is pushed to your client.

Search a hotel or restaurant by name and its address, phone, website and rating attach to the item. The client's copy carries an embedded map and a one-tap directions link.

Each item takes formatted notes: headings, lists, links, tables, and images you paste or drop straight in. Confirmation blocks paste in whole and keep their shape.

A forecast chip on every dated day, in the builder and in the client's view. Beyond the forecast window it says so rather than inventing a number.

A three-hour-plus hole between timed items is flagged in the builder: dismissable, because sometimes the afternoon is free on purpose.

Cost per item, marked total or per person, paid or unpaid. The header carries the running trip total and a per-day breakdown.

Save an item, or a whole trip, and reuse it. The library is searchable by name, tag and category, and on Agency it is shared across the team.

Every save snapshots the trip. Restore any earlier version; the restore itself is snapshotted first, so undoing an undo is possible.

A live link, no account and no login for the client. Edit the trip and their page updates. You are never re-sending a corrected copy.

Server-rendered, print-quality: cover photo, chapter dividers per section, a photo per day, confirmation chips, packing list. Day headers never strand at the foot of a page. That is enforced by a test, because it happened once.

Attach tickets, waivers, vouchers or confirmations to the item they belong to. Your client downloads them from the same page they read the trip on. Files are private and served through expiring links.

Logo, accent colour, phone, email and website. Three layouts (Classic, Editorial, Minimal), three cover treatments, and a title scale. The only Onflux on a client's copy is one line in the footer.

Send two or three versions of a trip as options. The client compares them side by side and picks one; you see which they opened and which they chose.

Generated from the trip's destination, length and activities. The client ticks items off on their phone.

Send the trip for a formal yes. The client approves, requests changes, or comments on a specific day. You are notified either way, and the trip's status follows.

Optional, off by default. When on, a client can leave a note on any single day; you resolve them from the builder.

Every traveller's contact details, travel documents, preferences and full trip history in one profile, with a running total of what they have spent with you.

Send an intake or preferences form, and the answers land against the client's record. Sensitive fields are encrypted at rest.

Invite a colleague to a trip as an editor or a viewer. You can see who else has it open while you are both in it.

Owner, admin and agent roles on the Agency plan; an admin can step into any member's trip when someone is out.

One locked brand for the whole agency, and a shared template library, new members are on-brand from their first trip.

Which trips have been opened, commission and revenue by month, and where your value is concentrated.

Optional TOTP on your own account. Your client list and their passport details are worth protecting properly.

Group trips into folders on the dashboard; group days into named sections inside a long trip (“Week 1, Paris”).