Maintenance & Repair Request — Report a Jobsite or Office Issue

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. Please remove this content before publishing the form to the public.

Overall Form Summary

This Jobsite & Office Maintenance and Repair Request Form is an exceptionally comprehensive and well-structured document designed to capture every dimension of a facility issue — from the identity of the reporter and the precise location of the fault, through safety hazards and evidence, to cost estimates, scheduling preferences and formal declarations. The form's architecture reflects a deep understanding of the facilities management workflow: it collects data in a logical sequence that mirrors how a maintenance team would triage, assess, dispatch and resolve a request. By front-loading requester identity and contact details, then moving through location, description, safety and impact before logistics and approvals, the form ensures that the most operationally critical information is gathered first, reducing the risk of incomplete submissions for urgent issues.

Among its many strengths, the form stands out for its intelligent use of conditional follow-up questions, which tailor the data collection to the user's specific situation without overwhelming them with irrelevant fields. The inclusion of safety and hazard assessment as a dedicated section underscores a commitment to occupational health and safety compliance, while the evidence upload section and previous-request log promote diagnostic accuracy and continuity of care. The form also demonstrates strong user experience design through clear placeholder examples, progressive disclosure via yes/no and single-choice branching, and a welcoming introductory paragraph that sets expectations. Potential areas for refinement include the overall length of the form, which may deter some users in urgent situations, and the balance between mandatory and optional fields — though the current mandatory set is generally well-chosen. Overall, this form is a best-in-class example of a maintenance request instrument that balances thoroughness with usability.

Section: Requester Information

Question: Full name of person submitting this request

The question Full name of person submitting this request serves as the foundational identity anchor for the entire request. In a facilities management context, knowing who reported an issue is essential not only for follow-up communication but also for accountability, audit trails and compliance with workplace safety regulations. Without a named requester, the maintenance team would be unable to confirm details, seek clarifications or provide updates, effectively rendering the request anonymous and unactionable.

From a design perspective, making this field mandatory is an excellent decision. The placeholder example e.g. Jordan Alvarez provides a clear, culturally diverse example that sets expectations for the format. The single-line text type is appropriate — a full name does not require multiline input, and the field is positioned at the very top of the form, following the natural flow of who is submitting this?

In terms of data collection, this field will yield a straightforward string of text. The quality of data here is generally high, as most users know their own name. Privacy considerations are minimal since the name is being submitted voluntarily within an organizational context, though the form should ensure that personal data is stored in compliance with applicable data protection regulations such as GDPR or local equivalents.

From a user experience standpoint, asking for the name first is intuitive and low-friction. Users expect to identify themselves at the start of any formal request. The mandatory status is well-justified — a request without a known requester cannot be processed. The field's simplicity ensures that users can complete it in seconds, contributing to a positive first impression of the form.

Question: Employee/Contractor/Visitor ID number

The question Employee/Contractor/Visitor ID number is designed to capture a unique organizational identifier for the requester. In large facilities with hundreds or thousands of personnel, a name alone may be insufficient to uniquely identify someone. An ID number links the request to the organization's HR or contractor management systems, enabling cross-referencing with access records, training certifications and employment status.

The design choice to make this field optional is pragmatic. Not all requesters will have an ID — visitors, for instance, may not be issued one. The placeholder e.g. EMP-10482 or CTR-2291 helpfully illustrates both employee and contractor formats, reducing ambiguity. The single-line text input is appropriate for this alphanumeric identifier.

Data collected here will be an alphanumeric string that can be validated against internal databases. The optional nature means some records will lack this identifier, which is acceptable given that the full name field is mandatory and serves as the primary identification. Privacy considerations are slightly higher here, as ID numbers can be used to access personal records — the form should ensure this data is handled securely.

For user experience, this field is well-placed immediately after the name field, forming a natural identity block. The optional status reduces friction for users who may not have their ID handy or who are external visitors. The clear placeholder examples ensure that users understand the expected format without confusion.

Question: Department, team or contracting company

The question Department, team or contracting company captures the organizational unit to which the requester belongs. This is critical for routing the request to the appropriate maintenance team, understanding the operational context of the issue and determining which budget or cost center should be charged for the repair. In a multi-departmental facility, knowing the department helps prioritize requests based on operational impact.

Making this field mandatory is a sound design decision. Without departmental context, the maintenance team cannot assess the business impact of the issue or determine cost allocation. The placeholder e.g. Site Operations, Facilities, Northgate Construction Ltd. effectively shows that both internal departments and external contracting companies are valid inputs, reflecting the form's inclusive design for various stakeholder types.

The data collected will be a free-text organizational unit name. While this provides flexibility, it may lead to inconsistent entries. A dropdown or autocomplete feature could improve data consistency, though the free-text approach accommodates the wide range of possible departments and companies. The data quality is generally high as users know their department or company.

From a user experience perspective, this question is straightforward and low-friction. Users know their department or company name. The mandatory status is justified — it is a core piece of routing and accountability information. The field's placement within the identity block maintains logical flow.

Question: Job title or role on site

The question Job title or role on site adds another layer of contextual information about the requester. Understanding the requester's role helps the maintenance team gauge the authority level, the type of work being interrupted and the potential urgency of the request. For example, a site supervisor reporting a safety hazard carries different weight than a visitor reporting a cosmetic issue.

This field is optional, which is a reasonable choice. While useful, job titles are not essential for processing the request — the department and contact information are more critical. The placeholder e.g. Site Supervisor, Office Administrator, Electrician provides diverse examples that help users understand the expected input.

The data collected will be a free-text job title string. This may include a wide variety of roles across different organizations. The quality of data is likely to be high since users know their own job title, though formatting may vary. Privacy considerations are minimal.

For user experience, this optional field is well-positioned within the identity block. Its optional status means it does not add friction for users who want to submit quickly, while still capturing useful context for those who provide it. The clear placeholder reduces ambiguity.

Question: Email address

The question Email address is one of the most critical fields in the entire form. Email serves as the primary channel for sending request confirmations, status updates, resolution notifications and any follow-up correspondence. In modern facilities management, email is the backbone of communication and documentation — it creates an auditable trail of all interactions related to the request.

Making this field mandatory is absolutely essential. Without an email address, the maintenance team cannot send automated confirmations, track the request lifecycle or provide updates. The placeholder e.g. jordan.alvarez@example.com clearly indicates the expected format. The single-line text input is standard and appropriate.

The data collected will be an email address string. This should ideally be validated for format to prevent typos. Email addresses are personal data and must be stored and processed in compliance with data protection regulations. The form should ensure that email addresses are not exposed to unauthorized parties.

From a user experience standpoint, requesting an email address is a universally expected step in any online form. Users are accustomed to providing this information. The mandatory status is well-justified and unlikely to cause friction. The field's placement within the contact information block is logical and intuitive.

Question: Phone number (include country/area code if applicable)

The question Phone number (include country/area code if applicable) captures an alternative contact method that is especially important for urgent or emergency situations. When a safety hazard or operational disruption is involved, the ability to reach the requester by phone — rather than waiting for an email response — can be the difference between a timely resolution and a prolonged incident.

Making this field mandatory is a strong design choice that reflects the operational reality of facilities management. For urgent issues, phone contact is often the fastest way to gather additional details or coordinate access. The instruction to include country/area code is thoughtful, accommodating international contractors and multi-site organizations. The placeholder e.g. +00 555 0100 reinforces this format.

The data collected will be a phone number string. This is personal contact information and must be handled in accordance with privacy regulations. The form should ideally validate the format to catch obvious errors, though the free-text approach allows for various international formats.

For user experience, this field is well-placed alongside the email address, forming a complete contact block. The mandatory status is justified — having at least two contact methods ensures the maintenance team can reach the requester through multiple channels. The parenthetical instruction about country/area codes is a helpful touch that reduces ambiguity.

Question: What is the best way to contact you about this request?

The question What is the best way to contact you about this request? is an excellent example of user-centered design. Rather than assuming a one-size-fits-all communication approach, this question empowers the requester to specify their preferred contact channel, which directly improves the likelihood of successful communication and faster resolution.

The single-choice format with six options — Email, Phone call, SMS/text, Internal messaging platform, In person on site and No preference — covers a comprehensive range of communication methods suitable for diverse workplace environments. The conditional follow-up questions are particularly well-designed: selecting Phone call prompts for a phone number confirmation, SMS asks for a mobile number, Internal messaging platform requests the platform and username, and In person on site asks for location and availability. This progressive disclosure keeps the form clean while capturing exactly the information needed.

Data collected here will be a categorical selection plus conditional text fields. This structured approach enables the maintenance team to automate or streamline communication workflows. For example, requests with SMS preference can be routed to an SMS notification system. The data quality is high because the options are clearly defined and the follow-ups capture the specific details needed.

From a user experience perspective, this question demonstrates respect for the user's preferences and communication habits. The conditional follow-ups feel natural and relevant — users are not asked for information they do not need. The No preference option is a thoughtful inclusion that prevents forcing a choice on users who genuinely do not mind. This question significantly enhances the form's usability and the quality of post-submission communication.

Question: What is your relationship to this request?

The question What is your relationship to this request? captures the requester's role in relation to the issue — whether they are directly affected, reporting on behalf of others, a contractor, a public area reporter or a manager escalating an existing request. This contextual information is invaluable for the maintenance team in understanding the scope, urgency and stakeholder dynamics of the issue.

The single-choice format with five well-defined options covers the key scenarios in a facilities management context. The conditional follow-ups are particularly thoughtful: reporting on behalf of a team prompts for details about who is affected and how, while escalating an existing request asks for the original ticket number. These follow-ups prevent the need for the maintenance team to chase additional information later.

Data collected here will be a categorical selection plus conditional text fields. This structured data enables the maintenance team to prioritize requests — for example, a manager escalating an existing request may warrant immediate attention, while a contractor reporting a client-side issue may require different handling. The data quality is high due to the clear option definitions.

For user experience, this question is well-designed and relevant. The options are mutually exclusive and collectively exhaustive, covering all likely scenarios. The conditional follow-ups feel natural and are only shown when relevant, keeping the form efficient. The question's placement after the contact information block maintains logical flow — the form first establishes who you are and then why you are submitting this.

Question: Are you authorised to allow maintenance staff into the affected area?

The question Are you authorised to allow maintenance staff into the affected area? addresses a critical operational and security concern. Maintenance work often requires physical access to restricted or controlled areas. Knowing whether the requester can grant this access — or who can — prevents delays, failed site visits and security breaches.

The yes/no format with intelligent follow-ups is highly effective. If the requester answers Yes, the form asks for their access authority level or approval reference, which provides the maintenance team with confidence that access will be available. If No, the form asks who should be contacted to grant access, capturing the name, role and contact details of the appropriate person. This conditional logic ensures that the access question is always resolved before the request is submitted.

Data collected here will be a boolean selection plus conditional text fields. This information is operationally critical — it directly affects the scheduling and dispatch of maintenance personnel. The data quality is high because the follow-ups capture specific, actionable details.

From a user experience standpoint, this question is practical and well-timed. It is placed at the end of the requester information section, after the form has established the requester's identity and context. The question is clear and the follow-ups are relevant. This design choice significantly reduces the risk of failed site visits and improves the efficiency of the maintenance workflow.

Section: Location & Asset Details

Question: Site, building or facility name

The question Site, building or facility name is the first and most fundamental piece of location data. In organizations with multiple sites, buildings or facilities, this field ensures that the maintenance request is routed to the correct team and dispatched to the right physical location. Without this information, the request would be ambiguous and potentially sent to the wrong maintenance crew.

Making this field mandatory is essential. The placeholder e.g. Riverside Business Park — Building C effectively demonstrates the expected level of detail, including both the site name and the specific building. The single-line text input is appropriate for this type of identifier.

Data collected here will be a facility name string. This should ideally be validated against a master list of known facilities to prevent typos and ensure consistency. However, the free-text approach accommodates new or temporary facilities that may not yet be in the system. The data quality is generally high as users know their work location.

For user experience, this question is intuitive and low-friction. Users know where they work. The mandatory status is well-justified — location is the single most important piece of information for dispatching maintenance personnel. The field's placement at the top of the location section is logical and follows the natural flow from who to where.

Question: Floor, level, yard or zone

The question Floor, level, yard or zone adds the next layer of location precision. In multi-story buildings or sprawling industrial sites, knowing the floor or zone is critical for directing the maintenance crew to the correct area. This field narrows down the location from the building level to the specific level or zone within it.

Making this field mandatory is a sound decision. Without floor or zone information, the maintenance team may waste time searching for the issue within a large facility. The placeholder e.g. Level 3, North Yard, Zone B provides diverse examples covering office buildings, outdoor areas and industrial zones, reflecting the form's versatility.

Data collected here will be a location identifier string. Like the facility name, this could benefit from a dropdown or autocomplete for known floors and zones, though free-text accommodates the wide variety of possible layouts. The data quality is likely high as users know their immediate work area.

From a user experience perspective, this question follows naturally from the facility name, creating a logical location hierarchy: building to floor/zone to room/area. The mandatory status is justified and the field is quick to complete. The diverse placeholder examples help users from different types of facilities understand what is expected.

Question: Room, unit, bay or area identifier

The question Room, unit, bay or area identifier provides the most granular level of location detail within the form's location hierarchy. This field captures the specific room number, bay identifier, cabin number or area code where the issue is located, enabling the maintenance crew to go directly to the exact spot.

This field is optional, which is a reasonable design choice. Not all issues have a specific room or bay identifier — some may be in open areas, corridors or outdoor spaces. The placeholder e.g. Room 3.14, Loading Bay 2, Cabin 7 provides clear examples across different facility types. The single-line text input is appropriate.

Data collected here will be a room or area identifier string. This is the finest level of location granularity and significantly improves dispatch efficiency. The data quality depends on the facility's numbering system — well-numbered facilities will yield precise data, while less organized sites may produce variable descriptions.

For user experience, this optional field is well-placed within the location hierarchy. Its optional status prevents friction for users whose issues are not in a specific room, while still capturing valuable detail when available. The clear placeholder reduces ambiguity and helps users provide the right level of detail.

Question: Detailed directions to the exact spot

The question Detailed directions to the exact spot is one of the most practically valuable fields in the entire form. Even with a building, floor and room number, maintenance crews often struggle to find the exact location of an issue — especially in large, complex facilities. Detailed directions eliminate this ambiguity and ensure the technician arrives at the right spot on the first visit.

Making this field mandatory is an excellent decision. The placeholder example is a masterful demonstration of the expected level of detail — it provides step-by-step directions and uses landmarks, showing exactly the kind of information that is helpful. The multiline text input is appropriate for this descriptive content.

Data collected here will be free-text descriptive directions. The quality of data depends heavily on the user's ability to describe locations clearly. The excellent placeholder example sets a high standard that encourages thorough responses. This field directly impacts the efficiency of the maintenance workflow — poor directions lead to wasted time and multiple site visits.

From a user experience standpoint, this mandatory field is well-justified but does require more effort from the user than a simple identifier. However, the excellent placeholder example and the explanatory paragraph at the top of the section motivate users to provide thorough directions. The multiline input gives users ample space to describe the location clearly.

Question: Approximate location of the issue (map)

The question Approximate location of the issue uses a map element to provide a visual, geospatial reference for the issue location. This is a modern and effective design choice that complements the text-based location fields. A map pin gives the maintenance team an immediate visual understanding of where the issue is, especially useful for large campuses, outdoor areas or multi-building sites.

The map element includes longitude, latitude and a landmark reference (Main facility entrance), which provides a default starting point. The instruction to confirm or describe the exact spot above is thoughtful — it acknowledges that the map pin is approximate and directs users to the detailed directions field for precision. This prevents over-reliance on the map for exact positioning.

Data collected here will be geospatial coordinates plus a landmark reference. This data can be integrated with facility management systems, GIS platforms or navigation tools to optimize dispatch routes. The data quality is inherently approximate — map pins may not be precise to the meter — but the combination with text-based directions provides a comprehensive location picture.

For user experience, the map element is engaging and modern. It breaks up the text-heavy form with a visual interaction. However, it may present a minor friction point for users on mobile devices or those unfamiliar with map interfaces. The instruction to confirm or describe the exact spot mitigates this by making the map supplementary rather than primary. Overall, this is a strong design choice that enhances the form's functionality.

Question: What type of asset, system or area is affected?

The question What type of asset, system or area is affected? is a critical categorization field that drives the routing, prioritization and resource allocation of the maintenance request. By identifying whether the issue involves electrical, plumbing, HVAC, structural, IT, safety or other systems, the maintenance team can dispatch the appropriately skilled technician with the right tools and parts.

The single-choice format with 13 comprehensive options covers virtually every type of facility asset and system. The inclusion of Other with a conditional follow-up for free-text description ensures that unusual or unlisted issues are still captured. Making this field mandatory is essential — without categorization, the request cannot be properly triaged or routed.

Data collected here will be a categorical selection that can be used for automated routing, reporting and trend analysis. For example, a spike in Plumbing requests may indicate a systemic issue requiring capital investment. The data quality is high because the options are clearly defined and mutually exclusive. The conditional Other follow-up captures edge cases without compromising the structured data.

From a user experience perspective, this question is clear and easy to answer. The comprehensive option list covers the vast majority of scenarios, and the Other option prevents frustration for unusual cases. The mandatory status is well-justified and the question's placement within the location and asset section is logical — it naturally follows the physical location fields and precedes the asset identification fields.

Question: Asset, equipment or serial/tag number (if known)

The question Asset, equipment or serial/tag number (if known) captures the unique identifier for the specific piece of equipment or asset that is experiencing issues. This is invaluable for maintenance teams that maintain asset registers, as it allows direct linking of the request to the asset's maintenance history, warranty status and lifecycle data.

This field is optional, which is pragmatic — not all users will have access to asset tags or serial numbers, especially for building systems like plumbing or structural elements. The placeholder helpfully shows both internal tag numbers and manufacturer serial numbers. The single-line text input is appropriate.

Data collected here will be an alphanumeric asset identifier. When provided, this data can be cross-referenced with the organization's asset management system to pull up maintenance history, warranty information and replacement schedules. The data quality is variable — some users will provide precise identifiers while others may leave this blank.

For user experience, this optional field is well-placed within the asset identification block. Its optional status prevents friction for users who do not have this information readily available. The (if known) qualifier in the question text is a helpful touch that reduces anxiety about not knowing the answer.

Question: Manufacturer, brand or model

The question Manufacturer, brand or model captures the make and model of the affected equipment. This information is crucial for maintenance teams to identify replacement parts, consult manufacturer documentation, check for known defects or recalls and determine whether specialized expertise is needed.

This field is optional, which is appropriate — not all issues involve equipment with a specific manufacturer or model. The placeholder provides a clear example of the expected format. The single-line text input is suitable for this type of data.

Data collected here will be a manufacturer/model string. This data supports parts ordering, warranty claims and technical troubleshooting. The data quality depends on the user's familiarity with the equipment — some may know the exact model while others may only know the brand.

For user experience, this optional field is straightforward and quick to complete for users who know the information. The optional status prevents frustration for those who do not. The field's placement alongside the asset tag number creates a logical equipment identification block.

Question: Approximate age of the asset in years

The question Approximate age of the asset in years provides context about the asset's lifecycle stage. Older assets may be more prone to failure, may be approaching end-of-life and may not be worth repairing versus replacing. This information helps the maintenance team make cost-effective decisions about repair versus replacement.

This field is optional and uses a numeric input, which is appropriate for capturing a simple age value. The placeholder is clear and concise. The word Approximate in the question text is a helpful qualifier that reduces pressure on users to provide exact figures.

Data collected here will be a numeric value representing years. This data supports lifecycle analysis, capital planning and repair/replace decisions. The data quality is inherently approximate but still valuable for trend analysis and decision-making.

For user experience, this optional field is quick and easy to complete. The numeric input prevents formatting issues. The optional status is appropriate — not all users will know the age of the asset, especially for building systems installed before their tenure.

Question: Is the asset or installation still under warranty or a service contract?

The question Is the asset or installation still under warranty or a service contract? has significant financial implications. If an asset is under warranty or service contract, the repair may be covered at no cost to the organization. If not, the repair costs may need to be budgeted and approved. This question directly impacts the cost and approval workflow.

The yes/no format with intelligent follow-ups is highly effective. If Yes, the form asks for warranty/contract details, provider name and reference number — all essential for making a warranty claim. If No, the form presents a checkbox acknowledging that repair costs may be charged to the department's budget. This conditional logic ensures that both scenarios are properly documented.

Data collected here will be a boolean selection plus conditional text fields or a checkbox. This data directly affects the financial processing of the request. The data quality is high because the follow-ups capture specific, actionable details needed for warranty claims or budget allocation.

From a user experience standpoint, this question is clear and financially relevant. The conditional follow-ups feel natural and are only shown when relevant. The checkbox in the No branch is a thoughtful touch that ensures the requester is aware of potential cost implications before submitting. This design choice promotes transparency and prevents surprises.

Question: Is the affected area currently accessible without special equipment or permits?

The question Is the affected area currently accessible without special equipment or permits? addresses a critical operational and safety concern. Some maintenance work requires specialized access equipment, permits or security clearances. Knowing this in advance allows the maintenance team to plan appropriately and avoid failed site visits.

The yes/no format with comprehensive follow-ups is excellent. If Yes, the form asks about access hours or restrictions. If No, the form presents a multiple-choice checklist of access requirements including master key, security escort, elevated work platform, confined space permit, lock-out/tag-out, PPE, site induction and production shutdown. This conditional logic captures exactly the information needed for safe and efficient dispatch.

Data collected here will be a boolean selection plus conditional text or multiple-choice fields. This data is operationally critical — it directly affects the scheduling, resource allocation and safety planning for the maintenance visit. The data quality is high due to the structured options and detailed follow-ups.

For user experience, this question is practical and well-designed. The comprehensive access requirements checklist covers the most common scenarios in industrial and commercial facilities. The conditional follow-ups are relevant and only shown when needed. This question significantly improves the efficiency and safety of the maintenance workflow.

Section: Issue Description & Symptoms

Question: Short summary of the problem (this becomes the request title)

The question Short summary of the problem (this becomes the request title) serves a dual purpose: it captures a concise description of the issue and it becomes the title of the request in the maintenance management system. This is an excellent design choice that ensures every request has a clear, scannable title for tracking, reporting and communication purposes.

Making this field mandatory is essential. Without a summary, the request would lack a title, making it difficult to identify and track in a list of open requests. The placeholder is a perfect example — it is concise, specific and immediately understandable. The single-line text input enforces brevity.

Data collected here will be a short text string that serves as the request title. This data is used in dashboards, email subject lines, work order headers and status reports. The data quality is critical — a well-written summary enables quick triage and prioritization. The placeholder example sets a high standard for clarity and specificity.

For user experience, this mandatory field is quick to complete and immediately useful. Users understand the importance of a clear title, especially when the form explicitly states this becomes the request title. The single-line constraint prevents overly long summaries that would be unwieldy in list views. This is a well-designed field that balances brevity with informativeness.

Question: Full description of the problem

The question Full description of the problem is the narrative heart of the maintenance request. It allows the requester to describe the issue in their own words, including what they observed, when it started, how it has changed and any other relevant details. This free-text description is often the most valuable piece of information for the maintenance team in diagnosing the problem.

Making this field mandatory is essential. A maintenance request without a description is essentially useless — the team cannot diagnose or prioritize an issue they know nothing about. The placeholder is an outstanding example that demonstrates the level of detail expected — it includes timing, behavior, triggers and current mitigation. The multiline text input provides ample space.

Data collected here will be free-text narrative content. The quality of data varies significantly based on the user's descriptive ability and attention to detail. The excellent placeholder example sets a high standard and encourages thorough responses. This field is the primary source of diagnostic information and directly impacts the quality of the maintenance response.

From a user experience standpoint, this mandatory field requires more effort than simple dropdowns or checkboxes, but it is absolutely necessary. The multiline text input provides ample space for detailed descriptions. The explanatory paragraph at the top of the section guides users to provide sensory details that are invaluable for diagnosis. The mandatory status is well-justified.

Question: Which symptoms are you experiencing? (select all that apply)

The question Which symptoms are you experiencing? uses a multiple-choice checklist to capture the observable symptoms of the issue. This structured approach to symptom identification is highly effective — it ensures that common symptoms are not overlooked and provides the maintenance team with a quick diagnostic overview.

The 12-option checklist covers a comprehensive range of symptoms: visible damage, leaks, unusual noise, unusual smell, power loss, water/heating/cooling loss, reduced performance, error messages, vibration, pest activity, mould/air quality and None of the above. The conditional follow-ups for specific symptoms are particularly well-designed — they ask for detailed descriptions that are critical for diagnosis.

Data collected here will be a set of categorical selections plus conditional text fields. This structured data enables automated triage and routing — for example, an unusual burning smell could trigger an immediate safety escalation. The data quality is high because the options are clearly defined and the follow-ups capture specific details.

For user experience, this checklist is comprehensive yet manageable. The None of the above option prevents forcing users to select irrelevant symptoms. The conditional follow-ups are relevant and only shown when needed. The question's placement after the description fields creates a natural flow from narrative to structured symptom identification.

Question: When did you first notice the problem?

The question When did you first notice the problem? captures the onset date and time of the issue. This temporal information is critical for understanding the duration of the problem, identifying patterns and assessing urgency — a problem that started 5 minutes ago may be treated differently from one that has persisted for 5 weeks.

Making this field mandatory is a sound decision. The date/time input type is appropriate and ensures structured data capture. Without this information, the maintenance team cannot assess the age of the problem or identify trends.

Data collected here will be a date/time value. This data supports trend analysis, SLA tracking and root cause investigation. The data quality is generally high — users typically know when they first noticed a problem, though there may be some imprecision for gradual issues.

For user experience, this mandatory field is straightforward. The date/time picker reduces formatting errors and ensures consistency. The mandatory status is well-justified — temporal context is essential for effective triage and prioritization.

Question: How is the problem behaving over time?

The question How is the problem behaving over time? captures the trajectory of the issue — whether it is constant, intermittent, one-time, worsening, improving or condition-dependent. This behavioral information is invaluable for diagnosis and prioritization. A progressively worsening problem may require more urgent attention than a stable one.

The single-choice format with six options covers the key behavioral patterns. The conditional follow-up for Only happens under specific conditions asks for the triggers, which is critical for diagnosis. The option descriptions are clear and unambiguous.

Data collected here will be a categorical selection plus conditional text. This data supports diagnostic reasoning and prioritization. For example, Getting progressively worse could trigger a higher priority rating. The data quality is high due to the clear option definitions.

For user experience, this question is clear and easy to answer. The options are mutually exclusive and cover the main scenarios. The conditional follow-up is relevant and only shown when needed. The question's placement after the onset date creates a natural temporal narrative.

Question: Is the problem still happening right now?

The question Is the problem still happening right now? captures the current status of the issue. This is operationally critical — if the problem is ongoing, the maintenance team may need to take immediate action. If it has stopped, the team can plan a diagnostic visit without the same level of urgency.

The yes/no format with intelligent follow-ups is highly effective. If Yes, the form asks how quickly the situation is changing. If No, the form asks when it stopped and what changed. These follow-ups provide crucial context for the maintenance team's response strategy.

Data collected here will be a boolean selection plus conditional text or choice fields. This data directly affects the urgency and response strategy. The data quality is high because the follow-ups capture specific, actionable details.

For user experience, this question is clear and timely. The conditional follow-ups are relevant and only shown when needed. The question's placement within the issue behavior block creates a logical flow from onset to behavior to current status.

Question: Has any temporary fix, workaround or repair already been attempted?

The question Has any temporary fix, workaround or repair already been attempted? captures whether any interim measures have been taken. This is important because it prevents the maintenance team from duplicating work, provides diagnostic clues and helps assess whether the temporary fix is sufficient or if permanent repair is needed.

The yes/no format with follow-ups is well-designed. If Yes, the form asks what was done, by whom and whether it helped. If No, a checkbox confirms that the area has been left untouched for inspection. These follow-ups provide valuable diagnostic and operational context.

Data collected here will be a boolean selection plus conditional text fields or a checkbox. This data supports diagnostic reasoning and prevents redundant work. The data quality is high because the follow-ups capture specific details about the temporary fix.

For user experience, this question is practical and relevant. The conditional follow-ups are natural and only shown when needed. The checkbox in the No branch is a thoughtful touch that encourages users to preserve the original condition for inspection.

Question: How severe is the impact on your work or the site?

The question How severe is the impact on your work or the site? uses a 5-point digit rating scale to capture the subjective severity of the issue. This is a critical input for the priority scoring formula. Severity directly influences how quickly the maintenance team responds and what resources are allocated.

Making this field mandatory is essential. Severity is one of the three key inputs to the priority calculation, and without it, the request cannot be properly prioritized. The scale anchors are clear and help users calibrate their rating. The digit rating input type is appropriate for this quantitative assessment.

Data collected here will be a numeric value from 1 to 5. This data feeds directly into the priority scoring algorithm and enables consistent, data-driven prioritization across all requests. The data quality is inherently subjective but the clear scale anchors improve consistency.

For user experience, this mandatory field is quick and intuitive. The 5-point scale is a familiar format that most users can complete in seconds. The clear anchors reduce ambiguity. The mandatory status is well-justified — severity is essential for fair and effective prioritization.

Question: How many people are affected by this issue?

The question How many people are affected by this issue? captures the scale of the impact. An issue affecting one person is very different from one affecting an entire department of 50 people. This information helps the maintenance team understand the breadth of the impact and prioritize accordingly.

This field is optional and uses a numeric input. The placeholder is clear and concise. The optional status is reasonable — not all users will know the exact number of affected people, especially for issues in shared or public areas.

Data collected here will be a numeric value. This data supports impact assessment and prioritization. Combined with the severity rating, it provides a more complete picture of the issue's impact. The data quality is inherently approximate but still valuable.

For user experience, this optional field is quick and easy to complete. The numeric input prevents formatting issues. The optional status prevents frustration for users who do not know the exact number.

Question: Is normal work, production or site operations being interrupted?

The question Is normal work, production or site operations being interrupted? captures whether the issue is causing operational disruption. This is a critical factor in prioritization — an issue that halts production is far more urgent than one that is merely inconvenient. This question also feeds into the Impact component of the priority scoring formula.

The yes/no format with a follow-up asking for specific activities interrupted and operational impact is highly effective. The placeholder is an excellent example that quantifies the impact, enabling cost-benefit analysis of the repair.

Data collected here will be a boolean selection plus conditional text. This data directly affects prioritization and resource allocation. The data quality is high because the follow-up captures specific, quantifiable impact details.

For user experience, this question is clear and operationally relevant. The conditional follow-up is natural and only shown when needed. The question's placement within the impact assessment block creates a logical flow from severity to people affected to operational interruption.

Question: Priority score equation

The equation element displaying P = S x U x I (Priority = Severity x Urgency x Impact) is a transparent and educational design choice. Rather than hiding the prioritization logic in a black box, the form explains to the requester how their inputs are used to calculate the priority score. This transparency builds trust and helps users understand why certain requests are prioritized over others.

This element is informational rather than interactive — it does not collect data but rather explains the methodology. The use of KaTeX for mathematical formatting is a professional touch that enhances readability. The equation is simple and intuitive, making it accessible to users without mathematical expertise.

From a data perspective, this element does not collect data but provides context for the data collected in the severity, urgency and impact fields. It helps users understand the importance of providing accurate ratings in those fields.

For user experience, this equation is a positive addition that demystifies the prioritization process. It is placed at the end of the issue description section, after the severity and impact fields, which is the perfect timing. This transparency enhances trust and engagement.

Section: Safety, Hazards & Risk Assessment

Question: Does this issue pose an immediate safety or health risk to people?

The question Does this issue pose an immediate safety or health risk to people? is arguably the most critical question in the entire form. Safety is the paramount concern in any facilities management operation, and identifying immediate risks enables the maintenance team to take emergency action, escalate to safety officers and prioritize the request above all others.

Making this field mandatory is absolutely essential. The yes/no format with comprehensive follow-ups is excellently designed. If Yes, the form presents a 9-option multiple-choice checklist of risk types with a conditional follow-up for hazardous substances. If No, a checkbox confirms the area is safe for normal access. This conditional logic ensures that safety risks are thoroughly documented.

Data collected here will be a boolean selection plus conditional multiple-choice and text fields. This data triggers safety protocols, emergency responses and priority escalation. The data quality is critical — inaccurate safety information could lead to injuries or fatalities. The comprehensive risk type checklist ensures that common hazards are not overlooked.

From a user experience standpoint, this question is placed prominently within a dedicated safety section, with a clear warning paragraph at the top advising users to contact emergency services if anyone is in immediate danger. This framing emphasizes the importance of safety and guides users on what to do in emergencies. The mandatory status is non-negotiable.

Question: Which hazards should the maintenance team be warned about? (select all that apply)

The question Which hazards should the maintenance team be warned about? uses a 12-option multiple-choice checklist to capture specific hazards present in the work area. This information is essential for the safety planning of the maintenance visit — technicians need to know about live electrical components, chemical spills, asbestos, confined spaces and other hazards before they arrive on site.

The checklist covers a comprehensive range of hazards: electrical, water/electrical proximity, chemical spillage, asbestos, dust/silica, mould, working at height, confined space, heavy lifting, noise, moving vehicles and No special hazards identified. This breadth ensures that the most common workplace hazards are captured.

Data collected here will be a set of categorical selections. This data directly informs the safety planning, PPE requirements and permit-to-work needs for the maintenance visit. The data quality is high because the options are clearly defined and cover the major hazard categories.

For user experience, this checklist is comprehensive yet manageable. The No special hazards identified option prevents forcing users to select irrelevant hazards. The question's placement within the safety section is logical and follows the immediate risk question, creating a flow from is there danger to what specific hazards exist.

Question: Has the area been isolated, cordoned off or taken out of service?

The question Has the area been isolated, cordoned off or taken out of service? captures whether safety measures have already been implemented. This is critical for the maintenance team to understand the current state of the work area and plan accordingly. An already-isolated area may be ready for immediate work, while an unisolated area may need isolation before any inspection.

The yes/no format with intelligent follow-ups is highly effective. If Yes, the form asks for details of the isolation measures and who applied them. If No, the form asks whether the area should be isolated before work begins, with options ranging from isolate immediately to not sure. This conditional logic ensures that isolation needs are properly assessed.

Data collected here will be a boolean selection plus conditional text or choice fields. This data directly affects the safety planning and scheduling of the maintenance visit. The data quality is high because the follow-ups capture specific, actionable details.

For user experience, this question is practical and safety-focused. The conditional follow-ups are relevant and only shown when needed. The Not sure option in the No branch is a thoughtful touch that allows users to defer to the maintenance team's expertise.

Question: What personal protective equipment (PPE) is mandatory in this area?

The question What personal protective equipment (PPE) is mandatory in this area? captures the PPE requirements for the work area. This is essential for the safety of maintenance personnel — they need to know what protective equipment to bring and wear before entering the area. Incorrect or missing PPE can lead to serious injuries.

The multiple-choice checklist covers the most common PPE items: hard hat, safety glasses, high-vis clothing, safety boots, hearing protection, gloves, respiratory protection, fall-arrest harness and Standard office attire only. This comprehensive list covers the PPE needs of most industrial and commercial environments.

Data collected here will be a set of categorical selections. This data directly informs the preparation of maintenance personnel and the safety planning for the visit. The data quality is high because the options are clearly defined.

For user experience, this checklist is clear and easy to complete. The Standard office attire only option is a helpful inclusion for office environments where no special PPE is needed. The question's placement within the safety section is logical and follows the hazard identification questions.

Question: Is a permit-to-work or formal risk assessment required before repairs start?

The question Is a permit-to-work or formal risk assessment required before repairs start? captures whether formal safety documentation is needed before work can begin. In many organizations, certain types of work require permits or risk assessments. Knowing this in advance prevents delays and ensures compliance with safety regulations.

The yes/no format with a follow-up asking for the responsible person is effective. If Yes, the form asks who is responsible for issuing the permit or risk assessment. This information enables the maintenance team to coordinate with the appropriate safety personnel before scheduling the work.

Data collected here will be a boolean selection plus conditional text. This data directly affects the scheduling and compliance requirements for the maintenance visit. The data quality is high because the follow-up captures specific responsibility information.

For user experience, this question is clear and compliance-focused. The conditional follow-up is natural and only shown when needed. The question's placement at the end of the safety section is logical — it addresses the formal documentation requirements after the physical hazards have been identified.

Question: I confirm that the hazard information provided above is accurate to the best of my knowledge

The checkbox I confirm that the hazard information provided above is accurate to the best of my knowledge serves as a declaration of accuracy for the safety information provided. This is important for legal and compliance purposes — it establishes that the requester has made a good-faith effort to provide accurate hazard information, which protects both the organization and the maintenance personnel.

The checkbox format is appropriate for this declaration. It is a simple, binary confirmation that does not require additional input. The wording to the best of my knowledge is a legally appropriate qualifier that acknowledges the possibility of unknown hazards.

Data collected here will be a boolean confirmation. This data serves as a legal record of the requester's attestation to the accuracy of the safety information. The data quality is inherently dependent on the user's honesty and awareness.

For user experience, this checkbox is quick and straightforward. It is placed at the end of the safety section, after all hazard information has been provided, which is the logical position for a confirmation. The checkbox format is familiar and low-friction.

Section: Evidence, Photos & Supporting Documents

Question: Photo of the fault or damage (close-up)

The question Photo of the fault or damage (close-up) requires the requester to upload a close-up photograph of the issue. Visual evidence is one of the most powerful diagnostic tools in facilities management — a clear photo can convey more information than paragraphs of text and enables remote diagnosis, reducing the need for initial site visits.

Making this field mandatory is an excellent decision. A close-up photo of the fault is the single most valuable piece of evidence for diagnosis. The image upload input type is appropriate and modern. The instruction to provide a close-up ensures the photo captures the relevant detail.

Data collected here will be an image file. This data supports remote diagnosis, documentation, insurance claims and trend analysis. The data quality depends on the user's photography skills and the clarity of the image. The form's introductory paragraph provides helpful guidance on taking clear photos.

For user experience, this mandatory field is straightforward — most users have a smartphone camera and can take a photo quickly. The mandatory status is well-justified — visual evidence dramatically improves the quality and speed of the maintenance response. The image upload interface is familiar and intuitive.

Question: Photo showing the wider area and surroundings

The question Photo showing the wider area and surroundings complements the close-up photo by providing context. A wider shot helps the maintenance team understand the environment around the fault — nearby equipment, access constraints, safety hazards and the general layout of the area.

This field is optional, which is reasonable — the close-up photo is the primary evidence, and the wider shot is supplementary. The image upload input type is appropriate. The form's introductory paragraph encourages both types of photos, which is helpful guidance.

Data collected here will be an image file. This data provides contextual information that supports planning and preparation for the maintenance visit. The data quality depends on the user's photography and the relevance of the wider shot.

For user experience, this optional field is easy to complete for users who have already taken a close-up photo. The optional status prevents friction for users who may only have one photo available. The question's placement immediately after the close-up photo creates a logical photo documentation block.

Question: Photo of any asset nameplate, serial number or warning label

The question Photo of any asset nameplate, serial number or warning label captures visual identification of the affected equipment. Nameplates and serial numbers are often difficult to read from text descriptions but are clearly visible in photos. This evidence supports parts ordering, warranty claims and asset tracking.

This field is optional, which is appropriate — not all issues involve equipment with nameplates. The image upload input type is suitable. The question's specificity guides users to take the right kind of photo.

Data collected here will be an image file. This data supports asset identification, parts ordering and warranty verification. The data quality depends on the legibility of the nameplate in the photo.

For user experience, this optional field is quick to complete for users with equipment issues. The optional status prevents friction for non-equipment issues. The question's placement within the evidence section is logical and follows the fault photos.

Question: Supporting documents (inspection reports, manuals, invoices, previous work orders, screenshots)

The question Supporting documents allows the requester to upload any relevant documentation — inspection reports, manuals, invoices, previous work orders or screenshots. This supplementary evidence can provide valuable context that photos alone cannot capture, such as technical specifications, maintenance history or error logs.

This field is optional, which is appropriate — not all requests will have supporting documents. The file upload input type is versatile and accommodates various document formats. The question text lists specific examples of useful documents, which guides users on what to upload.

Data collected here will be one or more document files. This data supports diagnosis, parts ordering, warranty claims and historical analysis. The data quality varies based on the relevance and completeness of the uploaded documents.

For user experience, this optional field is flexible and non-intrusive. Users can upload as many or as few documents as they have. The clear examples in the question text help users understand what kind of documents are useful. The question's placement within the evidence section is logical.

Question: Video or audio recording of the fault (if it makes noise or moves)

The question Video or audio recording of the fault captures dynamic evidence that static photos cannot. For issues involving unusual noises, vibrations or movements, a video or audio recording can be invaluable for diagnosis — a technician can hear the grinding noise or see the vibration pattern without being on site.

This field is optional, which is appropriate — not all issues produce noise or movement. The file upload input type accommodates video and audio files. The parenthetical qualifier is a helpful guide on when this field is relevant.

Data collected here will be a video or audio file. This data supports remote diagnosis of dynamic issues and can be shared with specialist technicians for expert opinion. The data quality depends on the clarity and relevance of the recording.

For user experience, this optional field is relevant for specific types of issues. The optional status prevents friction for static issues. The question's placement within the evidence section is logical and follows the photo uploads.

Question: I confirm that images and files uploaded relate to this request and do not contain unrelated confidential information

The checkbox I confirm that images and files uploaded relate to this request and do not contain unrelated confidential information serves as a data privacy and relevance declaration. This is important for protecting the organization's confidential information and ensuring that the uploaded evidence is relevant to the request.

The checkbox format is appropriate for this declaration. It addresses two concerns: relevance and confidentiality. This dual-purpose declaration is efficient and comprehensive.

Data collected here will be a boolean confirmation. This data serves as a legal record of the requester's attestation and protects the organization from inadvertent data breaches through file uploads.

For user experience, this checkbox is quick and straightforward. It is placed after all file uploads, which is the logical position for a confirmation about uploaded content. The checkbox format is familiar and low-friction.

Question: Has this issue (or a similar one) been reported before?

The question Has this issue (or a similar one) been reported before? captures whether the issue is recurring. Recurring issues may indicate systemic problems that require more than a simple repair — they may need root cause analysis, capital investment or process changes. This question also helps prevent duplicate requests and enables the maintenance team to link related issues.

The yes/no format with follow-ups is well-designed. If Yes, the form asks for previous request numbers, dates and what was done. If No, a checkbox confirms this is the first occurrence. These follow-ups provide valuable historical context.

Data collected here will be a boolean selection plus conditional text fields or a checkbox. This data supports trend analysis, root cause investigation and duplicate detection. The data quality is high because the follow-ups capture specific historical details.

For user experience, this question is clear and relevant. The conditional follow-ups are natural and only shown when needed. The question's placement at the end of the evidence section is logical — it addresses historical context after the current evidence has been provided.

Question: Log of previous related requests (table)

The table Log of previous related requests provides a structured format for recording the history of related maintenance requests. The table includes columns for request/ticket number, date reported, short description, outcome/status and whether it was fully resolved. The pre-populated example rows demonstrate the expected format and level of detail.

This table element is optional and provides a comprehensive historical record. The structured format enables easy comparison and trend analysis. The pre-populated example rows are excellent examples that show how to fill in the table with specific dates, descriptions and outcomes.

Data collected here will be structured tabular data. This data supports root cause analysis, trend identification and maintenance planning. The data quality depends on the accuracy of the historical records provided by the user.

For user experience, the table format is clear and organized. The pre-populated examples reduce ambiguity and set expectations. The optional status prevents friction for first-time issues. The question's placement after the Has this issue been reported before question creates a logical flow from general to specific historical information.

Section: Urgency, Impact & Business Continuity

Question: What level of urgency do you believe this request has?

The question What level of urgency do you believe this request has? captures the requester's assessment of the urgency level. This is a critical input for the priority scoring formula and directly influences the response time and resource allocation for the request. The requester's perspective on urgency is valuable because they are closest to the operational impact.

Making this field mandatory is essential. Urgency is one of the three key inputs to the priority calculation. The 5-level scale with clear descriptions for each level is excellent — it helps users calibrate their assessment. The conditional follow-ups for Emergency and Urgent are particularly well-designed.

Data collected here will be a categorical selection plus conditional text fields. This data directly feeds into the priority scoring algorithm and enables consistent, data-driven prioritization. The data quality is inherently subjective but the clear level descriptions improve consistency.

For user experience, this mandatory field is clear and important. The level descriptions help users make informed assessments. The conditional follow-ups are relevant and only shown when needed. The mandatory status is well-justified — urgency is essential for effective prioritization.

Question: How much does this issue affect day-to-day operations?

The question How much does this issue affect day-to-day operations? uses a 5-point rating scale to capture the operational impact of the issue. This is distinct from the severity rating — severity measures how bad the problem is for the individual, while operational impact measures how much it disrupts the organization's activities.

The rating scale with clear anchors covering the full spectrum from no effect to operations halted is well-designed. The scale covers the full range of operational impact scenarios.

Data collected here will be a categorical rating. This data supports prioritization and resource allocation. Combined with the severity and urgency ratings, it provides a comprehensive impact assessment. The data quality is inherently subjective but the clear anchors improve consistency.

For user experience, this question is clear and easy to answer. The rating scale is familiar and the anchors are unambiguous. The question's placement within the urgency and impact section is logical.

Question: Is there a deadline, audit, inspection or event that makes timely repair critical?

The question Is there a deadline, audit, inspection or event that makes timely repair critical? captures external time pressures that may not be apparent from the severity or urgency ratings. A regulatory audit, safety inspection or client visit may create a hard deadline that dramatically increases the urgency of the repair.

The yes/no format with a follow-up asking for details of the deadline and its date is effective. The placeholder is an excellent example that shows the kind of context needed for deadline-driven scheduling.

Data collected here will be a boolean selection plus conditional text. This data supports deadline-driven scheduling and prioritization. The data quality is high because the follow-up captures specific deadline details.

For user experience, this question is clear and relevant. The conditional follow-up is natural and only shown when needed. The question's placement within the urgency section is logical — it addresses external time pressures after the internal urgency assessment.

Question: Is there a workaround or alternative area your team can use meanwhile?

The question Is there a workaround or alternative area your team can use meanwhile? captures whether the affected team has alternative arrangements. If a workaround exists, the urgency may be lower. If no workaround exists, the issue may require more immediate attention.

The yes/no format with intelligent follow-ups is well-designed. If Yes, the form asks for details of the workaround and how long it can be sustained. If No, the form asks what support is needed. These follow-ups provide actionable information for interim support planning.

Data collected here will be a boolean selection plus conditional text or choice fields. This data supports interim support planning and urgency assessment. The data quality is high because the follow-ups capture specific, actionable details.

For user experience, this question is practical and empathetic — it acknowledges that the issue affects real people and asks how to support them in the interim. The conditional follow-ups are relevant and only shown when needed. The question's placement within the business continuity section is logical.

Question: Matrix rating — impact statements

The matrix rating Please rate the following statements about the impact of this issue uses a 5-point agreement scale to capture the requester's assessment of five impact dimensions: safety risk, output quality, cost, comfort/wellbeing and professional appearance. This multi-dimensional assessment provides a nuanced understanding of the issue's impact beyond simple severity ratings.

The five sub-questions cover the key impact dimensions in a facilities management context. The 5-point agreement scale is a standard and well-understood format. The matrix layout is efficient — it allows users to rate multiple statements in a compact format.

Data collected here will be a set of ordinal ratings across five dimensions. This data supports multi-dimensional impact analysis and prioritization. The data quality is inherently subjective but the structured format enables comparison and analysis.

For user experience, the matrix rating is efficient and familiar. However, matrix questions can be cognitively demanding — users must evaluate five statements simultaneously. The clear statement wording and standard scale help mitigate this. The question's placement at the end of the urgency and impact section is logical.

Section: Preferred Solution, Scheduling & Access Times

Question: Please rank the following resolution approaches in order of your preference

The question Please rank the following resolution approaches in order of your preference uses a ranking format to capture the requester's preferred approach to resolving the issue. This is valuable because it provides insight into the requester's priorities — do they want a permanent fix, a quick temporary solution or just an inspection first.

The five ranking items cover the main resolution approaches: permanent repair, full replacement, temporary fix, relocation and inspection/advice. The ranking format forces users to prioritize, which provides more nuanced data than a simple selection.

Data collected here will be an ordered list of preferences. This data supports solution planning and helps the maintenance team understand the requester's expectations. The data quality is high because the ranking format captures relative preferences.

For user experience, the ranking format is engaging and thought-provoking. It encourages users to think about their preferred outcome. However, ranking can be slightly more complex than simple selection. The question's placement at the top of the scheduling section is logical — it addresses the what before the when.

Question: Preferred date for the first inspection or repair visit

The question Preferred date for the first inspection or repair visit captures the requester's preferred date for the maintenance visit. This information helps the scheduling team coordinate the visit with the requester's availability and operational needs.

This field is optional and uses a date input. The optional status is appropriate — the maintenance team may not always be able to accommodate the preferred date, and some users may have no preference. The date input type ensures structured data capture.

Data collected here will be a date value. This data supports scheduling and coordination. The data quality is high because the date picker ensures a valid date format.

For user experience, this optional field is quick and easy to complete. The date picker is familiar and intuitive. The optional status prevents friction for users who are flexible on timing.

Question: Preferred time window for the visit

The question Preferred time window for the visit captures the requester's preferred time of day for the maintenance visit. This is important for coordinating with the requester's schedule and minimizing disruption to their work.

The single-choice format with seven options covers a comprehensive range of time windows, from early morning to overnight, plus any time and no preference. This flexibility accommodates various work schedules and shift patterns.

Data collected here will be a categorical selection. This data supports scheduling optimization. The data quality is high because the options are clearly defined.

For user experience, this question is clear and easy to answer. The comprehensive options cover most scheduling scenarios. The No preference option prevents forcing a choice on flexible users.

Question: Earliest date the area can be made available for work

The question Earliest date the area can be made available for work captures the earliest date when the affected area can be accessed for maintenance. This is distinct from the preferred date — it represents a hard constraint based on operational availability.

This field is optional and uses a date input. The optional status is appropriate — some areas may be available immediately, while others may have scheduling constraints. The date input ensures structured data capture.

Data collected here will be a date value. This data supports scheduling constraints and helps the maintenance team plan around operational availability. The data quality is high because the date picker ensures a valid date format.

For user experience, this optional field is quick and easy to complete. The question's placement after the preferred date creates a logical scheduling block.

Question: Can the work be carried out outside normal working hours?

The question Can the work be carried out outside normal working hours? captures whether out-of-hours work is possible. This is important for minimizing disruption to normal operations and for scheduling flexibility.

The yes/no format with follow-ups is well-designed. If Yes, the form asks which out-of-hours windows are acceptable. If No, the form asks for an explanation of the restriction. These follow-ups provide specific scheduling constraints.

Data collected here will be a boolean selection plus conditional text. This data supports scheduling optimization and helps the maintenance team plan work during less disruptive times. The data quality is high because the follow-ups capture specific constraints.

For user experience, this question is practical and relevant. The conditional follow-ups are natural and only shown when needed. The question's placement within the scheduling section is logical.

Question: Would you like to be present while the work is carried out?

The question Would you like to be present while the work is carried out? captures whether the requester wants to be on site during the maintenance work. This is important for coordination — if the requester wants to be present, the visit must be scheduled around their availability.

The yes/no format with a follow-up asking for availability is effective. If Yes, the form asks for specific availability details. This conditional logic ensures that scheduling constraints are captured.

Data collected here will be a boolean selection plus conditional text. This data supports scheduling coordination. The data quality is high because the follow-up captures specific availability details.

For user experience, this question is considerate and user-focused. It acknowledges that some users want to oversee the work while others prefer to delegate. The conditional follow-up is natural and only shown when needed.

Question: Are there any special arrangements needed on the day of the visit?

The question Are there any special arrangements needed on the day of the visit? uses a multiple-choice checklist to capture logistical requirements for the maintenance visit. This is essential for ensuring that the visit goes smoothly — the maintenance team needs to know about parking, loading dock access, security escorts, noise restrictions and other logistical needs.

The 8-option checklist covers the most common special arrangements: parking, loading dock/freight lift, security escort, noise/dust restrictions, work stoppage in adjacent areas, parts delivery scheduling, interpreter assistance and No special arrangements needed. This comprehensive list covers the major logistical considerations.

Data collected here will be a set of categorical selections. This data supports visit planning and logistics coordination. The data quality is high because the options are clearly defined.

For user experience, this checklist is comprehensive yet manageable. The No special arrangements needed option prevents forcing users to select irrelevant arrangements. The question's placement at the end of the scheduling section is logical.

Question: On-site contact person if you are unavailable

The question On-site contact person if you are unavailable captures an alternative contact for the maintenance visit. This is important for ensuring that someone is available to provide access, answer questions and oversee the work if the primary requester is not present.

This field is optional and uses a single-line text input. The placeholder provides a clear example of the expected format including name, role and phone number. The optional status is appropriate — not all users will have an alternative contact.

Data collected here will be a contact information string. This data supports visit coordination and ensures continuity of access. The data quality depends on the completeness of the contact information provided.

For user experience, this optional field is practical and helpful. The clear placeholder reduces ambiguity. The question's placement at the end of the scheduling section is logical — it addresses the who after the when and how have been established.

Section: Cost Estimate, Budget & Approval

Question: Is there an existing work order, project code or budget allocated for this repair?

The question Is there an existing work order, project code or budget allocated for this repair? captures whether financial provisions already exist for the repair. This is important for streamlining the approval process — if a budget is already allocated, the repair can proceed without additional financial approval.

The yes/no format with follow-ups is well-designed. If Yes, the form asks for the work order/project/budget code. If No, the form asks who should approve the expenditure. These follow-ups ensure that the financial routing is clear regardless of the answer.

Data collected here will be a boolean selection plus conditional text or choice fields. This data supports financial processing and approval routing. The data quality is high because the follow-ups capture specific financial identifiers or approval contacts.

For user experience, this question is financially relevant and practical. The conditional follow-ups are natural and only shown when needed. The question's placement at the top of the cost section is logical — it addresses the financial framework before specific cost details.

Question: Cost centre, department or client account to be charged

The question Cost centre, department or client account to be charged captures the financial account to which the repair costs should be allocated. This is essential for accurate cost tracking, budgeting and financial reporting.

This field is optional and uses a single-line text input. The placeholder provides a clear example of the expected format. The optional status is appropriate — not all users will know the specific cost centre code.

Data collected here will be a cost centre/account identifier string. This data supports financial allocation and reporting. The data quality depends on the user's knowledge of the financial coding system.

For user experience, this optional field is straightforward for users who know their cost centre. The optional status prevents friction for those who do not. The question's placement within the cost section is logical.