AI service scope and change-control agreement
Prepare the decisions needed for a written automation scope and later changes. This is not a ready-to-sign legal agreement.
Done when: Deliverables, acceptance, ownership, cost boundaries and the change process are clear enough for the parties' appropriate review.
Enable JavaScript for on-page entry and smart printing, or print a blank copy from your browser and complete it offline.
Included workflow and deliverables
Name the exact systems, outputs and implementation tasks included, using business-only descriptions.
Exclusions and client responsibilities
List excluded work, required approvals, content/access readiness and who owns each dependency.
Acceptance and evidence
Define measurable synthetic tests, review responsibility and what demonstrates that the agreed delivery is complete.
Costs, timing and support
Record the approved commercial source, recurring third-party costs, schedule assumptions and support boundaries. Do not invent a price or deadline.
Change request and approval
Describe how a requested change is documented, assessed and separately approved before additional work or charges.
Ownership, exit and qualified review
Identify customer-owned data/assets, export and access removal, unresolved legal terms and the appropriate reviewer. Never make leaving harder to keep a customer.
Reference links and review boundary
Use the current issuer, payer, regulator, platform or qualified professional for your exact activity and location. These links informed the planning questions; they do not make this an official form, full compliance review or permission to operate.
Healthcare businesses are welcome for business education. PublicProof does not receive, store or process patient information. A completed worksheet does not establish HIPAA compliance, transport qualification, professional authority, account approval, a credential, reimbursement or revenue.
Worksheet updated October 20, 2026. Verify changing requirements before relying on them.