Download the template (CSV)

Open it in Excel, Numbers or Google Sheets, one trip per row, then save or export as CSV. Keep the first line as it is; the column order does not matter, and extra columns are ignored.

Columns

ColumnWhat to put
from_cityWhere the trip started: a city ("London"), a city with its country ("London, Canada") or an airport code ("LHR"). Optional.
to_cityWhere it arrived, the same way. Required unless to_country is given.
to_countryOptional column: the country only ("Switzerland", "CH", "UK"), for trips where the city does not matter or is not known, or to say which "London" you mean.
depart_localLocal date and time of departure, YYYY-MM-DD HH:MM. Optional.
arrive_localLocal date and time of arrival, YYYY-MM-DD HH:MM. Required. A date without a time is read as midday (and a departure without a time as 09:00).
methodflight, train, car, bus, boat or other. Optional.
flight_or_train_no"CX260", "9023". Optional; used to spot duplicates.
transityes when you only passed through (did not leave the airport or station). Optional.
notesAnything for yourself while preparing the file. Not imported.

Dates

Write dates as 2026-03-04 (year first). Atrium also reads 04/03/2026 and 04.03.2026 as day-first, and 4 Mar 2026. A date that could be either day-first or month-first, such as 03/04/2026, is refused rather than guessed: the review screen shows it as "Check dates" and asks for the year-first form.

Times are local to each place: the departure in the departure city's time, the arrival in the arrival city's. Atrium works out the time zones from the cities.

What the review shows

Imported trips are marked as imported, are counted like any other trip, and are not verified by the import itself; attach documents later if you want evidence behind them. The owner can undo a whole import afterwards (assistants can import but not undo, since only owners delete). Up to 2,000 rows and 5 MB per file.