# A route planner that helps you get home earlier

Build a native Tauri application for someone whose work takes them to several places in a day. Give their existing coding agent proper tools to plan that work alongside them. Build it extremely well: the benefit is less time driving, appointments kept, and an earlier return home. Follow the [shared launch](../shared/launch.md).

Discover the kind of visits the person makes and the area they cover. Prepare a fictional set of stops with enough real-world variety to demonstrate a useful working day. If they already use the [calling desk](../desktop/calling-follow-up-desk.md), carry its agreed visits into planning with their context intact.

## Plan the work the journeys serve

Let the person supply places, expected visit lengths, opening hours, appointment windows, and the practical commitments that determine where they can go. Include the beginning and end of the day, breaks, and priorities that matter to this job. Make uncertain locations or missing information easy to resolve.

Present the stops on a useful map and as a legible schedule. Show travel, work, waiting, and the expected return time. A fixed appointment, a flexible visit, and a proposed arrangement should have recognizable meanings.

Let the person move a stop, fix an appointment in place, change a duration, or explain a preference in ordinary language. Both direct changes and agent actions should update the same plan.

## Give the agent the information and tools to improve it

Use calculated road travel times and distances to evaluate candidate plans. Keep a reusable travel-time matrix where it serves this workload, with enough source context to understand what the estimates represent. Choose suitable routing and mapping services or local software for the person's area and resources; handle their setup as part of the build.

Give the existing agent access to the current stops, constraints, selected plan, travel calculations, and meaningful operations for proposing, evaluating, and applying changes. Reuse its established installation and account. Make it a native collaborator in the app.

Let the agent explore useful alternatives autonomously within the person's direction. It can compare a geographically tidy route with one that fits a difficult appointment and avoids an hour of waiting. Have it surface consequential compromises, including a day that cannot accommodate every requested visit.

Keep the calculation and the judgment inspectable. A map should show the chosen journey; the explanation should tell the person why that journey serves their working day. Label estimated travel appropriately, including whether current traffic informed it.

## Handle the day changing

A customer cancels, a visit runs long, or the person finishes early. Let them record what actually happened and ask for a revised remainder of the day. Preserve completed visits and commitments already made while the agent works from their current position and situation.

Keep candidate alternatives distinct from the selected plan. Support a useful return to an earlier plan, and make changes to externally agreed appointments explicit. The person should be able to send the next destination to navigation without losing the schedule here.

## Deliver a day someone can use

Complete the installed app, routing setup, agent connection, and ownership arrangements. Work through the example day, compare alternatives, change an appointment directly, and have the agent revise the remaining work. Judge the resulting schedule against the actual constraints and explain any unresolved tradeoff.

Teach the division of labor through this experience: software calculates journeys; AI reasons about what makes a good day of work. A later phone connection can bring current progress and traffic information into that same planning process while the person is away.