What is your full home address?
Planning needs the start city and the first hotel, not a home address. A home address adds personal data without changing a single day of the plan.
A custom itinerary request form collects the brief your agency needs to plan a day-by-day itinerary: the dates, who is traveling, the pace and the kinds of experiences the traveler wants. It does not create the itinerary itself, and it does not produce a document. Ask for interests and limits in the traveler's own words, and leave out identity numbers and card details.
Planning needs the start city and the first hotel, not a home address. A home address adds personal data without changing a single day of the plan.
The count and each companion's general interests are enough for a day plan. Full details about other people are not needed, and each companion can share their own preferences.
Account access goes well beyond what a trip plan needs. Ask the traveler to share the photos or saved places they choose instead.
| Field | Type | Required | Why you ask it |
|---|---|---|---|
Traveler name | Short text | Required | Identifies whose itinerary this is. Use the name the traveler uses day to day. |
Number of travelers | Number | Required | Sets how many people each day plan has to suit, including how transport is counted. |
Start city | Short text | Required | Where the trip begins. The first day starts with the journey from here, so the planner needs it even before a hotel is chosen. |
Places to includeEnter one place per line. A rough order is enough. | Long text | Required | The destinations the traveler expects to visit, in the order they have in mind. |
Trip start date | Date | Required | Starts the day-by-day schedule. Your planner checks closures and opening days against this date. |
Trip end date | Date | Required | Sets how many days the itinerary covers. |
PaceSlow, one main plan per dayBalanced, a morning and an afternoon planFull, from an early start to late eveningVaries by day | Single choice | Required | Sets how many activities fit in one day, so it shapes every day that follows. |
InterestsFood and drinkHistory and museumsNature and outdoorsShoppingNightlifeFamily activities | Multiple choice | Optional | Lets the planner weight the days toward the subjects the traveler cares about. |
Must-see and must-avoid itemsName the place or activity. Leave out personal details about other people. | Long text | Optional | Captures the few things the traveler will not skip and the things they do not want, in their own words. |
Accommodation or base area | Short text | Optional | The hotel or area the days are planned around. Leave blank if no base is chosen yet. |
Getting aroundWalking and public transitRental carPrivate driverNot sure yet | Single choice | Optional | Shapes the travel times between stops: walking and transit, a rental car, or a private driver. |
Daily spending rangeLowerMiddleHigherPrefer not to say | Single choice | Optional | Helps the planner choose between types of venue. A range is easier to name than an exact figure. |
Access needs on the routeDescribe the route need, for example step-free access. Leave out the medical reason. | Long text | Optional | Lets the planner choose step-free routes and rest stops without asking for a diagnosis. |
Contact email | Required | Where the draft itinerary is sent for comments. |
Example only, not a real submission
Look up closures, holidays and opening days for the trip dates before you draft. A brief that reads well can still fail on a day when a museum is shut.
Give the reason for each stop, so the traveler can move one item rather than reject the whole plan. Mark the items that depend on a booking or a fixed time.
Briefs are stored and processed by a scheduled job that runs hourly in production; the creator is then notified. You can review them in the grid and export them as CSV. When a trip starts within a week, call the traveler directly.
A list of a dozen interests produces a plan with a little of everything. Ask for the top two or three, and keep the rest optional.
A standard seven-day layout ignores the traveler's pace and the opening hours of each place. Start from the traveler's answers, and use a layout only to format the finished plan.
Without a start city, the first day cannot begin with the journey. Ask for it even when the traveler has not chosen a hotel.
A full timetable leaves no room for weather, a late breakfast or a second look at a gallery. Plan the anchor points for each day and leave the rest open.
This page is a request form, not a template. It gathers the brief your agency plans from. Attain OS does not produce itinerary documents, so the planner writes the finished plan in whatever format your agency already uses.
No. The form asks someone else to plan the trip. If you want to build an itinerary yourself, use a planning document you already know, and send the finished version to your agency for comments.
The time depends on the number of days, the number of places and how many rounds of changes the traveler asks for. Tell the traveler the review window your agency works to and how many rounds are included, so the scope is clear before planning starts.
Treat each change as a new line in the brief. Note what changed, which days it affects and whether a booking has already been made, so the planner does not work from memory.
Yes, but tell the planner which parts the traveler must not see in advance, such as a proposal or a birthday dinner. Otherwise a draft sent to the wrong person can spoil the plan.
Choose a category and a form type in the wizard. Answer three Atty Suggestions questions, then give the form a title. Atty builds the fields in the background. Edit the fields and ask Atty to refine them, then publish and share the /f/ link.