Service
What is the customer asking for?
Record the service, expected duration, and any pricing, tax, or promotion details that change this case.
Start with a situation your team knows well. Record what can change the result—service, duration, price, area, availability, absence, promotion, or exception—then have unclear points confirmed.
The guide recommends documenting how the business actually works. Start with a common case, record only what changes the decision, and keep exceptions clearly identified.
A familiar appointment or workday quickly shows which decisions need to be clarified.
You do not need a complete manual. A short note should let another person understand the situation and the known exceptions.
Describe the case using words your team already uses.
Record the services, durations, prices, taxes, areas, availability, absences, promotions, or exceptions that matter.
State what your team expects to see or be able to do.
Keep anything that is not yet decided clearly identified.
Responsibilities should be clear: the business confirms how it wants to work, and MapMyStaff supports configuration within the agreed scope.
Record who on the business side can confirm this way of working.
First decide what the business wants to do, then check how it is configured.
Keep a record when a decision or exception changes.
Then use the specialized collection for booking, staff, territories, pricing, or security.
Before expanding, verify a real scenario and at least one relevant edge case to see whether the configuration matches the decision.
Use a situation that represents your operations.
Compare what is observed with what was decided.
Add a less common case that may change the decision.
Record the difference before changing another rule or setting.