Tourviaformerly RouteForceFree planning utility Browser-only scenario calculator
Test the visit capacity behind a field-sales coverage plan.
Estimate how many visits fit into a field day, week or planning period, then compare that modeled capacity with the coverage target you enter. The calculation uses only your assumptions.
- Local: no scenario data is uploaded
- Transparent: every result explains its arithmetic
- Bounded: this is not a route, forecast or staffing recommendation
Local workspace
Model capacity from your own operating assumptions.
All fields start blank. Enter a planning case, calculate it locally, then adjust assumptions to compare cases. No inputs, results or downloads are sent to Tourvia.
Calculation method
Every number can be checked.
- Usable time = field hours × 60 − reserved non-visit minutes, never below zero.
- Daily visits = floor((usable time + travel) ÷ (visit duration + travel)). Travel is applied only between consecutive visits.
- Weekly and period capacity = daily visits × field-day allocation × team size × planning weeks.
- Required volume = accounts in scope × target visits per account.
- Minimum reps is a mathematical result under the same assumptions, not staffing advice.
Fractional field days produce planning averages. They do not represent part of a customer visit.
Scenario result
Modeled capacity from your assumptions
All figures are arithmetic outputs, not operating recommendations or guarantees.
Waiting for inputs
Complete the assumptions above to compare an entered target with modeled capacity.
Reserved time leaves 0 usable field minutes under these assumptions.
Time behind the result
Coverage behind the result
Even-share cadence at full modeled capacity:
Minimum reps under these assumptions: Not available
Interpret the gap
A positive balance does not prove a route will work.
Routes and calendars rarely behave like averages. Customer availability, territory geography, traffic, cancellations, parking, holidays and priority rules can change what fits on a particular day. Use an actual routing or scheduling workflow for a dated field plan.
Test the account policy
First check whether the entered coverage target reflects the commercial reality of your accounts.
Test a representative map
Then sample geography, visit locations and territories in Salesforce before relying on one travel estimate.
Test a real field day
Finally validate day constraints, routes and Salesforce Event creation with the people who execute the plan.
Privacy
Your assumptions stay in this tab.
Calculations and CSV creation happen in your browser. The calculator does not send your inputs or results to Tourvia. Page analytics may record a page visit, but not the values you enter, calculate or download. Reloading or closing the page clears your scenario.
Use your own internal planning policy. The calculator does not process Salesforce records, modify your CRM or replace a capacity plan, territory decision or data-processing agreement.
Questions
Before you use a capacity scenario
What does “modeled capacity” mean?
It is the largest whole daily visit count that fits the entered time assumptions, multiplied across the team and planning period.
Why can weekly capacity include a decimal?
Fractional field days represent an average allocation. The daily visit result remains a whole number.
Does this calculator optimize routes?
No. It uses one average travel-time assumption and does not inspect locations, roads or calendars.
Is the cadence a recommendation?
No. It is an even-share rate produced by distributing modeled capacity across the accounts you entered.
Are my assumptions uploaded?
No. Calculation and CSV creation occur in the browser. The site’s usual audience measurement may record the page view, not your scenario values.
Next field check
Once capacity looks plausible, test the route workflow.
Use Salesforce records, territories and actual day constraints to evaluate whether selection, route planning and Event creation fit the way your team operates.
Continue the evaluation
Read the field sales route optimization guide before validating a route workflow in the target org.