How the Uncharted Planning Process Works, Step by Step

If you've made it to this page, you probably wanted to know what you'd actually be paying for before you paid it. That's the right instinct. Most travel-planning services explain what they do in five clean steps and leave the how deliberately fuzzy. The fuzziness makes a planning fee feel risky — you see the inputs and outputs, but the middle is a black box.

This is the long version of the middle. The high-level overview lives at how it works and walks the five steps in a paragraph each — intake, review, tier and payment, design, delivery. This post goes inside each step and names what I'm actually doing. The judgment calls. The cuts. The places I most often turn out to be wrong, and what I do about it.

I'll lose some of you in the next few thousand words. That's fine. The traveler who reads the whole post and still wants to outsource the work is the traveler I'm built to serve. The skeptic isn't the obstacle. The skeptic is the customer.

Step one — intake, and why the form is the brief

The intake form takes about three minutes on a phone. From your side, it looks like ten short sections — name, dates, destination, group, budget, travel style, must-dos, must-not-dos, the kind of help you want, the tier you're leaning toward. From my side, it's the brief.

The form is doing more work than it looks like. The destination field is a question about how much edge work the trip needs — a city I've designed twenty trips in is different from one I've designed two. The dates field is a question about season, light, and which restaurants will or won't be open. The departure city tells me how the trip starts and how tired you'll be on arrival, which changes day one. The group composition tells me which neighborhoods read well at night, whether I should think about kids' menus, and whether one of you is going to want a slow morning while the other wants a long walk.

The section that does the most lifting is the personalization block — three must-dos, three things to avoid, and a free-text box for anything that didn't fit. People sometimes leave this section thin because the prompts feel small. They aren't small. The must-dos tell me what the trip is for — the moment that has to happen, the experience the trip is being built around. The avoid list tells me where to not waste your hours. The free-text box is where the real briefs come out, and it's the field I read first. Two sentences in there are usually worth more than the rest of the form combined.

What I'm looking for in the intake isn't a complete picture. It's a shape. The shape is the answer to one question: what kind of trip do you want to come home from. Not where, not how long, not how much. The shape is the function I'll apply to every later decision, and it's the part I most need from you up front. The intake is engineered to surface it without asking you to write a personal essay. If the shape is in the form, I have what I need. If it isn't, the next step is where I get it.

Step two — review, and what I'm actually doing in those forty-eight hours

The clock between submission and my reply is twenty-four to forty-eight working hours, and almost none of it is me admiring your form. Here's what's happening in that window.

First, I read the intake twice. The first read is for the shape — what kind of trip is this, what's the constraint, what's the must-have. The second read is for what's not in the form. Travelers leave things off, sometimes deliberately, sometimes because they didn't know they mattered. The not-said is often more useful than the said. If the must-do list is all activities and no food, the trip has a different shape than if it's all restaurants and no activities. If the avoid list is all crowds and no specific places, you're telling me about your nervous system, not your taste. I read for the silences as carefully as I read for the words.

Second, I check whether the trip is fit-for-Uncharted. There are trips I'm not the right person for. A pure beach week at an all-inclusive doesn't need me. A multi-week backpacking route through a region I haven't worked in deeply doesn't get my best work. A trip where the calendar is so locked you're really hiring me to fill in the blanks — that's a different service, and the right move is to say so. About one in ten intakes gets a polite redirection rather than a tier recommendation, and that's a feature of the process, not a hole in it. The wrong fit produces the wrong deliverable.

Third, I sketch the trip in my head. Not in detail — in gesture. Roughly where you'd stay. Roughly how the days would split. Roughly which one or two anchor experiences would be the trip's center of gravity. This is the part that determines the tier recommendation, and it's the part that takes the most of my time in the review window. I'm not designing the trip yet. I'm checking whether the trip you're describing is one I can deliver well at the depth that fits your budget — and whether the depth and the budget point at the same tier or at different ones.

Fourth, I write back. The reply is short on purpose. It names the tier I'd recommend, in plain language, with one sentence on why. It includes any clarifying questions that would change the recommendation if the answers came back differently. And it includes a payment link tied to the tier. That's it. The reply isn't a proposal. The proposal is the deliverable, and the deliverable doesn't get drafted until you've confirmed the tier and paid the fee. The review window is a fit check, not a sales pitch.

If the answer is no, the answer is no in the same window. I'd rather lose the project at this stage than at delivery. The version of this work where I take every project that comes in and grind out something passable is a version I won't run.

Step three — package fit, and how I decide which tier is the right one

The three Curation tiers are Wanderlight, Uncharted Core, and Deep Uncharted. They aren't a price ladder — they're three different deliverables for three different shapes of trip, and the tier choice is mostly about the trip, not about the wallet. The conversation below is about all three.

Wanderlight is the long-weekend tier. Two or three days, one place, one stay, three restaurants worth booking, two experiences worth the calendar block. The deliverable is a one-page itinerary, day by day, that you can put on the lock screen of your phone and travel from. This is the right tier when the trip is small and the planning would still take you a weekend. It's also the wrong tier for a week in Provence, no matter how much you'd like to pay less, because the deliverable can't carry the trip.

Uncharted Core is the most-trips-fit-here tier. Four to ten days, one place — or one place plus a clear day trip or two — with the full trip dashboard built around it. Seven sections inside the dashboard, a stay or two with notes, a restaurant strategy rather than a list, an embedded map you can actually hand to a driver, packing notes specific to the city. This is the tier that matches the trip most travelers think they want when they imagine "a real, planned week away." It's the conversion sweet spot because it's the truthful answer to most well-defined trips.

Deep Uncharted is the multi-stop, milestone-grade tier. Ten or more days, multiple destinations, transitions designed in instead of bolted on, hard-to-get reservation strategy, on-trip support recommended. This is the honeymoon, the sabbatical, the once-in-a-decade move. It's not Core with more days. It's a structurally different deliverable — fewer options per stay, deeper notes, a travel companion document you read like an editorial feature instead of scanning like a spreadsheet.

When I recommend a tier in my reply, I'm running roughly this filter. How long is the trip and how many places. That's the first cut. How much pre-arrival editing does the trip need versus how much can happen at the curb. That's the second cut — a city I know well at three days needs less than a region I've worked in twice at fourteen. How much does the trip's outcome matter to you, in absolute terms. That's the third — a tenth-anniversary trip and a long weekend with friends are different stakes, and I size the deliverable accordingly. The first cut is mechanical. The second and third are where the judgment is.

There's a fourth thing I weigh, and it's the one that occasionally moves me to recommend down rather than up. Are you going to use the depth. The trip dashboard at the Core tier has packing notes, neighborhood notes, a restaurant strategy with reservation timing, an embedded map, and a flex section. That's a lot of artifact. Some travelers use every piece. Others want a one-page itinerary and would experience the longer document as overhead. If the form tells me you're the second kind — a brisk planner, a confident eater, a traveler who'd rather have less and decide more on the ground — I'd rather route you to Wanderlight and deliver tightly than to Core and over-deliver on the page. That conversation usually happens explicitly in my reply.

The single most useful sentence I can write in the tier recommendation is I think you're between tiers, and here's why I'd pick the lower one. That sentence almost never goes the other way. If I think you're between Wanderlight and Core, I'll say it and let you decide. The trust I build by occasionally talking you out of the higher tier is worth more than the upgrade fee.

Step four — design, and what the work actually consists of

This is the longest stretch. Three to fourteen days of design, depending on tier, with priority delivery cutting the window in half if your calendar is the constraint. From your side, it's quiet. From mine, it's where the real work lives.

The first day or two of design is research, and it's the part that doesn't show up in the deliverable. I open every reservation system I'd consider using, every map layer I trust, every saved note from prior trips in the region, and a small handful of locals or operators I've kept in touch with. I draft a long list of options. The long list is twice as long as the trip will be, often more. It's the longer document I mentioned above — the one most of which gets thrown away. Nothing on the long list is a recommendation yet. It's the candidate pool.

Then I write the trip backward. The center-of-gravity moment first — the one experience or one stay or one neighborhood the rest of the trip is built around. Then the shape that surrounds it. Then the days that fit the shape. Then the meals that fit the days. Then the routes that fit the meals. Then the windows of unfilled time that the trip needs to actually feel like a trip and not a sequence of appointments. The order matters. If I start with the meals or the activities and build outward, the trip becomes a list. If I start with the moment and build inward, the trip has gravity.

The cut process happens in roughly four passes. The generic pass — anything on the list because everyone recommends it cuts unless it's earned a specific reason to stay. The hour-ratio pass — anything that costs more time than it gives back cuts, including the things you have to travel an extra hour to reach for a half-hour payoff. The shape pass — anything that contradicts the trip's shape cuts, even if it's a good thing. The high-energy excursion adjacent to the slow week. The famous viewpoint at the wrong time of day for the route you're on. The completeness pass — anything I'm including because I feel like I should mention it cuts, hard. This is the most tempting cut to skip, because it's the cut that makes the trip dashboard look thinner than other trip plans, and travelers sometimes read thin as careless. Thin is the editorial position. Thin is what you're paying for.

By the time the cuts are done, the surviving list is shorter than the long list by at least half, often more. That surviving list is the trip. A handful of the rejections make it into the final deliverable as considered and ruled out, here's why. Travelers tell me they didn't expect to find that section useful, and they end up referring to it most. The cuts are the editorial signal — how you know the trip was edited.

The design work also includes a quiet step that doesn't have a clean name. I call it running the trip in my head. Once the document is roughly built, I read it as if I were the traveler. I trace the route, picture the walk to dinner, check whether the day's pace breaks where I think it'll break. I check whether the transition between stays will read as designed or as a logistical hassle. I check whether the trip feels like the shape we agreed on, not just whether it matches it on paper. A trip that works on paper and doesn't run in the head doesn't run on the ground.

A surprising amount of the design phase is also not designing. Travelers assume that more time means more activities. The opposite is true. Most of the back half of the design window is removing things, holding white space on the calendar, naming a window for do not plan this hour. The design is finished when there's nothing left I'd cut. Not when there's nothing left I'd add.

Step five — delivery, and what's inside the trip dashboard

Delivery is a single moment, and the deliverable is a shareable trip dashboard that opens cleanly on phone or laptop. The Core tier ships seven sections inside the dashboard — overview, daily itinerary, stays, food, embedded map, travel notes, one flex section. Wanderlight ships a tighter one-page itinerary. Deep ships a longer dashboard with multi-destination routing, transitions, and a more editorial reading experience.

What's in the document, mechanically, is named places, named times, named hours, named seats. You don't get try the local food — you get the specific corner restaurant, the booking timing that works, the dish to start with, the table to ask for if available. You don't get visit the historic neighborhood — you get the entry point, the street to take, the hour to be there. You don't get good restaurants nearby — you get a strategy for which kinds of meals to book in advance, which to walk in for, which to skip, and which to keep flexible because the day will tell you which one fits.

The overview is the trip in plain language — shape, gravity moment, rhythm. Read it on the flight out so you arrive remembering what kind of trip you're on. The daily itinerary names each day for its center of gravity rather than for a list. The stays section has options, not the same five Booking results. The food section is a strategy. The map is embedded and works on the phone. Travel notes cover the small specifics you'd otherwise have to ask three forums about — etiquette, tipping, payment quirks, the thing about taxis everyone learns the hard way. The flex section depends on the trip — a day-trip pack, a creative-residency block, a hard-to-get reservation backstop.

What's not in the document is also part of the deliverable. There are blank windows on most days, marked deliberately. Each one has a sentence on what it's for — recovery, weather buffer, slow lunch, the unscheduled hour to follow what you find. The blanks are the trip's lungs. A document with no blanks is a calendar, not a trip plan.

After delivery comes the revision round. You read the document, mark what doesn't fit, send it back with notes. Most revisions are small — pace, a single restaurant swap, a stay you'd rather try, a window you'd rather fill. Occasionally the shape is off, and we re-shape. The revision round is built into the schedule and the price. It's the second draft, where the trip locks in and starts to feel finally like yours rather than mine. The first version is a serious proposal. The second version is the trip.

The trip itself is yours to live. I'm a text away if it shifts mid-journey, with the optional on-trip support add-on for trips where same-day swaps and weather contingencies are likely. Most trips don't need it. Honeymoons and multi-destination Deep trips usually do.

What this whole process costs you, beyond the fee

The planning fee is the obvious cost. There are two less-obvious ones, and they're worth naming if you're trying to decide whether the process is for you.

The first is the wait. From intake to delivery is one to three weeks, depending on tier and add-ons. If you've been used to a chatbot producing an itinerary in ninety seconds, the slowness will feel strange. The slowness is the point — most of what you're paying for is time spent thinking about the trip, not typing it up. If your window is genuinely tight, priority delivery cuts the design phase in half. The intake-to-reply window doesn't change. That stays human.

The second is the loss of the hobby, if planning was your hobby. Some travelers love the open-tab research weekend the way others love jigsaw puzzles. If that's you, hiring a curator removes a thing you enjoyed. I've sent travelers home with a recommendation to keep planning their own trips. That's a perfectly good answer — not the one most people who reach this page are looking for, but the honest one when it's true.

If neither of those costs is a deal-breaker, and you've made it this far down the page, the rest of the answer is in the deliverable. The fastest route from here is the intake form. The form is the brief. Once it's in, the process I just described starts running.

What to read next

• How curated travel works (and why it beats more research) — the sister cornerstone, on what curation actually means in practice.
• Planning a honeymoon without the hype — a deeper look at how this process applies to milestone trips for two.
• The services page lays out the three Curation tiers side by side.
• The how it works overview is the five-step version of this post.

The skeptic's question — what am I actually paying for — is, in the end, a fair one. The answer isn't a single thing. It's a stretched-out act of editing that produces a shorter document than you'd expect, with deliberate gaps, named specifics, and a logic underneath. The fee is the time it takes to do the editing well, plus the constraint of taking only as much work as I can do at this depth. If the answer reads as honest, the next step is the form.