An AI visibility statement of work should tell the agency, the business and its website team what each person must deliver, when the next person can start, and what evidence will close each milestone. A single line such as “optimise the service pages” leaves several decisions open. The writer may expect to supply drafts, the buyer may expect live pages, and the developer may have no release booked.
Start with the agreed project scope and turn it into a delivery register. Give each deliverable an identifier, owner, dependency, due date and acceptance check. Link each change or exception to the affected row. That way the statement of work can guide the project after kickoff, when facts change and someone needs to decide whether work can proceed.
AI Visibility is published by Lunasol, which offers GEO and AEO services. The worked statement below is fictional. It draws on public examples and documentation checked on 5 November 2026. Lunasol public service overview
Define the working boundary
Name the buyer decision, the service, the site or properties involved, and the relevant languages. Identify the page addresses or attach a versioned page inventory. If the team will choose pages during discovery, state how many it can select, who approves the list and when that selection becomes the working scope.
Write down what the work can change. A project can include revising an existing page, preparing an update for the customer’s developer or publishing through an authorised account. Use the verb that describes what the assigned person actually does. If the team must make a choice between possible methods after discovery, specify who makes the choice and which deliverables depend on it.
Give the team a simple way to reference the current version. For a small project that might be an approved scope document with dated attachments. Put the effective date on the page list and use the same row IDs in the weekly delivery report. A newly suggested page can then be discussed without anyone silently replacing the approved inventory.
The existing audit guide explains the evidence to ask for when commissioning an investigation. The statement of work takes the agreed outputs and assigns the people, checks and handoffs that will govern their delivery. AI Visibility audit guide
Separate approval from release
AmCham-Jordan’s public website procurement document separates staff acceptance testing, fixes, a coordinated launch and post-launch monitoring. It also asks for training and documentation. A small AI visibility project can use the same separation at a different scale. A person can approve the facts on a draft, another can approve staging, and the release owner can confirm what actually went live. AmCham-Jordan website request for proposals, section 4
The City of Tacoma’s public website modernisation request lists a content inventory, a migration plan, quality assurance, redirects and user acceptance results as separate items in its pricing schedule. The practical lesson is to name the evidence for each step. If redirects are part of your project, a content approval does not tell the website team which redirects it needs to verify. City of Tacoma website modernisation request, pricing schedule
These are public website procurements. The example below adapts the distinction between approval, release and evidence to a smaller discovery project. It uses its own tasks and review conditions.
Build the register around real dependencies
Consider a fictional Dubai cycling business that wants customers to find accurate group ride information. Its project covers one English schedule page and one route from that page to a contact or booking destination. The schedule owner approves the operating details. An agency prepares the update. The business’s website team publishes it.
The Cycle Hub’s public ride page shows why the distinction matters. Its listings include details such as ride type, time and meeting location. Its official Instagram reel from 12 October 2026 directs readers to its bio link for ride details. The reel illustrates a dated discovery route. An editor would still need the current approved schedule before publishing a change about an upcoming ride. The Cycle Hub group rides and official ride reel
For the fictional project, the schedule owner supplies the current ride information and designates the source that staff will maintain. The agency uses those facts to prepare the page and a short test script. The website team confirms the draft can be staged and schedules the release. If the schedule owner is unavailable, the agency can prepare the structure and log which facts await confirmation. The milestone for approved copy stays open.
| Item | Deliverable and owner | Dependency | Acceptance evidence |
|---|---|---|---|
| D01 | Approved schedule record, ride organiser | Confirmation of time, meeting point and participation conditions | Dated record approved by organiser |
| D02 | Revised page draft and test script, agency editor | D01 and agreed page address | Service owner checks draft against the approved record |
| D03 | Published update and contact route, website team | D02 approval and release slot | Live page shows approved details and the intended destination opens |
| D04 | Dated discovery review, agency analyst | D03 live and agreed review window reached | Results and unavailable checks logged by agreed surface |
| D05 | Maintenance handover, project lead | Delivery and review records collected | Receiving owner opens the files and confirms the next update responsibility |
Give each owner a due date in the actual scope. For example, tie the draft deadline to receipt of the approved schedule record, and tie the post-release observation window to the verified release date. If the business needs a fixed launch deadline, include a point at which the project lead must decide whether to defer, cut scope or schedule a later release.
Define what each verification step proves
For the fictional ride page, the release check can include opening the public page, comparing the displayed information with the approved schedule and following the contact or booking link far enough to confirm its destination. Give the reviewer an agreed test route if the work includes submitting a test enquiry. If the project stops at verifying the link, record that boundary in the test script.
Search Console adds a separate check when it is included and the team has access. Google’s URL Inspection documentation distinguishes the most recently indexed version from a live test of the page. It also explains that a positive live result cannot guarantee indexing or appearance in Search. Record which view was used and the observation date. The public release check and the indexing observation each get their own evidence. Google URL Inspection documentation
The discovery review comes later. The statement can specify which question set and surfaces the analyst will observe, and what happens if an agreed check is unavailable. A result showing an older fact belongs in the evidence log. The review can then determine whether to investigate further and whether another observation is warranted. Google describes eligibility for links in its AI features separately from whether a page is ultimately shown. Google guidance on AI features and websites
Choose conditions that match what is being accepted. The release owner can demonstrate that approved text is public and a link opens. The analyst can demonstrate that a documented review took place. An external platform may update on a different timetable, so keep its observations in the review rather than using them to close the release task.
Decide how to handle a change after approval
Imagine the organiser moves the meeting point after the draft is approved but before release. The change record should identify the previous approved fact, the replacement, the owner who confirmed it, and the affected deliverables. In this example D01 and D02 need revision. The website team may have to move D03, and the D04 review window would then move with it.
Assign one person to assess the schedule effect and one person to authorise the change. They may be the same person on a small project. Ask the person implementing the change to confirm which version they received. If work already began on an earlier version, mark what must be redone and what can still be used. Retain the earlier approval so the record explains why the schedule changed.
Distinguish a correction from a new requirement using the approved scope. If the published page carries the wrong meeting point relative to the approved source, the release task needs correction. If the buyer adds an Arabic page and a second ride after kickoff, the project lead needs to assess the new writing, approval, deployment and review work. Link the decision to both the schedule and the revised deliverable list.
A sample change entry could read as follows. On day 6, the organiser approves a new meeting point in schedule version 2. The editor replaces the map link and resubmits D02 by day 7. The website team moves the release from day 7 to day 9 and verifies the new destination. The analyst’s observation moves from day 14 to day 16, preserving the seven-day interval. The project lead approves the change and records that the number of pages and test surfaces stays within the agreed scope. These dates are illustrative and make the dependency visible.
Record exceptions with a reviewer and an expiry or revisit date. For example, if Search Console access is unavailable during release, the parties can complete the public page verification while keeping the tool check open. An exception record should say whether the project can move forward, who will arrange access and when the check will be reconsidered.
Make the final handover usable
Specify the format and destination for the agreed files. In a small project, the handover might include the approved facts, editable copy, final page addresses, dated release evidence, observation log and open change records. Decide which of those artefacts the client receives and which can be shared with another provider. Refer to the agreed access and usage terms when the material includes third-party exports or private records.
Have the receiving owner perform a representative maintenance task. In the ride example, the organiser can show which source they would update and how they would alert the website team if a ride changes. The website owner can locate the relevant page and review the release evidence. The project lead can identify the last approved version and any follow-up check that still has a date attached.
Schedule a final review against the register. A deliverable can be accepted, returned for correction or recorded as an agreed exception. Give each remaining issue a named owner and a next action. This lets the business close the delivered work and carry the remaining tasks into maintenance with a clear record.
Check the statement with the people who will use it
Before the statement becomes the working baseline, ask the service owner, editor, website owner and analyst to follow one row through to completion. Each person should be able to say what they receive, what they deliver and who needs their evidence. If two people think the other will publish or approve the same update, revise the row and confirm the assignment.
Review the change path with the same group. Give them a plausible event such as a late fact correction, a missed release slot or an unavailable reporting surface. Walk through which rows move, who approves the revision and what the client will see at the next review. The version that survives this rehearsal is the one to use when the project starts.



