Equipment Reservation Request Form
Free equipment reservation request form in Word and plain text. Keep borrower requests separate from staff allocation, acceptance and final confirmation.
Free Editable Template With Staff Confirmation Record
Summarize this article with AI
Summarize the manual request and staff decision while preserving acceptance, confirmation and product limits.
Download the equipment reservation request form
An equipment reservation request form records what a borrower wants and, separately, what staff agrees to provide. Submitting a request does not reserve anything.
Download the editable Word template or the complete plain-text form. Both contain the two records, status definitions, instructions and fictional examples reproduced below; no signup is required.
The Word file contains editable text and expandable tables. Copy a blank set for each request, add item rows as needed and keep the worked examples out of live records. This page does not save or submit requests.
What should the borrower request?
The borrower should name each item, quantity, requested start and end, and timezone. Include required accessories, collection location and a contact for the decision.
Keep the original request unchanged when staff offers a different quantity or window. Record the offer separately so an acknowledgement cannot be mistaken for approval.
When can staff confirm the allocation?
Staff can confirm after checking actual scheduling and current equipment, recording the agreed allocation centrally and communicating the final decision. Any change to the request needs explicit requester acceptance first.
Check specific assets, open checkouts, existing commitments, accessories and preparation time. The double-booking guide explains those scheduling checks; this form records the decision, not live availability.
Here, Partially confirmed means a provisional partial offer, not permission to rely on the available portion. List exactly what is allocated and what remains unallocated. After acceptance, recheck availability before final confirmation; recording a proposed allocation is not a software lock.
How do declines, waitlists and cancellations work?
A declined or waitlisted request has no confirmed allocation. Staff records the reason and tells the requester; a waitlist also needs a review owner and time, not an implied promise.
For a change or cancellation, preserve the earlier record and identify affected items and dates. Update the central schedule, release any affected booking or separately recorded hold, and record who notified the requester and affected staff.
A cancellation does not prove that equipment has returned. Keep physical custody separate; the equipment handover form covers a permitted transfer rather than this pre-use request and decision.
Complete copyable form and fictional examples
Everything in the downloads appears below in the same sequence. Record 1 belongs to the borrower; Record 2 and its continuation belong to staff.
Equipment Reservation Request Form
- Free Editable Template With Staff Confirmation Record
- WhoHasGear | Original manual template | October 28, 2026
- Submitting this request does not reserve anything. Recording a proposed allocation is not a software lock.
- How to use: copy the blank records for each request. The borrower completes Record 1; staff completes Record 2 and keeps dated updates. Duplicate item rows as needed. Keep the examples separate from live records.
- Use full dates, times and a named timezone with UTC offset on every event. Preserve the requested window even when the approved window differs.
- Staff must check actual scheduling and current equipment before deciding. Check existing commitments, current custody, required accessories and preparation/turnaround time in the team's central reservation record.
- For any changed quantity, item or time, record explicit requester acceptance before treating the request as confirmed. Recheck availability, update the central reservation record and communicate the final confirmation. Silence is not acceptance.
- This document does not show live availability, automate reservations, sync inventory, take payments or guarantee conflict prevention. It is not an issued/returned receipt.
- This original template has not been tested by operators. The examples are fictional, not customer outcomes.
- Source guide: https://whohasgear.com/blog/equipment-reservation-request-form
| Status | Meaning and next action |
|---|---|
| Pending | Request received; no equipment promised. Staff checks and decides. |
| Partially confirmed | Provisional allocation only in this template: list exact offered items, quantities and window. Await requester acceptance of changes; do not treat as Confirmed. |
| Confirmed | Staff checked availability, recorded the agreed allocation centrally and communicated final confirmation. Record acceptance first if anything changed. |
| Declined | No allocation confirmed. Record the reason and communicate the decision; release any separately recorded hold. |
| Waitlisted | No allocation confirmed. Assign a review owner/time and communicate that availability is not promised. |
| Cancelled | Request or booking withdrawn. Record the scope, communication and any central-record release; do not erase history. |
RECORD 1 — Borrower request
- Request ID / revision: ____________________
- Borrower / team: ____________________
- Contact for the decision: ____________________
- Purpose / event / location: ____________________
- Submitted by / date / time / timezone with UTC offset: ____________________
- Requested start date / time: ____________________
- Requested end date / time: ____________________
- Requested timezone with UTC offset: ____________________
- Requested collection location: ____________________
- Decision needed by (date / time / timezone): ____________________
- List every item and accessory. Item-level windows below override the overall requested window only when written explicitly.
| Requested item / specification | Quantity | Requested start–end / timezone (or same as above) | Acceptable alternatives to discuss |
|---|---|---|---|
| ________________ | ____ | ________________ | ________________ |
| ________________ | ____ | ________________ | ________________ |
| ________________ | ____ | ________________ | ________________ |
Borrower notes / flexibility: ____________________
Listing an acceptable alternative is not acceptance of a later offer. Staff must communicate the exact changed allocation and record requester acceptance.
Request acknowledgement sent by / to / channel / date / time / timezone: ____________________
Initial status: Pending. This acknowledgement is not a reservation confirmation.
RECORD 2 — Staff decision and confirmation
- Linked request ID / revision: ____________________
- Status (select one): Pending / Partially confirmed / Confirmed / Declined / Waitlisted / Cancelled
- Decision-maker / decision date / time / timezone with UTC offset: ____________________
- Scheduling and current-equipment check by / date / time / timezone: ____________________
- Central reservation record checked / reference: ____________________
- Current custody, accessory and preparation/turnaround findings: ____________________
- List each requested line, including anything not allocated. For tracked units, write every asset ID; for pooled items, write the pool reference and exact quantity.
- Allocated below means a staff proposal until the confirmation steps are complete. Writing it here does not create a hold or software lock.
| Requested line / allocated asset IDs or pool | Requested / allocated quantity | Approved start–end / timezone (proposed until confirmed) | Outcome / unallocated balance / reason |
|---|---|---|---|
| ________________ | ____ / ____ | ________________ | ________________ |
| ________________ | ____ / ____ | ________________ | ________________ |
| ________________ | ____ / ____ | ________________ | ________________ |
Approved collection location: ____________________
Changes offered / exact offer revision: ____________________
Offer communicated by / to / channel / date / time / timezone: ____________________
Requester acceptance: accepted / rejected / awaiting reply / not needed (unchanged request). Accepted items, quantities, window and offer revision: ____________________
Acceptance given by / received by / channel / date / time / timezone: ____________________
If changes are rejected or unanswered, do not mark Confirmed. Agree a revised request or record Declined, Waitlisted or Cancelled as appropriate.
Final availability recheck by / date / time / timezone / findings: ____________________
Agreed central reservation entry / revision / updated by / date / time / timezone: ____________________
Final confirmation: exact asset IDs or pool quantities / approved start–end / timezone / collection location: ____________________
Final confirmation communicated by / to / channel / date / time / timezone: ____________________
Final status / set by / date / time / timezone: ____________________
RECORD 2 continued — Other decisions, changes and cancellation
- Linked request ID / revision: ____________________
- Declined: reason / decision-maker / date / time / timezone: ____________________
- Waitlisted: reason / review owner / next review date / time / timezone: ____________________
- Decline or waitlist notice sent by / to / channel / date / time / timezone: ____________________
- Waitlisting is not a promise. If equipment later becomes available, recheck it and complete the acceptance and confirmation steps before changing the status.
- Change or cancellation requested by / received by / channel / date / time / timezone: ____________________
- Scope: whole request / specified lines only. Affected asset IDs or pool quantities / window: ____________________
- Reason / previous confirmed revision / proposed new revision: ____________________
- Staff decision on change / by / date / time / timezone: ____________________
- For a change, preserve the old allocation until staff resolves it; record which old commitments remain effective. Recheck the new allocation and repeat acceptance and final confirmation above.
- Cancellation recorded by / date / time / timezone: ____________________
- Central record release: affected entry / asset IDs or pool quantities / released window / by / date / time / timezone: ____________________
- If no allocation or separate hold existed, write 'No allocation or hold to release'. If release is outstanding, name its owner and due time: ____________________
- Temporary hold, only if separately entered in the central record: reference / scope / owner / expiry date / time / timezone: ____________________
- Release an expired or withdrawn hold deliberately in that record. This form neither creates nor removes holds automatically.
- Change/cancellation notice sent by / to requester and affected staff / channel / date / time / timezone: ____________________
- Remaining confirmed lines / final status / next action and owner: ____________________
- For a partial cancellation, retain the unaffected confirmed allocation and identify cancelled lines individually. Cancelling a booking does not establish that checked-out equipment has physically returned.
Fictional pending example
- Fictional training case only; not a customer result. All timestamps use America/New_York (UTC−04:00).
- Record 1: REQ-028-A, revision 1. Borrower Maya, workshop team; contact via the team's request inbox. Submitted October 28, 2026 at 09:10.
- Requested: two portable speakers and two speaker stands, October 30, 2026 from 13:00 to 17:00. Collection: equipment room. No substitutes specified; decision requested by October 29 at 12:00.
- Record 2: Rowan acknowledged the request to Maya through the team inbox on October 28 at 09:20. Status: Pending. No allocated asset IDs, approved window or final confirmation.
- Next action: Rowan checks the central schedule, current custody and the required stands by October 29 at 10:00. No allocation or hold to release.
- Maya has asked for equipment, but the acknowledgement does not reserve it. If the check finds no suitable equipment, Rowan records and communicates Declined or Waitlisted, with a review owner/time for Waitlisted.
Fictional partial-then-confirmed example
- Fictional training case only; not a customer result. All timestamps use America/New_York (UTC−04:00).
- Record 1: REQ-028-B, revision 1. Borrower Ellis, interview team; contact via the team's request inbox. Submitted October 28, 2026 at 10:00.
- Requested: two recorders and two headsets for October 30, 2026, 09:00–16:00; collection at the equipment desk.
- Record 2 at October 28, 10:30: Noor checked schedule REG-30, current custody and preparation needs. Only recorder REC-021 and headset HDS-007 could be offered for the requested window; the second recorder and headset were committed elsewhere.
- Status: Partially confirmed, provisional only. Offer revision 2 lists recorder REC-021: requested 2, allocated 1, unallocated 1; headset HDS-007: requested 2, allocated 1, unallocated 1. Proposed approved window: October 30, 09:00–16:00. Nothing is confirmed yet.
- Noor sent the exact one-recorder/one-headset offer to Ellis through the team inbox on October 28 at 10:35. No separate hold was entered. Noor explained that availability would be rechecked after acceptance.
- Requester acceptance: Ellis accepted revision 2 through the team inbox on October 28 at 10:50; Noor received it at 10:52. Ellis explicitly accepted one recorder and one headset for the unchanged window and dropped both unallocated items, rather than waitlisting them.
- Noor rechecked REG-30 and current equipment on October 28 at 10:55; the proposed assets remained available. Noor recorded REC-021 and HDS-007, quantity 1 each, in central entry RES-104 at 10:57 for October 30, 09:00–16:00.
- Final confirmation: Noor emailed Ellis and the equipment-desk staff on October 28 at 11:00 with REC-021 and HDS-007, quantity 1 each, the approved window and equipment-desk collection. Noor set the status to Confirmed at 11:00. The original two-of-each request and acceptance remain in the history.
- No cancellation in this example. If Ellis cancels, staff records the request, updates RES-104 to release the affected commitments, and logs who communicated the cancellation and when. The form cannot perform that release.
What evidence supports this template?
The sources support basic request and confirmation fields, not the effectiveness of this template. Oregon State asks for advance equipment requests and says requesters will be contacted if an item is unavailable.
The University of South Carolina form includes equipment quantity, day/date, from/to times and a separate confirmation field. Its printed date is August 12, 2014. We have not copied its responsibility clauses or either institution’s local deadlines.
Both primary sources were retrieved October 28, 2026. The status definitions, acceptance sequence and cancellation record are our original design, not an institutional standard.
An older r/livesound discussion describes a buyer seeking event bookings, double-booking support and event-specific job sheets. Retrieved through an archive on October 28, 2026, it supplies buyer context only—not proof of demand for this form or evidence that the template works.
Who should use this manual form?
This form suits a small team with a named staff member reviewing requests against a central schedule. It does not suit a borrower who needs an immediate, self-service reservation or live availability.
This original template has not been tested by operators. Research was limited to the cited documents and one older buyer discussion; the worked cases are fictional, not customer success stories.
WhoHasGear is QR-based equipment checkout and reservation software for small teams.
This downloadable form is separate from the software. It does not provide live availability, automated reservations, inventory sync, payments or guaranteed conflict prevention. To explore the product, create a WhoHasGear account or view plans.