# How to create custom work order templates in Field Service Lightning A template starts the job complete: skills, parts, tasks, and a duration taken from real work. A blank form with a logo is stationery. **Published:** 2026-04-06 **Canonical:** https://synconai.com/custom-work-order-templates-field-service **Author:** SynconAI Architecture Team ## In short A template should start the job complete: tasks, required skills, parts, and a duration that is not a guess. Maintenance plans and templates exist to standardise field service tasks, so the same work is not rewritten for every asset. A blank form with a logo is not a template. 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 > Create maintenance plans and templates to standardize your field service tasks. - **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. ## What to take away - Maintenance plans and templates exist to standardise tasks. Use them for the skills, parts, and duration, not for branding. - The work order still carries preferences, required skills, and parts. A template that does not fill those in has not started the job. - Duration comes from watched jobs. A mandatory one-hour default will be scheduled as if it were true. - One template per kind of work. Customer-specific site rules are preferences, not a reason to clone the whole task list. ## The guide The dispatcher had thirty seconds and a blank work order with a logo in the corner. The skills were empty. The parts were empty. The duration was one hour because the field was mandatory. They guessed, and the next shift guessed differently. By Friday the same kind of job had three durations and two skill lists, and the scheduling optimizer had built three different days from one kind of work. The logo had printed nicely. It had not started the job. People still search for custom work order templates in Field Service Lightning. The product is Agentforce Field Service and Operations, formerly Field Service. The help page already says what a template is for, and it is not a logo. "Create maintenance plans and templates to standardize your field service tasks." Standardise the tasks. The same job, on the next asset, starts with the same steps. "Schedule one-time or recurring work orders for customers, and add details about worker preferences, required skills, and parts." The template earns its name when those details arrive already filled. ## What complete means Open a new work order from the template and read it as a dispatcher who has thirty seconds. Can you see the required skills, the parts, the tasks, and a duration? If any of those is blank, the template is a form. The dispatcher will guess, the guess will differ by shift, and you will be back to reinventing the job. Tasks are the steps a competent person follows, in order, including the checks that stop a return visit. Write them so that person can do the job without a side document. A task that says "complete the service" is a heading, not a step. A task that says which check comes before the unit is closed up is a step. The order matters. A check that sits after the close-up in the list will be skipped, and the skip will be blamed on the crew. Skills are the ones that change who may do it, not a generic "technician" skill everyone holds. If the template requires a skill nobody can fail, it does not route. If it requires a stack nobody holds, nothing schedules, and someone will strip the skills off the work order "just this once." The once becomes the copy everyone clones. Put the refusal skills on the template: the ticket, the trade, the isolation. Leave the decoration off. Parts are the ones you expect to use, with enough detail that the van can be stocked before it leaves. A part line that says "as required" cannot be picked. The technician finds out at the asset. The return trip is the duration you forgot to store, and the next customer waits. List the usual kit. The surprise part can be added on the visit. It should not be an excuse to leave the usual kit blank. Duration is the time that class of job actually took, from jobs you have watched, not the number that made a project plan look neat. A mandatory one-hour default will be scheduled as an hour. The optimizer accounts for that hour, plus travel time, skill, and location. It will fill the day. The day will not fit. Correct the template when the watched jobs disagree with it. Do not correct the crew's speech about "updating their time" while the template still lies. ::: warn A blank form with a logo is stationery. It does not fill skills, parts, tasks, or duration. The scheduler cannot read a PDF. The dispatcher will guess, and each shift will guess a different job. The template is the record that creates the work order already able to be scheduled. ::: ## Maintenance plans versus a one-time job A maintenance plan says this asset gets this standard job on a pattern. The template is the standard job. Together they stop a planner rewriting a service every time a serial number comes due. A one-time breakdown can still start from the same template, without being a recurring plan. Recurrence is for work that really returns. The template is for work that should look the same whenever it happens. Using the plan for a one-off crisis will bring the crisis back next interval. You will cancel it, or someone will attend a job that should not exist. Using no template for the one-off, because "plans are for services," sends the breakdown back to a blank page. Start the breakdown from the template for that failure mode. Leave the plan for the work that belongs on a calendar. Preferences usually stay off the shared template. They belong to the customer or the site: access hours, induction, a contact. The template can leave them empty on purpose. Do not hard-code one customer's gate rule into a template used for the whole fleet. The gate rule goes on the work order when that customer is the customer. A template that includes it will send every other customer the same instruction, and one of them will be wrong in a way that wastes the visit. ::: note Empty preferences on a shared template are deliberate. Site rules are not tasks. The tasks, the skills, the usual parts, and the duration are the template. The gate code is the visit. ::: ## One template per kind of work Build one template per kind of work: install, inspect, replace this assembly. If two customers need different steps, you have two kinds of work, or you have one kind of work plus preferences. Find out which before you clone. Cloning a template per account feels helpful and becomes fifty drifting copies, each missing a safety step someone updated in only one of them. The drift is predictable. Engineering changes a torque value. They tell the person who owns "the" template. Three of the fifty copies get the change, because those were the ones open on a screen. The other forty-seven keep the old value. A crew that worked the updated account last week will use the new value on an old copy, or the old value on a new one, depending on memory. The record will not match the spanner. One template makes the change once. New work orders get it. In-flight work orders keep what they started with, unless you deliberately update them and tell the people already on site. A heavy equipment fleet feels the drift faster, because the serial numbers look like a reason to customise and the job is long enough to hide a wrong step until dusk. The asset changes. The job definition should not. That pattern is laid out for manufacturers in [Field Service for heavy equipment](/field-service-heavy-equipment-manufacturing). The same rule holds for a short visit. Customer-specific steps are either a real second kind of work, or they are preferences. They are not a reason to fork the task list. | Kind of difference | Where it goes | What cloning the template does | | --- | --- | --- | | The steps, the skill, the usual parts, the duration | One template for that kind of work | You now have two standards to forget to update | | Access, induction, a contact, a gate | Preferences on the work order | The fleet inherits one customer's site | | A part this visit discovered | That work order, until it stops being rare | The freak becomes everyone's standard kit | | A logo or a branded sheet | The paper the customer wants, if they want it | Nothing on the board changes. It is not the template | | How often the standard job returns | A maintenance plan, when it truly recurs | A one-off crisis comes back next interval | ## Keep it true After a month, compare durations on the template with time technicians recorded, by work type. If they diverge as a pattern, change the template. If one job diverged because something failed, leave the template and keep the note on that work order. A template that stays wrong teaches the scheduler the wrong day, every time someone uses it. The fortnight of finished work is the source. A workshop vote is how the hour got there. Review the template with someone who does the job, not only with someone who configured the object. Read the tasks aloud on site, in order, with the tools in front of you. A step that looks obvious in an office and is wrong on site will be skipped, and the skip will look like non-compliance. Fix the step. Then the template is something the crew will start from, which is the only way it standardises anything. The mobile app is offline-first. The tasks have to be on the work order the technician downloaded, not in a related file they cannot open in a basement. If the "template" is a PDF on a desktop library, it is not on the job. Put the steps on the record that syncs. A crew that cannot see the step will invent one, and the invention will not match the next crew. When you change a template, say what happens to work already scheduled. Leaving it implicit means some dispatchers push the change onto live jobs and some do not. The fitter who left at dawn may be out of coverage with the old list, which is the correct list for that visit if you did not deliberately brief them. New work gets the new list. That single rule stops the record and the spanner diverging in secret. Name an owner for each template. Not a committee. The owner is the person who may change the tasks, the skills, the parts, and the duration, and who must say no to a copy per account. When engineering changes a part, they tell that owner, and the owner changes the one record. A template with no owner will be edited by whoever is annoyed this week, and the annoyance will not match the last annoyance. The crew then stops starting from it, which is the failure. A template nobody starts from does not standardise anything. It sits in the list while the real job is invented on the phone. The owner also watches the month's comparison of stored duration against time on site. If they cannot see that comparison, they cannot keep the template true, and the scheduler will keep building from the old hour. Give them the comparison. Do not give them a new template for each complaint. Agentforce Field Service and Operations, still searched as Field Service Lightning, will schedule the work order the template created. Fill the skills, the parts, the tasks, and a duration from watched jobs. Leave the logo on the paper. The thirty-second read is the test. If a dispatcher still has to guess, you do not have a template yet. ## Questions ### What should a work order template contain? Tasks, required skills, parts, and a duration taken from real jobs of that kind. Maintenance plans and templates exist to standardise field service tasks. A blank form with a logo does not do that, and the scheduler cannot read a PDF. Open a new work order from the template and see whether a dispatcher can staff it in thirty seconds. If they have to guess, the template is still a form. Preferences such as a gate code stay off the shared template on purpose; they belong to the site, on the work order. ### How is a template different from a work order? The template is the standard. The work order is the job for a customer, with preferences, required skills, and parts. The template should fill the skills, parts, tasks, and duration so the dispatcher is not inventing them per shift. A maintenance plan says which asset gets that standard job on a pattern, when the work truly recurs. A one-time breakdown can still start from the template without being a recurrence. Recurrence for a one-off crisis will bring the crisis back next interval. ### Should every customer have their own template? Only when the tasks themselves differ. Site rules and access windows are preferences on the work order. Cloning the whole template per account creates copies that drift apart, so a safety step updated on one account never reaches the fleet. If two customers need different steps, decide whether you have two kinds of work. A logo is not a difference. Engineering changes one template, once; in-flight jobs keep the list they started with unless you deliberately update them and tell the people already on site. ### Where does duration come from? From jobs of that kind you have watched. A default of one hour, chosen because the field was mandatory, will be scheduled as an hour. The optimizer will stack the day from it, plus the travel time it already accounts for. Compare the template with recorded time after a month and correct the template where the gap is a pattern. Leave a single freak overrun on that work order. A workshop vote is how the fictional hour got there; the fortnight of finished work is the source. ### What is the product called? Agentforce Field Service and Operations, formerly Field Service. Field Service Lightning is the search name, and the help page still says Field Service where it names maintenance plans and templates. The template is the record that starts the work order already able to be scheduled, not a branded sheet. Name one owner who may change it and who refuses a copy per account. A template nobody starts from does not standardise the work. The crew will keep inventing the job on the phone. --- 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).