Decide what you can book before choosing its length
You may know enough to arrange a first assessment without knowing how long the eventual work will take. The booking should preserve that distinction. 'An assessment visit is arranged' tells the next person something different from 'the repair will be finished that morning.'
Start by naming the purpose and agreed limits of the visit. Then ask the person responsible for planning that work to estimate the time it needs, with the assumptions visible. If the information does not support a useful estimate, identify what must be clarified rather than choosing a short slot to make the calendar fit.
Microsoft's Field Service documentation separates an arrival/start window from the duration of the work. It also describes duration estimates attached to defined service tasks and services. The decision aid below applies that distinction to manual planning. It is suggested administrative guidance, not a description of Worganizer fields or a trade procedure.
References: Microsoft Learn: arrival/start constraints and work duration · Microsoft Learn: duration estimates for tasks and services
Choose one of three planning routes
Use the request and existing job record to choose a route. An unknown matters when it changes the visit purpose, required person, time allowance, or commitment you can make. Other details may be collected later with a named owner. The route labels are suggestions for discussion, not software statuses.
- Defined task: the work is agreed and the necessary arrangements are sufficiently clear. Ask the responsible planner to estimate that specific scope using relevant completed work and current conditions. Record important assumptions, including any dependency that could change the estimate.
- First assessment: the purpose is to establish what further work may be needed. Agree what this first visit covers and reserve time for that purpose using the team's approved planning process. Keep possible additional work separate until its scope, resources, timing, and customer decision can be reviewed.
- Pending information: a missing answer prevents you from choosing a suitable visit or time allowance. Record the exact question, the person obtaining the answer, and the next update point. Keep a proposed slot clearly distinguished from a confirmed appointment while that decision is open.
Write down the estimate you are actually planning around
A time range can help the dispatcher test more than the most convenient outcome. It still needs a basis. Use a range the responsible person can explain for the agreed visit purpose, and state what it includes. If the work could extend beyond any useful range, reconsider the visit plan instead of presenting an invented upper limit as dependable.
Keep time at the property separate from preparation, record completion, and travel when those are separate parts of your plan. An arrival window describes when the visit starts; the reserved work allowance describes capacity you are using afterward. Neither establishes that all possible follow-on work will be completed during that allowance.
- Visit reference and agreed purpose: _____. What is outside this booking? _____
- Estimated time for that purpose: _____. Who supplied it, based on what information? _____
- What the estimate includes: _____. Preparation, notes, and travel to allow separately: _____
- Assumptions or dependencies that could change the plan: _____. Which are confirmed? _____
- Next fixed commitment and its location: _____. Does the plan still fit at the longer end of the chosen range? _____
- Review point: _____. Who obtains the update, and who handles any affected booking? _____
Fictional example: compare two possible start times
This example is fictional. Coordinator Morgan is arranging an initial assessment of Item A for Tuesday, October 27, 2026. The visit purpose is already agreed; further work has not been booked. The training plan assumes 60-90 minutes at the property, 15 minutes afterward for the visit record, and 30 minutes to reach the next appointment. These are invented planning assumptions for arithmetic, not recommended service durations or a travel estimate for any real location.
The next appointment has a fixed 11:30 a.m. arrival commitment. Morgan compares a 9 a.m. start with a 9:30 a.m. start, using the same assumptions for both. All times below are local, and the example begins with the technician already at the first property. Travel to the first visit must be planned separately.
The 9 a.m. option leaves 15 minutes between the later modeled arrival and the 11:30 commitment. That is the remaining space under this scenario, not evidence that the allowance is sufficient in practice. The 9:30 option extends to 11:45 at the longer end, so Morgan cannot rely on its earlier possible finish to protect the existing 11:30 commitment.
If the customer can only accommodate 9:30, Morgan needs another reviewed arrangement. Shortening the written estimate without new information would leave the same uncertainty hidden. Any changed customer commitment still needs to be checked and agreed.
- 9 a.m. start: 60-90 minutes at the property gives an estimated 10-10:30 finish. Add 15 minutes for records and 30 minutes for onward travel: modeled arrival at the next appointment is 10:45-11:15 a.m.
- 9:30 a.m. start: the same work allowance gives an estimated 10:30-11 a.m. finish. Add the same 45 minutes for records and travel: modeled arrival is 11:15-11:45 a.m. The later outcome misses the 11:30 commitment by 15 minutes.
- Booking decision: propose the 9 a.m. assessment only after checking the first arrival, required arrangements, and customer agreement. Record the assessment purpose and a 10:15 a.m. status review by Morgan. Completion of additional work remains unconfirmed.
Set a review point while there is still a planning decision to make
In the fictional plan, Morgan's 10:15 status review checks the available update on what the current visit is expected to require next and whether the later booking needs attention. It is an administrative checkpoint, not an instruction to rush or stop technical work. The team uses its approved service procedures for the work itself.
When more work becomes clear, separate its scope from the original assessment. Check the required resources, estimate, customer decision, and effect on later commitments before treating it as part of the day's confirmed plan. If the timing remains unknown, Morgan owns the next customer update rather than inventing a new arrival time.
Write the changed assumption into the record. A useful update says which visit is affected, what remains uncertain, what arrangement is currently agreed, and who will make the next decision. Use the arrival-window message guide when a customer needs a timing update.
References: For timing changes: customer arrival-window messages
Keep the next estimate connected to what was learned
After the visit, record the actual visit purpose, work performed, relevant times, and unresolved items. Identify what changed the planning assumption: additional scope, an access wait, missing information, or another recorded reason. Keep unavailable details marked unknown. One visit is context for a future estimate, not a universal duration for every job with the same label.
The next booking may be for a now-defined task, another assessment, or a request still waiting for information. Choose its route from the current record. The job-notes template can preserve that handoff without copying a speculative completion promise into the next appointment.
References: Record the outcome: service job notes template
Read the booking back before confirming it
Use this final check with the colleague handling the request. Try the worksheet on one booking and adjust any wording that leaves them guessing about the plan. For the wider daily capacity plan, use the main scheduling guide.
- The customer and technician can identify what this visit covers and what remains undecided.
- The arrival arrangement, work allowance, and any completion commitment are stated separately.
- The estimate has an identified basis, and separate planning time has been included.
- The longer modeled outcome has been checked against the next fixed commitment, with remaining uncertainty visible.
- A named person owns the review point and any affected customer update.
References: For the whole day: build a field service schedule