Draft scope and exclusions with an AI assistant using each room's equipment list and your standard exclusions library, have the system engineer check the draft against the design, then store the approved wording in the proposal tool's scope, description and terms fields. The assistant drafts; the engineer owns every line that reaches the contract.
A proposal with a good price and a vague scope produces change-order arguments. "Supply and install a conferencing system" means one thing to the integrator and another to the client who assumed network ports, ceiling work and software licences were included. Scope lines say what is in, room by room. Exclusions say what is out. Assumptions say what must be true for the price to hold.
The running example, an illustrative one, is a proposal for a specialist food importer's new head office: a 14-seat boardroom, a 24-seat tasting and training room and a four-person huddle room. The boardroom carries most of the detail below. For the step before this one, where scope lines come from a client's discovery conversations, see drafting an AV scope of work from discovery notes; here the scope already exists in rough form and the job is to turn it into proposal text that survives contact with the contract.
Have four things to hand before you start: each room's equipment list exported from your proposal tool, the drawing references with their revision letters, the survey notes, and three or four past proposals to mine for your own wording. If the survey notes are thin, fix that first, because no draft can recover a fact nobody recorded.
What three proposal tools say about scope text and AI
Vendors sell features, so start with what the tools actually offer for words. The table summarises the vendors' own pages as read in October 2026. Features and prices change, so check the live pages before you decide.
| Tool | Where scope and terms text goes | AI on the pages read | Entry price on its page |
|---|---|---|---|
| D-Tools Cloud | Proposal templates; a Quick Quote layout with client information, scope of work, pricing, contract and payment terms and a signature line; service contracts that carry a scope of service and equipment coverages and exclusions | One line on the features page mentions "creating AI-powered scopes of work", with no detail on inputs or editing | Single plan $99 a month on monthly billing or $89 a month on annual billing, plus a $250 one-time setup fee, for new subscribers |
| Portal.io | Proposals with Good-Better-Best options (its "optional items"), proposal expiry, change orders and digital signatures | None mentioned | Lite $29 a month for one user and 10 new proposals a month; Pro $89 a month for two users and unlimited proposals. The pricing page does not show which features sit on which plan |
| XTEN-AV | X-DOC proposals with 100+ templates and digital signatures; XAVIA, described as capturing scope, pricing, terms and revision history from a single prompt | XAVIA features ticked on every plan, including "auto-proposals, crafted by AI" | Per user: Basic $139 and Business $149 a month on monthly billing; the annual prices were printed without decimal points, so confirm them with the vendor |
Two points follow. On Portal.io's pages the words are yours: the tool gives you places to put scope and terms, not a writer. And where a tool does advertise AI, the promise is general: D-Tools Cloud's "AI-powered scopes of work" sits in a single sentence about the sales workflow, and XTEN-AV's XAVIA works from "a single prompt". Neither vendor's pages said whether the generated text can be built from your own approved exclusions, so ask before you assume. A general AI assistant used beside the proposal tool is a fair alternative, and it is the route taken below.
Scope, exclusions and assumptions: what each one is for
Keep five kinds of text apart. Mixed together, they leave the client unable to find the one sentence that matters when something goes wrong. The table shows each layer with a line from the boardroom.
| Layer | The question it answers | Example line |
|---|---|---|
| Scope line | What do we supply and do, in which room? | "Supply and install one 86-inch commercial display on a fixed wall mount at the position shown on drawing AV-101 rev B." |
| Exclusion | What is deliberately not included? | "Electrical supply to equipment positions is by others; our work starts at the socket." |
| Assumption | What must be true for this price to hold? | "Cable routes in the ceiling void are reachable without removing fixed ceilings." |
| Client responsibility | What must the client do, and by when? | "Provide live network ports at the rack and table positions before installation starts." |
| Change control | How are changes priced and approved? | "Changes after design approval are quoted as a change order before work proceeds." |
The difference between vague and specific is usually a drawing reference, a quantity and a boundary. Vague: "Supply and install a conferencing system in the boardroom, fully programmed." Specific: "Supply and install one conferencing bar below the display (drawing AV-101 rev B), connect it to the table connectivity box and the network, and configure the AV devices listed in section 3. Network ports, platform accounts and licences are by the client." The second version is longer and still easier to read, because every phrase can be checked.
Equipment list wording the client can read
Distributor descriptions are written for buyers, not for clients. They are also where scope text goes wrong, because the AI will rely on whatever words the line contains. Rewrite equipment lines into plain descriptions before you ask for scope, with one rule: keep every figure and every model number exactly as supplied, and add nothing.
| Line as exported | Client-facing wording | Check before you accept it |
|---|---|---|
| [model] 86IN UHD COMM DISP 500CD/M2 RS232 | 86-inch 4K commercial display, 500 cd/m2 brightness, with a control port | Does the manufacturer's sheet say "commercial" and list that control port? |
| [model] CONF BAR 4K CAM+MIC+SPK USB-C | Conferencing bar with a 4K camera, microphones and speakers, connected by USB-C | Does the manufacturer's sheet confirm the 4K camera and the USB-C connection? |
| [model] 2CH AMP 70/100V | Two-channel amplifier for the ceiling speakers | Does the speaker design use constant-voltage lines? If not, say nothing about 70 V or 100 V |
Prompt: one room's equipment list into scope lines
Work one room at a time, because a single room's list fits comfortably in a prompt and its errors are easy to spot. Export the room's equipment lines from your proposal tool, rewrite them as above, and attach the exclusions library. Keep the prompt and the library in a ChatGPT Project or a Claude Project so every proposal starts from identical instructions. Strip the client's name and all prices from what you paste unless you need them.
You are drafting the scope section of an AV proposal for ONE room. Use only the EQUIPMENT LIST and DRAWING REFERENCES below.
Write:
1. SCOPE LINES: one line per equipment group, starting "Supply and install" (or "Supply" if no install is listed). Include quantities and the drawing reference for position. Finish with one line for configuration and commissioning of the listed AV devices only.
2. ASSUMPTIONS: only assumptions the equipment list or survey notes support. Mark any other assumption you would like to add as "PROPOSED: engineer to confirm".
3. CLIENT RESPONSIBILITIES: items the list implies the client must provide (for example network ports, power, licences).
4. QUESTIONS FOR THE ENGINEER: anything in the list that is missing, inconsistent or unclear.
Rules:
- Do not add equipment, functions, features, standards, certificates or cable types that are not in the list.
- Do not refer to documents I have not given you.
- Do not write prices, dates or warranty terms.
- Do not write exclusions; I will choose those from the library.
- Plain English, short sentences, with spellings such as "metre" and "colour".
ROOM: Boardroom, 14 seats
EQUIPMENT LIST:
[paste]
DRAWING REFERENCES:
[paste]
SURVEY NOTES:
[paste]The boardroom list has 12 lines: one 86-inch display and mount, a conferencing bar, two ceiling speakers and a two-channel amplifier, a wireless presentation receiver, a table connectivity box, a touch panel and control processor, an eight-port network switch, a wall rack and a cable schedule. A first draft might read as follows.
Scope (boardroom). S1. Supply and install one 86-inch commercial display on a fixed wall mount at the position on drawing AV-101 rev B. S2. Supply and install one conferencing bar below the display. S3. Supply and install two ceiling speakers and one two-channel amplifier for presentation audio. S4. Supply and install one wireless presentation receiver connected to the display. S5. Supply and install one table connectivity box with HDMI, USB-C and power at the table position on drawing AV-101 rev B. S6. Supply and install one tabletop touch panel and one control processor and program them as described in the control narrative. S7. Supply and install one eight-port network switch and one 6U wall rack. S8. Supply and install all cabling and containment required for a complete working system. S9. Configure the AV network and commission the system.
Assumptions. A1. Cable routes are accessible without removing fixed ceilings. A2. The wall at the display position can carry the display. PROPOSED: engineer to confirm.
Client responsibilities. Provide live network ports at the rack and table positions.
Questions for the engineer. The list shows no speaker cable. Is it on the cable schedule?
What the engineer corrects in an AI scope draft
The draft is a good start, and the engineer has five corrections to make before it can go near a client. Each one shows a way AI drafting can go wrong, which is why the check is not optional.
- S8 promises more than was priced. "All cabling and containment required for a complete working system" is open-ended. The list only itemises a cable schedule, and containment is a building matter. Replace it with "the cables and connectors itemised on cable schedule rev B".
- S6 cites a document nobody supplied. There is no control narrative in the inputs. Either write the functions in a short list (display on and off, source select, volume, mute, conferencing) or remove the reference.
- S9 reaches into the client's network. "Configure the AV network" can read as taking on VLANs and firewall rules. Change it to "configure the AV devices listed above on the network provided by the client".
- S2 guesses a position. "Below the display" is typical, but the drawing may place the camera above it. Use the drawing reference instead of a position word.
- A2 is a structural assumption. An AI cannot know what the wall is made of. The engineer confirms it at survey, or the line becomes an exclusion that puts wall suitability on the client until survey.
The assistant's question about speaker cable is the most valuable line in the output. It found a gap in the equipment list, and the engineer fixes the list as well as the scope. Count how many of these catches you get over a month; that count is one of the numbers to track later.
An exclusions library the engineer approves once
Exclusions are where an AI's habit of sounding helpful is most dangerous, because a creative exclusion can quietly shift liability. So the assistant never invents exclusions for a live proposal. Your engineer approves a library once, gives each clause an ID, and the assistant only selects from it. The wording below is a starting point for your own lawyer-checked set, not a finished clause list.
| ID | Starting wording | Survey fact that triggers it |
|---|---|---|
| EX-01 | Electrical supply and sockets at equipment positions are by others; our work starts at the socket. | Any powered device in scope |
| EX-02 | Structural work, cutting of structural elements, making good, painting and decoration are excluded. | Mounting, cable routes or fixings through the building fabric |
| EX-03 | Network ports, VLANs, firewall rules, internet access and Wi-Fi are by the client's IT team unless listed in the scope. | Any networked device |
| EX-04 | Conferencing platform, room booking and cloud service accounts and licences are by the client. | Conferencing bar, booking panel or control app |
| EX-05 | Existing equipment that is reused is accepted in its present condition; we do not warrant its performance. | Reuse of existing displays, speakers or cabling |
| EX-06 | Removal or treatment of hazardous materials found on site is excluded. | Older building, work in ceiling voids |
| EX-07 | Programming changes requested after design approval are chargeable; two review rounds are included. | Control or DSP programming in scope |
| EX-08 | One training session of up to 90 minutes per room is included; further sessions are chargeable. | Any room with a control panel |
| EX-09 | Work is priced for normal working hours with clear access; out-of-hours or restricted access is extra. | Occupied building, security rules |
| EX-10 | Interfaces to fire alarm, lighting, blinds or access control are included only where listed; the other contractor's work is excluded. | Any third-party system mentioned in survey notes |
| EX-11 | Prices are valid for 30 days; lead times are estimates and manufacturer price changes pass through. | Every proposal |
| EX-12 | Support after handover is covered by the warranty and any service agreement, not by this proposal. | Every proposal |
Notice the numbers in EX-07, EX-08 and EX-11. They are placeholders for your own policy, not recommendations; set them to what you will actually honour. The wording protects you only as far as the client's contract lets it, so have a lawyer read the library once and again whenever you change it. EX-12 hands off to the support terms in the AV service agreements tutorial, which is where post-handover obligations belong.
Drafting the library from your past proposals
The first draft of the library is where AI can write exclusions safely, because it is collecting what you already say and not inventing what you might. Give the assistant three or four past proposals with names and prices removed, and ask it to extract and compare. Then you and the engineer edit, number and approve each clause, and for anything that limits liability a lawyer reads it too. That approved set is the only text the assistant may select from afterwards.
Here are four past AV proposals with client names and prices removed.
Extract every exclusion, assumption and client responsibility in them.
Group them by theme: electrical, building work, network and IT, software and licences, reused equipment, programming and training, access and hours, third-party systems, validity and lead times.
Where two proposals word the same exclusion differently, show both versions side by side and say whether the meaning differs.
Do not write new clauses and do not improve the wording.
List separately any theme that appears in only one proposal.
PROPOSALS:
[paste]A typical finding looks like this. Under electrical, proposals 1 and 3 say "power by others", while proposal 2 says "dedicated circuits by the client's electrician". The meanings differ: only the second names who does the work and says the circuit is dedicated. The team picks one wording, which becomes EX-01. Do the same for each theme and you have a library built from your own history, with the contradictions found before a client finds them.
Choosing which exclusions apply to this site
With the library in place, the second prompt is a selection task, which AI handles well because it is matching, not inventing. Paste the survey notes and the library; ask for the IDs that apply and the survey fact behind each.
Here is our exclusions LIBRARY (IDs and wording) and the SURVEY NOTES for one site.
Task:
1. List the IDs that apply to this proposal, with the survey fact that triggers each. Use the library wording exactly; never rewrite it.
2. List any ID you chose NOT to apply and why.
3. List any survey fact that suggests an exclusion we do not have. Do not write it; describe the gap in one sentence.
4. List any survey fact that contradicts an assumption or exclusion already chosen.
LIBRARY:
[paste]
SURVEY NOTES:
[paste]For the boardroom, the assistant might pick EX-01, EX-02, EX-03, EX-04, EX-07, EX-08, EX-09, EX-11 and EX-12, and it might flag that the survey note "client wants the display above the credenza, wall is old brick" suggests a structural exclusion not in the library. That is the useful output: not a new clause, but a gap for the engineer and lawyer to fill.
The three-way match: drawing, equipment list, scope text
Most scope disputes are not caused by a bad clause. They come from three documents that drifted apart as the design changed. Before anything goes into the tool, line the three up. An assistant can compare an equipment list with scope text, because both are text. It cannot read a drawing reliably, so the engineer checks the drawing column by eye. In the example, the match turned up this:
| Item | Drawing | Equipment list | Draft scope | Action |
|---|---|---|---|---|
| Ceiling speakers | 4 | 2 | 2 | Drawing was revised after the list. Engineer confirms 4, the list and price are updated, then the scope |
| Display size | "85-inch" label | 86-inch | 86-inch | Similar panel sizes carry different labels from different manufacturers. Confirm the model number and use one wording everywhere |
| Live network ports (client) | 3 (rack, table, wall panel) | Not listed | 2 | Fix the client responsibility to 3 |
The engineer's own check goes beyond matching. For each room, confirm that the equipment is compatible and the signal paths carry the resolution promised; that cable types, lengths and counts are right; that rack space, power and heat suit the rack; that network ports and power over Ethernet can be supplied; that the wall or ceiling can take the fixings; that any standards named in the client's specification are met; and that the lead times fit the project programme. These are judgements about the design. The assistant has no view on any of them, and the scope text must never imply that it has.
Getting the approved text into the proposal tool
Once the engineer signs off, move the text into the tool in three places. Put each room's scope lines where the tool shows a scope or description to the client; in D-Tools Cloud, for example, the features page describes a Quick Quote layout with a scope of work section. Put the exclusions, assumptions and client responsibilities in the terms or notes section. Put the rewritten equipment descriptions on the line items. Then save the room text as a reusable template so the next boardroom starts from the approved version.
Send yourself a test proposal and read it as the client would, on a phone as well as a laptop. Check that nothing is cut off, that lists have kept their numbering and that the exclusions appear before the signature, not after it. If the tool has an options feature such as Good-Better-Best or optional items, make sure each option's scope lines move with it; an option that changes the equipment but not the scope text is a quiet source of disputes. The wider question of which tool fits your business is covered in the comparison of AV integrator software.
Testing an AI proposal feature before you pay for it
If a vendor sells AI that writes scope and terms, test it with your own rooms, not the demo's. Run three past rooms through it: a simple huddle room, a room that reuses old equipment and a room with a third-party interface such as blinds or a fire alarm link. Compare the output with the text your engineer approved at the time. Count the lines your engineer would reject, and note whether the feature used your exclusions or wrote its own.
Then ask the vendor six questions and record the answers in writing. Which fields does the AI write into? Can it use my approved exclusions library? Can I lock approved clauses so staff cannot edit them? Is there a record of who approved each text? Where do my prompts and client data go, and are they used to train models? What does it cost, in credits or per user? On this last point, XTEN-AV's pricing page, read in October 2026, listed no AI credits or usage limits for any plan, so a buyer should ask rather than guess.
When the scope changes after approval
Clients add rooms, move displays and swap sources after the proposal is signed. Update the scope text at the same time as the price: raise a change order, reissue the affected room's scope lines with a new drawing reference and a version note, and keep the old version. An assistant can draft the change-order wording from the changed lines, as in the example below, and the engineer checks it before it goes out. For a longer treatment of the wording, see how electrical firms ask for extra payment in a change order.
CHANGE ORDER CO-02: Boardroom
Reason: client request on [date] to add a second 86-inch display on the side wall.
Added scope: supply and install one 86-inch commercial display on a fixed wall mount at the position on drawing AV-101 rev C; one HDMI output and cable from the control processor to the new display.
Changed scope: S1 now covers two displays; S9 commissioning now includes the second display.
Not included: wall strengthening, electrical supply to the new position (EX-01, EX-02).
Price change: [amount, from the pricing tool]. Programme change: [days].
Approval: the work proceeds on written approval of this order.Minutes per room, before and after the library
Before you change anything, time your current routine for one proposal. The figures here belong to the three-room example; use your own. By hand, a room takes about 55 minutes: 15 to rewrite the equipment lines for the client, 25 for scope, assumptions and responsibilities, 10 to choose and paste exclusions, and 5 for an engineer's check that is often skipped. With the library and an assistant the same room takes about 27 minutes: 3, 7 and 2 minutes for the first three steps, and 15 minutes for an engineer's check that is never skipped.
Over three rooms that is 165 minutes against 81. The saving looks small, but the real change is in the last step: the engineer's check moves from "when there is time" to a fixed step, and that is the step that catches scope errors before the client does. Track four numbers across your next ten proposals. Lines the engineer corrected per room, gaps found in the equipment list, change orders per project, and how many of those change orders trace back to an unclear scope line. If corrected lines stay high after a month, tighten the prompt rules and the library before you blame the tool.
Questions about AI scope text in AV proposals
Can the proposal software's own AI write the exclusions?
If your tool has an AI feature, test it before relying on it. Ask whether it writes into the scope, description and terms fields, whether it can use your own approved exclusions library or invents its own, and whether approved clauses can be locked. Whatever it produces still goes to your engineer, because the proposal carries your name.
Who is responsible if AI-written scope text is wrong?
You are. The proposal is your document, whoever or whatever drafted it. That is why an engineer approves each scope line against the design, and why new exclusion wording is read by a lawyer once before it enters the library. Treat the assistant as a fast first drafter, never as the author.
How detailed should a room-by-room scope be?
Detailed enough that a stranger could count what is included: one line per equipment group per room, with quantities, a drawing reference and the functions to be programmed. Keep exclusions and assumptions in separate lists so the client can find them. If a room needs pages of text, the room is probably two systems.
Where should the exclusions library live?
Keep one master document that the engineer owns, dated and versioned. Copy it into a ChatGPT Project or Claude Project so drafts start from the same wording, and into the proposal tool's templates so the approved text is what clients see. When the master changes, update both copies on the same day.
Further reads
- AV Installation Checklist: Commissioning Tests and Punch List With AI — The tests that prove each scope line at handover.
- Asphalt Paving Proposal Template: Scope, Exclusions and Weather Terms — A copy-ready asphalt paving proposal: scope, base condition assumptions, exclusions, weather terms and payment, drafted with AI and checked by you.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: D-Tools Cloud pricing and features pages, Portal.io home and pricing pages, XTEN-AV home, pricing, X-DOC and XAVIA pages (all read October 2026).