Replace a run's documents
THE WHOLE LIST, replaced, the way the legs are: the list is the answer. A document that keeps its name keeps its ticks, so re-ordering does not lose what somebody has collected; one that is no longer on the list takes its ticks with it, because nobody is missing a document the run does not need. Needs write on Animals.
Authorizations
Response
The run.
Who is driving the run (Phase 436). On a run with legs this is whoever is in charge of the whole journey; each leg has its own driver. Empty text or null clears it. An address is only rewritten when its key is sent, so a patch about a date never clears one somebody verified.
Who to ring at the start (Phase 449b). An address gets a van to a car park; a name and a number get an animal out of it. Either half may be empty; both empty reads back as null. Only rewritten when the key is sent, so a patch about a date never clears a number somebody finally got hold of. An unknown field is refused rather than dropped.
Who to ring at the end (Phase 449b). An address gets a van to a car park; a name and a number get an animal out of it. Either half may be empty; both empty reads back as null. Only rewritten when the key is sent, so a patch about a date never clears a number somebody finally got hold of. An unknown field is refused rather than dropped.
Whether somebody decided this run goes (Phase 449d). Nothing here checks the weather - we do not know it - so this records that a person looked and what they said. Setting it stamps who and when; re-sending the same decision does not re-stamp it, and clearing it clears the stamp.
go, hold, null 
