# How to link a sick request to a prior illness

**For:** Manager | Admin
**You'll need:** A **'Pending'** sick-leave request on a spell-tracking policy with a configured linking window. See {doc}`/manage-leave/leave-policies/efzg-spell-linking`.

You'll mark a new sick spell as a continuation of an earlier one rather than a fresh entitlement, when the two fall inside the policy's EFZG §3 linking window.

## Open the request

::::{tab-set}
:sync-group: platform

:::{tab-item} Web
:sync: web

1. In the header, go to **Company → Leave requests**.
2. Click the row of the **'Pending'** sick request you want to review.
:::

:::{tab-item} Mobile app
:sync: mobile

1. Tap **More → Manager → Leave requests**.
2. Tap the **'Pending'** sick request you want to review.
:::
::::

## Spot the linking alert

::::{tab-set}
:sync-group: platform

:::{tab-item} Web
:sync: web

If a prior spell for this person ended inside the policy's linking window, an alert appears above the action buttons:

> *This person had a recent illness within the linking window. You can link this request as a continuation of that spell.*

A **'Link to prior illness spell'** checkbox sits below the alert with the prior spell's date range shown for reference.

If no prior spell qualifies, no alert appears — approve normally per {doc}`approve-a-leave-request`.
:::

:::{tab-item} Mobile app
:sync: mobile

The mobile app doesn't show the linking alert or the prior spell's dates. The **'Links to previous illness'** switch is offered on the approve sheet for every sick request, whether or not a qualifying prior spell exists — so mobile can't tell you which earlier illness you'd be continuing.

If you need to see the prior spell before deciding, review the request in the web app.
:::
::::

## Link and approve

::::{tab-set}
:sync-group: platform

:::{tab-item} Web
:sync: web

1. Tick the **'Link to prior illness spell'** checkbox to mark this absence as a continuation.
2. (Optional) Add context in the **'Admin notes'** textarea — doctor's note reference, conversation with the worker.
3. Click **'Approve'**.
4. In the **'Approve leave request?'** dialog, click **'Approve request'** to confirm.

If you decide the new request is a separate illness instead, leave the box unticked and approve normally — {{ app_name }} will open a fresh spell.
:::

:::{tab-item} Mobile app
:sync: mobile

1. Tap **Approve** at the bottom of the request.
2. Turn on **'Links to previous illness'** in the sheet to mark this absence as a continuation.
3. (Optional) Add context in **'Notes (optional)'** — doctor's note reference, conversation with the worker.
4. Tap **Approve** in the sheet to submit.

If the new request is a separate illness instead, leave the switch off and approve normally — {{ app_name }} will open a fresh spell.
:::
::::

## What happens

- Status flips to **'Confirmed'**.
- A `SPELL_EXTEND` transaction is written instead of a `SPELL_OPEN` — the original spell's continued-pay clock keeps running rather than restarting.
- The calendar event spawns and reviewer stamps are written exactly as in a normal approval.

## Verify it worked

The request reloads with a **'Confirmed'** badge. In the {doc}`/manage-leave/leave-transactions/view-the-leave-ledger`, the new row is tagged as a spell extension and references the original spell.

## Related

- {doc}`/manage-leave/leave-policies/efzg-spell-linking`
- {doc}`/manage-leave/leave-policies/tracking-modes`
- {doc}`approve-a-leave-request`
- {doc}`/manage-leave/leave-transactions/view-the-leave-ledger`