Employee and departure
Identify the handoff.
Connect the return to the correct person and departure before listing property.
- Employee ID, department, manager, and worksite.
- Last day, return date, and onsite or remote method.
Describe your issued property and departure process. Makeform creates a return of property form that records each item, its condition, exceptions, and the receiving team.
Route property-return records to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it, or send it to the builder. The fields shown are planning examples.
Audience
HR coordinators closing a departing employee's file
Format
Exit checklist with item-by-item return status
Prompt size
367 chars
Example form structure
Exit checklist with item-by-item return status
Employee, department, manager, and last day
Which assigned items are being returned?
Asset tag and condition for each item
Are any items missing or damaged?
Employee and receiver acknowledgment
Suggested routing tags
Complete
Missing item
Follow-up needed
Ask for each item's asset tag and condition so the record shows exactly what remains outstanding.
Step 1
Reconcile
compare the employee record with assigned property
Step 2
Receive
record each item, identifier, date, and receiver
Step 3
Inspect
note condition, accessories, and visible damage
Step 4
Close
route exceptions and mark the handoff complete
Why use a return form
One structured record connects HR completion, facilities access, and IT device checks.
Record asset tags and quantities against the assigned-property list.
Capture working status, accessories, damage notes, and photos.
Reveal exception questions and name the responsible follow-up team.
One process, several handoffs
Keep shared core fields, then add each team's property and receipt steps.
Connect employee, manager, last day, and completion status.
Record asset tags, accessories, and the technician's inspection.
Account for badges, keys, passes, and lost-access escalation.
Add tracking, package evidence, delivery, and unpacking checks.
Property-return workflow
Turn the equipment list into a clear employee and receiver workflow.
Name the items and identifiers your organization tracks.
Set asset tags, condition choices, quantities, evidence, and follow-up.
Send a return link or complete the form at handoff.
Notify the responsible team and keep unresolved items visible.
Form vs email vs checklist
A structured form records which item arrived, its accessories, and who owns any exception.
Field guide
Build the form around reconciliation: what was assigned, what came back, its condition, and what happens to every exception.
Employee and departure
Connect the return to the correct person and departure before listing property.
Assigned inventory
Use separate entries and identifiers so each team can reconcile its register.
Return status
Mark each item returned, shipped, pending, lost, or retained, then request exception details.
Condition and evidence
Use a consistent condition scale, notes, and photos to preserve receipt observations.
Exceptions
Capture the responsible team, due date, status, and resolution note.
Acknowledgment and receipt
End with a summary and confirmations from the employee and receiver.
Related tools
Use live Makeform tools for assignment, checkout, transfer, inspection, and employee-exit steps around the final return.
Coordinate access removal, knowledge handoff, benefits, payroll, and property tasks for a departure.
Open toolRecord who received each asset, its identifier, issue date, expected return, and condition at checkout.
Open toolMaintain structured ownership, location, status, and custodian updates throughout an asset's use.
Open toolUse consistent inspection questions and photo evidence when returned equipment needs a closer review.
Open toolDocument a device or other property moving between employees, teams, sites, or custodians.
Open toolOrganize the return alongside account closure, document handoff, exit tasks, owners, and due dates.
Open toolFAQ
Practical answers for HR, facilities, IT, and operations teams documenting an employee property return.
It records company items returned by an employee or contractor. It identifies the person and departure, then records each item's identifier, status, condition, return date, receiver, and follow-up.
Include employee and departure details; item, asset tag, quantities, status, date, method, receiver, accessories, condition, evidence, exception owner, acknowledgments, and review status. Remove fields your process does not need.
Either can. Employees confirm planned returns; receiving staff verifies identifiers and condition. For valuable equipment, give both participants a section in the same record.
Yes. Add carrier, tracking number, ship date, package count, and receipt photo. Use an internal section for delivery, contents, condition, discrepancies, and receiver.
Show conditional questions when an exception is selected. Ask for factual notes, evidence, an internal owner, due date, and resolution status, then route the record for review.
Yes. Group items by team or use repeated entries. Keep shared identifier and status fields, then show category-specific questions for device accessories or access deactivation.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and reuse the return workflow without a response cap. The paid tier removes the Makeform badge.
Submissions can reach your Makeform inbox, Google Sheets, Slack, or connected apps through Zapier. Route exceptions to the responsible HR, IT, facilities, security, or operations owner.
Close the departure with a clear property record.