A new location can look ready long before it is ready to operate. Desks may be installed and equipment delivered while the internet order remains uncertain, application access has not been tested and nobody owns the building’s communications cabinet. These gaps become expensive when they are discovered after an opening date has already been announced.
New location IT due diligence is an early assessment of whether the site can support the intended business activity and what must happen before it does. It combines physical infrastructure, connectivity, applications, security and operating responsibilities. The purpose is to make commitments with an evidence-based understanding of the work, dependencies and remaining uncertainty.
The assessment should begin while there is still room to change the plan. A branch, warehouse, clinic administration office and shared workspace have different needs. Reusing the head office equipment list without examining the new site’s workflow can miss the conditions that determine whether staff can actually work there.
Define the operating day before counting devices
Describe what happens at the location from opening to closing. Identify the staff roles, customer interactions, transactions, document handling and communication needs. Include peak periods, shift changes and activities that depend on another office or an external system.
Translate those activities into services. A reception desk may need identity access, appointment administration and printing. A warehouse may need scanners, inventory transactions and dispatch documents. The important unit is the completed task, not simply the laptop or access point used along the way.
Ask which activities must work on the first day and which can be introduced later. Record the accepted limits of a phased opening. A clear minimum operating scope helps the team prioritise preparation without pretending that unfinished services are already available.
Inspect the site with the right people
Arrange a site assessment involving the business representative, technical team and relevant building or facilities contacts. Review equipment locations, cable routes, communications spaces and access arrangements. Use qualified specialists for electrical, cooling, structural or other work that requires their expertise.
Record observations with location references and photographs where appropriate and authorised. A statement that cabling exists is less useful than identifying which outlets are installed, where they terminate and what evidence supports their suitability. Mark unknowns so they become investigation tasks rather than assumptions.
Consider the practical environment. Dust, restricted access, shared spaces, delivery routes and the position of working areas can influence equipment placement and maintenance. The assessment should explain the operational consequence of each constraint so the project team can choose a suitable solution.
Verify connectivity availability and delivery dependencies
Obtain provider confirmation for the specific premises and required service. General coverage information does not establish that a particular connection can be delivered through the building’s available route. Identify survey requirements, landlord permissions and other dependencies that could affect installation.
Record the distinction between a requested date, a provider commitment and a service that has been installed and accepted. These are different states. The opening plan should not treat an order reference as proof that connectivity will be ready for business use.
Assess the need for a secondary path and any temporary operating option. Verify its actual limitations, including application access and expected workload. A temporary connection can support a bounded opening plan only when the business understands what it can and cannot do.
Check the existing infrastructure before reusing it
Existing switches, wireless access points and cabling can appear to reduce the work, but they need assessment. Establish ownership, supported condition, configuration access and available documentation. Equipment left by a previous occupier may not include transferable management access or a suitable support arrangement.
For cabling, request the appropriate installation and test records and involve a qualified installer where verification is needed. Labels, outlet locations and patching records should match the intended working areas. Avoid accepting an installation solely because one device connects successfully at one outlet.
Review capacity and dependencies for the actual design. The number of network ports, power requirements of connected equipment and uplink arrangement all influence whether the system works as a whole. Exact specifications should be checked against the selected models and intended deployment rather than inferred from brand names.
Trace application access from a real workstation
A location is not operational merely because it can browse the internet. Test the applications that staff will use, including authentication, permissions, document access and transaction completion. Use representative accounts with the correct roles rather than an administrator account that bypasses normal restrictions.
Identify dependencies on head office, hosted platforms, supplier systems and specialised peripherals. A new public address, network segment or device configuration may affect access. Obtain the required approvals and supported configuration changes before the commissioning exercise.
Include shared services that users rarely mention until they fail. Name resolution, time settings, print queues and access to necessary templates can influence the workflow. Keep the checks tied to a user task so the acceptance process remains understandable to the business owner.
Decide how the site separates different users and devices
List the groups that will use the network: employees, guests, contractors and operational equipment. Determine which resources each group needs and which it should not reach. Use those requirements to guide the network and access design.
Do not assume that assigning different wireless names creates adequate separation. The technical team should verify the relevant access controls and test both permitted and prohibited communication. Document the intended boundaries and the owner who approves exceptions.
Consider administration separately from ordinary use. Equipment management access should follow an approved design with accountable identities and suitable recovery arrangements. The business needs to understand who can change the site configuration and how control is maintained when staff or providers change.
Establish power and environmental responsibilities
Identify which facilities conditions the IT service depends on and who maintains them. Equipment may require suitable power, ventilation, physical protection and access for servicing. Qualified specialists should assess the relevant requirements and implementation.
Clarify what happens during a power interruption or an environmental alarm. A protective device or cooling system does not create a complete response plan by itself. Assign responsibility for assessing the condition, contacting the appropriate specialist and coordinating any approved shutdown or recovery procedure.
Record shared responsibilities with the building operator where applicable. The IT team may depend on a room or power arrangement it does not control. The opening plan should identify the contact and escalation route rather than assuming facilities issues will be resolved informally when needed.
Make support ownership visible before handover
Define how staff at the new location request help and how the support team identifies the affected site and equipment. Include local contacts, access arrangements and any constraints on onsite attendance. A support provider needs more than an address to respond efficiently.
Update the asset register, service scope and supplier records. Assign owners for renewals, connectivity faults, application support and facilities escalation. If different teams cover different components, appoint a coordinator for incidents affecting the overall site.
Maxicon’s IT consultancy service is a relevant starting point for bringing these dependencies into a single readiness assessment. The useful output is a clear list of decisions and evidence needed before the location is accepted for operation.
Build a commissioning plan with acceptance evidence
Create test cases from the operating-day description. Each case should identify the user role, required task, expected result and person who accepts the outcome. Include representative transactions and the relevant exception paths, such as a failed login or unavailable peripheral.
Schedule commissioning after the required components are installed but early enough to correct faults. Testing at the end of the final evening leaves little room to resolve an access problem or replace unsuitable equipment. Protect time for retesting instead of assuming every first attempt will pass.
Record results honestly. Passed, failed, not tested and accepted with limitation describe different conditions. A test that could not run because a provider was unavailable should remain open. An accepted limitation should identify the approving owner, workaround and date for completing the remaining work.
Evaluate the fallback as a business process
If the site cannot operate as planned, determine which alternative actions are authorised. Staff may work from another location, use a limited temporary service or postpone selected activities. The choice depends on the business and should be agreed by the relevant owners.
Test the fallback to the extent practical. Confirm access, capacity, communication and the handling of records created during the disruption. A manual process can create later reconciliation work, so identify who captures transactions and who verifies them when normal service returns.
Set a decision deadline before opening. The sponsor should know which unresolved conditions trigger a reduced scope, delayed opening or other agreed action. This prevents a technical team from being pressured to declare readiness simply because equipment has arrived and the date is approaching.
Keep the first working day inside the project
The project should include support for the initial operating period. Real users may reveal workflow details that were missed during testing, especially when several teams work concurrently. Provide a clear route for reporting issues and distinguish urgent operating faults from later improvements.
Review the first day’s transactions and any workarounds with the business owner. Confirm that records reached their intended systems and that temporary access or test configurations have been removed or formally retained. Update documentation to reflect the deployed arrangement.
A good due-diligence report finishes with an actionable readiness decision, not a catalogue of equipment. It should explain what is ready, what remains uncertain and who must act next. To assess a proposed location before commitments become difficult to change, contact Maxicon with the site details, intended workflows and opening objectives.
Frequently asked questions
When should IT due diligence begin for a new location?
Begin while the site, timing and operating scope can still be adjusted. Early assessment can identify connectivity, facilities and access constraints before they affect the opening plan. Update the findings as providers confirm delivery and the layout or business requirements change.
Can existing equipment be reused without a full replacement?
Potentially, but verify ownership, condition, supportability, administrative access and suitability for the intended workload. Request documentation and relevant test evidence. Reuse should be an informed decision, with any gaps addressed before the equipment becomes part of the live operating environment.
What is the difference between installation and commissioning?
Installation places and configures components. Commissioning demonstrates that the intended users can complete agreed business tasks through the combined system. It includes acceptance evidence, fault correction and retesting. Delivered equipment or an active internet circuit alone does not establish operational readiness.
Who should approve opening with unresolved IT issues?
An authorised business sponsor should decide based on clear operational consequences, tested workarounds and advice from the responsible teams. Record the accepted limitation, owner and completion date. Technical staff should report evidence and uncertainty accurately rather than making an unsupported business commitment.
What should be included in the final handover?
Include verified configuration and asset records, service ownership, support contacts, access arrangements, commissioning results and outstanding actions. Document the fallback process and initial support plan. The receiving team should be able to operate the site and obtain help without relying on undocumented project knowledge.
Related technology support
For an additional service perspective related to this guide, explore Trubyte’s IT strategy and consulting services.
Discuss your requirements with Maxicon
Tell us about your business, current environment and the support you need.
