Shift Pattern
A shift pattern is a reusable Salesforce record that defines a repeating sequence of shifts, so schedulers can generate many shifts at once instead of building each one by hand.
Definition
A shift pattern is a reusable Salesforce record that defines a repeating sequence of shifts, so schedulers can generate many shifts at once instead of building each one by hand. The pattern is measured in days, and it points to shift templates that supply the actual start time, end time, and other details for each day in the cycle.
Shift patterns are part of the shift scheduling tools shared by Field Service and Workforce Engagement. A scheduler defines a pattern once, like three morning shifts and two evening shifts across a week, then applies it to a worker or to open demand and repeats it as many cycles as needed.
How shift patterns turn a repeating schedule into one configuration
What a shift pattern is and where it lives
A shift pattern is a configuration of shifts that repeats over a fixed window of days. Salesforce stores it as a ShiftPattern record, and you reach the list view through the App Launcher by entering Shift Patterns. The record carries a name, a description, a pattern length in days, and a flag for whether it is active. Length is always counted in days, so a weekly pattern has a length of 7 and a monthly pattern usually runs 28 to 31. The pattern itself does not hold start and end times. Those come from shift templates that the pattern references. This separation keeps the design clean. You build the time-of-day details once as templates, then arrange them into a repeating shape as a pattern. Shift patterns belong to the shift scheduling tools that Field Service and Workforce Engagement share, alongside shifts, shift templates, service resources, and service territories. Because the pattern is a record, it can be cloned, edited, deactivated, and reported on like any other object, which is what lets a contact center or field operation keep a tidy library of repeatable schedules.
Shift pattern entries: the days inside the cycle
The repeating shape comes from shift pattern entries. Each entry is a child record that links the pattern to a shift template and places that template on a specific day position inside the cycle. For a weekly pattern, the day position runs from 1 to 7, matching the days of the week. An entry says, in effect, on day 3 use this template. A single day can hold more than one entry, so you can stack a morning template and an evening template on the same date when the schedule needs two shifts that day. Any day with no entry becomes a day off, which is how a 5-on, 2-off rhythm is expressed: five days carry entries and two days are left empty. The template referenced by each entry decides the start time, end time, time slot type, and the other shift fields, while the entry decides where in the cycle that shift falls. Plan the entries before you apply the pattern. The arrangement of entries across the cycle is the part that defines the worker experience, so getting day positions right matters more than any single field on the parent pattern.
Resource-based versus need-based patterns
A pattern can be applied in two ways, and the difference is whether a worker is named up front. A resource-based pattern is tied to a specific service resource, meaning the generated shifts already belong to that person. Use this when a named agent or technician works the same rhythm every cycle. A need-based pattern leaves the assigned service resource blank, so the generated shifts are open and unassigned. This fits demand planning, where you know the work that must be covered but not yet who covers it. A common example is a restaurant that needs three cooks and four waiters every weekend evening for six months. You set up a monthly pattern of unassigned shifts and repeat it six times, then fill the open shifts later. The same idea applies to a contact center that knows it needs ten agents on the phones each weekday morning. Need-based patterns pair well with later assignment, where supervisors or automation slot workers into the open shifts. Choosing the right mode at apply time keeps the schedule honest about what is committed and what is still open.
Generating shifts: New from Pattern
Applying a pattern is how shifts actually get created. From the Shifts list view, choose New from Pattern, pick the pattern you want, and set a start date. Then you tell Salesforce how far to go, either by entering an end date or by entering the number of repetitions. Each repetition runs the full cycle again, so a weekly pattern repeated four times produces four weeks of shifts in one action. If the pattern is resource-based, every generated shift carries that service resource. If it is need-based, the shifts come out unassigned. This is the payoff of the whole model. The repetitive work of stamping out dozens or hundreds of shifts collapses into a single dialog. Behind the scenes Salesforce also exposes this through the platform, so the same generation can be triggered programmatically when shifts need to be produced as part of a larger flow. Pick the date range carefully, because a long horizon with a short cycle can create a large number of shift records quickly. Many teams generate a few cycles ahead, review them, then extend the horizon once the pattern proves correct.
A worked example: a 5-on, 2-off agent week
Picture a support center that runs morning coverage. First you build a shift template named Morning Phones with a start time of 8:00 AM and an end time of 4:00 PM, plus the right time slot type and territory. Next you create a shift pattern named Standard Weekday Mornings, set the length to 7 days, and mark it active. Then you add shift pattern entries for day positions 1 through 5, each pointing at the Morning Phones template, and you leave day positions 6 and 7 empty so the weekend reads as days off. With the pattern built, you go to the Shifts list view, choose New from Pattern, select Standard Weekday Mornings, pick the resource Priya Rao, set the start date to the first Monday, and enter four repetitions. Salesforce generates four weeks of weekday morning shifts already assigned to Priya. To staff a second agent on the same rhythm, you apply the same pattern again with a different resource, or leave the resource blank to create open shifts that another worker fills later. The pattern stays in your library, ready to reuse next month.
Why scheduling teams lean on patterns
Patterns matter because contact center and field schedules are mostly repetition. The same rhythms come back week after week, and building each shift by hand wastes supervisor time and invites mistakes. A pattern turns that repetition into reusable configuration. Define the rhythm once, apply it to many people or to open demand, and regenerate it whenever the calendar rolls forward. Mature operations keep a library of patterns for different roles and scenarios, so a new schedule is a matter of picking the right template and applying it. Consistency is the second payoff. When everyone on a team draws from the same pattern, start and end times line up, coverage gaps are easier to spot, and the schedule is easier to audit. Patterns also play nicely with the rest of shift scheduling. They feed shifts, which connect to service resources and service territories, which in turn drive availability and assignment. That makes the pattern a planning lever rather than just a convenience. Get the patterns right, and the downstream scheduling, assignment, and coverage analysis all start from a clean, repeatable base.
How to create and apply a shift pattern
You create a shift pattern as a record, then add shift pattern entries that map templates to day positions. Build your shift templates first, since the pattern references them. Then apply the finished pattern from the Shifts list view to generate shifts.
- Open Shift Patterns
From the App Launcher, enter Shift Patterns and open the list view. Click New to start a pattern.
- Set the pattern details
Give the pattern a clear name and description, set the length in days (7 for a weekly cycle), and mark it active so it can be applied.
- Add shift pattern entries
For each working day, add an entry that links the pattern to a shift template and sets the day position (1 to 7 for a week). Leave a day with no entry to make it a day off, and add two entries to one day for a double shift.
- Apply the pattern to create shifts
Go to the Shifts list view and choose New from Pattern. Select the pattern, set a start date, choose a service resource or leave it blank for open shifts, then enter an end date or number of repetitions.
A descriptive label for the pattern, like Standard Weekday Mornings, so schedulers can find and reuse it.
The number of days in one cycle. A weekly pattern is 7; a monthly pattern is roughly 28 to 31.
Marks the pattern as usable. An inactive pattern cannot be applied to generate shifts.
The template each shift pattern entry references, which supplies the start time, end time, and time slot type for that day.
Where in the cycle the entry falls, from 1 to 7 for a weekly pattern, placing the template on a specific day.
- Build shift templates before the pattern. Pattern entries cannot reference a template that does not exist yet.
- Length is always in days, not weeks. A weekly pattern is 7, so a four-week schedule is generated by repeating a 7-day pattern four times, not by setting length to 4.
- Leave a day empty to make it a day off. There is no separate off-day record; an absent entry is what creates the gap.
- Leaving the service resource blank at apply time creates unassigned shifts for demand planning, which still need a worker assigned later.
- A long date range over a short cycle can generate a large volume of shift records fast, so generate a few cycles, review, then extend.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Shift Pattern.
- Simplify Shift Creation with Templates and PatternsSalesforce
- About Shift Scheduling ToolsSalesforce
Hands-on resources to go deeper on Shift Pattern.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Shift Pattern?
Q2. What problem do they solve?
Q3. How should patterns be managed?
Discussion
Loading discussion…