ONSITE IT SERVICE CATALOG

Onsite IT Service Catalog for Multi-Location Businesses

Find the onsite work your team needs, from a single support visit to a move or multi-site rollout. ALL I.T. coordinates and carries out the agreed work, with your IT team retaining technical direction.

Browse 19 services below to compare typical tasks, what to prepare and the records available at handover. Services can be combined in one visit or project; the accepted work order confirms the actual deliverables.

For MSP client sites, review white-label delivery.

Download the service catalog

Keep a copy for planning, supplier evaluation or sharing with your team. The PDF covers the same 19 services, ordering information and responsibilities.

Version 2.7 · November 16, 2026 · Free download; no form required.

Find the work your team needs

SVC-01 · Routine field service

Onsite incident support

Purpose: Investigate a device or connectivity fault at a branch or other business location.

Typical scope: Desktop, laptop, printer and peripheral troubleshooting; cable and power checks; approved component swaps; and escalation. POS and specialist devices require confirmed skills and vendor support.

What to prepare: Affected devices, symptoms, previous troubleshooting, replacement parts and an available remote team or vendor. Identify a user or contact who can reproduce the fault and help test the result.

Possible completion records: Findings, actions and agreed photos; functional test results; and a status of restored, workaround or unresolved, with remaining actions and owners.

Scope boundaries: Attendance does not guarantee resolution. Parts, carrier faults, software defects and recovery outside the accepted scope need separate action.

SVC-02 · Routine field service

Smart hands and remote hands

Purpose: Give your remote engineers hands onsite for a defined task or live support session.

Typical scope: Console connections, authorized reboots, cable changes, equipment swaps, visual inspections, indicator readings and rack photographs under your engineer’s direction.

What to prepare: Asset IDs, room or rack locations, task sequence and port references. Confirm the remote engineer, access permissions, adapters, downtime approval and authority to stop or reverse work.

Possible completion records: Directed actions and affected assets or connections; agreed before-and-after evidence; the engineer’s validation; and failed or deferred steps with follow-up owners.

Scope boundaries: Your team owns technical and configuration decisions. Independent engineering needs separate scope; a completed physical task does not establish application recovery.

SVC-03 · Scoped coverage

Scheduled and temporary onsite support

Purpose: Cover recurring site tasks, a temporary staffing gap or a workplace launch.

Typical scope: Planned troubleshooting, equipment checks, installations, replacements and follow-up. Temporary user assistance can include workstation, printer and authorized account or software tasks with your service desk.

What to prepare: Sites, local coverage hours, dates, required skills and any technician-continuity requirement. Agree task priorities, permissions, spares, escalation, reporting and approval for extra hours.

Possible completion records: Visit or daily summaries, tickets addressed, validation results, completed and blocked tasks, and a handover of parts or vendor dependencies.

Scope boundaries: Extensions need agreement. Continuous monitoring, a fully outsourced service desk, unlimited labor and dedicated staffing are not included by default.

SVC-04 · Routine work with scoped specialties

End-user equipment deployment and MACD

Purpose: Install, move, change or remove workplace equipment as users and locations change.

Typical scope: Workstations, laptops, tablets, monitors, printers and peripherals; approved imaging or configuration; refreshes and returns. MACD means Moves, Adds, Changes and Deletes of approved equipment or connections.

What to prepare: Device and user lists, desk assignments, staged equipment, approved setup instructions, licenses, remote support and acceptance tests. Confirm vendor participation for specialist devices and the destination of removed assets.

Possible completion records: Device and location records; agreed connection, peripheral, print or transaction tests; user or remote-team verification; and a handoff of old equipment and unused parts.

Scope boundaries: Application ownership, licensing, payment-system certification and business-data migration remain with your team or vendor unless expressly included.

SVC-05 · Scoped service

Voice and telecom field support

Purpose: Complete the onsite work for a voice deployment, fault or carrier handoff.

Typical scope: Handsets, gateways, voice equipment, phone and data lines, demarcation extensions, patching and onsite assistance during circuit or voice cutovers.

What to prepare: Affected circuits or phones, carrier reference, demarcation location, port assignments, equipment and approved configuration. Confirm building access, the carrier or telecom engineer, downtime, rollback authority and tests.

Possible completion records: Equipment, endpoint, label and patching records; agreed call or connectivity test results; and provider handoffs with unresolved activation issues and owners.

Scope boundaries: Circuit delivery, carrier repair, number porting, subscriptions, platform administration and new electrical circuits are separate responsibilities.

SVC-06 · Routine field work with scoped engineering

Network equipment installation and change

Purpose: Install or replace branch network hardware within an approved change window.

Typical scope: Switches, routers, firewalls, rack mounting, patching, component replacement and loading client-approved configuration. Advanced engineering is matched and quoted separately.

What to prepare: Models, asset and port maps, rack and power details, compatible optics or cables, approved configuration and confirmed hardware receipt. Arrange remote engineering, validation tests and rollback equipment.

Possible completion records: Installation and asset or port records, connection photos, agreed link or connectivity tests, cutover or rollback status, and the location or return status of replaced hardware.

Scope boundaries: Architecture, change authorization, firewall management and security monitoring are outside routine installation. Configuration changes require explicit approval.

SVC-07 · Routine installation with scoped surveys

Wireless installation and site surveys

Purpose: Install access points or gather the evidence needed for a wireless deployment decision.

Typical scope: AP mounting, replacement or relocation, cabling and PoE checks. Survey work distinguishes visual discovery, active or passive RF measurement and post-installation validation.

What to prepare: Plans, AP models and positions, mounting details, access restrictions and controller support. For surveys, agree the purpose, test areas, representative devices, criteria, method, tools and report format.

Possible completion records: For installations: AP locations, port or PoE checks and agreed connection tests. For surveys: the ordered inventory, annotated plan, measurements or coverage results, with gaps and untested areas identified.

Scope boundaries: Visual discovery provides no RF certification. Predictive design, controller programming, formal certification and performance guarantees require specialist scope.

SVC-08 · Routine field service

Structured copper cabling

Purpose: Add or restore physical data connections for users and site technology.

Typical scope: Cat5e, Cat6 and Cat6A runs; outlet and patch-panel terminations or repair; cable dressing, labeling and fault isolation. Certification uses agreed qualified resources and test equipment.

What to prepare: Endpoints, run counts, cable category, labels, required tests and available plans or photos. Confirm pathways, ceiling heights, access, PoE needs, and responsibility for materials, lifts and pathway work.

Possible completion records: Installed and labeled runs, an agreed outlet or port schedule, specified results tied to tested cables, and any ordered route records or photos. Failed or inaccessible runs remain identified.

Scope boundaries: Continuity checks and certification are different deliverables. Penetrations, firestopping, permits, lifts and pathway work must be scoped; mains electrical work is excluded.

SVC-09 · Rack work with scoped fiber specialties

Rack installation and fiber services

Purpose: Mount equipment, organize a rack or complete a defined fiber connection.

Typical scope: Rack-and-stack, approved rack layouts, identified power and network reconnection, and cable organization. Fiber patching is separate from specialist installation, termination, splicing, OTDR and loss testing.

What to prepare: Rack elevation, asset and port maps, power feeds, equipment weights, matched rails and mounting hardware. Confirm lifting, access and downtime; for fiber, specify media, connectors, optics, tests and reports.

Possible completion records: Agreed equipment placement, labels, updated records and photos; results for tested links; remaining tracing or hardware issues; and specialist test reports when ordered.

Scope boundaries: Configuration, cutover decisions, electrical or structural work, and power or cooling engineering need separate scope. Extra tracing or recabling requires approval.

SVC-10 · Discovery with scoped technical assessment

Site and rack surveys and asset inventories

Purpose: Understand a location before an installation, move, refresh or remediation quote.

Typical scope: Asset and serial records, rack positions, visible connections and power, photos, measurements, access and readiness. Cable tracing and technical tests are separately defined.

What to prepare: The decision the survey must support, areas and assets to inspect, an agreed checklist, methods and report format. Provide available plans, photo permissions and site or remote contacts.

Possible completion records: The agreed inventory, annotated plans or rack records, photos and specified measurements or tests. Readiness gaps and inaccessible areas distinguish observations, estimates and verified results.

Scope boundaries: Visual discovery is not an engineering, code or cybersecurity audit. Design, destructive inspection, installation pricing and specialist testing are separate outputs.

SVC-11 · Routine cameras with scoped security systems

IP cameras and physical security infrastructure

Purpose: Install or service the physical connections for approved security equipment.

Typical scope: IP-camera mounting, replacement, relocation and aiming; PoE cabling; basic CCTV troubleshooting; and NVR or VMS connection checks. Door-system cabling and specialist work require defined scope.

What to prepare: Models, quantities, locations, required views, mounting heights and network needs. Arrange vendor access and a validator; for door systems, name the qualified provider responsible for hardware, programming and approvals.

Possible completion records: Device and location records, agreed photos, labeled connections, and power, network or authorized function tests. Untested functions and vendor-dependent issues are handed over.

Scope boundaries: Monitoring, retention policy, system design, access-control programming, integrations and regulated security or life-safety work are not implied.

SVC-12 · Routine installation with scoped specialties

Meeting room AV

Purpose: Install conferencing and presentation equipment for the agreed meeting-room functions.

Typical scope: Meeting-room displays and mounts, HDMI and network cabling, Teams Rooms equipment, cameras, microphones, speaker bars, room PCs and consoles. Extenders, distribution and commercial audio are scoped.

What to prepare: Models, display sizes and weights, mounting surfaces, hardware, room plans and cable routes. Confirm power, network, licenses, platform support and a user or remote participant for the agreed tests.

Possible completion records: Room and equipment records, mounting and connection photos, and ordered display, audio, camera, presentation or meeting test results. Missing parts and untested functions have follow-up owners.

Scope boundaries: New mains power, structural modification, AV design and ongoing platform administration need separate scope or the relevant trade.

SVC-13 · Case-by-case specialist scope

Building technology low-voltage support

Purpose: Arrange limited physical installation work for approved building devices.

Typical scope: Scoped sensor cabling and mounting, and paging or notification-speaker cabling and connections. Smart or PoE lighting and other specialties depend on the system and qualified-provider availability.

What to prepare: Device list, approved system design, locations, cable specifications, site access and materials responsibilities. Name the building-system provider responsible for programming and commissioning, and agree qualifications and acceptance checks.

Possible completion records: For accepted work: installation and label records, agreed photos, specified connection results and remaining commissioning actions. Specialist reports are supplied only when expressly included.

Scope boundaries: Control programming, HVAC service, energy engineering, electrical trade work and regulated life-safety commissioning are outside this limited offering unless separately arranged with qualified providers.

SVC-14 · Scoped project

Office moves and new site deployment

Purpose: Open, move, expand or close a location with coordinated onsite IT support.

Typical scope: Inventory and labels, destination readiness, disconnect and packing, equipment reconnection, site testing, day-one support and agreed old-site teardown. Carrier transport is separately scoped.

What to prepare: Origin and destination plans, desk and asset assignments, dates, priority users and arrival schedules. Confirm circuit and power readiness, building or mover contacts, transport responsibilities and remote IT coverage.

Possible completion records: Desk or area completion records, placement and connection checks, agreed photos, and a launch issue list with owners. Old-site teardown, returns and launch support are recorded separately.

Scope boundaries: Furniture, construction, circuit delivery, application or data migration and transport are separate scopes. Launch dates depend on site and equipment readiness.

SVC-15 · Scoped project

Multi-site rollouts and hardware refresh

Purpose: Deliver the same technology change across an agreed group of locations.

Typical scope: Pilots, work instructions, deployment waves, technician coordination, network or endpoint installations, replacements, site records, issue tracking and closeout reporting.

What to prepare: Confirmed sites, contacts, per-site tasks and quantities, access windows and blackout dates. Agree hardware shipping, remote-team roles, skills, crew sizes, readiness checks, pilot acceptance and reporting.

Possible completion records: Wave schedules and site reports, installation or swap records, agreed asset updates, validation and acceptance records. Blocked sites, shortages, changes and return visits are reconciled to the approved site list.

Scope boundaries: Additional sites, changed hardware or cutovers, and repeat visits caused by unmet dependencies need approval and may change cost or schedule.

SVC-16 · Scoped project with partner logistics

Data center relocation and lab infrastructure

Purpose: Move and reconnect physical server, lab or network infrastructure.

Typical scope: Inventory and rack mapping, readiness checks, labeled disconnect, de-rack, packing, carrier coordination, receiving, re-racking, power and network reconnection, optics and physical decommissioning.

What to prepare: Reconciled assets and connections, live-equipment exclusions, matched rails, destination rack plans, power, optics and facility access. Agree handling, carrier roles, move waves, backups, shutdown/startup authority and validation gates.

Possible completion records: Movement and receiving records, condition photos and rack or connection updates. Physical reconnection and link tests are separated from system-owner startup and application validation; open issues have owners.

Scope boundaries: Physical relocation excludes cloud, virtual-workload and application migration. Cross-border transport and customs require agreement with the carrier, broker and client.

SVC-17 · Scoped with disposition partners

Decommissioning and IT asset disposition

Purpose: Remove and route retired equipment through an authorized disposition plan.

Typical scope: Identification, labeling, disconnect, de-rack, inventory reconciliation, packing, collection and return, redeployment, resale or recycling coordination. Sanitization and destruction are separately specified.

What to prepare: Asset identifiers, retirement authorization, live-equipment exclusions, retention requirements and approved destinations. Specify custody records, any sanitization or destruction method, the performing provider and required evidence.

Possible completion records: A reconciled removed-asset inventory, retained assets and discrepancies, agreed custody handoffs, and ordered destination receipts. Asset- or media-specific treatment certificates are supplied only when expressly included.

Scope boundaries: Collection or scrapping does not prove data destruction. Resale value, destruction methods, certification, environmental obligations and reporting are agreed for each engagement.

SVC-18 · Scoped project

Project management and delivery coordination

Purpose: Coordinate field delivery across sites, technicians, suppliers and your IT team.

Typical scope: Scope development, planning, technician briefings, work instructions, dependency tracking, milestone reporting, escalation, change control and completion-document coordination.

What to prepare: Sites, assets, objectives, dates, suppliers and decision makers. Agree readiness gates, reporting, change-approval limits, acceptance owners and closeout requirements, with ticket or purchase-order references.

Possible completion records: An agreed delivery plan and milestone or site reports; documented decisions, issues and authorized changes; consolidated completion evidence, acceptance status and open-action owners.

Scope boundaries: Coordination does not transfer technical approval, application ownership, site readiness or business acceptance. Independent design and specialist engineering require explicit scope.

SVC-19 · Scoped project with partner transport

IT equipment logistics and relocation

Purpose: Move equipment and associated parts between facilities with agreed preparation, collection, receipt and handover.

Typical scope: Inventory, labeling, authorized disconnect and de-rack, matching rails and accessories, packing, carrier coordination, custody handoffs, receiving checks and staging by destination.

What to prepare: Addresses, collection and receiving contacts, dates, asset counts, dimensions, weights and access restrictions. Agree move waves, handling, packaging, carrier, insurance, storage and custody responsibilities; cross-border moves need a customs and broker plan.

Possible completion records: An asset and package manifest, matched accessory records, collection and receiving reconciliations, ordered condition photos, and exceptions with next-action owners and destination handoff.

Scope boundaries: Freight, specialist lifting, crating, insurance, storage, customs and materials are identified in the quotation. Re-racking and operational tests are separate when included; system owners retain backups, shutdown/startup approval and application validation.

Choose how the work is delivered

Use ad hoc support for a defined incident, survey, installation or directed task; scheduled coverage for agreed visits or temporary support; and project delivery for a move, buildout or rollout with milestones.

Coverage includes the continental United States and major Canadian metropolitan markets. Coverage, travel, access and qualified-resource availability are confirmed for each location; rural and special locations require review.

Timing is agreed in local site time. Eligible sites may have contracted next-business-day arrival; urgent and after-hours work depends on confirmed availability. Technician arrival, physical completion and restoration are separate milestones.

Prepare a service request

Send the required outcome, locations, preferred timing, equipment details and any ticket or purchase-order reference. Include what is already known, where discovery is needed, the remote technical contact, and who can approve extra work.

Your site contact confirms access, local restrictions, delivered equipment and a person available for agreed user checks. Your IT team or vendor supplies approved configurations, licenses, change permissions and technical decisions.

Existing clients can use their established ALL I.T. contact or client portal. For new work, share your requirements and we will review scope, skills, dependencies, timing and commercial terms.

Agree what completion means

Select the records your team needs before the work starts: quantities, labels, tests, photos, inventory reconciliation or milestone acceptance. The listed outputs are typical options; your accepted work order defines what is included.

The handover separates work performed, tests completed, customer validation and open actions. A physical installation can be complete while a carrier, parts, vendor or application issue still needs attention.

Changes to scope, quantities, configurations, access or deliverables require approval and may affect price or schedule. Your quotation or agreement sets rates, minimums, travel, materials and any other charges.

Service descriptions built for clear decisions

These ITIL-aligned descriptions identify service outcomes, scope, prerequisites, responsibilities, validation and acceptance. Incident and request handling, approved changes, asset records and project coordination support the agreed field delivery.

The master agreement, statement of work and accepted work order govern each engagement. For MSP assignments, you retain your customer relationship and technical direction, with branding and communication agreed for the work.

ALL I.T. Service Delivery · Version 2.7 · November 16, 2026. ITIL is a registered trademark of the PeopleCert group; no affiliation or organizational certification is implied.

LET’S PLAN THE ONSITE WORK

Discuss the onsite work.

Tell us the locations, tasks and timing you have in mind. We’ll review the scope, responsibilities and next steps with your team.

"*" indicates required fields

Your details will be used to respond to your inquiry. Privacy policy.