What exactly is a “Mission” — and how does it differ from a simple “route” or “trip”?

In SwiftWay, a Mission is your primary operational goal: a complete body of work that must be carried out—whether it’s delivering packages, performing service visits, or collecting items across multiple locations over time.

Unlike traditional route planners that focus only on “getting from A to B,” a Mission captures what needs to be done, not just how to drive.

What is a Mission?

A Mission is everything you need to get done.
It includes all the places you have to visit and all the tasks you need to complete at each location—like deliveries, pickups, inspections, etc.

A Mission is made up of waypoints.
Each waypoint is an address + a time window (for example: “10 Lenin St — tomorrow between 10 AM and 12 PM”).

You can attach one or more tasks to each waypoint:

• deliver 3 packages,
• collect a return,
• take a photo of the storage area, and so on.

In short:
🔹 Mission = your entire job,
🔹 Waypoint = where and when,
🔹 Task = what to do there.

The same address can appear multiple times in a mission—if you visit it at different times. Each visit is a separate waypoint with its own tasks.

Crucially:

A Waypoint is not just an address—it’s an address combined with a time window.
The same physical location can appear as multiple distinct Waypoints if you visit it at different times or under different constraints.

For example:

• “123 Main St, Monday 10–12” → Waypoint A
• “123 Main St, Thursday 14–16” → Waypoint B

These are two separate Waypoints in the same Mission—because the when changes the operational context.

Tasks live on Waypoints

Each Waypoint can carry one or more Tasks, such as:

• Deliver 3 packages to Client X,
• Pick up returned equipment,

Tasks are the units of work, while Waypoints are the when-and-where containers for that work.

Why this matters

Traditional apps treat routing as a geometric problem: “Find the shortest path through these pins.”
But real-world logistics is a temporal and operational problem:

“Which stops can I actually serve within their allowed time windows, given my vehicle, my schedule, and my workload?”

SwiftWay’s Mission model respects that complexity from the start. It doesn’t just reorder stops—it validates feasibility, honors time constraints, and ensures every Task has a proper Waypoint in time and space.

In short:

• Route = sequence of coordinates (navigation layer).
• Mission = full work assignment with time-aware stops and actionable tasks (operational layer).

So instead of just plotting points on a map, you’re building a real work plan.
Create a Mission, add the addresses you need to visit, attach what needs to be done at each stop, check the route for efficiency — and you’re ready to go.