Describe your school devices and return process. Makeform creates a student device check in form that matches each learner to an asset, records condition and accessories, and routes issues for follow-up.
Send device return records to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it to your inventory process, or send it to the Makeform builder.
Audience
School IT staff receiving one-to-one laptops
Format
Staff-assisted form with condition checklist
Prompt size
229 chars
Example form structure
Staff-assisted form with condition checklist
Student, grade, and homeroom
Laptop asset tag and serial number
Device condition by component
Which accessories were returned?
Damage photos and staff notes
Suggested routing tags
Complete returns
Missing accessories
Damage review
Ask staff to read the asset tag on the physical device because roster assignments may not reflect swaps.
Step 1
Identify
match student, asset tag, and serial number
Step 2
Inspect
test functions and record physical condition
Step 3
Account
check charger, case, stylus, and other accessories
Step 4
Route
close complete returns or send issues for follow-up
Why structured check-in matters
A returned laptop may have the wrong charger, a cracked hinge, or no receiver record. A structured form gives IT consistent evidence.
Record physical asset and serial numbers alongside the student so swaps surface during check-in.
Use the same power, screen, input, battery, and casing checks at every desk.
Show detail questions only for damage or missing accessories to create a focused issue queue.
Built for school return days
Choose a return event, then edit its devices, conditions, accessories, and routing rules.
Close each Chromebook, laptop, or tablet assignment after verifying the asset and accessories.
Record room, teacher, cart, and slot for each returned tablet.
Use a compact midyear return flow that expands when IT follow-up is needed.
Route findings to cleaning, reimage, parts, vendor repair, or retirement.
Device return workflow
Use your inventory labels and inspection standard so each submission can hand issues to IT.
Name your device types, identifiers, checks, accessories, and staff roles.
Use your models and asset-label language, require identifiers, and add concise staff instructions.
Show photos, details, priority, and owner fields for damaged or incomplete returns.
Notify IT about exceptions and send structured records to a shared sheet.
Form vs roster vs paper checklist
A generated form connects student, asset, inspection, accessories, evidence, and next action in one record.
Field guide
These six sections verify the return, document its state, and create a next step.
Student context
Use familiar school identifiers to find the assignment record, and name the receiver so later questions have an owner.
Asset identity
Roster assignments become stale after swaps. Physical identifiers let inventory staff reconcile the device on the table.
Functional test
Use pass, issue, or not tested for essential functions. Flag deeper diagnosis without turning intake into repair work.
Physical condition
Separate ordinary wear from cracks, missing keys, bent ports, loose hinges, and casing damage. Record locations and notes.
Accessories
Change accessory lists by device type. Mark each adapter, case, cable, cover, or stylus as returned, missing, damaged, or not assigned.
Evidence and routing
For failures or missing items, collect photos, details, priority, storage location, and owner before equipment leaves intake.
Related tools
Connect check-in with checkout, inventory, inspection, repair, and student technology planning using other Makeform generators.
Record who receives each device and the expected return details at the start of the assignment.
Open toolMaintain structured asset identity, location, status, and ownership details across school inventory.
Open toolBuild a deeper inspection checklist for equipment that needs more than a quick intake test.
Open toolCollect detailed fault reports and route repair work after an issue is found at check-in.
Open toolReconcile physical counts and recorded inventory after devices have been returned and sorted.
Open toolAsk families and learners about access needs before the next device assignment cycle begins.
Open toolFAQ
Answers for school IT teams planning device returns.
It records a student's returned laptop, Chromebook, tablet, hotspot, or related equipment. The submission connects the learner to the asset, condition, accessories, receiving staff member, and follow-up status.
Collect student ID plus the asset tag and serial number printed on the equipment. Device type, model, school, cart, or storage slot may also help. Read the physical label because rosters may miss a swap.
Separate power and function checks from physical condition and overall status. Pair choices such as good, ordinary wear, damaged, and not tested with the affected location, notes, and optional photos. Leave deeper diagnostics to repair intake.
Yes. Mark each assigned accessory as returned, missing, damaged, or not assigned. Conditional logic can show laptop accessories for laptops and tablet accessories for tablets.
Yes. Damage, a failed function, or a missing item can reveal detail, photo, repair category, priority, owner, and storage fields. Notifications or a connected sheet can create a filtered technician queue.
Yes. Focus required questions on student, asset, power, visible condition, accessories, and receiver. Show photo and repair questions only for exceptions. Multiple stations can use the same published link.
Yes. Makeform is unlimited free for creating, publishing, and collecting responses with your student device check in form. The paid tier only removes the Makeform badge.
Submissions appear in the Makeform inbox and can be sent to Google Sheets, Slack, or Zapier. Consistent statuses help IT sort records and assign exceptions.
Track every return.
