Skip forward into hiring notes
RosterAcorn

Shift swap approval: 5 steps for staffing placements

Approve shift swaps by setting request rules and notifications, reviewing pending requests, checking shift balance, then approving or declining from the shift and saving.

Key takeaways

  • Set approval rules separately for each request type.
  • Turn on notifications and arrange cover when you are away.
  • Check pending requests against the shift and the client's requirements.
  • Save each decision, record a reason, and tell the worker the outcome.

Placed workers sometimes ask to trade a shift with a colleague, or to take over a shift that another worker can no longer work. Those requests land with the staffing coordinator, and somebody has to decide what happens next. When that decision is slow, unclear, or made in a text thread that nobody else can see, the schedule can drift away from what the client expects. It also becomes hard to explain later why a particular person ended up on a particular shift.

This post is for the coordinator who handles those requests at a small staffing firm, who may be doing other work at the same time. It gives you 5 steps for handling them. The steps assume you have a scheduling tool and a handful of placements to manage, and they are meant to be simple enough to follow on a busy day. They are general practice, not a rule set by any agency, and they do not replace the terms in your client contracts or your worker agreements. Where the post mentions a specific product, the detail comes from that product's help center and describes that product only.

Two of the steps are setup work you do once. The other three are things you do each time a request arrives.

Illustrative example: review a proposed swap

In this illustrative example, a shift has 10 workers. Imagine a placed worker asks to swap a Saturday shift with a colleague who has less experience at the site. Without a review step, the swap might go through in a text thread, and the shift could end up with a different mix of people than the client expects. With the steps below, the request waits as pending, you check the balance, and you decide from the shift itself, with a note on file.

Step 1: Set approval separately for each request type

Request types do not all need the same level of review. Connecteam's help article on admin approval for shift replacements says that you can require approval for each request type separately, enabling it for one type without the other. Connecteam calls these requests shift replacements, which is its term for them.

Start by listing your request types on paper or in a shared document. For a staffing firm, a request to swap shifts between two placed workers is one kind of request. An offer to take a shift that another worker has given up is a second kind. A worker might also ask to change a start time, which is not a swap at all. Put each kind on its own line and note who is allowed to approve it.

Then decide, type by type, whether the request needs your sign-off before it changes the schedule. A firm with a tight client agreement may want to approve every change. A firm with simple, low-risk shifts may choose a lighter review for some kinds of request.

Write the rule for each type in plain words. For example: "Swaps between two placed workers need coordinator approval before the schedule changes. Taking an open shift needs approval only if the worker has not been placed at this site before." These sentences are examples, so adjust the wording to fit your firm. For related planning, see shift swap approval criteria.

If your scheduling tool lets you turn approval on for one type and off for another, set it to match your written list. If the tool does not offer that control, keep the list next to the schedule and check it before each decision. Review the list again when you add a new client or a new kind of placement, because the types you need to review may change with the work.

Step 2: Turn on notifications so you hear about each request

To receive each request notification in Connecteam, enable shift replacement notifications in the Schedule settings, on the Notifications tab, as its help article explains.

Decide where notifications should go, whether that is your email, a shared inbox, or a phone, and make sure the person covering for you can see them too. A coordinator who is out for a day should not return to a pile of requests that nobody has looked at.

A worker who is waiting for an answer and hears nothing may follow up, and a follow-up can be harder to handle than the original request, especially when the shift is close. Quick notifications give you time to look at a request carefully before the shift arrives, instead of making a rushed call at the last minute.

Test the setup once before you rely on it. If your tool offers a test shift or a test account, send a request through it and confirm that the notification arrives where you expect. Write the setting down in your procedures so that a new coordinator can find it without asking around.

If your tool cannot send notifications for these requests, set a fixed time to check the request list instead. Write that time into your handover notes, so that whoever covers for you knows to check it too.

Step 3: Review pending requests before they take effect

In Connecteam, requests that require approval appear in the Job Scheduler as pending approval; only approved requests take effect, according to its help article.

Open the pending list at a set time each day, or at each handover, whichever fits your firm, and work through it. Some requests will be quick to decide. Others will need a question back to the worker first. Keep the list clear enough that you can see at a glance which requests still need you.

When you open a request, read it in full. Note who is asking, which shift it refers to, the date and time, and who would take the shift. Check whether the requester is still placed at that site and whether the shift is still open. A request can look routine and still refer to a shift that has already changed, so look at the shift itself and not only at the names.

Keep a simple record for each request as you go. Write down the date you reviewed it, what you decided, and any question you sent back to the worker. A short line in a shared sheet or a folder is enough. The record is what lets someone else pick up the request if you are away, and it is what you will want when a worker asks why a request was handled a certain way.

Ask any follow-up question in writing, keep the reply with the request, and leave the request pending until the answer comes in. A verbal answer is hard to check later, and a written one gives you a record for your own file.

Do not approve a request just to clear the list. A pending request that waits a little longer is better than an approved request you have not checked.

Step 4: Check that the swap keeps the shift balanced

Check that the swap keeps the shift balanced before you agree to it. Connecteam's example is declining a swap if the replacement has less experience, potentially changing the shift's overall dynamic.

Balance means different things on different placements. On one placement it might mean the experience level on the shift. On another it might mean the skills the client asked for, or the number of people who already know the site. Write down which of these matter for each placement, so the check is the same every time and not a guess made under pressure.

Ask three questions before you agree. Who is being replaced, and what do they bring to the shift? Who is taking the shift, and do they match what the client asked for? Would the shift still make sense to the client with this mix of people on it? Keep the questions short and the answers in your notes, so you can repeat the check without starting from scratch.

If the replacement does not meet the shift's requirements, decline the request or ask the worker for another option. A decline is about the balance of the shift, not a judgment of the worker. Tell the worker which part of the shift needs a different match, so they know what kind of option you are looking for. A clear reason makes it easier for them to come back with a better request.

If the replacement meets the requirements, continue to the decision step. A short line such as "approved, experience and site knowledge match the client's request" is enough.

If the client has named specific requirements for a shift, write them next to the placement in your notes. Then check each request against those written requirements, not against your memory of what the client said on a phone call. When the requirements and the request disagree, the request goes back to the worker with a clear explanation, and it stays pending until a better match comes in.

Step 5: Approve or decline from the shift, then save

In Connecteam, click the pending request symbol under the shift, then approve or decline and save, as shown in its help article.

Before you click approve, compare the request with the shift details once more. Confirm the date, the time, and the names. Requests can be sent for the wrong shift, and a quick check here is faster than correcting a schedule after the shift has started.

After you decide, add a short reason in your own records. "Declined, replacement has less experience at this site than the person being replaced" is more useful than "declined." Your reason should be clear enough that a colleague can understand the decision later, even if they were not part of it. For another decision-recording process, see hiring decision debrief notes.

Then tell the worker the outcome in a short message. Say whether the request was approved or declined, which shift it refers to, and what they should do next. For example: "Your swap for Saturday's shift is approved. Please check the schedule again before the shift starts."

Keep the message in the same channel you used for the request, so the history stays in one place. If someone later asks what happened, you can point to the request, your note, and the message without searching three different inboxes.

A worker may ask again after a decline, sometimes with a new request for a different shift. Treat that as a new request. Run steps 3, 4, and 5 only, and do not assume the earlier decision still fits. The balance of the shift may be different now, and your notes will show you what changed.

Keep the process current

If a setting does not work the way these steps describe, say so and handle the affected requests by hand until you have checked it. A one-time check is quicker than fixing a schedule that went wrong. Write down what you found, so the next coordinator does not have to rediscover it.

Small firms have less room for mistakes in a schedule, so keep the steps short and repeatable. Review your written rules regularly, and update them when your tool, your clients, or your placements change. The goal is a process that a careful person can follow every time, and that leaves a clear record of why each shift looks the way it does.

Your next step today

List your request types and who can approve each one, then compare that list with your scheduling settings.

Questions about shift swap approval

Which steps are setup work?

Steps 1 and 2 are setup work: choose approval settings and arrange notifications before handling requests.

Does a pending request change the schedule in Connecteam?

No, when a request type requires approval, only approved requests take effect.

What should a decision note include?

Include the review date, the decision, and a specific reason that a colleague can understand later.

Sources