> For the complete documentation index, see [llms.txt](https://docs.shortcutco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shortcutco.com/readme/dispatch/crew-ownership.md).
# Crew ownership (recurring jobs)
If you run more than one crew, every recurring job can have an **owner crew**. New visits are assigned to the owner automatically — no more re-assigning the same customers in Dispatch week after week.
{% hint style="info" %}
Only companies with two or more crews see crew ownership. If you run one crew, everything is already assigned to it.
{% endhint %}
## Setting the owner
* **When you first schedule** a recurring job, the scheduling window asks which crew should own it. Pick one (or leave it unowned — you can decide later).
* **From Dispatch**, drag a visit to a different crew and Shortcut asks whether this is a one-time thing or the new normal — choose to make that crew the owner to move the whole series.
* A visit's detail panel also offers **This visit only** vs **This and future visits** when changing the crew.
## One-off exceptions
Moving a single visit to another crew doesn't change the owner. The visit shows a small marker in Dispatch so you can see it's off its usual crew, and next cycle's visit goes back to the owner as normal.
## Finding jobs without an owner
On the [Jobs](https://shortcutco.com/jobs) page, the **Crew filter** has a **No owner** option — your to-do list of recurring jobs that still need a home. Imported jobs start unowned.
The No owner filter on Jobs — recurring work that hasn't been given a home crew yet.
## Deleting a team
If you delete a team that owns jobs, Shortcut asks **which crew should take over** before the deletion goes through. Nothing ends up unassigned by accident, and completed history stays exactly as it was.
Still stuck?
Email **** with the customer name and which crew should own the job.