Quick answer: Do not accept an IT deployment merely because the network lights are on, Wi-Fi connects and the rack has been photographed. Compare the approved design with the installed configuration, test representative user journeys, verify access and recovery, record open defects, and hand over accounts, diagrams and operational ownership. Sign off on tested scope with evidence; each unresolved item needs an owner, due date and retest condition.
This guide covers project acceptance for a new or refreshed office or branch, not monthly maintenance. If storage architecture is still undecided, compare NAS, file server and SharePoint. For survey-to-handover implementation, see business IT system design and deployment.
Agree on acceptance criteria before cutover
Start with the contract scope, approved design, final equipment list and applications that must work. Operations should identify journeys that cannot fail: sign-in, printing, files, meetings, VPN and business applications. IT turns them into tests with expected outcomes. Do not invent a bandwidth, coverage or recovery threshold after the fact if none was approved; record the limitation or agree an addendum.
The implementer supplies configuration and evidence; internal IT or an independent representative repeats technical tests; business owners verify applications and data; an authorized person signs the record. Use real role-based test accounts, not only an administrator account.
Six evidence groups for the acceptance record
Adapt this example to the purchased scope and risk. Not every site includes servers, guest Wi-Fi or a secondary Internet connection.
| Area | Practical test | Handover evidence | Approver |
|---|---|---|---|
| Physical and power | Cable/port labels, rack, UPS, power path and basic alerts | As-built cabling/port diagram, serials, photos and controlled power-test result | IT operations |
| Network and Wi-Fi | VLAN/SSID, DHCP/DNS, guest isolation, backup link if contracted | IP/VLAN map, saved configurations, AP locations and tests at work areas | IT and site lead |
| Identity and access | Sign-in, scoped MFA, user groups, folder rights and privileged accounts | Approved access matrix and positive/negative user tests, admin inventory | Data owner and IT |
| Compute and storage | Applications, capacity, alerts, time sync and data access | Inventory, versions/configuration, owners, role-based test results | Application owner and IT |
| Backup and recovery | Job, copy location, backup rights and sample restore | Job log, restore record, elapsed time and open defects | Data owner and IT |
| Operations | Monitoring, alert recipient, support, licenses and warranties | As-built documents, company-owned accounts, runbook and supplier list | Business representative |
Test four user journeys, not just equipment statistics
New joiner: create an approved identity, sign in, access the right data and confirm another department’s restricted area remains inaccessible. Record the test account and remove it afterward.
Role transfer: remove old group membership, add the approved new role and inspect direct sharing links. Compare the result with the departmental access matrix. Admin-only testing cannot prove effective end-user rights.
Component failure: where contracted and safely permitted, simulate a brief power or secondary-link event. Observe application impact, failover time and recovery. Never run a destructive production test without a window and rollback plan.
Accidental deletion: restore a sample to an isolated location; validate content, version and permissions. A green backup-job status alone does not show the data is usable.
Blockers, exceptions and conditional sign-off
Critical applications failing, excess access to sensitive data, no tested restore, missing company-owned administrator access or insufficient as-built documentation may block sign-off. Rate defects by business impact rather than technical label alone. For each open item record actual/expected behavior, evidence, workaround, owner, deadline and retest date. A verbal promise to fix later is not completed work.
A minor issue can be accepted conditionally if authorized stakeholders agree in writing and warranty/support implications are clear. That does not override the data owner’s approval for access or data-loss risk.
The documents the business should retain
Keep current physical/logical diagrams, equipment serials and warranties, IP/VLAN/SSID records, saved configurations and recovery method, company-owned admin credentials, license list, owner-approved access matrix, backup/restore runbook, application test results, change record and support contacts. Transfer secrets through a company-controlled vault or secure channel, not a widely circulated sign-off document.
The acceptance record should name document version, date, environment, tester, expected and actual results and the appropriate signatories. Update the as-built record after post-acceptance changes; the original design is not automatically an accurate map of what was installed.
Frequently asked questions
Must every Wi-Fi point be tested? Test the agreed work zones and risk spots; a coverage commitment needs an approved method and threshold.
Who signs off without in-house IT? Business owners validate workflows and can commission an independent technical review or require a documented demonstration. The company still needs ownership of administrative accounts.
Is scheduled backup enough? No. Restore a sample and verify content and rights against the project’s objectives.
Does this checklist replace the contract? No. Scope, targets and warranties follow the approved contract and addenda.
Technical references
Microsoft Learn: deployment testing, approval and rollback; Microsoft Learn: Windows access control.
