Requester
Keep a route back to the reporter.
Capture name, team, email, and a reliable contact method so a technician can confirm symptoms or access.
- Name, department, and contact method.
- Backup contact and preferred access time.
Describe your equipment, sites, and repair workflow. Makeform turns the brief into an equipment repair request form that helps staff identify the asset, explain the fault, attach evidence, and route a complete request to facilities or IT.
Send repair requests to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a complete prompt, adapt it to your operation, or send it to the Makeform builder. The example structure previews the requested fields.
Audience
Staff reporting broken building equipment
Format
Repair intake with location and safety screening
Prompt size
242 chars
Example form structure
Repair intake with location and safety screening
Building, floor, and room
Equipment type and asset tag
What is wrong and when did it start?
Safety concern, impact, and photo
Suggested routing tags
New request
Safety review
Repair scheduled
Ask for an asset tag and exact location separately. A description like printer upstairs is difficult to assign and even harder to reconcile with an asset record.
Step 1
Identify
asset tag, equipment type, and exact location
Step 2
Describe
symptoms, timing, impact, and attachments
Step 3
Route
facilities or IT reviews priority and ownership
Step 4
Repair
technician follows up with a complete intake record
Better repair intake
A structured equipment repair request form gathers the identifiers and evidence missing from scattered messages.
Equipment type, asset tag, serial number, and location clarify the subject before inspection.
Ask what failed, when it began, whether it is intermittent, and what was happening.
Work impact, people affected, and safety concerns help reviewers assess urgency.
One intake, different equipment
The core request stays familiar while conditional sections collect the details that matter for each equipment group.
Reveal operating system, error message, connectivity, and loaner questions when someone selects a laptop, monitor, dock, or printer.
Collect room access, power or water involvement, shutdown status, and signs that the surrounding area needs review.
Ask for runtime readings, operating conditions, fault codes, isolation status, and the supervisor already notified.
Keep intake simple for appliances and meeting-room gear while still requiring a location, identifying detail, symptom, and photo.
Build the workflow
Start with the equipment groups your team supports, then shape the form around identification, impact, evidence, and assignment.
Name the equipment groups, locations, and people who will submit requests.
Add sites, asset categories, fault types, branches, and required fields.
Direct submissions to the responsible facilities or IT inbox.
Share the link on your intranet, help center, or an equipment QR code.
Structured request vs scattered message
The easiest reporting channel is not always the clearest handoff. Compare what arrives after the employee presses send.
Field guide
These six sections turn a vague fault report into a request that can be identified, assessed, assigned, and followed up.
Requester
Capture name, team, email, and a reliable contact method so a technician can confirm symptoms or access.
Asset identity
Structured identifiers route the work and distinguish similar units better than one description box.
Location & access
Record a precise location plus the access details the service team needs.
Fault details
Ask what the reporter observed and whether the problem is constant, intermittent, or tied to a task.
Impact & immediate state
Capture work impact, people affected, safety concerns, and whether the equipment is stopped or isolated.
Evidence & follow-up
Attachments clarify damage or fault messages. Finish with a visit time and follow-up contact.
Related tools
Build neighboring forms for inspections, maintenance records, general service intake, and equipment custody.
Collect maintenance issues that may cover rooms, utilities, fixtures, and equipment in one intake.
Open toolCreate repeatable condition checks that can surface faults before equipment fails in use.
Open toolRecord completed service, dates, technicians, parts, and notes after maintenance work.
Open toolExpand intake beyond hardware repair to access, software, device, and general IT service needs.
Open toolTrack who takes shared equipment, its condition at issue, and the expected return date.
Open toolBuild a broader repair intake for property, fixtures, products, or assets beyond internal equipment.
Open toolFAQ
Practical answers for facilities coordinators, IT teams, and operations managers building repair intake.
It lets staff report faulty equipment consistently, identifying the reporter, asset, location, fault, impact, current state, evidence, and access details.
Include contact, location, category, asset tag, model, symptoms, timing, fault code, impact, safety concern, shutdown status, troubleshooting, attachments, and access time. Use conditional fields for different equipment.
Collect stopped work, people affected, workaround availability, unavailable services, and safety concerns. Reviewers can then apply the team's priority definitions.
Yes. Branch by equipment category. IT may need operating system and error questions; facilities may need access, utility, and isolation details. Both share asset, impact, attachment, and follow-up fields.
Yes. Add uploads for an equipment overview, damage close-up, error screenshot, or short clip. Keep a text field where the reporter explains each attachment.
Yes. Makeform supports unlimited free forms and responses for generating, editing, publishing, and collecting repair requests. The paid tier removes the Makeform badge.
Use category, location, or department to route notifications and workflows. Send computers to IT, appliances to facilities, and machinery to maintenance, with a fallback owner.
Require asset identifier, location, symptoms, and contact details. A QR code beside fixed equipment can open the right form, with an asset tag prefilled when supported. Let reporters add evidence or note a changed condition on an existing issue.
Replace vague broken-equipment messages.