Equipment Checkout Form — shared by the community

Who this template is for

Equipment Checkout Form is built for carriers, couriers and operations teams who need to record consignment detail and proof at each handover.

• Carriers, couriers and operations teams working in logistics & field ops.
• Teams who need to record consignment detail and proof at each handover without writing code or paying for a custom build.
• Anyone replacing disputes with no record of what was collected or delivered with one structured record per enquiry.
• Respondents are shippers, drivers and warehouse staff — the form asks them 15 questions across 2 screens.
• Mobile-heavy audiences, thanks to the one-question-per-screen card layout.

Why this form is useful

It removes the cost of disputes with no record of what was collected or delivered and turns each submission into a record your team can act on immediately.

• 8 questions are required, so submissions arrive complete instead of needing a follow-up email.
• It records a signature you can keep as proof of agreement.
• It pins the request to a specific date.
• Conditional logic hides 3 questions until they are relevant — shorter forms convert better than long ones.
• Splitting the form across 2 pages keeps each screen short and shows respondents how much is left.
• Every response is stored, searchable and exportable, so nothing depends on one person's inbox.

How to use this template

From copy to live form is a few minutes of work, and every step is reversible.

1. 1Press “Use this template” — a fresh copy of Equipment Checkout Form lands in your workspace, ready to edit.
2. 2Rename or delete any question, and change what is required. Nothing here is fixed.
3. 3Open Notifications and add the email addresses that should be alerted on each submission; add an auto-reply to the respondent if the form collects an email address.
4. 4Publish it, then either share the link directly or paste the embed snippet into your site — the embedded form resizes to fit and loads no marketing or advertising trackers.
5. 5Watch responses land in Submissions, where you can filter, label and export them to CSV or PDF.

Logic and conditions blueprint

Exactly how this form behaves as it is answered — 3 conditional rules ship with it.

• Features conditional validation: if “Condition at checkout” is Damaged or worn (noted below), “Describe existing damage or wear” becomes mandatory before the form can be sent.
• Features conditional validation: if “Has the item been returned?” is Yes, “Condition at return” becomes mandatory before the form can be sent.
• Features conditional validation: if “Condition at return” is Damaged — new issue found, “Describe the new damage” becomes mandatory before the form can be sent.
• All 3 rules are editable in the Logic tab, and the built-in checker warns about rules that contradict each other.