Observed baseline
$600,000 in annualized revenue and $120,000 in estimated profit based on configured costs.
Before changing operations
If you add more appointments, can your team actually absorb the workload?
Test a change in volume, price, capacity, costs, or territory using a reference period and the available data. MapMyStaff keeps observed information separate from simulated results so you can compare effects and limits before changing operations.
From baseline to scenario
To compareStart from an explicit baseline
01
Reference baselineClosed month or historical average
OBSERVED02
Modified leverVolume, price, capacity, cost, or route
ASSUMPTION03
Calculated resultRevenue, profit, margin, and workload for the scenario
SIMULATED04
Reading to compareCapacity, limits, and scenario differences
TO EVALUATE01Baseline and assumption
Test a decision from an observed baseline.
The simulator starts from an exact closed month or a historical average, then isolates an assumption involving volume, price, cost, or capacity. The observed baseline and simulated result remain separate.
The active baseline and confidence score help flag cases where limited history, incomplete data, or a narrow baseline call for a more cautious reading.
iIllustrative example—fictional data and coherent calculations. Values do not represent verified customer results.
Isolated assumption
+15% appointments, without changing the average price.
Visible limitation
Simulated demand exceeds the selected monthly capacity by 60 hours.
OBSERVED vs SIMULATED
Observed revenue
600 000 $
Simulated revenue
690 000 $
Result breakdown
Simulated costs included561 000 $
Observed and simulated trajectory
02Capacity
Check whether capacity keeps up with the scenario.
The simulator puts scenario volume alongside the capacity represented by the available data and settings: historical capacity, added capacity, simulated hires, logistics, and planner volumes.
A capacity overrun remains visible even when simulated revenue or profit increases. Financial results and capacity therefore need to be read together before evaluating the scenario.
iIllustrative example—fictional data and coherent calculations. Values do not represent verified customer results.
690 000 $
According to the active assumption
129 000 $
After $561,000 in simulated costs
+9 000 $
Difference from the reference
18,7 %
Based on configured costs
ResultCapacityTerritoriesSensitivity
Scenario capacity
Available
920 h/month
Required
980 h/month
Difference
+60 h
Travel burden
03Territories and route
See where route load weighs more heavily across territories.
The territory view brings together available volume, travel time, revenue, and efficiency by area. It supports comparisons between geographic areas and schedule models.
These indicators help identify where a territory deserves closer review; by themselves, they are not an automatic decision about that area.
iIllustrative example—fictional data and coherent calculations. Values do not represent verified customer results.
$158/h
2
Territory C
$24/h
Territory comparison
Territory A
$152/h
18.4 h travel
$152/h
18.4 h travel
Territory B
$168/h
13.2 h travel
$168/h
13.2 h travel
Territory C
$124/h
15.1 h travel
$124/h
15.1 h travel
Territory D
$181/h
12.8 h travel
$181/h
12.8 h travel
Territory indicator
Detailed area analysis
| Area | Index | Volume | Travel burden | Performance | Models compared |
|---|---|---|---|---|---|
| Territory A | 62/100 | 62 appts | 34 % | $152/h | Fixed / periods |
| Territory B | 74/100 | 78 appts | 25 % | $168/h | Fixed / periods |
| Territory D | 82/100 | 96 appts | 20 % | $181/h | Fixed / periods |
04Scenarios to compare
Change one element, then compare the scenarios you retain.
The simulator can compare explicitly saved scenarios and show how changes such as capacity, customer attrition, or selected costs affect simulated revenue, profit, and margin.
Autosave keeps the current workspace in the browser. Checkpoints are intermediate work states, while a scenario enters the library only when it is deliberately saved; a summary can be copied or exported as a PDF.
iIllustrative example—fictional data and coherent calculations. Values do not represent verified customer results.
Session continuity
Restore the latest work state or create a checkpoint before testing a new assumption.
Scenario comparator
Scenario A — Volume +15%
Scenario B — Price +5%
| Measure | Volume +15% | Price +5% |
|---|---|---|
| Annual revenue | 690 000 $ | 630 000 $ |
| Estimated profit | 129 000 $ | 147 000 $ |
| Estimated margin | 18,7 % | 23,3 % |
| Capacity ceiling | Reached | Not reached |
Save workspace
Scenario name
Status: draft
Comparison summary
Intent: Compare a volume increase with a price increase.
Reading: In this example, the two scenarios produce different profit and capacity differences.
05Limits and method
Keep the scenario limits visible.
The confidence score considers factors such as historical depth, reference-window width, data completeness, profit stability, and penalties associated with capacity or a narrow baseline.
The score is a reading aid, not a statistical guarantee. A scenario is not a guaranteed forecast, and profit should be read cautiously when actual production costs are not fully structured in the source data.
iIllustrative example—fictional data and coherent calculations. Values do not represent verified customer results.
Data and confidence
Confidence score
72/100
Data completeness
83 %
Two employees do not yet have usable hours; the scenario should be interpreted cautiously.
Change in one parameter
| Test | Revenue | Profit |
|---|---|---|
| Active scenario | 690 000 $ | 129 000 $ |
| Capacity −20% | 600 000 $ | 102 000 $ |
| Customer attrition +10% | 621 000 $ | 108 000 $ |
Operational assumptions
| Reference period | Average of the last 3 months |
| Available capacity | 920 h/month |
| Route-related assumption | 0 % |
| Additional simulated costs | $81,000/year |
Scenario formula
Estimated profit = simulated revenue − fixed costs − variable costs
Simulated revenue
690 000 $
Included costs
561 000 $
Estimated profit
129 000 $
Saved scenarios
Explicitly saved scenarios retain a stable fingerprint, reference period, and main settings to facilitate comparison and return to an earlier decision.
06FAQ
Frequently asked questions
Detailed definitions remain available when the team needs to verify the baseline, capacity, confidence score, or method behind a scenario.
Are simulated revenue and profits guaranteed?
No. A scenario is not a guaranteed forecast. Results depend on the reference period, available data, and selected assumptions; profit should also be read cautiously when actual production costs are not fully structured in the source data.
What is the difference between observed, assumption, and simulated?
Observed refers to the selected historical baseline. Assumption refers to a value changed for the test. Simulated refers to the result calculated from that baseline and assumption.
How is scenario capacity estimated?
The calculation combines theoretical historical capacity, explicit added capacity, simulated hires, capacity recovered through logistics, and planner capacity. The result depends on the data and settings present in the scenario.
What does the confidence score measure?
It aggregates factors including historical depth, reference-window width, data completeness, profit stability, and penalties related to capacity or a narrow baseline. It is a reading aid, not a statistical guarantee.
Can several scenarios be saved and compared?
Yes. Autosave keeps the current workspace in the browser, checkpoints serve as intermediate work states, and deliberately saved scenarios populate the local library. A summary can be copied or exported as a PDF.
View the AcademyNext step
Request a targeted demoLet’s test a change you are actually considering.
Use a reference period, the available data, your configured costs, and the represented capacity to compare a scenario before changing operations.