> ## Documentation Index
> Fetch the complete documentation index at: https://help.usetapp.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Approve or reject a shift request

> Review a request to take an offered shift and check the assignment after your decision.

An Owner or Manager must approve a request before an offered shift transfers to another team member. This does not exchange two shifts automatically.

## Who can do this?

Owners and Managers can review requests for their shop. Staff can submit their own requests but cannot approve or reject them.

## Where to do it

In the web app, select your shop, open **Shifts**, then select **Claims**. The **Shift requests** panel has **Pending approvals** and **History** tabs.

## Review and decide

1. Open **Pending approvals**. Requests are ordered by the upcoming shift time. Scroll to load more if needed.
2. Read the shift date, hours, work role and the two names. Check who is offering the shift and who wants to take it.
3. Choose **Approve** to transfer that assignment to the person requesting it, or **Reject** to decline this request. The decision is submitted when you select the button; there is no separate confirmation step.
4. Wait for the result, then check **History** for the decision.
5. After approval, open the shift in the calendar and check **Assigned staff** to confirm who is now scheduled.

Approving one request also rejects other pending requests for that same offered place. Rejecting a request leaves the original person assigned and does not by itself close the offer to everyone else.

## If approval is refused

The offer must still be available and the original person must still hold the assignment. The person taking it must meet the work-role requirement and have no overlapping shift. Their availability can change between submitting the request and your decision.

Approval is also refused when the original worker has already checked in and that attendance record has not been cancelled. This includes a completed attendance record, not just someone currently checked in. Check what actually happened and contact Tapp support if attendance needs correction; do not cancel a valid record just to force a transfer.

## Platform notes

In the mobile app, open **Work** → **Pending approvals**. Swipe through the preview or select **View all** for **Shift requests**. Review both people and the shift details. Select **Approve** or **Reject**, then confirm. **Cancel** leaves the request unchanged. Wait for the result and check the assignment.

Use **Pending approvals** or **History** and scroll for more. Mobile history groups decisions by their date in the shop’s time zone, newest first; the card shows the shift date. Pull down to refresh from the beginning. For a loading error, select **Try again**. If cards repeat or look outdated, reopen the list before deciding.

A pending request is not a confirmed assignment. History lists decisions, not attendance or every withdrawn request.

A **Rejected** result can also follow the offer being taken back, the original person checking in, or another teammate’s request being approved. Check what happened before treating the status as an individual rejection by a manager.

History uses the shift details available now. Names and work roles can change or be missing; history does not preserve their original details.

## Market notes

This approval flow is available for shops in Great Britain and Germany. Read the date and hours shown on the request and compare them with the shop's calendar, especially when working across time zones or reviewing an overnight shift.

## Troubleshooting

* If a decision reports an error, reload the requests and check the assignment before retrying. Another person may already have acted on the request, or the offer may have closed.
* If a person is not identifiable or **Any role** looks unexpected, check the shift and its assigned staff before deciding. Missing details can affect the labels shown.
* If the list fails to load, reopen it. An error is not proof that there are no requests.
* If a request is missing from the displayed history, check the actual shift and ask Tapp support when the assignment remains unclear.

## Related articles

* [Request an offered shift](/en/shift-management/request-an-offered-shift)
* [Create and staff a shift](/en/shift-management/create-and-staff-a-shift)