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

# Paperwork, reminders and the day of the run

> The reminders before a run, the chain of custody, the run sheet, the documents a run needs, and agreements.

Open a run from the [Transports](https://docs.rescueconsole.com/animals/transports.md) list. This page is what happens around the day itself: the reminders before it, the handovers along the way, the run sheet, the documents a run needs, and the agreements that travel with it. Changing a run needs **Change** on Animals.

## Chain of custody

Who handed the animals to whom, where, and when.

It is the only thing that settles it when an animal is hurt or missing and two organizations remember the handover differently, which is why **nothing here can be edited or removed**. A mistake is a second handover saying what actually happened.

**Record a handover** asks:

| Field | What it means |
| - | - |
| **Where** | One of the stops this run makes. |
| **Handed over by**, **Received by** | Names, typed. Neither has to be somebody on your people list: the other side of a handover is usually a volunteer from the receiving rescue, a vet tech, an adopter. |
| **Which animals** | Tick the ones that changed hands. Each must be on this run. |
| **Signed by, if they signed** | Typed, the way an adopter signs a contract. |

Recorded handovers are listed oldest first with the animals each one covered.

> [!NOTE]
>
> The [run sheet](#the-run-sheet) prints **lines to sign** at every stop with nothing recorded yet, and prints what happened at the stops that have one. That is the half a phone cannot do in a car park with no signal: the paper comes back and gets typed in.

## The run sheet

**Run sheet**, beside **Status** at the top of the run, is the page a driver prints or holds on a phone. **Print** puts it on Letter, and nothing else: the header and the breadcrumb trail stay on the screen.

It is the run in the order the day happens, with nothing on it to press:

* the stops in order, each with its kind, address, who to ring, when the van arrives there and when it leaves, in that order, and who is driving the next leg. A round trip’s two ends are two stops with their own times;
* the vehicle, when it is known: the year, make, model, color and plate, so the far end knows which van to wait for;
* who gets **On** and **Off** at each stop;
* every animal riding, with its crate, where it gets on, where it gets off and its note;
* the [agreements](#agreements) signed for this run - what paperwork is traveling;
* the [documents](#paperwork) each animal needs, with **MISSING** against any that are not in hand;
* the [weather band and the decision](https://docs.rescueconsole.com/animals/transport-route.md#weather), if either was recorded;
* and at every stop, the [handover](#chain-of-custody) that happened there, or lines to sign for the one that has not.

An animal that rides the whole journey shows the first stop and the last rather than a blank: a driver reading an empty cell has to guess, and the guess is what leaves an animal in a car park.

> [!NOTE]
>
> What is deliberately NOT on the sheet is **Things to sort out**. A sheet in somebody’s hand at six in the morning is not the place to discover that leg three has no driver; that belongs on the run, while there is still time. The sheet prints what was arranged.

## Paperwork

What a journey has to carry, and which animals have it.

Moving a dog or a cat across a US state line generally needs a **certificate of veterinary inspection** and a current **rabies certificate**, and a number of states require an **import permit** obtained beforehand. The requirements are the destination state's, they differ, and they change.

> [!WARNING]
>
> RescueConsole does not know them, and does not pretend to. Nothing here has a list of states or rules in it: **you** write down what you know a journey needs, because you are the one who knows where you are going and what that state asks for. A list we maintained would be wrong somewhere within a year, and wrong in the direction that matters - you would trust it.

### Your documents

**Documents**, from the link at the top of the runs list, is your own list: a name and a note about where it comes from.

| Field | What it means |
| - | - |
| **What it is called** | What a coordinator ticks and a driver reads. No two may share a name. |
| **Where it comes from** | From the vet, within 10 days of travel. Apply to the state 30 days ahead. |
| **Offered on a run** | Untick to stop offering it while keeping it readable. |

Picking one onto a run **copies** its name, so renaming or deleting a line here never rewrites what an earlier journey recorded - the same rule as a [saved place](https://docs.rescueconsole.com/animals/transport-route.md#saved-places).

### On a run

**Paperwork**, on the run itself. **What this run needs** ticks documents from your list, or adds one this run alone needs - an import permit for one state, say.

Each animal riding then gets a box per document. They save as you tick them, because the answers arrive days apart: the vet issues a certificate on Thursday and somebody ticks it on Thursday.

Under the grid, in amber, is **what is still missing and who is missing it**. An animal nobody has said anything about is missing it: nothing is in hand until somebody says it is.

> [!NOTE]
>
> A missing document does **not** stop a run being confirmed. That is a timing fact rather than a soft line: a certificate of veterinary inspection is issued within days of travel, so a run confirmed on Tuesday for Saturday cannot have one yet. A gate that refused Tuesday would be one rescues turn off, and then it protects nobody. What the product does instead is say what is missing on the run and print it on the [run sheet](#the-run-sheet) the driver carries.

## Agreements

The paperwork that travels with the journey: the release a clinic wants before it treats an animal, the risks of a surgery, what to do before and after one. One agreement covers every animal in the van.

Write them first in [Settings, Contract templates](https://docs.rescueconsole.com/settings/contract-templates.md#a-transport-agreement), choosing **Transport** under **For**. A template can be narrowed to the kind of place a run ends at, so the surgery paperwork is offered on clinic runs and nowhere else.

On the run, **Agreements** works the way an adoption contract does:

**1. Choose the agreement**

**Sign** and choose which agreement. The ones offered for this run come first, with the reason.

**2. Show the contract**

**Show the contract** renders it with the run filled in: the date, both ends, the address at each end, the driver, and every animal riding with its ID and microchip.

**3. Sign it**

Type the name of whoever is signing, tick the consent box, and **Sign**.

The addresses come from the run, which means from the [saved place](https://docs.rescueconsole.com/animals/transport-route.md#saved-places) somebody checked once. Nobody retypes a clinic address onto an agreement.

> [!NOTE]
>
> Signing stores a permanent copy of the exact text. Editing the template afterwards does not change it, and a signature is never deleted - a mistake is **Void**ed, with a reason, and stays on the run.

A template written for adoptions cannot be signed against a run: `{{adopter_name}}` and `{{fee}}` have nothing to fill in, and the preview names the field rather than printing a gap.

## Reminders before it happens

A confirmed run reminds everybody twice on its own: **three days before**, and **the day before**. Nobody has to remember to send anything, and there is nothing to turn on.

Three days out is far enough to still fix something - find a driver, borrow a crate, move a vet appointment. The day before is the last word.

Who is told:

| Who | What they are told |
| - | - |
| The driver of the run | The journey and the date, and how many of your animals are riding |
| The driver of each leg | Their own legs, named, with the time each one leaves |
| Each rescue holding space on it | That your transport is coming, and that their animals are on it |

A volunteer who drives two legs gets one reminder listing both, not two reminders. A rescue holding space is told through its organization admins, because the space belongs to the rescue rather than to a person.

Reminders go out **once** each. The reminder is recorded as it is sent, so a run cannot be reminded about twice on the same day however many times the nightly job runs.

The run says what has gone out - **Reminders sent 3 days before: 4 people told** - above the places. Everybody a reminder reaches has it in their own bell, and the one person who does not is whoever planned the run and wants to know the van has been talked about. A reminder that reached nobody says **nobody to tell**, which happens when a confirmed run has had its driver cleared since.

> [!NOTE]
>
> Only a **confirmed** run is reminded about. A run still being planned has nothing agreed to remind anybody of, and **Things to sort out** on the run itself is where what is missing belongs. A canceled or completed run sends nothing.

The reminders arrive on the bell and in the nightly email, the same as everything else.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.