# How to handle multi-day scheduling in Field Service Lightning A multi-day job is one piece of work with an order. If day two needs a part that day one discovers, the later days have to be allowed to move. **Published:** 2026-01-13 **Canonical:** https://synconai.com/multi-day-scheduling-field-service **Author:** SynconAI Architecture Team ## In short A multi-day job is one piece of work with an order, not five unrelated appointments. If day two needs a part that day one discovers, the later days have to be allowed to move. Put the known tasks, skills, parts, and duration on a template, and leave room for what the first visit finds. The product is Agentforce Field Service and Operations. ## Sources - **Agentforce Field Service and Operations** (retrieved 2026-10-10) https://help.salesforce.com/s/articleView?id=service.fs_overview.htm&type=5 > Schedule one-time or recurring work orders for customers, and add details about worker preferences, required skills, and parts. - **Agentforce Field Service and Operations** (retrieved 2026-10-10) https://help.salesforce.com/s/articleView?id=service.fs_overview.htm&type=5 > Create maintenance plans and templates to standardize your field service tasks. ## What to take away - Book the days as one job with a sequence. Separate appointments with no link can be moved independently, and day two can land before day one. - Put the known tasks, skills, parts, and duration on a maintenance plan template so the first day does not start from a blank work order. - Leave later days movable. The part day one finds is a normal outcome, not an exception you failed to prevent. - Use a recurring work order for work that truly repeats. A multi-day repair is not a recurrence. ## The guide Thursday's fit was scheduled for Monday. The skill matched, the travel looked shorter, and nothing on the five appointments said they were one repair. The machine was still in pieces from an inspection that had not happened yet. The customer had a reminder for a Thursday that was no longer Thursday. The part day one was supposed to name had not been named, because day one was now after day two. People still search for Field Service Lightning. The product is Agentforce Field Service and Operations, formerly Field Service. Multi-day work uses the same two objects as a short visit. The mistake is treating Tuesday as a stranger to Monday. Salesforce says you can "Schedule one-time or recurring work orders for customers, and add details about worker preferences, required skills, and parts." Recurring means the job comes back on a pattern. A three-day repair is one-time work that happens to span days. Do not force it into a recurrence to make the calendar look full. The other sentence is the template: "Create maintenance plans and templates to standardize your field service tasks." The known steps belong there. The unknown part, the one day one discovers, is why the rest of the booking cannot be frozen. ## One job, in order Write the sequence on the work order in language a dispatcher can follow. Day one: make safe, inspect, name the part. Later days: fit the part, test, hand back. If those are five unrelated appointments, the scheduling run is free to treat them as five jobs. It can move Thursday to Monday because the skill and the travel look better. The machine is then waiting on a step that has not happened. The optimizer is not being difficult. It accounts for worker skill level, travel time, location, and other factors. Unrelated appointments give it nothing else to respect. Sequence is not in that published sentence. You have to represent the sequence yourself, on one work order or on an explicit link your people already understand, so nobody has to remember that these five pins are one repair. A link that lives in a dispatcher's memory will be forgotten on the busy day, which is the day the move hurts. Keep the same work order, or that explicit link. Preferences, required skills, and parts sit on that work order. The skill for day one may differ from the skill for the fit. Say so. Sending the inspector to do the rebuild, because you only stored one skill, wastes the inspector and the fitter. Sending the fitter to do the inspection, because they were closer, wastes the inspection. Both failures look like routing. Both are a missing distinction on the job. Duration is per step, from jobs you have watched. A single hour stretched across a week is a lie in both directions. The inspection looks longer than it is, so the day one person is blocked out for work they could have done. The fit looks shorter than it is, so the completion is promised into a gap that cannot hold it. Put the watched duration on each step. Leave the freak overrun on that appointment. Change the template when the same step is always long. ::: warn Five appointments with no link are five jobs. The efficient move can put the fit before the inspection. The machine waits, the customer holds the old day, and the board still looks tidy. The link is what makes the order visible to the next run. ::: ## The part day one finds Assume the first visit will change the plan. That is what inspection is for. The template lists the parts you always need. The work order gains the part you did not know about. The later appointment has to move until that part is on site. A schedule that cannot move will be rewritten by phone, and the phone version will not match the board. Name who is allowed to move it. The dispatcher, on the day the part is identified, not a weekly planning meeting after the customer has already been given a Thursday they will not get. The permission should be ordinary. If moving the later day requires a meeting, people will not move it. They will promise Thursday and apologise on Thursday. The apology is more expensive than the move, and it trains the customer not to believe the next window. Tell the customer the later day is held, not promised, until the part is confirmed. A reminder for a day you do not have is how you create the angry call. Confirm the window, then talk about it. Appointment Assistant is the name on the help page for that message. Use it for a window a dispatcher would defend. Do not send it for a hold. A hold said out loud, by a person, is honest. A text that looks like a confirmation is not. If two people are required on the fit day, both names are part of the dependency. Moving one without the other is the same failure as doing day two first. The second trade might be a contractor with hours that do not match your roster. Their user, their hours, and their territory have to be free on the day you move to, or you have moved a job onto a person who is not engaged. Check that before you tell the customer the new window. ## What is firm, and what is held | Step | What you can tell the customer | What has to be true first | | --- | --- | --- | | Make safe and inspect | A window you will keep | The skill for inspection, and a duration from watched inspections | | Name the part | Nothing about the fit day yet | The inspection actually happened | | Fit and test | A window, once, when the part is on site | The part, both people if the fit needs two, and the later duration | | Hand back | The same window as the fit, if hand-back is the end of that visit | The fit step is still attached to it | A customer who wants every row promised on the first phone call is asking you to lie about the part. Say which row is firm. The inspection can be firm. The fit is held. People accept a held day more easily than a broken confirmation, and your reminder volume will show it. If reminded customers still call to ask whether Thursday is real, you sent the message too early. ## Templates for the known half Build the template for the class of multi-day job: the tasks, the skills, the usual parts, the durations. Maintenance plans fit when that whole job recurs on an asset. A one-off failure uses the template once, as a one-time work order. Forcing the repair into a recurrence because the calendar tool made that easy will bring the same crisis back next interval. You will spend a morning cancelling it, or a technician will attend a job that should not exist. Do not clone last month's appointment and change the date. Cloning copies last month's wrong duration, last month's missing skill, and last month's part that was a one-off. The template is the place you correct the pattern. The appointment is the place you allow the exception. What belongs on that template, and why a logo is not one, is set out in [custom work order templates](/custom-work-order-templates-field-service). Start multi-day work from there. The sequence and the permission to move are what this page adds. After the job, write down what day one found that the template lacked. If the same part appears three times, it belongs on the template. If it was a freak failure, leave it off. That is how the known half gets bigger and the surprise half gets rarer, without pretending you can see the future. Do the write-down while the fitter still remembers. A review a month later will invent a tidier story, and the tidier story is how the template stays wrong. ::: note Recurrence is for work that returns on a pattern. A repair that spans days is one-time work with an order. The template still applies. The calendar coming back next month does not. ::: ## The day the part is not there Sometimes the part is late, or wrong, or the inspection finds that the job is a different job. The later appointments should come off the board the same day, not sit as if the fit were still happening. A ghost appointment occupies a person the optimizer could have used, and it still shows the customer a window. Cancel or move it in the record. A note that says "probably not" will be missed. Site preferences do not pause because the work spans days. Induction on day one may not cover the second trade on day two. A delivery window for the part may be morning only. Those preferences belong on the work order before the fit is promised. A multi-day job that ignores them will pass the sequence test and still fail at the gate. The mobile app is offline-first. The technician on day one may be out of coverage when they learn the part number. The briefing pack has to let them record it on the work order without a signal, and the clash rule has to say that their note stands when it meets a dispatcher edit. If the part number only exists in a phone call that nobody typed, day two will be staffed for the template part, and the van will be wrong. The sequence is only as good as the fact day one managed to store. Continuity of people is part of the order, and it is easy to lose. Day one may need the inspector. Day two may need the fitter. When it is the same person, say so, because a scheduler that sees two skills and no preference will pick the nearest legal match for each day and you will brief two strangers on one machine. When it must not be the same person, say that too. An inspector booked back for a fit they are not ticketed for is the skill failure again, spread across a week so it looks like a diary problem. Hand-over between those people has to be on the work order, not in a call that day one could not make from a dead zone. The part name, the hazard, the panel that was left open: if it is not on the record, day two starts from the template alone. The template is the known half. The note is the half day one was sent to discover. Lose the note and you have paid for the inspection twice. Agentforce Field Service and Operations, which people still call Field Service Lightning, will schedule whatever appointments you give it. Give it one piece of work, in order, with the later days allowed to move when day one learns something. Then the efficient day and the machine can agree. ## Questions ### Should a multi-day repair be a recurring work order? No. Salesforce distinguishes one-time and recurring work orders. Recurrence is for work that returns on a pattern. A repair that spans days is one-time work with a sequence. Forcing it into a recurrence to fill the calendar will bring the same crisis back next interval, and someone will spend a morning cancelling it. Use a template so the known steps, skills, parts, and durations still start complete; the surprise part stays off the template until it stops being a surprise. ### What happens if each day is its own appointment with no link? Each day can be moved on its own. Day two can be scheduled before day one if the skill and the travel look better that way, because the optimizer is treating them as five jobs. The machine then waits on a step that has not happened, and the customer may already hold a reminder for the old day. Keep the sequence on one work order, or on an explicit link people already understand. A link that lives only in a dispatcher memory will be forgotten on the busy day. ### How do we handle a part discovered on day one? Add it to the work order. Move the later days until the part is on site, and name the dispatcher who is allowed to do that on the day, not at a weekly meeting after the promise is already public. Tell the customer the later window is held, not confirmed. A frozen booking will be rewritten by phone anyway, and the phone version will not match the board. If two people are required for the fit, move both. Moving one is the same failure as doing day two first. ### What belongs on the template? The tasks, required skills, usual parts, and durations for that class of job. Maintenance plans and templates exist to standardise those tasks. Do not clone last month's appointment and change the date, because you will copy last month's missing skill and last month's one-off part. The template is where you correct the pattern. The appointment is where the exception is allowed. If the same discovered part appears three times, it belongs on the template; a freak stays on the work order. ### Which product is Field Service Lightning now? Agentforce Field Service and Operations, formerly Field Service. The help page still uses the Field Service name in places. Field Service Lightning is the search phrase. Multi-day work uses the same work orders and templates as a short visit. The product will not infer that Tuesday depends on Monday unless you represent that order. Recurrence will not do it for you; recurrence means the job comes back, not that it lasts three days. --- SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Field Service (https://synconai.com/salesforce-field-service).