How TabiTabi works.

Start from the main action on the home page. When the new-trip form opens, almost all of it can wait.

Only the name is required. Destination and dates are optional — a trip can stay a draft for as long as the idea does. Dated trips can run up to 1,000 days.

Pick the base currency with care. Every budget total is shown in it, and it locks once the trip has its first expense, because every stored amount and exchange rate is denominated against it.

Solo is the default. The primary traveler starts as you. There is no party-size question — add companions only when you need them.

Statuses take care of themselves. Draft, upcoming, or past comes from the dates; the pill on each trip card updates on its own.

The itinerary tab holds anything with a time and place — or without one: flights, lodging, transport, activities, food, drinks, shopping, and everything else.

Dates and times are optional. Undated items wait under Unscheduled. Dated items group into their days, where you can step them up and down with the arrows, send one straight to the top or bottom of its day with ⤒ and ⤓, or sort a day by time.

Flights and transport go between places. They take From and To instead of a single place, and the flight fields search real airports. Picking a suggestion pins that airport's code to the item; free text stays free text.

One record can span days. Lodging takes a check-out date and appears across the stay; a flight or transport that arrives on a later day shows an arrival card there. Every one of those cards is the same record — edit it anywhere.

A trip can gain or lose a day in the middle. For a trip with a date range or planned length, its owner finds ＋ Insert a day before this, ＋ Insert a day after this and Delete this day in the ⋯menu beside each numbered day. Inserting adds a day on that side of it: the trip runs a day longer, and everything planned from there on — costs included — moves along too. A stay spanning the new day gains a night instead of moving. Deleting a day shifts the later plan back and also removes that day's own stops and the costs planned for them; the confirmation says how many before anything goes. A trip always keeps its last day.

Arriving a day earlier is its own case. ＋ Insert a day before this on day one is the only one that changes nothing you planned: the trip simply starts a day earlier, and every date you entered stays where you put it. Every other day moves the plan, so the confirmation says which is about to happen. Anything already planned for the new first day joins the trip rather than being pushed aside. This insertion has no inverse among the day controls: deleting that first day back out shortens the trip at the end and re-dates the later plan instead of restoring it.

If a day reads “Outside trip dates”. Changing a trip's dates now moves everything planned with it, so day one stays day one. A trip re-dated before that was true kept its plan — and its expenses — on the old dates. To bring one back, openEdit trip details three times: clear both dates and save, set the dates the trip used to have and save, then set the real dates and save. That last step moves the whole plan by exactly the right amount.

Costs attach where they happen. Add a cost from an item’s Edit dialog and it is saved as an expense linked to the item: description, category, and date start from the item and stay editable there or from the Budget tab.

The budget tab is one ledger shared with the itinerary — expense by expense, in whatever currency the money was actually spent.

Any currency, one base. A foreign-currency expense takes an exchange rate, prefilled from a public rate source and editable before saving. The saved rate never changes on its own, and the original amount always appears first with the conversion beside it.

Unit price times quantity. Four nights or six tickets are one expense with a quantity, not six entries.

Split it three ways. Equal divides the total among the travelers you check, individual hands it to one person, and custom takes exact amounts that must add up to the total.

Paid by is what settles up. Record who fronted the money and the budget can work out who owes whom. Skipping it is fine — the expense still counts towards every total, it just sits outside that particular sum.

Who owes whom. Travelling with someone else, the budget tab sets each person's paid amount against their share of the expenses included in the settle-up and lists the payments that square everyone up. It labels that scope and says what was excluded, so a partial figure never reads as the whole trip.

Summaries stay live. The trip total, each traveler's allocated responsibility, and a by-category breakdown are always current, all in the base currency.

Travelers are who the costs are split between. Add or rename them on the People tab; the Travel party card sits beside every trip.

Add companions when they matter. A trip supports up to 10 travelers, and each traveler's number on the budget tab is the share allocated to them.

Your colour is yours to pick. Everyone in the party gets a colour, and it is how the itinerary, the budget, and the split rows tell one person from another. Select your own dot in the Travel party card to change it. You can change only your own — a colour someone else is already wearing is shown faded and cannot be taken.

Removing someone is deliberate. The first traveler anchors the trip and stays. Anyone else can go once nothing points at them — no share of an expense, no itinerary item assigned to them — and the People tab says which of the two is still in the way. Removing then takes a typed confirmation, the same as deleting a trip.

The Packing tab is one shared checklist for the whole party. Add a thing, give it a category so the list stays scannable, and tick it off when it is in a bag.

The list belongs to the trip, not to a person. Anything on it is something the party needs. For a shared thing, once anybody has ticked it, it counts as packed.

Unless it is somebody’s job in particular. Assign a thing to one or more travelers and it is packed only once every one of them has ticked it, so a passport each shows as two of two rather than done after the first. Assigning nobody leaves it shared with the whole trip.

Every mark says who it is for. A mark is always about a particular traveler. A box appears for the people a thing is for; a shared thing is for everybody, and ticking one records exactly who it was for.

A tick says who ticked it. Marking something records which account marked it, so a shared list can be trusted. Where a companion has no account with current access to the trip, an editor can mark it for them as a proxy — the list shows it was marked on their behalf rather than by them, and never pretends otherwise. A mark you make for yourself is a self mark.

The checkbox is not the pen. Adding, renaming, recategorizing, reordering, assigning and removing things is for editors, but anyone who has a traveler of their own can tick that traveler's box — including a companion with view-only access, because packing your own bag is not editing somebody's plan. Until somebody is linked to a traveler there is no box that is theirs, and the tab says so rather than leaving them guessing.

A starter list, if you want one. Editors can ask for a suggested packing list from the top of the tab. Google receives the destination you pick from the trip's own list, how long the trip is, who you are travelling with, how much you like to bring, where you are staying, and your baggage choice (carry-on only or checked) — plus the trip's month when it has real dates. If you leave Bag as Not decided yet, no baggage choice is sent. It does not receive the trip's name, notes, itinerary, budget, or travelers. There is a daily limit, and it is the same one the Ideas tab's draft plans come out of.

Nothing is packed until you choose it. Suggestions arrive as a list to tick through, not as a list already added: pick the ones you want and add those. Anything already on the list is shown as already there rather than offered twice, and what you add starts unassigned and unticked, so who is bringing it is still yours to say. Suggestions stay in that one browser tab across tab switches and reloads, until you close the tab, sign out, leave or delete the trip, or delete your account. Changing where the trip goes, or its dates, means suggesting again before they can be added.

Marks stay. A mark is part of the trip's record. Nothing quietly unticks itself, and clearing a mark is something a person does on purpose. Narrowing who a thing is for can clear somebody else's mark, and it names whose before it does. Making a shared thing assigned clears the marks of anyone left out; widening it again or returning it to shared keeps its marks.

An empty Day 1 is the hardest part. The Ideas tab turns a few choices into a rough day-by-day plan you can pull pieces from.

You pick from menus, not a prompt box. Choose one of the trip's own destinations, how many days, who you're travelling with, your pace and spending level, whether each stop should come with a start time, whether to suggest places to eat, and up to six interests. There is nothing to type. Google receives those choices and, when the trip has a start date, its month; it does not receive the trip's name, notes, itinerary, budget, or travelers.

Nothing is added until you say so. Suggestions are just a list, in the order the day is meant to run. Start times are left open unless you asked for them, so a suggested day is a shape to follow rather than a schedule to keep. Add on one opens the ordinary new-item form with the details filled in, so you can change anything before saving.

They wait for you, until the browser tab closes. Switching to another tab or reloading the page keeps the suggestions you already have, because getting them back would cost another of the day's runs. They live in that one browser tab and never reach your trip: close it, or sign out, and they're gone. Only what you saved stays.

Treat it as a starting point. The suggestions come from Google Gemini and are generated text: a place may have closed, moved, or never have been quite right. Check anything that matters. There is a daily limit, shared across the site, so a run may sometimes have to wait until tomorrow.

The People tab is part of every trip. After you sign in, it also shows which people have accounts and any invitations.

Invite with a link. Owners send an Editor or Viewer link from the row of the person it will seat. Anyone who has a live link can join with the access it grants — the link is the invitation, so treat it like a key and revoke it to stop it working.

Three roles, one extra switch. Owners have full access, including trip details, sharing, and deletion. Editors shape the itinerary and travelers. Viewers read. Expense editing is granted separately, so an editor can plan without touching money — or a viewer can manage money without touching plans.

Members plan, travelers split costs. Joining through a person's link makes you a member and links your account to that person's place in the party, including their share of the costs.

Leaving and handing over. Any member except the owner can leave a trip. Their person and share of the costs stay in the party while their account is unlinked and loses access. An owner hands the trip over by making someone else an owner — the new owner can then change or remove the old owner's access. Or delete the trip, which removes it for every member.

TabiTabi shows you what it does before you sign in, and keeps what you plan once you do.

Signed out, you get an example. A fresh signed-out app starts with one example trip, there so the planner has something to show. A browser may also keep trips made with an earlier version. Everything shown while signed out stays in this browser and is never carried into an account. When a foreign-currency expense needs a rate, TabiTabi sends only the trip's base-currency code to the public rate source.

Sign in to plan your own. Planning a trip of your own starts with signing in. Account trips sync to every member's devices, and they are the only trips TabiTabi stores for you.

Deleting is deliberate. Deleting a trip takes a typed confirmation, and it cannot be undone.