---
title: "Deployment Agent for discovery — Kiweely"
description: "Workday has not published a fit-gap workshop. Use Ask in a non-Production tenant to inspect what is already configured before the workshop decides."
url: https://kiweely.com/guides/ai-workday-discovery-fit-gap-workshops
---

# Discovery questions Workday’s Deployment Agent can answer

A fit-gap workshop is a project meeting, not a Workday product. Deployment Agent can explain, inspect calculated fields and security in a non-Production tenant, and suggest Configuration Catalog packages. It cannot sign a fit decision. Read-only as documented; changes are in partner early access.

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

Workday has **not** published a fit-gap workshop, a discovery module, or a scoring method for “fit.” Discovery is your meeting. What Workday has published is a way to walk into that meeting already knowing what the non-Production tenant contains.

Deployment Agent with **Ask** runs in Implementation, Preview, Sandbox, and Customer Central. It grounds answers by searching, opening tasks, and running reports, and it retrieves Administrator Guide and Community content. The concept topic calls the configuration inspection read-only. It will not mark a requirement as in scope, and as documented it does not create the configuration the workshop just approved. Workday says that with [Configuration Cloud](https://blog.workday.com/en-us/configuration-cloud.html), in opt-in early access for Workday partners since 18 November 2026, Deployment Agent can carry out changes once approved.

## What to open before the workshop

Implementation tenants are Workday’s space for testing, prototyping, and training. Customers may have several, for integrations, legacy data, and unit and end-to-end testing. Sandbox is typically a copy of Production. Sandbox Preview is that copy plus functionality coming in a release, delivered to preview about five weeks ahead of the feature release. The Global Modern Services tenant is sample data for a fictitious customer, for research and learning, not a record of your design.

Use Ask in the tenant the workshop is talking about. In Implementation, Sandbox, and Preview it reads the **active** tenant. From Customer Central, name the connected tenant. Workday’s check that you are in the right place is: “What tenants are available to me?”

There is no badge that Ask is on. Before the session, ask for five calculation fields and confirm them in **View Calculated Field**. If the names are fiction, you are on documentation Q&A. Deployment Agent (Q&A) cannot see instances or security policies.

## A workshop sequence that stays inside the product

Agree the requirement in one sentence in the room. Then use one prompt per requirement, in a **new chat**. Workday summarizes long threads and deletes history after 14 days. The decision log is the record, not the chat.

| Question the room is actually asking | Workday capability to use | Prompt shape Workday published |
| --- | --- | --- |
| Do we share a definition? | Knowledge discovery | Role, concept, “bullet points.” The published example is Top of Stack for a Workday administrator. |
| Does this tenant already do it? | Tenant inspection | “In my tenant, how does this calculated field work: \[Calculated Field\]” or custom reports by user or security group. |
| What would we configure? | Configuration intelligence | Functional area, “in my tenant,” numbered steps. The published example is a Financials calculated field for Scheduled Weekly Days. |
| Is there a delivered package? | Configuration Catalog, via Ask’s catalog support, then the catalog itself | Ask for smart package suggestions. Then open **View Configuration Catalog Content** in Customer Central and filter by SKU or country. |
| What will it hit? | Workday Touchpoints Kit, in the tenant, not in the agent | The HCM course describes the kit as the picture of data flows and configuration relationships across areas you have deployed and areas you have not. |

### Worked prompts

**Shared definition, first ten minutes.**

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

Stop there. Put the bullets on the wall. Do not continue into design in the same thread.

**What is already configured.**

> In my tenant, show me all custom reports created by \[security group\]. For each report, name the data source.

Workday’s published inspection prompt names the report list. The “for each, name the data source” clause is your addition. If Ask is on, check two reports in the tenant before you trust the list. If a report name does not open, discard the list.

**A gap that is really a missing field.**

> I am an implementer working on Financials. In my tenant, provide step-by-step instructions on how to create a calculated field that counts Scheduled Weekly Days. Provide the answer in a numbered list of steps.

That is Workday’s new-configuration example plus “in my tenant,” which the sample-prompt topic says to include because nothing on screen shows that Ask is enabled. Take the steps to **Create Calculated Field** after the workshop. The agent does not create the field.

**Delivered content instead of a custom build.**

Configuration Catalog, in Customer Central, migrates Workday-provided content to implementation and sandbox tenants with Object Transporter, at no cost. Packages are sample locale-based reports, dashboards, integrations, and related items. Workday’s example is the HCM Condition Rules package: common condition rules and calculated fields you can use in business processes or change. Each package description includes the applicable SKU, the content, and prerequisites. Ask can suggest packages. The catalog task is where you see them. Test the content before anyone migrates it toward Production. Workday says that confirmation is yours.

### What the agent must not decide

| Workshop temptation | Why it is outside the product |
| --- | --- |
| “Mark this requirement Fit.” | No such status exists on the pages above. |
| “Configure the default business process now.” | Inspection is described as read-only. The examples end with you editing. |
| “Use the GMS tenant as our design.” | GMS is fictitious sample data. |
| “The chat is the requirements record.” | Deleted after 14 days, and summarized when the thread gets long. |
| “Skip security until build.” | The security example shows a field the role cannot see because a domain policy is missing View. That shows up in discovery if you ask. |

## How to record a fit decision without inventing a Workday object

For each requirement, write four lines in the project record the same day:

1.  The sentence the business asked for.
2.  The tenant you inspected, and whether Ask returned objects you could open.
3.  The Workday object family involved: a delivered business process type, a calculated field, a report, a domain policy, or a Configuration Catalog package. The HCM course is explicit that customers do not change delivered domains or the items secured on them. They define business process definitions and grant security groups on policies.
4.  The open point a person must confirm. Workday says the agent can be incomplete. A citation to the Administrator Guide is a lead, not a signature.

Workday’s optimization example belongs in this meeting when the requirement is “keep compensation grades and job requisitions consistent during high-volume hiring.” Ask for the practices, then open the grades and requisitions in the tenant and see whether those practices describe your data.

## Failure modes

-   Running discovery in Production. There is no conversational Deployment Agent there.
-   Running it in Customer Central without naming the tenant. You may inspect the wrong connected tenant, or none.
-   Accepting a package suggestion without **View Configuration Catalog Content**. The suggestion is not the package.
-   Using Sandbox after a refresh as if last week’s prototype were still there. Sandbox is a copy of Production. Prototype work lives in an Implementation tenant, or in an extract you reloaded.
-   Letting one long chat cover security, a calculated field, and a report. Start a new chat per topic so summarization does not drop the field names.

## Frequently asked questions

### Can Deployment Agent run the fit-gap workshop?

It can answer the questions above in a non-Production tenant. It cannot host the workshop, score requirements, or store the decisions.

### Should we inspect Production configuration by refreshing Sandbox?

Sandbox is typically a copy of Production, so a fresh Sandbox is the usual place to inspect what Production contains. Confirm the refresh has finished before you treat it as Production’s copy. Implementation tenants are the place for prototype configuration that Production does not have yet.

### Does the Touchpoints Kit replace the agent?

No. The HCM course describes the kit as a visual of data flows and configuration relationships. Ask answers questions about configuration and documentation. Use the kit when a design in one area will hit another.

### What if Ask and the task disagree?

Believe the task. Workday tells you to validate every suggestion against official documentation, and to rate the answer after you have checked it.

## Sources checked

Public Workday topics listed above, fetched 2026-11-16. No Workday page fetched for this article defines a fit-gap workshop.

## 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)
-   [Deployment Agent Skills and Capabilities in 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-skills-and-capabilitie.html)
-   [Deployment Agent in 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/concept--deployment-agent-in-implementation-enviro.html)
-   [Workday Tenants and Tools](https://doc.workday.com/workday-education/en-us/course-manuals/hcm-core-for-administrators/workday-tenants-and-tools.html)
-   [Concept: Configuration Catalog](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/fzu1561545120344.html)

## Related guides

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

-   [### The 2026 Workday AI map: Sana, ASOR, Workday-built, custom, partner, and external agents Workday’s public AI story has five layers: Sana orchestrates, ASOR governs, Workday-built agents ship in the product, partners and customers bring their own, and build tools such as Developer Agent create new ones. This guide places each layer with Workday’s own words.](https://kiweely.com/guides/workday-ai-ecosystem-map-2026)
-   [### What Workday’s Deployment Agent Can and Cannot Do in Your Tenant Workday’s ASOR-enabled Deployment Agent reads tenant configuration in Implementation, Sandbox, Preview and Customer Central. It doesn’t run in Production, and edits configuration only in partner early access. Workday publishes no price; the Rate Card meters 5 credits per Ask interaction.](https://kiweely.com/guides/workday-deployment-agent-tenant-inspection)

### More guides on Custom agents and Workday AI

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

-   [Use Deployment Agent beside Object Transporter, not instead of it](https://kiweely.com/guides/ai-assistant-workday-object-transporter)
-   [Planning Agent and Decision Intelligence](https://kiweely.com/guides/workday-planning-agent-decision-intelligence)
-   [Partner-built agents and the Workday marketplace](https://kiweely.com/guides/workday-partner-built-agents-marketplace)
-   [Financial Audit Agent and Revenue Contract Agent](https://kiweely.com/guides/workday-financial-audit-revenue-contract-agents)
-   [Set up the VNDLY Contingent Sourcing Agent](https://kiweely.com/guides/workday-vndly-contingent-sourcing-agent)
-   [CRAFT prompts for the Workday Deployment Agent](https://kiweely.com/guides/workday-deployment-agent-admin-prompt-patterns)
-   [How to use Deployment Agent through an implementation](https://kiweely.com/guides/workday-deployment-agent-implementation-phases)
-   [A Workday admin’s first week with Deployment Agent](https://kiweely.com/guides/workday-admin-first-week-deployment-agent)

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

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

-   [What Clients Will Still Pay Humans for After Agents Ship Extend Apps](https://kiweely.com/blog/what-clients-still-pay-humans-for-after-agents-ship-extend)
-   [How FDEs Scope AI Agent Work Without Becoming the Unpaid Helpdesk](https://kiweely.com/blog/fde-scope-ai-agent-work-without-unpaid-helpdesk)
-   [FDE vs Workday Partner SOW: Who Owns Tenant Risk When the Agent Writes](https://kiweely.com/blog/fde-vs-partner-sow-tenant-risk-when-agent-writes)

## 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.
