Skip to content
KiweelyKiweelyKiweely

What to put in a Workday SOW when agents are in scope

A statement of work is your contract, not a Workday feature. Scope tenants, packages, security activation, and test events. If an agent is in scope, quote the limits: read-only inspection as documented, no Production chat, and 14-day history.

  • By Kiweely
  • Updated
  • 6 min read
On this page

Workday has not published a statement of work, a rate card for “AI implementation,” or a clause that makes an agent’s answer a deliverable. The SOW is yours. If you leave the agent unnamed, the client will hear “configured” when the team means “the assistant described it.” Write the difference into the scope.

Scope lines that match Workday objects

Write this Do not write this
Write thisConfiguration of named business process types on named supervisory organizations, in a named Implementation tenant, migrated to Production with Object Transporter after a reviewed diff. Do not write this“Configure HCM end to end.”
Write thisDomain and business process security policies for named groups, activated with Activate Pending Security Policy Changes. Do not write this“Security design complete” with no policy names.
Write thisInbound integrations chosen in Workday’s tool order, launched and verified. Do not write this“Data conversion by AI.” Workday has not published that product.
Write thisClient tests as named security groups, evidenced by business process events. Do not write this“UAT sign-off by the agent.”
Write thisCustomer Central administrators retained by the customer, at least two security administrators and two customer-central administrators when a partner is involved, because the partner will roll off. Do not write this“Partner holds the only Customer Central admin.” Workday recommends the customer keep those accounts. The initial owner account deactivates after 60 days.
Write thisReference IDs assigned before the first migration. Do not write this“IDs to be cleaned up in hypercare.” Mismatched IDs stop the prerequisite check.

Customer Central is included for new customers at no additional cost, is not part of the service, and its data is not customer data. One Customer Central tenant is enough. Say who the named support contact is. A single Customer Central account cannot hold multiple roles.

Implementation tenants are for prototyping, training, integrations, legacy loads, and unit and end-to-end testing. Sandbox is a copy of Production and refreshes. Do not sell Sandbox-only configuration as a durable deliverable unless the SOW also includes the extract or the migration that puts it somewhere a refresh will not erase.

If Deployment Agent is in scope, quote the product

Use language you can point at in the admin guide:

  • Available as a conversational assistant in Implementation, Preview, Sandbox, and Customer Central connected to non-Production. Not in Production.
  • Requires the agreement path Workday states: available on the Universal Main Service Agreement; a Main Service Agreement must opt in.
  • Ask grounds answers by searching, opening tasks, and running reports, and by retrieving documentation. The concept topic describes configuration inspection as read-only. Workday’s Configuration Cloud, in opt-in early access for Workday partners since 18 November 2026, adds that Deployment Agent can carry out changes once approved, so scope it separately if the team will use it. The client still gets the configured tenant, not the transcript.
  • No on-screen indicator that Ask is on. The team must verify with a prompt that only the tenant can answer.
  • Chat is isolated by tenant and deleted after 14 days. The SOW’s deliverable cannot be “the agent transcripts.”
  • Setup in each tenant. Setup in Production is how Sandbox refreshes keep the registration. Ask does not consume Flex Credits in Production and costs 5 per interaction in Implementation and Sandbox tenants. Deactivate in Production if the client does not want the agent to return on every refresh.
  • Answers can be incomplete. The team validates against the task and the Administrator Guide. A wrong suggestion is not a defect in the client’s configuration until someone has confirmed it in the tenant.
  • Object Transporter faults are in the sample prompts. Running the migration is not.

Out of scope unless a different Workday-built agent is actually registered: Payroll Agent “completing payroll,” Financial Audit Agent “closing the books,” BP Optimize “signing the process design.” The catalog describes those agents more narrowly. Do not bundle them because AI is a heading in the SOW.

If a desktop agent is in scope, say whose sign-in

Kiweely Vine signs in as the user, asks before a change, and can test with Start Proxy in a browser you watch. It can draft design documents and test scripts from the tenant and file them on the project. Extend apps are promoted through Sandbox; Workday checks the version; Production stays the customer’s.

Put in the SOW:

  • Whose Workday sign-in the agent will use. Each Vine conversation is one client. Do not leave “the firm’s agent” ambiguous across clients.
  • That approval is required before a change, and that a transcript is not the approval record.
  • That proxy tests count only for the proxied security group, and the client’s own test is a separate deliverable.
  • The commercial terms you are actually selling. Vine Free is free on that person’s Workday personal developer tenant. Any other tenant needs a Personal license at $99 a month or a firm seat at $149 a month, two seats at least. Do not describe that as a Workday subscription.
  • That Vine is not a Workday-built agent and is not registered by the Deployment Agent setup.

A desktop agent with no Workday sign-in can draft a workbook. Do not price that draft as configuration.

Acceptance

Accept a workstream when a person who is not the agent can open:

  1. The definition, policy, report, or integration in the tenant named in the SOW.
  2. For anything that had to move, the post-migration summary. Those summaries last two years. Tenant Compare is the additional proof when “tenants match” is the claim. Unmatched Reference IDs mean one side is missing the instance.
  3. For anything the client was to do, the event run as that client’s security group.
  4. For agent-assisted analysis, a decision-log entry written the same day, not a chat archive.

Reject “the agent confirmed” as acceptance language.

Failure modes that become contract fights

  • Scope says “Production-ready AI support.” Deployment Agent cannot be used in Production. You just sold an absence.
  • Scope says the partner will “own Customer Central until go-live” and nobody at the client can create users on day 61.
  • Data conversion acceptance is a spreadsheet the agent filled, and Object Transporter never ran because the objects were transactional. Transactional data is not what Object Transporter migrates.
  • Two clients in one desktop-agent workspace because the SOW said “the partner’s AI.” Keep the sign-ins separate.
  • Flex Credits assumed to be zero for every agent because they are zero for Ask in Production. Only say that where Workday says it.

Frequently asked questions

Should the SOW ban agents?

No. Ban unlabeled agents. Name Deployment Agent’s tenants and retention. Name any desktop agent’s sign-in and approval. Keep acceptance on Workday records.

Who pays for a wrong agent answer that we configured anyway?

The team that configured it. Workday says to validate suggestions. The SOW should say the tenant, not the chat, is the work product. The commercial remedy is whatever you negotiate; Workday’s pages do not set it.

Can we promise 14-day chat export as audit evidence?

You can promise to copy decisions out before day 14. You cannot promise Workday will keep the chat. Post-migration summaries are the long-lived product record.

Does a Workday deployment include these agents automatically?

Deployment Agent is not turned on in every non-Production tenant by itself. Someone must set up security and activate it in each tenant. Customer Central setup does not enable the others. The SOW should name that setup as a task with an owner, or explicitly exclude it.

Sources checked

Public Workday topics listed above, fetched 2026-11-16. Commercial terms for Kiweely Vine are from kiweely.com, not from Workday. Workday does not publish an SOW template on the pages checked.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

We’ll email you once to confirm. Unsubscribe in one click from any issue.