On-Site IT Visit Preparation Checklist for Businesses

A useful on-site IT visit begins before the technician arrives. Someone must be able to open the right doors, demonstrate the problem, authorize the agreed work and test the result. If those responsibilities are unclear, an appointment can turn into a search for keys, account owners and missing information.

This checklist is for a planned visit to an operating office or store. It focuses on getting the location ready, not choosing a support provider or attempting repairs yourself. For an active outage or suspected security incident, contact your support provider immediately rather than waiting to finish a planning worksheet. Confirm the visit's scope and timing directly with the provider.

1. Define what the visit should accomplish

Write one sentence describing the business task that needs to work. “The receiving desk must print shipping labels from its normal application” is more useful than “fix the network.” Add the affected location, the people impacted and any working alternative. This gives the visit a practical finish line without presuming the cause.

Separate the main issue from additional requests. A Wi-Fi problem, a new workstation and an unrelated email question may require different permissions, parts or appointments. Send the list in advance and ask which items are included. Do not assume every request can fit into the same visit.

Our on-site IT support page provides a starting point for discussing the work. Confirm the actual appointment, service scope and any charges before committing; this checklist does not establish service terms.

2. Make the location accessible

Confirm the full address, suite, entrance and check-in procedure. Identify a primary site contact and a backup who will be present. In a multi-tenant building, ask management whether visitor registration, escorting, loading access or advance contractor paperwork is required. Requirements differ by building, so verify them rather than relying on the last visit.

Make sure the contact can reach the equipment involved. A store manager may have front-door access but not the key to a shared communications room. Determine who controls each necessary space and when it is available. Keep access arrangements in the approved appointment channel; do not post alarm codes or sensitive building details in public comments.

Clear a safe working area around the agreed equipment without moving cables or opening electrical enclosures. Tell the provider about construction, restricted areas or other hazards. Let the technician assess installation work; preparation is not permission to dismantle equipment.

3. Prepare evidence the technician can use

Record the exact symptom, when it last happened and how to reproduce it. Include whether it affects one workstation, one room or the entire site. Note recent changes such as moved desks or replaced equipment, but label them as observations rather than proven causes.

For intermittent faults, a short log helps: time, location, task attempted, visible error and duration. A fictional example might read, “Tuesday, 10:15 a.m., receiving desk: label job stayed queued while the front register continued printing.” That is a testable observation, not a diagnosis of a failed printer or switch.

Identify the right device

Use the asset label or another agreed identifier so everyone discusses the same equipment. For a Windows PC, Microsoft's device-information guide explains how to find device and Windows information in Settings, under System and About. Provide only the details requested through the approved support channel; redact unrelated personal or customer information from screenshots.

Leave settings unchanged unless the provider directs otherwise. Repeated resets or cable swaps can remove useful evidence and introduce new variables before the scheduled visit.

4. Have the right people available

Arrange for someone who uses the affected workflow to demonstrate it. A person unfamiliar with the application may be unable to distinguish the original problem from normal behavior. If the issue involves a specific employee account, agree on a safe way to test it without sharing that person's password.

Identify the authorized administrator and relevant outside vendors. Internet service, POS software, payment equipment and building-managed networks can have different owners. Record existing ticket references and support contact details, and check whether a vendor needs to join during the appointment. Do not assume an on-site technician can change every system in the building.

Arrange account access through your approved process. Keep passwords, recovery codes and payment data out of the general visit notes. If additional access is requested, confirm its purpose, scope and who is authorized to approve it before proceeding.

5. Agree on disruption and approval boundaries

Identify business activities that cannot be interrupted during the visit. Ask which proposed tests might disconnect users, restart equipment or stop a checkout station. Agree on the work window and the person who can approve any change to it. Notify affected staff so a planned interruption is not mistaken for a new incident.

For network-related work, record the locations that need retesting afterward, not just the equipment closet. The network cabling and Wi-Fi installation service page can help frame that discussion. The visit should remain within the agreed scope unless an authorized decision-maker approves an expansion.

Confirm who can approve parts, additional time or follow-up work. Also agree on what happens if a required part, account owner or vendor is unavailable: document the blocker and next action instead of treating the appointment as a completed repair.

6. Close with a demonstrated result

Before the technician leaves, repeat the original business task with an appropriate user present. If the issue was intermittent, distinguish a successful spot test from a confirmed long-term resolution. Record what was tested, the result and any follow-up observation period agreed with the provider.

Use a short handover record: original issue; work performed; test result; unresolved limitation; next action; responsible person; target date. Keep appointment attendance separate from problem resolution. An unresolved vendor dependency is still open even when the on-site work is finished.

Retain the notes where the business can find them, and review any temporary access with the authorized administrator. Ready to coordinate a visit? Contact Sosa Solutions NYC with the affected location, business task and preferred work window so the next steps can be discussed clearly.