Multi-stepOperations
Know what went out and what is due back.
Create a lightweight equipment register and checkout log with a request form, editable tables, and a view of outstanding returns.
A complete worked example
Know who has the camera before the next shoot.
A small studio shares a camera kit, microphone, and tripod. Staff need a simple record of handoffs and returns.
Fictional project and sample data. This preview does not submit, publish, or change access.
Studio team · illustrative result
Studio equipment log
The team records each handoff and checks availability before issuing an item.
- Next return
- Camera kit · October 4
- Process
- Staff confirm the physical handoff
| Item | Borrower | State |
|---|---|---|
| Camera kit A | Maya | Out · due Oct 4 |
| Microphone B | Leo | Out · due Oct 3 |
| Tripod C | — | Returned |
A shared operational record
This tracks recorded handoffs. It does not reserve inventory transactionally or prevent two people from requesting the same item; the team confirms actual availability.
What the recipient can access
The staff form and authorized equipment records.
Kept out of this handoff
Borrower contact details and private damage notes outside that audience.
How it runs
- Register the equipmentCreate an assets table with stable references and a separate checkout table.
- Record each handoffUse a form to collect the asset reference, borrower, and expected return date.
- Track returnsUpdate return status in the table and keep a saved view of outstanding checkouts next to the team's instructions.
- You getAssets and checkouts in one project database, instructions beside them, and a view that makes overdue follow-up easier.
A prompt to start with
Copy this into your AI tool after connecting it to Fermium. Replace the bracketed details and let it ask for the context it needs.
Create a lightweight equipment checkout database in Operations with assets and checkouts tables. Use stable text asset references in both tables. Make a checkout form with asset reference, borrower, checkout date, and due date. Add an internal return-status field and a saved view of outstanding returns. Keep an HTML instructions page beside the database. Use the Operations folder permissions and explain how staff record a return.
What this workflow needs
Asset references are ordinary fields in this version. Automatic relationships, availability locking, and conflicting-booking prevention require additional logic.
Does this automatically prevent two people reserving the same item?
No. This workflow records checkouts and supports staff review. Reservation locking needs an additional workflow or application feature.