---
title: "CRAFT prompts for Deployment Agent — Kiweely"
description: "How to write Deployment Agent prompts with Workday's CRAFT method: Context, Role, Action, Format, and Tone, plus the published samples."
url: https://kiweely.com/guides/workday-deployment-agent-admin-prompt-patterns
---

# CRAFT prompts for the Workday Deployment Agent

Workday’s Deployment Agent sample-prompts topic, updated 2026-11-06, says accurate answers come from five CRAFT elements. This guide restates that method, shows which elements you can omit, and rewrites the published samples so an administrator can see what each word is doing.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend**
-   9 min read
-   Published November 16
-   By Kiweely

Workday’s sample-prompts topic for Deployment Agent in implementation environments and Customer Central (last updated 2026-11-06) does not ask you to “be more detailed.” It names five elements and calls them CRAFT: **Context, Role, Action, Format, Tone**. Use them when you open **Deployment Agent** from global search in an Implementation, Preview, Sandbox, or Customer Central tenant where the agent is activated. The agent is not a Production assistant.

Two facts from that topic change how you write every prompt:

-   There is no on-screen indicator that the Ask skill is enabled. If you need the answer grounded in this tenant’s configuration, include a phrase like **in my tenant**. In Customer Central, name the connected tenant: **in my \[tenant name\] tenant**.
-   You may omit Role when the persona is already obvious, omit Format when you are fine with the default paragraph or the default step-by-step how-to, and omit Tone when the default professional voice is enough. Context and Action are the parts Workday does not tell you to skip.

## The five elements, as Workday defines them

| Element | What to put in | Workday’s example | Safe to omit? |
| --- | --- | --- | --- |
| Context | Functional area, module, or project phase. Add “in my tenant” for configuration. In Customer Central, name the tenant. | “I am working on Financials in a Phase X implementation. In my tenant...” | No, when the answer must match your tenant. |
| Role | Your persona, so the advice matches the job. | “I am a Workday administrator...” or “As a configuration specialist,...” | Yes, if you already set the role earlier in the chat, or the persona is obvious. |
| Action | The how, why, or what. | “...how do I load project budgets in bulk?” | No. A topic with no task produces a lecture. |
| Format | The shape of the answer. | “Provide the answer in a numbered list of steps.” | Yes, if a paragraph or default steps are fine. |
| Tone | How technical, and for whom. | “Give me a layperson’s terms explanation of the concept: Top of Stack.” | Yes, for ordinary technical tasks. |

Tag each clause. If Context or Action is missing, rewrite the prompt.

## Workday’s six published samples, tagged

These are the sample-prompts table, not paraphrases.

### New configuration

> I am an implementer working on Financials. Provide step-by-step instructions on how to create a calculated field that counts Scheduled Weekly Days.

| CRAFT | Present? |
| --- | --- |
| Context | Financials. No “in my tenant,” so this is a how-to from implementation knowledge, not an inspection of your fields. |
| Role | Implementer. |
| Action | Create a calculated field that counts Scheduled Weekly Days. |
| Format | Step-by-step instructions. |
| Tone | Omitted. Default voice. |

### Troubleshooting errors

> I am getting a SOAP error while using Object Transporter to migrate Payroll data. What are the common causes for this error and how do I fix them?

Context is Payroll plus Object Transporter. Action is causes and fixes. Role, Format, and Tone are omitted. The prompt also does not paste an error string. Workday’s separate SOAP example shows why that matters: put the exact fault in the next sentence.

### Tenant inspection and configuration discovery

> In my tenant, how does this calculated field work: \[Calculated Field\]

> In my \[tenant name\] tenant, show me all custom reports created by \[User/Security Group\].

The whole point of these two lines is the Context marker. Without “in my tenant” or the tenant name, you have asked for a general explanation. The second prompt is the Customer Central form: the tenant name is required because Customer Central can see more than one connected tenant.

### Environment verification (Customer Central only, ASOR-enabled agent)

> What tenants are available to me?

Workday limits this sample to Customer Central. Do not reuse it as the pattern for a configuration question.

### Learning or refresher

> As a Workday administrator, give me a layman’s terms explanation of the ‘Top of Stack’ concept. Provide the answer in bullet points.

Role is the administrator. Tone is layperson’s terms. Format is bullet points. Action is explain Top of Stack. Context is the concept itself, not a tenant. That is correct for a definition. It is the wrong shape for “why did my rule skip.”

### Optimization

> Suggest best practices for linking Compensation Grades to Job Requisitions to ensure data integrity during a high-volume hiring phase.

Action and a thin Context (high-volume hiring, compensation grades, job requisitions). Role, Format, and Tone are omitted, which the topic allows. If you need this checked against your tenant, add “In my tenant” and name the grade and the requisition process. The published sentence does not do that, so treat the answer as general practice until you ask a follow-up that does.

## Three worked prompts from Workday’s examples

### Calculated field: Context, Role, Action, Format

Workday’s calculated-field example (updated 2026-09-18) uses this prompt for a Worker field that returns Manager or Individual Contributor:

> I am a Workday administrator. I need to create a calculated field on the Worker business object. The logic should be: if a worker’s ‘Management Level’ is ‘Manager’ or any level above that (like Director or VP), return the text ‘Manager’. Otherwise, return ‘Individual Contributor’. Can you provide the step-by-step configuration and the specific calculation type I should use?

Tagged: Role is administrator. Context is the Worker business object and the management-level rule. Action is the if/then text. Format is step-by-step plus the calculation type. Tone is omitted.

The example says the agent typically recommends **Evaluate Expression**, then these parameters for **Create Calculated Field**: business object Worker, default value Individual Contributor, a Management Level condition using an In Selection List operator, and return value Manager when true. You still open **Create Calculated Field** and compare the hierarchy to your tenant. The follow-up in the example is the pattern for a naming mismatch:

> My tenant uses ‘Lead’ instead of ‘Manager’. How should I update the condition to include ‘Lead’ and everything above it?

That second turn keeps the role from the first turn, which is why the CRAFT topic says you can omit Role once it is established.

### Security: force tenant inspection

The Ask-skill security example uses:

> I am a Workday security administrator. In my tenant, users assigned to the Payroll Specialist role cannot view the ‘Bonus Plan Override’ field on worker profiles. Please look in my tenant and inspect our security configuration to explain which domain security policy controls access to this field, which security groups currently have View access, and how to update the policy.

Every CRAFT element that matters for an audit is here. Context is “in my tenant” plus the field and the role. Role is security administrator. Action is three explicit questions: which domain, who has View, how to update. Format is the three-part explanation. Tone is omitted.

The example’s result names domain **Worker Data: Compensation Explicit** and says the Payroll Specialist role-based group is missing from View. It then points at editing domain security policy permissions and activating pending changes. A Customer Central follow-up from the same example:

> How would activating this security policy change impact downstream security group assignments in our impl2 tenant?

Use that shape when you want impact in another tenant: name the tenant. Do not assume the agent inspected impl2 because you were signed in to a different one.

### SOAP: Context and Role first, then the exact fault

The SOAP example splits CRAFT across two messages. First:

> I am an integration consultant working on a Financials implementation. I am calling the Submit\_Expense\_Report web service and receiving a ‘Validation error occurred’ message regarding a missing field.

Then the fault and what you already checked:

> The error says: ‘The field Expense\_Report\_Data is required.’ I have confirmed this field is in my XML. What are the most common hidden missing fields or security issues that cause this specific SOAP fault for this service?

Optional third turn, which is a new Action with a tighter scope:

> List the specific functional area and security domain permissions my Integration System User (ISU) needs to initiate this specific web service.

The example says Workday SOAP sometimes returns a parent-element fault when the real gap is a missing child element or a security requirement. Paste the string. Say what you already verified. Then ask for the domain permissions rather than “fix my integration.”

## What to cut

| If you write this | What you dropped | What you get |
| --- | --- | --- |
| “How do calculated fields work?” | Action is a definition, Context has no object | A glossary entry. Fine for Tone=layperson. Useless for a build. |
| “Look at my security” | No field, no group, no “in my tenant” | General domain theory. Ask may not be engaged. |
| “In my tenant, best practices for everything in HCM” | Action is unbounded | A long list you cannot test. |
| A Customer Central prompt that says “in my tenant” but never names the tenant | The connected-tenant Context | Inspection of the wrong tenant, or a clarifying question. |
| Repeating your job title on every turn | Nothing required | Allowed, but the topic says to omit Role once it is established. |

## A blank you can fill

> I am a \[role\]. I am working on \[functional area\] in \[phase or tenant type\]. In my \[tenant name\] tenant, \[one task: how, why, or what\]. \[Optional: numbered steps, a table, or bullet points.\] \[Optional: layperson’s terms, or for a security administrator.\]

Send it only from a tenant where **Deployment Agent** is on global search and your group is on **Available To** for the skill you need. After you apply steps, use thumbs up or thumbs down. A thumbs down rates the guidance. It does not undo a domain change you already activated.

## Frequently asked questions

### Is CRAFT a Workday product setting?

No. It is the prompting method on the sample-prompts topic. You do not enable CRAFT in Agent Management Hub. You write it into the message.

### Which skills does “in my tenant” assume?

The security and SOAP examples say the **Deployment Agent** task reaches the tenant-aware agent when **Tenant Inspection** is enabled. The setup topic says Ask needs both Tenant Inspection and Implementation Knowledge. A prompt cannot turn a skill on.

### Can I paste a Community answer and ask the agent to confirm it?

Ask it as an inspection, not as “is this post true.” Use the security example’s shape: in my tenant, this field, this security group, which domain, who has View. Compare the answer to the domain policy before you activate changes.

### Why does the optimization sample ignore CRAFT?

It does not. It uses Action and a small Context, and it omits the three elements Workday says you may omit. Add “in my tenant” only when you want your grades and requisitions inspected.

## Sources checked

The four frontmatter pages, fetched 2026-11-16. Quoted prompts are the published samples and the three worked examples on those pages.

## Sources checked

-   [Deployment Agent Sample Prompts for Implementation Environments and Customer Central](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/deployment-agent-in-implementation-environments-an/reference--deployment-agent-sample-prompts-for-imp.html)
-   [Example: Create a Calculated Field with the Deployment Agent](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/deployment-agent-in-implementation-environments-an/example--create-a-calculated-field-with-the-deploy.html)
-   [Example: Troubleshoot Security Policy and Access Configuration with the Ask Skill](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/deployment-agent-in-implementation-environments-an/example--troubleshoot-security-policy-and-access-c.html)
-   [Example: Troubleshoot a SOAP Error with the Deployment Agent](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/deployment-agent-in-implementation-environments-an/example--troubleshoot-a-soap-error-with-the-deploy.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Financials and payroll prompts for the Workday Deployment Agent Workday’s samples already cover a Financials calculated field, an Object Transporter payroll error, a Submit\_Expense\_Report SOAP fault, and a Payroll Specialist field-access case. This guide quotes those prompts and shows the few fill-ins that stay inside the same CRAFT rules.](https://kiweely.com/guides/workday-ai-prompt-library-financials-payroll)
-   [### HCM prompt library for Workday implementers using Deployment Agent Workday published CRAFT and a handful of samples, including a Worker management-level calculated field and a tenant report listing. This library tags each HCM prompt as published or as a fill-in that uses only those elements, so you do not treat a pattern as a Workday-certified script.](https://kiweely.com/guides/workday-ai-prompt-library-hcm-implementers)
-   [### Review security group changes an AI assistant suggested in Workday Deployment Agent can name a domain and a missing View group. As documented, you still edit the policy (change-making is in partner early access), activate pending changes, and confirm View Security for Agent Skill is not Config Required. Constrained groups cannot administer Agent System of Record.](https://kiweely.com/guides/review-ai-workday-security-group-changes)
-   [### Prove an AI-suggested Workday calculated field before it drives a condition rule Deployment Agent’s documented example suggests Evaluate Expression logic for a Worker field and you build it in Create Calculated Field; Configuration Cloud (partner early access) can make approved changes. This guide shows how to prove the field before a rule or integration uses it.](https://kiweely.com/guides/ai-workday-calculated-fields-condition-rules-proof)
-   [### A Workday admin’s first week with Deployment Agent Deployment Agent is a non-production assistant for implementers and administrators. This week plan follows Workday’s setup: confirm UMSA, set up Agent System of Record per tenant, secure Deployment Agent Users, register skills, and prove one tenant-grounded prompt.](https://kiweely.com/guides/workday-admin-first-week-deployment-agent)

### More guides on Custom agents and Workday AI

[All 91 guides](https://kiweely.com/guides#custom-agents)

-   [How to use Deployment Agent through an implementation](https://kiweely.com/guides/workday-deployment-agent-implementation-phases)
-   [Workday Core Reporting Agent: when conversational reporting is enough](https://kiweely.com/guides/workday-core-reporting-agent)
-   [Workday Adoption Agent: Release Impact Analysis for Preview admins](https://kiweely.com/guides/workday-adoption-agent-release-impact)
-   [Workday-built AI agents catalog: what each agent is for](https://kiweely.com/guides/workday-built-ai-agents-catalog)
-   [The 2026 Workday AI map: Sana, ASOR, Workday-built, custom, partner, and external agents](https://kiweely.com/guides/workday-ai-ecosystem-map-2026)
-   [Why Generic IDE Agents Still Need Workday Developer Agent for Extend](https://kiweely.com/guides/why-generic-ide-agents-need-workday-developer-agent)
-   [Complimentary Workday Flex Credits: What They Are and What Happens When They Run Out](https://kiweely.com/guides/complimentary-workday-flex-credits-what-happens-when-exhausted)
-   [AI Agents That Edit Workday Studio XSLT Safely: Diff, AUnit, Then Deploy](https://kiweely.com/guides/ai-agents-edit-workday-studio-xslt-safely)

### From the blog on Custom agents and Workday AI

[All posts](https://kiweely.com/blog)

-   [Five Workday Custom Agents Worth Building First in HR and Finance](https://kiweely.com/blog/workday-custom-agent-use-cases-hr-finance)
-   [Workday Agent-Ready Tools Explained: Workday’s MCP Tools for AI Agents](https://kiweely.com/blog/workday-agent-ready-tools-explained)
-   [Using Workday Developer Agent in Claude Code, Cursor or VS Code](https://kiweely.com/blog/workday-developer-agent-claude-code-cursor)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
