Use this form to request any change to a server room, comms room, rack, or supporting critical infrastructure such as power distribution, cooling, fire detection, cabling, or physical security. Please answer as completely as you can. Wording here is descriptive only and does not replace any site procedures, permits, or reviews that may apply in your building or region.
Request reference or ticket number (if assigned)
Date of request
Requestor full name
Job title or role
Company or tenant organisation
Email address
Phone number
Is someone else acting as the technical contact for this work?
Technical contact name and how to reach them
All questions about this request will be directed to the requestor named above.
Building or site name
Floor, suite, or room identifier
What type of space is affected?
Dedicated tenant server room
Shared or multi-tenant comms room
Rack or cabinet within a larger data hall
Telecommunications or patch room
Other (please describe)
Please describe the space:
Affected rack, cabinet, or panel identifiers
Does the work require access to areas outside this room (for example risers, corridors, plant rooms, or roof space)?
Please list the additional areas and why access is needed:
Which categories of work are included? Select all that apply.
Rack installation, removal, or repositioning
Server, storage, or appliance installation or removal
Power distribution changes (outlets, PDUs, UPS, feeders)
Cooling or airflow changes (units, containment, venting)
Structured cabling or fibre work
Network hardware or patching changes
Fire detection or suppression related work
Physical security changes (locks, badges, cameras, cages)
Monitoring, sensors, or environmental alarms
Structural work (flooring, ceiling, walls, seismic restraint)
Other (please describe)
Please describe the other work:
Describe the alteration in plain language, including what will be added, moved, removed, or modified
How would you classify the scale of this change?
Minor — no service interruption expected
Moderate — brief interruption contained to a small number of systems
Major — significant interruption or room-level impact expected
Not sure yet — assessment needed
Will any existing equipment be permanently removed or decommissioned?
Please list the equipment being removed and how it will be disposed of or returned:
List the main items being installed or changed. Estimated power figures help reviewers understand the effect on existing capacity; please use nameplate or vendor figures where available.
Planned equipment and estimated load
Item or device | Make/model or description | Qty | Est. watts per unit | Total watts | Target rack or location | ||
|---|---|---|---|---|---|---|---|
A | B | C | D | E | F | ||
1 | Rack enclosure | 42U standard rack with front/rear doors | 2 | 0.0 | 0.0 | North wall, positions 1-2 | |
2 | Rack PDU | Vertical metered PDU, 16A | 2 | 3680.0 | 7360.0 | R04, R05 | |
3 | Network switch | 48-port access switch | 2 | 150.0 | 300.0 | R04 U32, R05 U32 | |
4 | 0.0 | ||||||
5 | 0.0 | ||||||
6 | 0.0 | ||||||
7 | 0.0 | ||||||
8 | 0.0 | ||||||
9 | 0.0 | ||||||
10 | 0.0 |
Total estimated additional power draw (watts)
Total estimated additional heat output (BTU per hour), if known
Is the existing power provision sufficient for the planned change?
Please explain how capacity was confirmed (for example a recent load survey or vendor calculation):
Please describe the additional power provision you believe is required:
What supply arrangement is expected?
Single supply
Dual supply from separate sources
Single supply with local UPS support
Dual supply with UPS support on one or both paths
Unsure — guidance requested
Is the existing cooling provision expected to handle the additional heat load?
Please explain how cooling suitability was assessed:
Please describe the cooling support you believe is required:
Will the change affect airflow containment, hot/cold aisle arrangement, or floor tiles?
Please describe the airflow or floor changes involved:
Which environmental conditions should be monitored or reported during the work? Select all that apply.
Temperature
Humidity
Water or leak detection
Smoke or fire detection status
Door or access events
Power quality or load
None expected to be affected
What cabling work is planned?
No cabling work
New copper patching only
New structured copper cabling
New fibre cabling (single-mode)
New fibre cabling (multi-mode)
Mixed copper and fibre work
Removal or rerouting of existing cabling
Approximate number of new cable runs
Will the work require any interruption to live network services?
Please describe the affected services, expected duration of interruption, and how it will be communicated:
Does the change involve any external carrier, service provider, or third-party cabling?
Please name the provider and the work they will perform:
Describe how the work will be carried out safely and how live services will be protected. This information is used for planning and review purposes only.
Outline the working method, including sequence of steps and any isolation or switching steps
Which hazards or sensitivities should reviewers be aware of? Select all that apply.
Live electrical work or energised panels
Working at height (ladders, lifts, ceiling access)
Manual handling or heavy items
Hot works (drilling, cutting, welding)
Dust, debris, or contamination risk to equipment
Noise affecting nearby occupants
Restricted or confined space
Work near fire detection or suppression systems
None of the above expected
Will any live production systems be at risk during the work?
Please identify the systems at risk and the safeguards or fallback arrangements planned:
Is a rollback or restoration plan available if the change cannot be completed as intended?
Please summarise the rollback plan:
Please explain how a partial or failed change would be handled:
Upload supporting documents (method statement, risk assessment, layout drawing, product data, or photos)
Requested start date
Requested completion date
Preferred working window
Standard business hours
Outside standard business hours
Overnight window
Weekend window
Flexible — please advise what is available
Estimated on-site duration (hours)
Number of people expected on site
Will contractors or third-party personnel attend?
Please provide the company name, number of attendees, and any induction or access arrangements they will need:
Does the work require deliveries, hoisting, or use of loading areas?
Please describe the delivery items, timing, and route or loading area needed:
What support is needed from building or facilities staff? Select all that apply.
Escort or supervised access
Permit or access pass issue
Power isolation or switching support
Delivery or waste removal assistance
Out-of-hours security cover
Temporary cooling or ventilation
No support required
Has this work been reviewed internally by your own IT or facilities team?
Who reviewed it and when?
Please consider an internal review before the work proceeds so that any internal requirements are captured early.
Are there any dependencies on other projects, vendors, or scheduled works?
Please list the dependencies and their expected dates:
Will the alteration affect any shared or multi-tenant systems?
Please describe the shared systems affected and how other parties will be notified:
Estimated cost of the alteration, if known
Any additional notes, constraints, or questions for the reviewer
By submitting this form, you confirm that the details provided are accurate to the best of your knowledge and that you will share any further information requested to help assess the request. Submission does not by itself authorise work to begin; please wait for written confirmation before proceeding.
I confirm the information provided is accurate and complete to the best of my knowledge
I understand that the requested work should not begin until the relevant approval or confirmation has been received
Typed full name (as signature)
Signature
Date signed
Analysis for Tenant IT Server Room & Critical Infrastructure Alteration 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 form is designed to collect structured information from tenants or occupants who wish to make alterations to server rooms, comms rooms, racks, or other critical IT infrastructure within a building. The form covers a broad but well-organized scope: requestor identification, site and room details, nature of the proposed work, equipment and load estimates, power and cooling considerations, cabling and connectivity, risk and working method, scheduling and access, impact and dependencies, and a declaration section. The form is described as short, and while it is comprehensive in coverage, the use of conditional follow-ups, clear section headings, and practical placeholder examples help keep the respondent experience manageable.
This opening section sets expectations by explaining what the form is for and clarifying that submission does not replace any site procedures, permits, or reviews that may apply. This is a strong design choice because it manages respondent expectations early and reduces the risk of misunderstandings about the form's authority or scope.
Request reference or ticket number (if assigned) — This optional field allows respondents to link the request to an existing internal ticket or reference system. It is useful for cross-referencing and tracking, and making it optional avoids penalising those who do not yet have a reference number.
Date of request — Capturing the submission date is essential for record-keeping and timeline tracking. It establishes when the request was raised, which helps reviewers prioritize and track response times.
This section collects identity and contact information for the person submitting the request and optionally for a separate technical contact. The conditional logic here is effective: if a technical contact is designated, their details are collected; if not, a reassuring message confirms that all communication will go to the requestor. This reduces ambiguity and ensures a clear communication channel.
Requestor full name — Identifies the primary contact and accountable person for the request. This is a foundational data point for any request-based workflow.
Job title or role — Optional, but useful for understanding the requestor's authority or area of responsibility. It helps reviewers gauge the context of the request.
Company or tenant organisation — Links the request to a specific tenant or occupant, which is critical in multi-tenant buildings where different organisations share infrastructure.
Email address — Provides a primary digital communication channel for confirmations, follow-up questions, and status updates.
Phone number — Optional but valuable for urgent or time-sensitive coordination, especially when work is scheduled and on-site access is needed.
Is someone else acting as the technical contact for this work? — This conditional question is well-designed. It routes follow-up collection to the right person and avoids unnecessary fields when the requestor is also the technical contact.
Precise location identification is critical for infrastructure alteration requests. This section captures the building, floor or room, and the type of space affected, ensuring reviewers can locate and assess the area without ambiguity.
Building or site name — Distinguishes between different properties or campuses, which is essential in multi-site environments.
Floor, suite, or room identifier — Narrows the location to a specific room or area, enabling accurate planning and access arrangements.
What type of space is affected? — The single-choice format with an 'Other' option and follow-up description field is effective. It categorises the space for quick assessment while allowing flexibility for unusual configurations. The follow-up for 'Other' ensures no information is lost.
Affected rack, cabinet, or panel identifiers — Optional but highly useful for pinpointing exact equipment locations within a room. This level of detail supports efficient planning.
Does the work require access to areas outside this room? — The conditional follow-up collects details only when needed. This is a good design choice because it flags potential complexity (risers, corridors, plant rooms) without burdening respondents whose work is confined to a single room.
This section is the core of the request. It uses a multiple-choice checklist for work categories, a free-text description, a scale classification, and a conditional question about equipment removal. The combination of structured and open-ended input is a strength: it allows quick categorisation while capturing nuanced detail.
Which categories of work are included? Select all that apply. — The multiple-choice format with an 'Other' option and follow-up text field covers a wide range of common infrastructure changes. This helps reviewers quickly assess the scope and complexity of the request.
Describe the alteration in plain language, including what will be added, moved, removed, or modified — This free-text field is essential for capturing the specifics that structured options cannot convey. The placeholder example is particularly helpful in guiding respondents toward the level of detail expected.
How would you classify the scale of this change? — A useful self-assessment field that gives reviewers an early indication of potential impact. The 'Not sure yet' option is a thoughtful inclusion that avoids forcing inaccurate classifications.
Will any existing equipment be permanently removed or decommissioned? — The conditional follow-up captures disposal or return details, which is relevant for asset tracking and waste management planning.
This section uses a structured table to capture planned equipment, quantities, estimated power, and target locations. The inclusion of a formula column (Qty × Est. watts per unit = Total watts) is a practical feature that reduces manual calculation errors and improves data consistency.
Planned equipment and estimated load — The table format is well-suited for this type of data. Pre-populated example rows help respondents understand the expected format and level of detail. The formula for total watts is a thoughtful automation that improves accuracy.
Total estimated additional power draw (watts) — A summary field that gives reviewers a quick aggregate figure for capacity assessment.
Total estimated additional heat output (BTU per hour), if known — Optional and acknowledged as 'if known,' which is appropriate since not all respondents will have this figure readily available. It supports cooling capacity planning when data is provided.
This section addresses two of the most critical infrastructure concerns: power and cooling. The use of mandatory yes/no questions with conditional follow-ups ensures that respondents must explicitly confirm or flag capacity issues, while the follow-up collects the reasoning or additional needs.
Is the existing power provision sufficient for the planned change? — The conditional follow-up is well-designed: 'Yes' prompts for how capacity was confirmed, and 'No' prompts for what additional provision is needed. This captures both the assessment and the gap in one question.
What supply arrangement is expected? — A single-choice field that categorises the power configuration. The 'Unsure' option is a good inclusion for respondents who need guidance.
Is the existing cooling provision expected to handle the additional heat load? — Mirrors the power question structure, ensuring consistent treatment of capacity concerns. The conditional follow-ups collect assessment details or additional cooling needs.
Will the change affect airflow containment, hot/cold aisle arrangement, or floor tiles? — A targeted conditional question that captures physical layout impacts only when relevant.
Which environmental conditions should be monitored or reported during the work? — The multiple-choice format covers common monitoring categories. The 'None expected to be affected' option is a practical inclusion that avoids unnecessary data collection.
This section addresses cabling scope, network interruption, and third-party involvement. It is well-structured and uses conditional logic to collect details only when relevant.
What cabling work is planned? — A single-choice field that categorises the cabling scope. The 'No cabling work' option is useful for respondents whose changes do not involve cabling.
Approximate number of new cable runs — A numeric field that provides a quick scale indicator for cabling work.
Will the work require any interruption to live network services? — The conditional follow-up captures affected services, duration, and communication plans. This is critical for coordination and impact assessment.
Does the change involve any external carrier, service provider, or third-party cabling? — Flags third-party involvement, which can affect scheduling, access, and coordination requirements.
This section is important for operational planning and review. It captures the working method, hazard awareness, live system risk, and rollback planning. The introductory paragraph appropriately notes that this information is used for planning and review purposes.
Outline the working method, including sequence of steps and any isolation or switching steps — This free-text field is essential for understanding how the work will be executed safely. The placeholder example provides excellent guidance on the expected level of detail.
Which hazards or sensitivities should reviewers be aware of? Select all that apply. — The multiple-choice checklist covers a comprehensive range of common hazards. The 'None of the above expected' option is a practical inclusion.
Will any live production systems be at risk during the work? — The conditional follow-up captures system identification and safeguards, which is critical for risk assessment.
Is a rollback or restoration plan available if the change cannot be completed as intended? — Both 'Yes' and 'No' have follow-ups, which is a strong design choice. It ensures that even when no formal rollback plan exists, the respondent must explain how a partial or failed change would be handled.
Upload supporting documents (method statement, risk assessment, layout drawing, product data, or photos) — An optional file upload field that allows respondents to attach relevant documentation. This is a practical feature for complex requests.
This section captures the logistical details of the proposed work: dates, working window, duration, personnel, deliveries, and building support needs. It is comprehensive and well-organized.
Requested start date and Requested completion date — These date fields establish the proposed timeline, which is essential for scheduling and coordination.
Preferred working window — A single-choice field that categorises the timing preference. The 'Flexible' option is a practical inclusion.
Estimated on-site duration (hours) — A numeric field that helps with resource planning and access scheduling.
Number of people expected on site — Useful for access control, security, and space planning.
Will contractors or third-party personnel attend? — The conditional follow-up captures company names, attendee counts, and induction or access needs. This is important for security and compliance with building access procedures.
Does the work require deliveries, hoisting, or use of loading areas? — The conditional follow-up captures delivery details, timing, and routing, which supports logistics planning.
What support is needed from building or facilities staff? Select all that apply. — The multiple-choice format covers common support categories, helping facilities teams plan their involvement.
This section captures internal review status, project dependencies, shared system impacts, cost estimates, and additional notes. It is a practical closing section that surfaces important context for reviewers.
Has this work been reviewed internally by your own IT or facilities team? — The conditional follow-up captures reviewer details, and the 'No' follow-up encourages internal review without being prescriptive. This is a balanced approach.
Are there any dependencies on other projects, vendors, or scheduled works? — Flags coordination requirements that could affect scheduling.
Will the alteration affect any shared or multi-tenant systems? — The conditional follow-up captures shared system details and notification plans, which is important in multi-tenant environments.
Estimated cost of the alteration, if known — An optional currency field that provides budget context when available.
Any additional notes, constraints, or questions for the reviewer — An open-ended field that gives respondents the opportunity to add context not captured elsewhere. This is a good practice for ensuring nothing is overlooked.
The declaration section is well-designed. It includes two confirmation checkboxes, a typed name field, a signature field, and a date field. The introductory paragraph clearly states that submission does not authorise work to begin, which is an important operational clarification.
I confirm the information provided is accurate and complete to the best of my knowledge — A confirmation checkbox that establishes respondent accountability for the accuracy of the submitted information.
I understand that the requested work should not begin until the relevant approval or confirmation has been received — This checkbox is a strong operational safeguard. It ensures the respondent acknowledges that submission alone does not authorise work.
Typed full name (as signature) — Provides a text-based record of the signatory's identity, complementing the signature field.
Signature — A signature field that adds a formal element to the declaration. Note that this field is not marked as mandatory in the current configuration.
Date signed — Captures when the declaration was made, supporting record-keeping and timeline tracking.
This form is well-structured and thoughtfully designed for its intended purpose of collecting alteration requests for critical IT infrastructure. Its strengths include clear section organisation, effective use of conditional follow-ups to collect detail only when relevant, helpful placeholder examples that guide respondents toward the expected level of detail, and a balanced mix of structured (single-choice, multiple-choice, numeric) and open-ended input types. The inclusion of a formula-driven table for equipment and load estimates is a practical feature that improves data consistency. The form also manages expectations well through its introductory and declaration paragraphs, clarifying that submission does not authorise work and does not replace site procedures.
Areas for potential improvement include: the form is described as short but contains a substantial number of fields across ten sections, so respondents may benefit from a progress indicator or the ability to save and resume. The signature field in the declaration section is not marked as mandatory, which may be an intentional choice but could be reviewed for consistency with the other declaration fields. Additionally, some optional fields (such as job title, phone number, and rack identifiers) could benefit from brief helper text explaining when they are useful to provide. Overall, the form strikes a good balance between comprehensive data collection and respondent usability, and its conditional logic is one of its strongest design features.
Mandatory Question Analysis for Tenant IT Server Room & Critical Infrastructure Alteration 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.
Date of request
Recommendation: Requiring this field establishes a clear timestamp for when the request was raised, supporting record-keeping and response time tracking. It is a foundational data point for any request-based workflow and helps reviewers prioritize and sequence requests. This field is straightforward and unlikely to cause respondent friction.
Requestor full name
Recommendation: Requiring the requestor's full name ensures that each submission is associated with a specific individual, supporting accountability and communication. It serves as the primary identifier for the request and enables reviewers to direct follow-up questions to the right person. Form administrators should consider whether a display name or formal name format better suits their internal record-keeping needs.
Company or tenant organisation
Recommendation: Requiring the organisation name links the request to a specific tenant or occupant, which is particularly important in multi-tenant buildings where different parties share infrastructure. This supports accurate attribution and helps reviewers understand the scope of impact. The necessity of this field depends on whether the form is used in a single-tenant or multi-tenant context.
Email address
Recommendation: Requiring an email address provides a reliable digital communication channel for confirmations, follow-up questions, and status updates. It supports automated or manual response workflows and ensures the requestor can be reached efficiently. Depending on your organisation's data handling practices, consider including a brief privacy notice about how contact details will be used and retained.
Building or site name
Recommendation: Requiring the building or site name ensures the request is associated with a specific property, which is essential in multi-site environments. It supports accurate routing to the correct facilities or infrastructure team. This field is low-friction and directly supports operational processing.
Floor, suite, or room identifier
Recommendation: Requiring the floor, suite, or room identifier narrows the location to a specific area, enabling accurate planning, access arrangements, and impact assessment. Without this detail, reviewers may need to follow up for clarification, which delays processing. This field is critical for any infrastructure alteration request.
What type of space is affected?
Recommendation: Requiring this classification helps reviewers quickly understand the nature of the space and the potential implications of the proposed change. Different space types (dedicated server room, shared comms room, data hall rack, etc.) may have different operational considerations. The inclusion of an 'Other' option with a follow-up text field ensures flexibility while maintaining structured data collection.
Which categories of work are included? Select all that apply.
Recommendation: Requiring this field ensures that the scope of work is categorised from the outset, enabling reviewers to quickly assess complexity and identify areas that may need specialist input. The multiple-choice format with an 'Other' option balances structured data collection with flexibility. This field is a key input for routing and prioritisation.
Describe the alteration in plain language, including what will be added, moved, removed, or modified
Recommendation: Requiring a plain-language description captures the specifics of the proposed change that structured options cannot convey. This free-text field is essential for reviewers to understand the full scope and implications of the request. The placeholder example provides excellent guidance on the expected level of detail. Consider whether a minimum character count might help ensure sufficient detail is provided.
Is the existing power provision sufficient for the planned change?
Recommendation: Requiring an explicit answer to this question ensures that power capacity is considered before work proceeds. The conditional follow-ups capture either how capacity was confirmed or what additional provision is needed, supporting informed decision-making. This is a practical operational checkpoint that helps prevent issues during or after the alteration.
Is the existing cooling provision expected to handle the additional heat load?
Recommendation: Requiring an explicit answer to this question ensures that cooling capacity is assessed alongside power. The conditional follow-ups capture assessment details or additional cooling needs, supporting infrastructure planning. This field mirrors the power question structure, providing consistent treatment of capacity concerns.
Outline the working method, including sequence of steps and any isolation or switching steps
Recommendation: Requiring a working method description ensures that respondents have considered how the work will be executed safely and how live services will be protected. This information supports planning and review processes. The placeholder example provides strong guidance on the expected format and level of detail. This field is particularly important for complex or high-risk alterations.
Requested start date
Recommendation: Requiring the requested start date establishes the proposed timeline for the work, supporting scheduling and coordination. It enables reviewers to assess feasibility and plan resources accordingly. This field is straightforward and directly supports operational processing.
Requested completion date
Recommendation: Requiring the requested completion date provides a clear end point for the proposed work, supporting scheduling, access planning, and impact assessment. Together with the start date, it defines the working window and helps reviewers coordinate with other activities. Consider whether validation logic to ensure the completion date is after the start date would be helpful.
I confirm the information provided is accurate and complete to the best of my knowledge
Recommendation: Requiring this confirmation checkbox establishes respondent accountability for the accuracy of the submitted information. It is a standard declaration practice that supports record integrity and sets clear expectations. This field is low-friction and directly supports the reliability of the collected data.
I understand that the requested work should not begin until the relevant approval or confirmation has been received
Recommendation: Requiring this acknowledgment is a strong operational safeguard. It ensures the respondent explicitly confirms that submission alone does not authorise work to begin, reducing the risk of premature or unapproved changes. This checkbox supports clear communication of the approval process and helps manage expectations.
Typed full name (as signature)
Recommendation: Requiring a typed full name provides a text-based record of the signatory's identity, complementing the signature field. It supports record-keeping and ensures the declaration is associated with a specific individual. Form administrators should consider whether this field should be validated against the requestor name captured earlier in the form.
Date signed
Recommendation: Requiring the date signed captures when the declaration was made, supporting record-keeping and timeline tracking. It provides a clear audit point for when the respondent confirmed the accuracy of the information and acknowledged the approval process. This field is straightforward and directly supports documentation completeness.
The form employs a substantial number of mandatory fields (18 in total), which reflects the complexity and operational significance of the request type. For infrastructure alteration requests involving critical systems, a higher proportion of required fields is generally justified because incomplete information can lead to delays, miscommunication, or operational risk. However, several considerations are worth noting:
Overall, the mandatory field strategy is well-aligned with the form's purpose of collecting detailed, actionable information for infrastructure alteration requests. The high number of required fields is proportionate to the operational significance of the request type, and the conditional logic helps mitigate respondent burden by collecting detailed information only when relevant.
To configure an element, select it on the form.