--- title: "What should a written AI build scope include?" description: "Write an AI build scope that names the function, inputs, permissions, cost controls, acceptance checks, ownership, training, and rules for changes." canonical: "https://scalewithsearch.com/articles/written-ai-build-scope" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # What should a written AI build scope include? A written AI build scope should state the function, result, approved inputs, action limits, human review, cost controls, acceptance checks, ownership, and training. It should also name exclusions and explain how changes are approved. Write the scope so a future operator can understand the purchase without attending the sales call. Give each promised result a corresponding check. Keep broader ambitions outside the first function until they receive their own scope. The example below is illustrative. It describes an internal weekly report draft, rather than a customer result or a ready-to-sign agreement. Adapt the structure to your own work. ## Begin with one function and one endpoint Write a short function name, then state what happens when it finishes. For the example: prepare a weekly progress report draft from approved project updates. Place it in the manager's review folder. Identify the person who sets direction and the person who checks the result. Specify whether they are the same person. State whether the function runs on a schedule or starts only when an operator requests it. Keep adjacent actions explicit. In this example, the function does not chase missing updates, send the report, or change project records. If you want those actions later, assess them separately. The first scope should have a visible stopping point. ## Name the source records and required inputs List each input by its role and location. For the report example, include the approved project list, current report template, reporting period, and authorized weekly updates. State which source takes precedence if records conflict. Identify who can approve a correction. Explain what happens when the function cannot find a required record or cannot establish which version applies. Include a buyer input list with an owner for each item. Avoid a general dependency on complete company data. Ask for the smallest set of records needed for the job. If preparing those records is included in the build, describe that work and its finish line. Otherwise, assign it to the buyer. ## Describe the output in inspectable terms Attach or reference a sample output with safe data. Name its format, destination, required fields, and visible treatment of missing information. For the example, require the reporting period, project name, source references, and unresolved questions. Describe what the reviewer must be able to check. Ask whether each report statement can be traced to an approved update. Decide whether incomplete inputs block the whole run or produce a clearly marked partial draft. Avoid acceptance language based only on appearance. A polished report can still use the wrong period or omit an active project. Define the content checks beside the formatting requirements, then have the operator review both. ## State permissions and human approval List what the function can read, write, and initiate. Identify the account and destination for each permitted write. State which actions require a person to approve the exact output. For the example, permit writing a draft into the review folder. Prohibit sending, publishing, deleting source records, or granting access. Assign the final report decision to the manager. Use the [approval matrix guide](/articles/ai-agent-approval-matrix) for a more detailed authority map. Keep the scope focused on the permissions needed for this function. Require a demonstration of the boundaries during acceptance, including an attempted action the function must refuse. Record the expected refusal before running that check. ## Specify costs, limits, and run records Identify the paid services used by the function and the accounts that hold them. Separate the build price from model usage, hosting, and other subscriptions. Name the monthly spend limit, alert recipient, and behavior at the limit. Explain any delay in cost reporting. Ask the builder to state how the proposed control handles retries and concurrent work. Require a record for each run. For this example, record the inputs, reporting period, output, blocked steps, model, and cost. Mark estimates as estimates. State where these records live and who can open them. Include a no-work result when there are no eligible inputs. ## Write the acceptance cases before delivery Name the acceptance owner and the evidence they will review. Include ordinary work, missing inputs, conflicting records, an attempted prohibited action, and recovery after a failed run. NIST's AI RMF Core includes documenting test sets, evaluation methods, and results. Use that reference to ask for repeatable checks tied to your function. [NIST AI RMF Core](https://airc.nist.gov/airmf-resources/airmf/5-sec-core/) (checked October 26, 2026). For the report example, remove an update and confirm the agreed incomplete-input behavior. Try a reporting period with no eligible records. Attempt a send without approval. Define what passes each case. The [build acceptance guide](/articles/what-a-build-acceptance-list-contains) expands this part of the scope. ## Include handoff, training, and maintenance boundaries List the business records, operating rules, configuration, code, checks, runbook, and run history included at handoff. Identify third-party licenses and services separately. State who controls each production account. Require the future operator to practice starting, checking, correcting, and pausing the function. Name the training deliverable and the person attending. Include an exercise using the runbook without the builder directing each step. Explain who handles defects after acceptance and for what period. Distinguish those obligations from new functions, changed dependencies, and additional training. Use the [ownership transfer checklist](/articles/ai-system-ownership-transfer-checklist) to plan proof that the buyer can operate the delivered result. ## Keep exclusions next to the result For the illustrative report, exclusions could include collecting missing updates, translating reports, preparing customer messages, and changing project status. Choose exclusions based on your actual agreement. Ask why each excluded item is outside the scope. If the function cannot produce its promised result without that item, resolve the dependency. Do not hide required work in an exclusion that nobody owns. State how additional work is proposed and authorized. Require the new result, price, schedule effect, and acceptance checks in writing. Name who can approve the change. Keep an accepted version of the scope so the delivery team can identify which instructions apply. ## Use a compact scope structure Draft the first version under these headings. Replace every placeholder before accepting it: ```text Function: [one recurring job] Result: [output and destination] Direction owner: [role or person] Review owner: [role or person] Inputs: [approved records and versions] Missing or conflicting input: [required behavior] Allowed actions: [accounts and destinations] Prohibited actions: [explicit boundaries] Spend: [services, limit, alert, stop behavior] Run record: [fields, location, readers] Acceptance: [cases, expected results, evidence] Handoff: [files, rights, accounts, runbook] Training: [operator exercises] Buyer inputs: [items, owners, needed dates] Exclusions: [work outside this function] Terms: [price, timing, payment, corrections] Changes: [written authorization process] ``` Treat this as an outline for purchasing and delivery. It does not replace the commercial terms or any professional review your agreement requires. ## Review the scope with the people using it Ask the operator to locate the next action after a failed run. Ask the manager to find the approval step. Ask the budget owner to locate recurring charges and the spend boundary. Then read the promised result against the acceptance cases. Check that every required input has an owner and every excluded dependency has a plan. Remove claims that cannot be demonstrated within the function's boundaries. Keep a simple trace from each promised behavior to its acceptance case. If the scope requires a pause at the spend limit, identify the test that demonstrates it. For a correction path, name an exercise where the operator changes the controlling record and checks the next run. Keep unresolved decisions visible. Revise the scope before treating them as settled. A useful scope should let your business explain what it is buying, what it must contribute, and what evidence will support acceptance. ## Put the first function into writing Scale With Search studies the business, sorts recurring work, and scopes one function at a time. The method uses a business-owned record and trains the people who direct, check, and correct the function. Read [AI systems for your business](/ai-systems) for the method and current terms. To define your first function, [send your brief](/work#send-your-brief). ## Related: Ownership and Migration - [An AI Agent Approval Matrix for Small Teams](/articles/ai-agent-approval-matrix) - [What a Build Acceptance List Contains](/articles/what-a-build-acceptance-list-contains) - [AI System Ownership and Transfer Checklist](/articles/ai-system-ownership-transfer-checklist) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```