# Flowtlas planning workshop

An editable preparation worksheet, not an app import specification.
The accompanying CSV contains fictional service visits with no real addresses or personal data.
It intentionally omits coordinates, vehicles and travel data; it cannot be solved as-is.

## 1. Describe the decision

- [ ] State which day or dated work periods you want to plan.
- [ ] Identify the owner who can approve a route plan.
- [ ] Separate fixed commitments from work that may move.
- [ ] Agree whether a partial plan with unassigned work is acceptable.

Our planning question:

## 2. Describe the jobs

- [ ] Collect a representative work list, not your entire operation.
- [ ] Give each job and location a stable identifier.
- [ ] Validate addresses and coordinates before using them for travel estimates.
- [ ] Include service duration, customer access windows and required skills.
- [ ] Keep pickup-before-delivery chains explicit.
- [ ] Use consistent units for load changes and capacity.

What is missing or uncertain?

## 3. Describe the resources

- [ ] List the available people and vehicles.
- [ ] Record dated working periods, breaks, start and end locations.
- [ ] Record relevant capacities and skill tags.
- [ ] Have a responsible person validate actual qualifications.
- [ ] Describe required depot returns or overnight stops explicitly.

Who owns these inputs?

## 4. Review the result

- [ ] Check assignments, stop order, arrival times and service time together.
- [ ] Review unassigned work and reported reasons.
- [ ] Check whether limitations came from inputs, constraints or search limits.
- [ ] Do not interpret complete coverage as proof of global optimality.
- [ ] Do not interpret an unsuccessful bounded search as proof of impossibility.
- [ ] Agree who verifies the plan before operational use.

What would make this result useful?

## 5. Confirm availability with Flowtlas

- [ ] Confirm which planning functions are enabled in your workspace.
- [ ] Confirm the actual data import/export formats and integrations.
- [ ] Identify the source and freshness of recorded operational state.
- [ ] Check live tracking, notifications and downstream workflows separately.
- [ ] Keep safety and legal-compliance checks in their verified operational processes.

Next step: https://flowtlas.com/contact/
Product data preparation reference: https://flowtlas.com/resources/guides/route-planning-data-checklist/