Item-level accuracy for equipment checkout and returns
A public land-grant university manages equipment loans in Airtable: off-premise requests come in through a form with Slack-based approvals, each checkout becomes its own item-level record, and a prefilled return form link goes out by email to the borrower. Return dates update automatically, and rollups close out the parent request once every item is back.
The problem
Equipment loans were tracked at the request level rather than the item level, which made it hard to tell exactly which item was still out when a borrower had checked out several at once. Approvals for off-premise use happened outside any system of record.
Check-ins were slow because return staff had to match physical items back to whatever paperwork or notes existed for that loan, with no consistent way to confirm every item in a batch had actually come back.
What they built
Operations built a request form for off-premise equipment use that routes through Slack for approval before anything leaves the building. Once approved, the system creates a separate checkout record for every individual item rather than one record per request.
Each checkout automatically generates a prefilled return form link, emailed directly to the borrower, so returning an item takes one click instead of a search for the right paperwork. Return dates update per item, and a rollup closes the parent record automatically once every linked item shows as returned.
The outcome
Staff can now see exactly which items are still checked out at any moment instead of working from batch-level guesses. Check-ins are faster because the return link takes the borrower straight to the right record.
The combination of Slack approvals, per-item records, and automatic rollup closure removed most of the manual tracking that used to fall on operations and IT staff handling equipment loans.
Inside the solution
Equipment Checkout and Return Tracking
IT Operations & Governance
- Off-premise request form with Slack approvals
- Per-item checkout record creation
- Prefilled return form generation and email
- Automated return date tracking and record closure
- Manual equipment tracking
- Difficulty identifying specific items to return
- Slow check-in process
- Item-level tracking accuracy
- Faster check-ins
- Reduced manual tracking
- User-friendly return links
- Operations
- IT
- Events
- Slack
- Batch Update extension
Equipment checkout and return tracking
Track department equipment loans at the item level: every asset tag has its own checkout record with a borrower, due date, condition, and a prefilled one-click return link, while parent requests roll up how many items are still out. Automations open per-item checkouts when a request clears chat-based approval, close the parent request the moment its last item is back, and email a weekly overdue digest, with AI fields drafting approval briefs, return reminders, and damage write-ups.
From batch-level guesses to item-level accuracy
Copy the templates
Build the approval and intake form
Automate the return links and rollups
FAQ
Frequently asked questions
A single request can include several items, and item-level records mean staff can see exactly which specific item is still out rather than guessing from a batch-level status on the whole request.
Off-premise requests post to Slack for approval before any checkout record is created, so nothing leaves the building without a documented sign-off.
Each checkout automatically generates a prefilled return form link and emails it to the borrower, so returning an item is a single click to the correct record instead of searching for paperwork.
A rollup field checks the return status of every linked item record. Once all of them show as returned, the parent request closes automatically without anyone updating it by hand.
No. The workflow runs on forms, Slack approvals, and rollup automation. The item-level records this creates would be a solid foundation for AI-assisted demand forecasting if that were added later.