Step 04: Verify

What happensTesting against what was agreed
What you getA test record and as-built drawings
What you prepareSite access and a few real devices
What happens

Tested where it matters, not just where it's easy.

A quick signal check near the front door says nothing about the loading dock at shift change or the conference room during an all-hands.

Verification goes back to the success measures agreed at the start. We test at the locations that matter, with the devices your people actually use, doing the things they actually do. Anything that falls short is fixed and retested. The level of testing matches the project, from a focused walk-through to a full measured survey.

  • Real devices
  • Real tasks
  • Fix and retest
  • As-built record
Verification test recordSix test points on the floor plan. Five pass the -67 dBm target on the first test. Test point 5 in the stairwell measured -74 dBm, an antenna was adjusted, and the retest passed at -63 dBm.04VERIFY · TEST RECORDNTSOFFICESWORKROOMOPEN AREACONFERENCESTAIRIDFTP-01TP-02TP-03TP-04TP-05TP-06POINTTARGETRESULTSTATUSTP-01−67−58 dBmPASSTP-02−67−61 dBmPASSTP-03−67−55 dBmPASSTP-04−67−60 dBmPASSTP-05−67−74 dBmRETEST↳ ADJ.−67−63 dBmPASSTP-06−67−57 dBmPASSILLUSTRATIVE · TARGET −67 dBm AT EACH POINT
A test record: measurement points on the floor plan, results against the agreed target, and what was fixed and retested.
One step or all five

An independent check of a network you already have.

Verification doesn't have to follow our install. If you're not sure a network does what you paid for, we can test it.

Just the verification

We measure coverage, speed, roaming, calls or failover where it matters, with the devices your people use, and tell you plainly what passes and what doesn't.

Yours to keepA test record and a list of what to fix.

As part of all five

When the project calls for it, we test against the success measures written down at the start, fix what falls short and retest before we call it done.

Carries intoManage →

Where it goes wrong

What “it's installed” often hides.

Tested in the wrong places

The easy spots get tested. The stairwell, basement or far corner of the yard don't.

What we do insteadWe test at the locations named in the requirements.

Tested with the wrong devices

A laptop connects fine. The handheld scanners and older phones don't.

What we do insteadWe test with the devices your people use every day.

No record of what's there

Six months later, nobody knows what was installed, where, or how it was set up.

What we do insteadYou get as-built drawings and settings, not just an invoice.

Our approach

How verification works.

  1. Plan the test

    Pull the success measures and test plan from design, or write them with you.

  2. Measure

    Coverage, speed, roaming, calls or failover, depending on the project.

  3. Fix and retest

    Adjust anything that falls short and measure it again.

  4. Document

    Test results, as-built drawings and final settings, handed to you.

Getting ready

What we prepare, and what you do.

01

A test plan

Built from what the network is supposed to do.

02

Tools and test devices

The right instruments, plus the kinds of devices your people use.

03

A punch list

Every issue found, what was done and the retest result.

04

As-built drawings and settings

A record your team or ours can support from.

What you get

What you walk away with.

Yours to keep, whether we do the next step or someone else does.

You keepWhat it is
Test recordWhat we measured, where, and the results against the target.
Punch list, closedEvery issue found, what we did and the retest result.
As-built drawingsWhat was installed and exactly where.
Final settingsConfiguration records your team or ours can support from.
Practical next step

Tell us which step you need.

One step or all five. Share the sites, the problem and the timing, and we pick up from there.

Start your project