Describe your devices and required details. Makeform creates an editable device registration form for owners, serial numbers, purchase records, and follow-up.
Send device records to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor it, or send it to the builder. Edit every example before publishing.
Audience
IT admins registering employee laptops and phones
Format
Internal form with ownership and asset fields
Prompt size
253 chars
Example form structure
Internal form with ownership and asset fields
Employee, department, and manager
Device type, manufacturer, and model
Serial number and asset tag
Assigned date and work location
Is this replacing another device?
Suggested routing tags
New registrations
Needs review
Support follow-up
Ask where the serial number is printed and show an example format; this reduces confusion between a serial number, model number, and asset tag.
Step 1
Identify
owner, model, serial number, and asset tag
Step 2
Verify
purchase or assignment details checked
Step 3
Route
record sent to the right team or system
Step 4
Support
device history available when help is needed
Why registration matters
Connect each identifier to an owner, purchase, assignment, or installation so teams can find the right device quickly.
Separate model, serial-number, and asset-tag fields create consistent, searchable records.
Show receipt, assignment, or commissioning fields only when they apply.
Send submissions to an inbox, sheet, or workflow for prompt follow-up.
Registration scenarios
Choose a scenario, then edit its labels, choices, instructions, and routing.
Connect employees to laptops, phones, or peripherals with identifiers and assignment details.
Capture purchase details and optional receipts while separating marketing choices.
Record the student, device, charger, accessories, and initial condition.
Link an installer and site to a unit, firmware, test result, and photos.
Build the workflow
Provide your identifiers, ownership details, and handoff rules, then test with a real label.
Name the products, registrants, label identifiers, and registration purpose.
Use dropdowns, require the serial number, explain its location, and separate optional choices.
Show replacement, troubleshooting, and receipt questions only when relevant.
Test a real label and confirmation, then share the form and notify its owner.
Choose a collection method
Preserve exact identifiers with enough context to recognize each device later.
Field guide
Start with these six sections, keep needed details, and explain unfamiliar identifiers.
Registrant and owner
The submitter and everyday owner may differ. Capture both when it affects support or follow-up.
Device identity
Models describe a product family, serial numbers one unit, and asset tags internal inventory. Separate them.
Purchase or assignment
Purchase and assignment details show when a device changed hands and who owns the record.
Technical profile
Ask only for software or connection details that change support decisions.
Condition and evidence
Condition notes and uploads distinguish initial issues from later support requests.
Consent and next steps
Explain data use, routing, and confirmation. Keep optional communications separate.
Related tools
Registration creates the first structured record. Connect it to checkout, transfer, inventory, maintenance, repair, and warranty intake as the device moves through use.
Record who receives an asset, which accessories leave with it, and when it is expected back.
Open toolDocument a device moving between people, departments, offices, or responsible teams.
Open toolCollect updates that keep internal asset ownership, status, and location records current.
Open toolCapture maintenance needs, device identifiers, symptoms, priority, and service follow-up.
Open toolGive owners a structured way to report faults and attach photos or supporting details.
Open toolCollect purchase and issue details when a registered product needs warranty review.
Open toolFAQ
Practical answers for IT admins, manufacturers, schools, dealers, and operations teams setting up device intake.
A device registration form connects a unit's model and serial number to an owner, purchaser, employee, student, site, or installer. The record can start inventory, onboarding, support, or follow-up workflows.
Start with owner details, device type, brand, model, serial number, and purchase, assignment, or installation date. Add asset tags, orders, locations, software, accessories, or uploads only when useful. Examples help prevent swapped identifiers.
Use a required short-answer field, explain where the serial number appears, and show an example format. Separate the model and asset tag. Allow an optional label photo if verification matters, then test several device models.
Yes. Begin with device type, then show identifiers and questions for laptops, phones, appliances, controllers, or peripherals. Keep shared owner and purchase fields visible while hiding irrelevant technical questions.
Yes. Add uploads for receipts, serial-number labels, condition photos, or installation images. Explain which files help and require them only when review depends on them. Keep searchable text fields beside attachments.
Yes. Makeform supports unlimited free forms and responses, so you can generate, edit, publish, and collect registrations without a response cap. The paid tier removes the Makeform badge. Test sample records before sharing.
Responses appear in your Makeform inbox and can route to Google Sheets, Slack, or Zapier. Include identifiers in notifications, assign exceptions, and test the destination with a sample submission.
Confirm the submitted model and serial number so errors are visible. Tag the response by device type or status, notify the right team, and define how missing or duplicate identifiers are handled.
Turn device labels into usable records.
