Use this form to report any maintenance, repair, or facility issue observed at a jobsite, office, warehouse, or shared work area. Clear and complete information helps the maintenance team respond faster and reduces the chance of repeat visits. Please answer each question as accurately as you can. If you are unsure about a detail, provide your best estimate and note the uncertainty in the description fields.
This form is intended for general reporting purposes and does not replace any emergency notification process. If there is an immediate risk to people, property, or the environment, follow your site's emergency procedures first and then submit this form.
Tell us who is submitting this request so the maintenance team can follow up with questions or status updates.
Full name of the person submitting this request
Job title or role
Department, team, or crew
Email address
Phone number (include country/area code if applicable)
What is the best way to reach you about this request?
Phone call
Text message
In person at my work area
Through my supervisor
Are you submitting this request on behalf of someone else?
Are you the person who first noticed the issue?
Accurate location details are the single biggest factor in how quickly an issue can be found and resolved. Please be as specific as possible.
Site, building, or facility name
What type of area is affected?
Office or administrative area
Jobsite or field work area
Warehouse or storage area
Workshop or maintenance bay
Restroom or washroom facility
Kitchen, break room, or cafeteria
Meeting room or training room
Corridor, stairwell, or lobby
Parking area, yard, or exterior grounds
Utility, plant, or mechanical room
Other:
Building, block, or zone identifier
Floor, level, or elevation
Room number, unit, or area name
Precise location within the area (landmarks, nearby objects, or directions)
Is the exact location difficult to describe in words?
Is this a shared or common area used by multiple teams?
Is the issue visible from a public-facing or customer-facing area?
Categorising the issue helps route your request to the right trade or specialist. Choose the closest match; the maintenance team can reclassify later if needed.
What is the primary category of the issue?
Plumbing, water supply, or drainage
Electrical, lighting, or power supply
Heating, cooling, or ventilation
Building fabric, walls, floors, ceilings, or roof
Doors, windows, locks, or access hardware
Furniture, fittings, or fixtures
Appliances, kitchen, or break-room equipment
IT, network, cabling, or audio-visual equipment
Safety equipment, signage, or protective systems
Cleaning, waste, or pest-related issue
Grounds, landscaping, fencing, or exterior surfaces
Vehicles, plant, machinery, or powered tools
Other
Are any of the following also affected? (Select all that apply)
Water or moisture
Electrical or power
Heating or cooling
Structural or building fabric
Security or access control
Fire or life-safety equipment
Network or communications
None of the above
How would you classify the nature of the work required?
Repair of existing item
Preventive or scheduled maintenance
Inspection and assessment only
Replacement of a part or component
Installation of a new item
Adjustment, calibration, or tuning
Cleaning or restoration
Not sure — needs assessment
Is this issue related to a previous repair or maintenance job?
Has this issue occurred before in the same location?
Describe what you observed in plain language. Include what you saw, heard, smelled, or felt. Avoid speculation about causes unless you have direct knowledge — describing symptoms accurately is more useful than guessing at the source.
Please describe the problem in detail
What symptoms did you notice? (sight, sound, smell, temperature, vibration, performance)
Is the issue constant or intermittent?
Constant — always present
Intermittent — comes and goes
Getting worse over time
Getting better on its own
Happens only at certain times
Not sure
When did you first notice the issue?
Date the issue was first observed
Approximate time the issue was first observed
Did the issue appear suddenly or develop gradually?
Is there an obvious visible cause (for example impact damage, spill, blocked item, disconnected part)?
Which of the following symptoms apply? (Select all that apply)
Visible leak, drip, or moisture
Crack, dent, scratch, or surface damage
Discolouration, staining, or mould
Unusual noise (buzzing, rattling, grinding, hissing)
Unusual smell (burning, musty, chemical, gas-like)
Excessive heat or cold in an unexpected place
Reduced performance or output
Complete failure or non-function
Loose, wobbly, or unstable component
None of the above
Have you already attempted any temporary fix or workaround?
Is any equipment, room, or area currently out of service because of this issue?
If the issue involves a specific item, machine, or system, the details below help the technician arrive with the right parts and tools.
Does the issue involve a specific piece of equipment, machine, or system?
Asset tag, serial number, or internal reference (if known)
Manufacturer or brand (if known)
Model or product name (if known)
Approximate age of the equipment in years (if known)
Is the equipment currently under a service agreement or warranty arrangement?
Is the equipment currently locked out, tagged out, or otherwise isolated?
Any recent service, inspection, or modification history you are aware of
Answering these questions honestly helps the team plan a safe response. Reporting a hazard does not create any obligation on your part beyond following your site's own procedures. If anything on this form raises an immediate concern, stop and use your site's emergency or escalation process first.
Do you believe the issue poses any immediate risk to people?
Has the area been cordoned off, marked, or restricted?
Are any of the following hazards present or suspected near the issue? (Select all that apply)
Water on walking surfaces
Exposed or damaged electrical conductors
Overhead work or elevated access required
Confined or restricted access space
Dust, fumes, or poor air quality
Noise levels that affect communication
Heavy or awkward lifting required
Hot surfaces or hot work nearby
Chemicals, fuels, or lubricants involved
None of the above
Has anyone been injured, made unwell, or affected by this issue?
No
Yes — minor, no first aid needed
Yes — first aid was given
Yes — professional medical attention was sought
Prefer not to say
Should the equipment or area be taken out of use until the repair is completed?
I confirm that the information I have provided about hazards and risk is accurate to the best of my knowledge
Priority is assessed using the details you provide. Please describe the real-world impact rather than choosing the highest option by default — accurate prioritisation helps everyone get the right help at the right time.
How would you describe the urgency of this request?
Critical — immediate risk to safety, security, or operations
High — significant disruption, work cannot continue normally
Medium — noticeable impact, workarounds are available
Low — minor inconvenience, no immediate impact
Planning only — for future scheduling
How is the issue affecting daily work?
No effect on work
Minor annoyance or inconvenience
Slowing down one or more tasks
A task or process cannot be completed
An entire area, team, or operation is stopped
Delivery, service, or deadline is at risk
Approximately how many people are affected by this issue
Is there a specific deadline, event, or date by which this must be resolved?
Is the issue causing any financial, material, or product loss?
Is the issue affecting the comfort of the workspace (temperature, lighting, noise, odour)?
Is any regulatory, contractual, or inspection deadline connected to this issue?
Let the maintenance team know how, when, and under what conditions they can access the area safely and efficiently.
Who can provide access to the affected area?
I can provide access myself
A named colleague or supervisor
Reception or front desk
Security or gatehouse
A contractor or site contact
Access is unrestricted
Other
Are there any access restrictions (keys, passes, permits, escort requirements, restricted zones)?
When is the best time to carry out the work? (Select all that apply)
Normal working hours
Early morning, before operations start
Evening, after operations end
Weekend
During a planned shutdown or quiet period
As soon as possible, any time
By arrangement with the site contact
Preferred dates or windows for the work
Is there any time when the area cannot be accessed or work cannot take place?
Will noise, dust, or disruption from the repair affect nearby work?
What site conditions should the technician be aware of? (Select all that apply)
Limited parking or loading access
Scaffolding, ladders, or elevated access needed
Working at height required
Restricted or tight working space
Live operations continuing nearby
Special clothing, footwear, or protective equipment required
Permit-to-work or approval needed before starting
None of the above
Is there anything else the technician should know before arriving on site?
Photos and supporting files make a significant difference to how quickly a problem can be diagnosed remotely. Please avoid capturing people, personal information, or sensitive screens in your images.
Please upload a photo showing the overall area and context
Please upload a close-up photo of the damage, fault, or affected component
Please upload any additional photo (for example a different angle, a label, or a serial plate)
Please upload any supporting documents (inspection notes, previous reports, manuals, or screenshots)
Do you have a short video showing the issue in action?
Are there additional photos or files you would like to send later?
If you already know something about the parts, materials, or budget involved, share it here. Estimates are helpful but not required — the maintenance team will confirm scope and any costs through the normal approval route.
Do you know which parts or materials are likely to be needed?
Are spare parts already held in stock on site?
What level of cost approval is expected for this work?
No cost expected — routine maintenance
Minor cost — within a standard maintenance allowance
Requires a quotation before work begins
Requires written approval from a budget holder
Not sure — please advise
Estimated budget or spending limit for this request (optional)
Would you like to be consulted before any chargeable work begins?
Is a temporary or interim solution acceptable while a permanent repair is arranged?
Sometimes one visible symptom points to a wider issue. This section helps capture anything that may be connected.
Have you noticed similar issues in other locations on site?
Is any other work currently happening in or near the affected area?
Which other teams or parties may need to be informed? (Select all that apply)
Facilities or building management
Health, safety, or environment team
IT or network support
Security team
Cleaning or janitorial services
External contractor or supplier
Building owner or landlord representative
Project or site management
None of the above
Would you like to be present when the technician attends?
How would you like to receive progress updates?
Email updates
Phone call
Text message
Update board or notice in the area
Through my supervisor
No updates needed
Is there anything about this request that is confidential or sensitive?
Use the table below to list the individual tasks, parts, or line items you believe are involved. Leave rows blank if you are unsure — the maintenance team will complete and refine this table during assessment.
Requested Work Items
Include? | Task or Item Description | Location or Asset | Qty | Est. Unit Cost | Est. Line Total | Priority (1 low – 5 high) | |
|---|---|---|---|---|---|---|---|
Replace worn flexible connector | Kitchenette sink, Room 108 | 2.00 | $12.50 | $25.00 | |||
Inspect adjacent pipework for corrosion | Kitchenette sink, Room 108 | 1.00 | $0.00 | $0.00 | |||
Replace damaged floor tile | Kitchenette, Room 108 | 1.00 | $18.00 | $0.00 | |||
$0.00 | |||||||
$0.00 | |||||||
$0.00 | |||||||
$0.00 | |||||||
$0.00 | |||||||
$0.00 | |||||||
$0.00 |
Total estimated cost (calculated or entered by the assessor)
Almost done. These final questions help us understand what a good outcome looks like for you and confirm the details of your request.
What would a satisfactory resolution look like from your point of view?
Would you like the repaired area to be cleaned or restored after the work is finished?
Would you like a follow-up check after the repair is completed?
Any additional comments, context, or requests
How clear and easy was this request form to complete?
Very difficult
Difficult
Neutral
Easy
Very easy
I confirm that the information provided in this request is accurate and complete to the best of my knowledge
I understand that submitting this request does not guarantee a specific response time or outcome, and that the maintenance team may contact me for further information
Type your full name to confirm your submission
Please sign to confirm this maintenance and repair request
Date of submission
Time of submission
Analysis for Jobsite & Office Maintenance and Repair Request Form
Important Note:
This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.
AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.
This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.
Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
This comprehensive maintenance and repair request form is designed to capture detailed, actionable reports for jobsite, office, facility, and equipment issues. The form demonstrates strong structural design across thirteen well-organised sections, progressing logically from requester identification through location details, issue classification, problem description, safety assessment, urgency prioritisation, access scheduling, evidence upload, cost considerations, wider impact, work item logging, and final confirmation. The progressive flow mirrors how a maintenance team would naturally triage and plan a response, which should support efficient routing and reduce back-and-forth clarification.
The form excels in several areas. First, it uses extensive conditional logic (follow-up questions triggered by specific answers) to keep the form relevant and avoid overwhelming respondents with irrelevant fields. Second, the inclusion of an emergency disclaimer in the introductory section sets appropriate expectations without creating confusion about the form's role. Third, the safety and hazard section is thorough and encourages honest reporting without implying obligations beyond the respondent's own site procedures. Fourth, the work items table with a built-in calculation formula for estimated line totals provides a structured way to capture cost estimates. Fifth, the form closes with feedback on form usability and clear confirmation checkboxes, which supports both data quality and user trust.
This field establishes the primary point of contact for the request. Knowing who submitted the report enables the maintenance team to follow up for clarification, provide status updates, and maintain a clear audit trail of who reported the issue. Making this mandatory is a practical choice, as it ensures every request can be traced to an individual.
Optional and useful for contextualising the reporter's perspective. A site supervisor may observe different aspects of an issue than an office coordinator. This field helps the maintenance team gauge the reporter's familiarity with the area or equipment involved.
This optional field supports internal routing and coordination. Knowing which team or department is affected helps the maintenance team prioritise alongside other operational needs and identify the right internal stakeholders.
A mandatory contact field that serves as a primary digital communication channel. Email enables written confirmations, status updates, and asynchronous follow-up. Its mandatory status ensures the team has at least one reliable way to reach the requester.
An optional secondary contact method. Including the area code prompt encourages complete, dialable numbers. This is particularly helpful for urgent issues where a phone call may be faster than email.
This single-choice question with conditional follow-ups is an effective design choice. It respects the respondent's communication preferences and, when 'Through my supervisor' is selected, captures the supervisor's details — ensuring the team knows exactly who to contact. The five options cover a realistic range of workplace communication methods.
This yes/no question with a follow-up captures important context about the original reporter. It supports accurate record-keeping when a supervisor or coordinator submits on behalf of a field worker. The follow-up prompt asking how the issue was reported (e.g., via radio) adds useful operational context.
Complementing the previous question, this helps establish the chain of observation. The conditional follow-up asking who noticed it first is useful for witness identification if the issue escalates or requires further investigation.
As a mandatory field, this is essential for routing the request to the correct location and team. Without knowing which site or facility is affected, the maintenance team cannot begin triage. The placeholder example encourages specific naming rather than vague descriptions.
This well-structured single-choice list covers eleven area types with an 'Other' option and conditional follow-up. It helps the maintenance team understand the operational context — a restroom issue has different implications than a workshop issue. The broad range of options reflects the form's multi-site, multi-purpose scope.
Optional but valuable for large or multi-building sites. This narrows down the location further and helps technicians navigate to the right area efficiently.
Another optional location detail that supports efficient dispatch. The placeholder examples cover common formats (floor numbers, basement levels, ground level) to guide consistent responses.
Optional and important for precise location identification. In combination with the building and floor fields, this creates a layered location description that should minimise wasted time searching for the issue.
This multiline field encourages descriptive, landmark-based location information. The placeholder example is excellent — it shows how to describe a location relative to visible objects, which is often more helpful than room numbers alone.
A thoughtful yes/no question with a conditional follow-up requesting step-by-step directions. This acknowledges that some locations (e.g., within ceiling voids or behind equipment) are hard to describe and provides a structured way to capture route information.
This simple yes/no question helps the maintenance team understand who else may be affected and whether coordination with multiple teams is needed before or during the repair.
This question with a conditional follow-up captures reputational and visitor-impact considerations. Issues visible to customers or visitors may warrant faster attention or interim measures, and the follow-up prompt helps quantify that impact.
As a mandatory field, this is a critical routing mechanism. The thirteen categories cover a comprehensive range of facility and equipment issues. The conditional follow-ups for plumbing, electrical, and HVAC categories add useful sub-classification, while the equipment category captures asset identifiers. The 'Other' option with a descriptive follow-up ensures no issue falls through the cracks.
This multiple-choice question captures secondary impacts that may not be the primary category. A water leak that also affects electrical systems, for example, needs different handling than a simple drip. The 'None of the above' option prevents forced selections.
This optional classification helps the maintenance team understand the scope of work. Distinguishing between repair, preventive maintenance, inspection, replacement, installation, adjustment, and cleaning supports appropriate resource allocation. The 'Not sure — needs assessment' option is a practical inclusion.
With a conditional follow-up for job reference numbers, this question helps identify recurring problems or potentially incomplete previous work. This is operationally valuable for quality tracking and identifying systemic issues.
The follow-up asking about frequency and last occurrence helps the maintenance team identify patterns. A recurring issue may need a different approach (e.g., root cause investigation) compared to a first-time occurrence.
As a mandatory multiline field, this is the core narrative of the request. The introductory guidance encouraging symptom description over speculation is excellent — it promotes factual, useful reporting. The placeholder example demonstrates the level of detail expected.
This optional field prompts multi-sensory observation, which is highly useful for diagnosis. The parenthetical hints guide the respondent to think beyond visual symptoms, potentially capturing clues that a technician would otherwise need to discover on site.
Understanding the temporal pattern of an issue is diagnostically important. The six options cover realistic scenarios, and the conditional follow-up for 'happens only at certain times' captures specific triggers. This can significantly reduce diagnostic time.
A mandatory field capturing the onset time in free text. This supports urgency assessment and helps establish a timeline. The placeholder example encourages approximate but useful time references.
An optional structured date field that complements the free-text onset description. Structured dates support sorting, filtering, and trend analysis in any downstream tracking system.
An optional structured time field that further supports timeline construction. Together with the date field, it provides machine-readable onset data.
This yes/no question with a conditional follow-up captures onset characteristics. The follow-up options (sudden, gradual, after an event, after nearby work, not sure) are well-chosen for maintenance diagnostics.
With a conditional follow-up requesting a description of visible damage, this question helps distinguish between obvious external causes and internal failures. This can influence whether the response is a simple fix or a more complex investigation.
This comprehensive multiple-choice list covers ten common symptom types with a 'None of the above' option. It provides a structured symptom profile that can be quickly scanned by triage staff, complementing the free-text descriptions.
The conditional follow-up asking what was tried and the result is operationally important. It prevents the technician from repeating failed approaches and indicates the severity of the respondent's concern.
With a follow-up capturing what is out of service and since when, this question directly supports operational impact assessment. Out-of-service areas typically warrant higher priority.
This yes/no question with a conditional follow-up for the equipment name acts as a gateway to the detailed asset information fields that follow. It prevents respondents from filling in irrelevant asset details when the issue is purely building-related.
Optional and valuable for asset tracking. When known, this information enables the maintenance team to pull up service history and warranty status from any asset management system they may use.
Optional and useful for sourcing parts or identifying specialist technicians. The '(if known)' qualifier appropriately manages expectations.
Optional and complementary to the manufacturer field. Together, these support accurate parts identification and service documentation lookup.
Optional numeric field that can inform repair-versus-replace decisions. Older equipment may have different parts availability or reliability considerations.
The conditional follow-up capturing provider name, reference, and expiry date is operationally useful. It helps the team determine whether the issue should be handled internally or referred to an external service provider.
This safety-relevant question with a follow-up about who applied the isolation and where the key is located is practical and important for safe work planning. It ensures the maintenance team understands the current safety state before attending.
Optional free-text field that captures relevant maintenance context. Recent work on or near the equipment may be relevant to the current issue.
As a mandatory yes/no question, this is a critical safety screening field. The conditional follow-up with nine risk categories (slip/trip, electrical, falling objects, chemical, fire, gas, structural, moving parts, other) enables rapid risk classification. The introductory paragraph appropriately frames hazard reporting as supportive rather than punitive.
This question with dual follow-ups (for both yes and no answers) is well-designed. It captures what restrictions exist and, if none, whether temporary measures are needed. This supports safe work planning and interim risk management.
This ten-option multiple-choice list covers common workplace hazards relevant to maintenance work. The 'None of the above' option prevents forced hazard selections. This structured hazard inventory supports pre-work safety briefings.
This single-choice question with graduated severity options and conditional follow-ups is thoughtfully designed. The 'Prefer not to say' option respects respondent privacy, and the follow-up prompts explicitly request brief descriptions without sensitive medical details — a good privacy-conscious design choice.
The conditional follow-up asking what should be shut down and who should be informed supports operational decision-making. This helps the maintenance team coordinate with operations staff to manage the impact of any shutdown.
This checkbox confirmation encourages respondents to take the hazard reporting seriously. It also creates a clear record that the reporter attested to the accuracy of their safety information.
As a mandatory single-choice field, this directly feeds into prioritisation. The five levels (critical, high, medium, low, planning only) are clearly defined with brief descriptions. The introductory guidance discouraging defaulting to the highest priority is a commendable design choice that promotes honest, accurate prioritisation.
This six-option scale captures operational impact with conditional follow-ups for the most severe levels. Understanding whether an entire operation is stopped versus a minor inconvenience directly informs response urgency and resource allocation.
Optional numeric field that quantifies the human impact. This can help justify resource allocation and prioritisation when multiple requests are being triaged simultaneously.
With a conditional date follow-up, this question captures time-bound requirements. This is operationally important for scheduling and may influence whether the request is treated as routine or urgent.
The conditional follow-up requesting a description of loss type (without requiring sensitive figures) is a balanced approach. It captures the nature of the impact while respecting the respondent's comfort with sharing financial details.
With an eight-option conditional follow-up covering temperature, lighting, noise, odour, air quality, and humidity, this question captures comfort-related impacts that may not be safety-critical but affect workplace productivity and wellbeing.
The conditional follow-up requesting general terms and the explicit note that the form does not provide compliance advice is a responsible design choice. It captures relevant scheduling context without making claims about regulatory obligations.
This single-choice question with three conditional follow-ups (for named colleagues, security, and other arrangements) is practical and well-structured. It ensures the maintenance team knows exactly how to gain access when they arrive.
The conditional follow-up requesting details about what is needed before work can begin is operationally important. Access restrictions can significantly affect scheduling and resource planning.
This multiple-choice question with seven scheduling options helps the maintenance team plan visits at convenient times. The 'as soon as possible' option captures urgent scheduling needs.
Optional free-text field that captures specific scheduling preferences. The placeholder example shows how to express time windows clearly.
With a conditional follow-up for blackout periods and reasons, this question prevents scheduling conflicts. It is a practical consideration that saves wasted trips and rescheduling.
The conditional follow-up asking who should be notified and what constraints apply supports considerate scheduling. This is particularly relevant in shared or occupied workspaces.
This eight-option multiple-choice list covers practical site conditions (parking, elevated access, restricted space, live operations, PPE, permits) that affect work planning and safety. The 'None of the above' option prevents unnecessary selections.
This catch-all question with a conditional follow-up for arrival instructions captures practical details that don't fit elsewhere. The placeholder example (parking, check in, contact point) illustrates useful content.
Image uploads are highly valuable for remote diagnosis and work planning. The introductory guidance about avoiding people, personal information, and sensitive screens in images is a thoughtful privacy consideration.
Close-up images complement the overview photo and can significantly accelerate diagnosis. Together, these two image fields capture both context and detail.
Optional additional image upload that accommodates situations where more visual evidence is helpful. The examples (different angle, label, serial plate) guide useful submissions.
File upload for documents adds depth to the request. Previous reports and inspection notes can provide valuable context for recurring or complex issues.
With a conditional file upload, this question captures dynamic evidence that photos cannot — such as intermittent noises, flickering lights, or vibrating equipment. This is a practical addition for certain issue types.
This question with a follow-up about how and when additional evidence will be sent helps the team plan for supplementary information. It acknowledges that not all evidence is available at the time of form submission.
With a conditional follow-up listing parts, this question can accelerate procurement and work planning. It is appropriately framed as optional — the introductory text notes that estimates are helpful but not required.
The conditional follow-up about storage location and who manages spares is operationally useful. It can reduce response time if parts are already available on site.
This single-choice question with a conditional follow-up for budget holder details helps the maintenance team understand the approval pathway before work begins. The five options cover realistic approval scenarios.
Optional currency field that captures budget expectations. The explicit '(optional)' label in the question text reinforces that this is not required.
This question with a conditional follow-up (for when the answer is no) respects the respondent's preference for involvement in cost decisions. It helps avoid misunderstandings about authorisation.
The conditional follow-up about acceptable temporary arrangements is practical. It helps the maintenance team provide immediate relief while planning a more complete fix.
With a conditional follow-up, this question helps identify systemic or widespread problems. A similar issue in multiple locations may indicate a common root cause that requires a broader response.
The conditional follow-up asking about concurrent work and its possible connection is operationally insightful. Nearby construction or maintenance work is a common cause of new issues.
This nine-option multiple-choice list covers common stakeholders (facilities, safety, IT, security, cleaning, contractors, landlord, project management). It supports coordinated communication and response.
With a conditional follow-up about suitable times, this question respects the respondent's desire for involvement. Being present can help the technician understand the issue more quickly.
This single-choice question with six communication options ensures the respondent receives updates through their preferred channel. The 'no updates needed' option respects those who prefer minimal communication.
With a conditional follow-up requesting general sensitivity descriptions and distribution guidance, this question demonstrates privacy awareness. It helps the maintenance team handle the request appropriately.
This structured table with checkbox inclusion, task description, location/asset, quantity, estimated unit cost, calculated line total (using a formula), and priority rating is an excellent operational tool. The formula IF(column1=1,column4*column5,0) automatically calculates line totals for included items. Pre-populated example rows demonstrate expected usage. This table bridges the gap between the requester's observations and the maintenance team's work planning.
This currency field captures the overall estimated cost, either calculated from the table or entered manually. It provides a summary figure for budget planning and approval routing.
This open-ended question captures the respondent's expectations for a good outcome. It helps the maintenance team understand what 'done' looks like from the user's perspective and supports satisfaction tracking.
With a conditional follow-up describing expected cleaning, this question ensures the maintenance team accounts for post-work restoration in their planning. It prevents the common frustration of a repair that leaves the area untidy.
With a conditional follow-up about timing, this question supports quality assurance and customer satisfaction. A follow-up check can confirm the repair was effective and identify any lingering issues.
This catch-all multiline field provides space for information that doesn't fit elsewhere. The placeholder example (noting a pattern of recurring issues) illustrates how this field can surface important observations.
This five-point rating scale captures form usability feedback. It demonstrates a commitment to continuous improvement and can inform future form revisions.
This checkbox confirmation encourages respondents to review their submissions and attests to data accuracy. It supports data quality and creates a clear record of respondent attestation.
This checkbox sets appropriate expectations about response times and outcomes. It is a transparent communication practice that helps prevent misunderstandings.
As a mandatory typed confirmation, this field serves as a digital signature equivalent. It reinforces the respondent's accountability for the submitted information and provides a clear record of who confirmed the request.
The signature field adds a formal confirmation layer. It creates a clear, attributable record of the submission and may support internal record-keeping practices.
Optional structured date field that timestamps the submission. This supports record-keeping and can be compared against the issue observation dates for timeline analysis.
Optional structured time field that completes the submission timestamp. Together with the date, it provides precise submission timing for record-keeping purposes.
Overall, this form is exceptionally well-designed for its purpose. Its strengths include comprehensive coverage of maintenance and repair scenarios, extensive use of conditional logic to keep the experience relevant, thoughtful privacy-conscious prompts (particularly around medical details and sensitive information), clear instructional text that guides respondents toward useful answers, and a structured work items table that bridges reporting and planning. The form also demonstrates strong safety awareness without overstepping into prescriptive territory.
Areas where the form could be further refined include: the overall length may present a completion burden for simple issues — a tiered or progressive disclosure approach (e.g., a short-form option for minor issues) could improve completion rates for low-complexity requests. Some optional fields (such as manufacturer, model, and equipment age) could benefit from being grouped behind a single 'I have equipment details' toggle to reduce visual clutter. The work items table, while powerful, may be challenging for respondents unfamiliar with cost estimation — the introductory text does acknowledge this, which is helpful. Finally, the form could consider adding a brief progress indicator or section navigation to help respondents understand how much of the form remains, given its considerable length.
Mandatory Question Analysis for Jobsite & Office Maintenance and Repair Request Form
Important Note:
This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.
Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.
Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
Full name of the person submitting this request
Recommendation: Requiring this field ensures that every maintenance request can be attributed to a specific individual, which supports follow-up communication, accountability, and record-keeping. Without a name, the maintenance team would have no reliable way to contact the reporter for clarification or status updates. Form administrators should consider whether capturing a display name or a formal legal name better suits their internal record-keeping practices.
Email address
Recommendation: Making email mandatory provides a reliable digital communication channel for sending acknowledgements, status updates, and follow-up questions. It serves as a primary touchpoint that supports asynchronous communication, which is especially valuable when the requester is not always available by phone. Depending on your organisation's data handling practices, consider providing a brief notice about how submitted contact details will be stored and used.
Site, building, or facility name
Recommendation: This field is essential for routing the request to the correct location and maintenance team. Without knowing which site or facility is affected, triage cannot begin. Requiring this field prevents incomplete submissions that would otherwise need to be returned to the requester for clarification. The necessity of this field depends on whether the organisation operates across multiple locations; for single-site operations, it may be possible to pre-fill or simplify this field.
What is the primary category of the issue?
Recommendation: Requiring issue categorisation supports efficient routing to the appropriate trade or specialist. It enables the maintenance team to assign the right resources and, where applicable, trigger category-specific follow-up questions (as the form's conditional logic does for plumbing, electrical, and HVAC categories). This field directly supports operational processing and helps prevent misclassification delays. The form appropriately notes that the team can reclassify later if needed.
Please describe the problem in detail
Recommendation: This mandatory multiline field captures the core narrative of the request and is the single most important piece of information for diagnosis and response planning. Requiring it ensures that every submission includes a substantive description rather than a bare category selection. The form's guidance encouraging symptom description over speculation is well-aligned with this requirement. Form administrators should be aware that some respondents may find detailed description challenging — the placeholder example is helpful in setting expectations for the level of detail desired.
When did you first notice the issue?
Recommendation: Requiring the onset time supports urgency assessment and timeline construction. It helps the maintenance team understand how long the issue has been present and whether it is a new or developing problem. This field is operationally important for prioritisation and for identifying patterns in recurring issues. The free-text format allows flexibility for approximate times, which is appropriate given that respondents may not always know the exact moment an issue began.
Do you believe the issue poses any immediate risk to people?
Recommendation: This mandatory safety screening question is critical for triaging requests that involve potential hazards. Requiring an explicit yes/no response ensures that every submission addresses safety, preventing hazardous issues from being overlooked. The conditional follow-up with risk categories further supports rapid hazard classification. The form's introductory text appropriately frames this as supportive reporting rather than a punitive measure, which encourages honest responses. Form administrators should ensure that 'yes' responses trigger appropriate internal escalation processes within their organisation.
How would you describe the urgency of this request?
Recommendation: Requiring an urgency classification directly supports prioritisation and resource allocation. The five clearly defined levels help respondents make informed choices, and the form's guidance discouraging defaulting to the highest priority promotes accurate self-assessment. This field is operationally central to the maintenance team's scheduling decisions. The necessity of making this mandatory depends on whether the organisation relies on requester-assessed priority or applies its own triage criteria — in the latter case, this could potentially be made optional with the team assigning priority during review.
Type your full name to confirm your submission
Recommendation: Requiring a typed name at the point of submission serves as a digital confirmation that reinforces respondent accountability. It creates a clear, attributable record that the requester reviewed and stands behind the information provided. This is particularly valuable in operational contexts where requests may be referenced later for follow-up, audit, or quality tracking purposes. Form administrators should consider whether the typed name should match the name captured at the beginning of the form or whether a different confirmation name is acceptable.
The form's mandatory field strategy is well-balanced and proportionate. Nine mandatory fields are distributed across the form — two in the requester information section, one in location details, one in issue classification, two in problem description, one in safety assessment, one in urgency classification, and one in the final confirmation. This distribution ensures that critical data is captured at each key stage of the request without creating an overwhelming barrier to completion.
In summary, the mandatory field strategy effectively prioritises the information that is most critical for routing, safety assessment, and communication while allowing extensive optional detail to be provided by respondents who have it available. This balance supports both operational efficiency and user experience.