AV Installation Checklist: Commissioning Tests and Punch List With AI

Cover six areas: rack, power and cabling; network; audio; video; control and conferencing; and documentation with training. Then close out with a punch list the client signs off. AI helps with the paperwork: room-specific test sheets, a tidy punch list from your notes and the sign-off page. The installer still runs and records every test.

The rule that keeps a test sheet honest is short: the installer measures, the installer records, and AI only formats. If an AI tool fills in a "Pass" or a number you never measured, you hold a document that looks like evidence and is not. The checklist and the AI steps below are built around that rule, starting with who does what on the day.

Follow me on Instagram@sagnikteaches

The illustrative room is a 12-seat boardroom with one 86-inch display, four ceiling microphones, two ceiling speakers, a DSP in a wall rack, a conferencing bar below the display, a wireless presentation unit and a control panel. Its test sheet runs to 64 lines. In the example, 57 lines pass first time, 7 fail, and the punch list ends at 8 items.

Connect on LinkedInSagnik Bhattacharya

Two terms first. Commissioning means proving the installed system does what the design said, room by room. A punch list is the written list of outstanding defects and unfinished items at handover; some firms call it a snag list. If your contract or the client's specification names its own tests, those come first and the lines below fill the gaps.

Subscribe on YouTube@sagnikteaches

Who does what on commissioning day

The people who built the system run the tests, record the results and fix the failures. The designer answers questions about intent, the project manager issues and chases the punch list, and the client watches a demonstration and signs. AI sits beside the paperwork and nowhere near the measurements.

Notice what the last row leaves out: the assistant never touches a meter, a laptop test or a signature. It handles words and tables. That is where it saves time, and it is also why the checks later on are all about stopping words from drifting away from what actually happened.

Rack, power and cabling checks

Most commissioning problems start here, because everything else depends on the physical build. Do these checks before you test any function, and photograph hidden work before ceilings and boxes are closed.

Network and AV-over-IP checks

These lines depend on the client's IT team more than any others. Ask for a named contact before the walkthrough, and log blockers as client-side items the moment you find them, not on handover day.

DSP and audio tests, with the numbers to record

Audio is where "it sounds fine" most often replaces a test. Every line below produces either a recorded value or a recorded yes or no. Design values come from your design documents; the one in brackets is only an example.

Speech intelligibility scoring and reverberation measurements are only worth adding if the design or the client asks for them. When they do, the design needs to state the target, and the installer needs the right instrument. An AI-written sheet that adds such a line with a made-up target is a mistake to catch, not a favour.

Display, video and source checks

Control system tests a client would notice

Clients judge the control system by the first five minutes of use. Test it the way a hurried meeting organiser would.

Every control, every state. Each button does what its label says, and the feedback matches reality: a mute light that glows means the microphones really are muted, whichever control caused it. Start-up and shutdown. The sequences complete in the designed order and time, and the idle timers run at the agreed interval. Failure behaviour. Unplug a source or the network cable and check that the panel says something clear and recovers when the connection returns. Access. The technician pages are protected, and user roles match what the client asked for. Integrations. If a room-booking screen, a schedule or remote monitoring is in scope, each is tested end to end.

Finish with the colleague test. Ask someone who did not build the system, ideally a member of the client's staff, to run a meeting from a cold start to shutdown with no help. Write down every place they hesitate. Hesitations make better punch-list items than anything in the technical sheet, because they predict the support calls you will receive.

Conferencing and wireless presentation tests

Use the client's own conferencing account and the platform they actually use, not the installer's. Join a call with a person at the far end and check, in both directions, that you can hear and see clearly. Frame the camera from the farthest seat, test the presets, and check that microphone pickup reaches the back of the room. Then try each way people will share content: the table input, the wireless presentation unit with a client laptop and with a phone, and a guest joining from outside the building. If the wireless unit uses a pairing code or a PIN, check that a person in the corridor cannot cast to the room by accident.

Documentation and training to hand over

A system that works but arrives with no records becomes a support problem the day your engineer leaves the building. The handover pack should hold as-built drawings and signal flow, the cable schedule and IP schedule, the equipment list with serial numbers, dated configuration backups for the DSP, control system and switches, a credentials handover agreed with the client's IT contact, a one-page user guide for each room, warranty details and the training record with names and dates.

If you want an outside reference for what a verification and documentation process looks like, AVIXA's published standards page lists AV Systems Performance Verification (D402.02, formerly INFOCOMM 10:2013, reaffirmed in 2024) and Documentation Requirements for Audiovisual Systems (D401.01), along with standards on cable labelling and rack design. Its listing describes the verification standard as covering which parts of a system to verify, when verification happens, how to set verification criteria and metrics, and how to report results. The standards are sold as documents through AVIXA's store, so work from the edition you hold rather than from a summary. If your contract cites one, use its own verification items in place of the lines above.

AI step 1: a room-specific test sheet from the design

Building a sheet by hand from the equipment list is slow and easy to get wrong in small ways. Give an AI assistant the design data and ask it for a blank sheet, with a firm rule about what it may fill in. The prompt below keeps the design values, and nothing else, in the sheet.

You are helping an AV installer prepare a commissioning test sheet for one room.
Use ONLY the DESIGN DATA below. Do not invent equipment, targets, tolerances, IP addresses or standards.

Produce a table with these columns:
ID | System | Test | Method (one sentence) | Design value | Measured value | Pass/Fail | Tester | Date

Rules:
- Group lines by system: rack and power, cabling, network, audio, video, control, conferencing, documentation and training.
- Write a Design value only if it appears in the DESIGN DATA. Otherwise write "not specified: designer to confirm".
- Leave Measured value, Pass/Fail, Tester and Date empty.
- Add one line for every item in the equipment list that has a network address.
- Keep method sentences short and neutral. Do not give electrical safety instructions or tell anyone to bypass an interlock or protection.
- After the table, list any design values that look inconsistent, for example a microphone count that differs between the equipment list and the signal flow.

DESIGN DATA:
[equipment list with locations and model numbers]
[signal flow description]
[IP schedule]
[design targets: levels, resolutions, response times]
[client requirements from the scope]

For the boardroom, a response begins like the rows below, with the empty result columns left out to save space.

Four things to act on in a draft like this one. Suppose the method for A04 says "pink noise at full level", which could damage speakers and ears; you change it to the agreed reference level. The assistant might also add a speech-intelligibility line with a target of 0.60 that the design never set, so it goes. It may combine "mute from every control point" into one line even though the room has three control points; split it, or tell the tester to record each one. And if it notes at the bottom that the microphone count differs between two documents, that is exactly the kind of catch worth the exercise: send it to the designer before the day.

A walkthrough script the client can follow and initial

Sign-off goes faster when the client watches a fixed sequence rather than a tour. Book the walkthrough only when the room passes a readiness gate: every test-sheet line carries a measured value or a result; no installer-side fault that stops the room being used is still open; the DSP, control and switch configurations are backed up and dated; the one-page user guide is printed; and someone with authority to accept is coming, bringing their own laptop and phone. A walkthrough that starts with a gap in any of these turns into a second commissioning day with an audience.

Then run the same script in every room of a type. An assistant can draft it from the scope's list of functions and the completed test sheet: one step per function the client was promised, in the order a meeting uses them, with the expected result in plain words. Check the draft against the scope, because a step for a function nobody bought invites a complaint, and a missing step leaves a function undemonstrated. The boardroom script runs to ten steps and about 25 minutes.

In the boardroom, steps 5 to 7 could not run on the day, because the wall port behind the credenza was dead and the conferencing bar never registered. Those steps stay uninitialled and reappear on the sign-off sheet against that punch-list item. Anything the client questions during the script goes into the walkthrough notes with its step number, and those notes are the raw material for the next step.

AI step 2: walkthrough notes into a punch list

During the walkthrough, technicians talk, type and photograph quickly. Notes read like this set from the boardroom, dictated into a phone and shown as typed:

ok boardroom walkthrough. wall port behind credenza dead, no link light, vc bar cant find network, test call failed. ceiling mic 2 has low rumble when ahu running, gate keeps opening. seat 12 only 66 on the meter, target 70. panel mute button doesnt light when mics muted from the table pad. usb-c laptop only gets 1080 not 4k, hdmi ok. rack door wont shut, patch lead too tight. blind motor no power at wall, client sparky. as-built pdf doesnt show dsp preset names. otherwise all good, photos 2231 to 2240.

Ask the assistant to turn that into rows, and give it the client's responsibilities from the scope so it can tell whose job each item is.

Turn these walkthrough notes into a punch list. One row per distinct issue. Use only what the notes say.

Columns: ID (P01, P02...) | Item | Category | Severity | Owner | Retest method
Category: Defect, Client-side, Design query, Documentation
Severity: A = room cannot be used for its main purpose; B = usable with a workaround or reduced performance; C = cosmetic or paperwork
Owner: only a role named in the notes or in the SCOPE EXTRACT; otherwise write "to be assigned"

Rules: do not merge separate faults. Do not state a cause or a fix the notes do not state. Keep measured values exactly as written. List at the end any note you could not place.

SCOPE EXTRACT (client responsibilities):
[paste]

NOTES:
[paste]

Read the table against the notes before it goes anywhere. Without the scope extract in the prompt, an assistant can mark P01 as an installer defect, because the notes do not say whose port it is, and that single mistake would send the client's IT team a defect report for something the contract puts on them. Check severity too: an assistant that sees the word "dead" can rate a cosmetic item as A. Finally, strike any cause or remedy the technician never wrote. "Replace the microphone" belongs on the list only if someone diagnosed it.

Compare the before and after on one line. A typical raw entry is "mic issue in boardroom". As P02 it names the microphone, the symptom, the condition that triggers it, the owner and the retest, so anyone can close it without a phone call.

Where the sheet and photos live

A spreadsheet is enough for a first month. After that, put the sheet where the photos already are. D-Tools Cloud's pricing page lists site notes and photos, task management and time tracking for field users on every plan, and shows no AI features on that page, so the assistant work above happens outside it. Prices there start at $99 a month for one office user and one field user on monthly billing, with a $250 one-time setup fee (list prices read in October 2026; the page says they are for new subscribers).

A dedicated inspection app is the other route. Mitti (by SafetyCulture) describes AI Issue Capture, which turns photos or voice notes into issues. Its pricing page, read in October 2026, shows a Free plan for up to 10 seats with up to 300 AI credits per seat a month and 5 active inspection templates, and Premium at $24 per seat a month billed annually ($29 billed monthly). Five templates is enough to start if you keep one per room type, for example huddle room, boardroom, training room, auditorium and digital signage. Whichever you use, a field person should be able to attach a photo to a line in seconds, because evidence collected a day later is evidence the technician has half forgotten. For capturing notes by voice, see the routine for turning on-site voice notes into job sheets, and for the habits behind a good list, photos and punch lists in the construction field.

AI step 3: the client sign-off page and its wording

The sign-off page is a one-sheet record of what was demonstrated, what remains, what was handed over and whether the client accepts. The project manager prepares it from the completed test sheet and the punch list. An assistant can lay it out, but it must be told to copy, not conclude.

Draft the acceptance sheet for this room from the records below. Use only what the records say.
- Do not state that a test passed unless the test sheet shows Pass for that line.
- List every open punch-list item exactly as written, with its owner and due date.
- Leave the acceptance tick-boxes unticked.
- Do not add legal wording. Where the sheet refers to the contract, use the clause reference I give you.

TEST SHEET (completed):
[paste]
PUNCH LIST (current version):
[paste]
HANDOVER ITEMS ISSUED:
[paste]
CONTRACT CLAUSE REFERENCE FOR ACCEPTANCE:
[paste]

Here is the shape of the finished page for the boardroom after the retest, with placeholders for names and dates.

ROOM ACCEPTANCE AND HANDOVER SHEET

Project: [project name]            Room: [room name and number]
Contract reference: [reference]    Walkthrough date: [date]    Retest date: [date]

Present at the demonstration
Installer: [name, role]    Client: [name, role]    Others: [name, role]

1. Tests demonstrated
Test sheet [reference, version] was completed on [date].
64 lines: 57 passed at the first attempt, 7 did not.
All lines are now recorded as Pass except those linked to the items in section 2.
Walkthrough script [reference]: steps 1 to 4 and 8 to 10 initialled;
steps 5 to 7 (test call, camera presets, content in a call) wait on P01.

2. Outstanding items (punch list version [n])
P01  Wall port behind the credenza not live (client IT), due [date]
P07  Blind motor power supply (client's electrician), due [date]
Items P02 to P06 and P08 were closed at the retest on [date].

3. Handover items
[ ] As-built drawings issued (version [n])
[ ] Equipment list with serial numbers issued
[ ] IP schedule and configuration backups issued (dated [date])
[ ] Credentials handed over as agreed with [client IT contact]
[ ] One-page user guide issued
[ ] Training given to [names] on [date]
[ ] Warranty start date confirmed: [date]

4. Acceptance (tick one)
[ ] The system is accepted as complete.
[ ] The system is accepted for use, with the exceptions in section 2.
[ ] The system is not accepted. Reasons: [reasons]. Retest on [date].

What this signature confirms is set out in contract clause [number].

Signed for the installer: [name]      Date:
Signed for the client: [name]         Date:

The three tick-box options matter because "accepted for use, with exceptions" is the honest outcome of most handovers. It lets the client use the room while two items wait on their own contractors, and it records those items with owners and dates. What a signature triggers, such as a payment milestone, the start of the warranty or the release of a retention, is decided by your contract and not by this page. Use your contract's own term for completion rather than inventing one, and have a lawyer read the template once before you reuse it.

What AI must never do on a commissioning day

Four rules cover almost every risk, and the first comes with a cautionary tale. Picture a technician with a long list of rooms who dictates notes for a boardroom and asks the assistant to "fill in the sheet". It writes Pass against 11 lines the notes never mentioned, including the feedback test. The error surfaces when the client's witness asks to see that test and nobody has run it. The fix is a prompt rule: every Pass or Fail must quote the note line it came from, and any line without a quoted note stays blank.

• It never records a result. Blank means untested. A value or a Pass appears only when the technician said it.
• It never decides pass or fail against a target. The design says what the target is, and the installer or designer judges the reading.
• It never changes a design value. If a result misses, the line goes to the designer as a query, not to the assistant for a suggestion.
• It never signs or ticks acceptance. Acceptance boxes stay empty until a person with authority ticks them.

Keep client data sensible, too. Network addresses, floor plans and login details do not belong in a consumer chat account. Use a business plan, which does not train on your content by default, or switch the model-training setting off on an individual plan, strip identifying details from what you paste, and never paste a credential.

Closing the list: chasing client-side items

A punch list loses value every day it goes unsent. Issue it within a day of the walkthrough, with client-side items split out at the top so the client sees what is theirs. The example room followed this sequence: the walkthrough on day 0, the punch list issued on day 1, a reminder on day 3 for any client-side item with no date, the retest on day 5, and the sign-off on day 6.

An assistant is useful for the chasing messages, as long as each carries the specific ask. This one is written for the client's IT contact (placeholders in brackets).

Subject: Boardroom 2: two items need your team before we can close the project

Hi [first name],

Thanks for joining the walkthrough on [date]. Everything we are responsible for is complete or booked in. Two items sit with your side:

1. Network port W-04 behind the credenza has no link. Please activate it on the room VLAN shown in row 14 of the IP schedule. Once it is live, the conferencing bar can register and we will repeat the test call within one working day.
2. The blind motor has no power at the wall. Your electrician needs to supply the socket shown on drawing [number]. We will test blind control as soon as it is on.

Could you tell me by [date] when each will be done? The attached sheet lists all eight items with owners.

Thanks,
[your name]

If the scope was clear that network ports and wall power are client responsibilities, this message is a reminder rather than an argument. That is the main reason the scope of work drafted from discovery notes should list client responsibilities in plain words. After sign-off, the relationship carries on through service agreements and renewals, and the handover pack is the first thing your support team will open. For another trade's version of a handover pack, see the CCTV installation checklist.

Measures that show the sign-off routine is working

Measure four things on each room and keep them in one table. First-pass rate: in the example, 57 of 64 lines, or about 89%. Items closed at the first retest: 6 of 8, or 75%, with the other two waiting on the client. Client-side share of the punch list: 2 of 8, which tells you whether scopes spell out client responsibilities clearly enough. Days from walkthrough to sign-off: 6 working days in the example. Watch the trend across rooms rather than any single figure, because a low first-pass rate usually points to a gap in the build checks and not to bad luck.

Once a month, audit three signed sheets against the raw notes and photos. For each Pass, look for the note or the photo that supports it. Any Pass without evidence is a process fault, whether an assistant or a tired technician wrote it. Keep the audit result in the same table, and use it to tighten the prompt rules above.

Questions about AV commissioning and sign-off

Who signs off an AV installation, the installer or the client?

Both sign different things. The installer signs the test records to say the tests were run and the results are true. The client signs the acceptance page to say they saw the demonstration and accept the system, with any exceptions listed. What acceptance triggers, such as a payment or the start of the warranty, comes from your contract, so use its own term.

Is a punch list the same as a snag list?

Yes. Both are the written list of defects and unfinished items found at handover. Different firms and trades use different names. What matters is that each item has a location, a severity, an owner, a retest method and a due date, so the list can be closed item by item rather than argued about in general terms.

How many test lines should a room sheet have?

Scale it to the equipment and functions in the room, not to a fixed number. A small huddle room with one display and a conferencing bar needs far fewer lines than a boardroom with a DSP, a control panel and a room-booking screen. Build the sheet from the equipment list so every device and every function in the design has at least one line.

What if the client refuses to sign at the walkthrough?

Ask which items they object to and write each one onto the punch list with an owner and a date. Then check what your contract says about acceptance and use of the room. Often the client will sign for use with exceptions once the open items are visible. If they will not, record the reasons and arrange the retest.

Further reads

• AV Integrator Software: Quotes, Projects and Service, AI Compared — Software that holds quotes, projects and service in one place.
• AV Proposal Software: Adding AI-Written Scope and Exclusions — Scope and exclusions that make commissioning disputes rarer.
• AI for a Painting Business: Snag Lists and Final Walkthrough Sign-Off — Another trade's snag list and final walkthrough sign-off.
• Boiler Installation Checklist: AI Sorts the Photos, You Sign the Records — A handover checklist where photos prove each record.
• AI for Electrical Project Management: Diaries, RFIs, Snag Lists — Site diaries and RFIs on the electrical side of a project.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: AVIXA published-standards page and its page for the AV Systems Performance Verification standard; Mitti pricing and product pages; D-Tools Cloud pricing page (all read October 2026).