Custody and returns

Know who has equipment and what is late back.

KitNDocs gives the team a simple custody record for each handover: who took the equipment, when it went out, and whether it is due back on a day or out until somebody returns it.

Equipment

Training harness 03

Custody: The shop
Not returned. It was due back on 16 Aug, 3 days ago.

Custody

The shop

Held since 12 Aug · due back 16 Aug
3 days overdue
Take back custodyPass custody

A normal handover

Give, pass and take back custody without losing the history.

The latest entry says who has the equipment now. Earlier entries stay on the record, so a return question does not depend on memory.

  1. Given toMara Evans12 Aug · due back 16 Aug
  2. Passed toNorth Loft Rigging16 Aug · no day set
  3. Taken backNobody holds it19 Aug · recorded by Alex

Due back

See late returns as soon as they are overdue.

When equipment goes out, the operator can set a due-back day or leave it open. If the day passes, KitNDocs shows that it is late.

Due on a day

The equipment list and record show when the equipment should be back and how late it is.

No day set

A piece at a rigging shop can stay out without a made-up return date.

Contacts are named parties

A contact can be a person, a shop or another organisation. They need no login and no email address.

Where the team sees it

Late returns show up without becoming an airworthiness warning.

The equipment record has its own late-return line. The dashboard groups late returns under Not back, below airworthiness work. The equipment list shows who has each piece and whether the due-back day has passed.

3 are out. 1 has not come back.

Passenger harness 07

Mara Evans
due back today

Reserve G-14

North Loft Rigging
no day set

Training harness 03

The shop
3 days late

Where it stops

Custody and service state stay separate.

A late return is separate from service state. Tasks, issues, defects, certificates and the current record still decide whether the equipment needs attention before use.

  • Confirm the equipment's current location separately.
  • Contact the holder and collect signatures outside KitNDocs.
  • Manage reservations and charges separately.
  • Record return condition separately.
  • Read return status and service state separately.