---
title: "Requirements into a business process — Kiweely"
description: "Workday does not store a BRD. Map a requirement onto a delivered business process type, its security policy, steps, and condition rules, then inspect it with…"
url: https://kiweely.com/guides/ai-brd-to-workday-business-process-design
---

# Turn a requirements note into a Workday business process

A business requirements document is your paper. Workday delivers business process types and lets you define definitions: steps, security groups, and timing. Deployment Agent can explain and inspect a non-Production definition; as documented, you edit it and activate security yourself.

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

A business requirements document is not a Workday object. Workday has not published a “BRD import.” What it has published is the business process framework: a delivered **business process type**, one **business process security policy** for that type, and one or more **definitions** that say which steps run, which security groups act, and when.

Deployment Agent with Ask can inspect definitions, condition rules, and reports in Implementation, Sandbox, Preview, and Customer Central, and can help explain why a rule did not fire. The concept topic describes that inspection as read-only. 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. The design becomes real when someone edits the definition and activates security policy changes.

## Translate one requirement into Workday’s three questions

The HCM core course states a business process as what, who, and when.

| Line in the requirements note | Workday object | Constraint Workday documents |
| --- | --- | --- |
| What must happen | A step on a definition: action, approval, to do, subprocess, or another delivered step type | You do not invent a new business process type. You configure a delivered type. The payroll course says the same: you cannot create a brand-new business process; you create versions for organizations. |
| Who does it | A security group on the step, and that group on the business process security policy | The policy secures initiate, approve, delegate, cancel, and the other actions for every definition of that type. A group on the step must be allowed by the policy. To do steps are the exception: they can be assigned to any active security group, but a task on that to do still requires the group to be able to open the task. |
| When it happens | Order, due date, delay, and a condition | Entry conditions decide whether a step runs. Validation conditions, on initiation and action steps, stop the process when they are true. Exit conditions complete an approval chain or integration step. While-running conditions apply to approval chains. |

Functional areas such as Staffing and Core Compensation contain both domains and business processes. Customers cannot change a delivered domain or the items secured to it. They grant security groups on the policy.

## Inheritance before you copy a definition

Workday recommends a **default** definition. Copy or link an organization-specific definition only when the steps really differ. Maintenance is harder when every copy shares the same steps, and testing “the” definition is harder when several exist.

When someone starts the process, Workday looks for a definition on that organization, then on superiors, then the default. A definition with errors, or an inactive one, is skipped and inheritance continues. Effective date matters: a future-dated definition is not the one running today.

The setup topic adds the routing ingredients: organizations, roles, hierarchies, and locations. Business process security policies, not domain policies, decide who may participate and which actions they may take. Each step still names a security group. Workday also says to limit the number of steps for performance. Rule-based definitions can pick a path from the goal of the process, the initiator’s role, or another condition. You can copy and modify a large library of preconfigured processes; the setup topic says “over 550.”

## A practical pass from the note to the definition

Do this in an Implementation tenant, or in Sandbox if you are changing a copy of Production. One requirement per pass.

1.  Name the delivered type. Hire, Change Job, and Propose Compensation for Hire are the HCM course’s common examples. Period Close Event is the course’s example of an accounting manager closing ledgers for operational transactions. If you cannot name the type, you are not ready to edit a definition.
2.  Open **Business Process Configuration Options** for that type and the security policy. The course tells you to use both.
3.  Ask Deployment Agent, in a new chat, with the tenant named:

> I am a Workday administrator. In my tenant, which business process definition runs for \[type\] on \[supervisory organization\]? List the steps, the security group on each step, and any entry condition. If a default and an organization-specific definition both exist, say which inheritance will use.

Check two steps in the definition before you trust the list. Ask has no on-screen “inspection on” badge.

1.  Write the delta in the project record: step to add or remove, group, condition, effective date. Do not leave it in the chat. History lasts 14 days.
2.  Edit the **business process security policy** first if the new group is not allowed to act. Use **Business Process Policy > Edit**, then **Activate Pending Security Policy Changes**. Only then **Business Process > Edit Definition**.
3.  Add conditions with **Create Condition Rule** (the rule goes into the library) and **Maintain Step Conditions** (the rule is applied to the step). The course’s fields are And/Or, the source field or rule, the operator, and the comparison value.
4.  After a real event exists, use **Business Process > Test Rule** from that event. You need the Business Process Administration domain. Some entry conditions are delivered and cannot be edited; yours are evaluated as well, and the step runs only if all of them pass.

### Worked example: “Managers must approve a title change”

The HCM course already uses Change Business Title as a pattern: the manager reviews the title, then the HR partner approves. Your note should say which supervisory organizations use that path. If only one organization differs, copy a definition for that organization rather than loading the default with exceptions. If the difference is a condition (“only when the worker is in this location”), keep the default and add an entry condition. The course says complex conditions on one definition can slow processing; organization-specific copies are easier to read and perform better, and they cost more to maintain.

Ask can explain the concept in lay terms first, using the knowledge-discovery capability, so the room agrees what an approval chain is. An approval chain walks a hierarchy until the top or an exit condition. A common exit is “only two managers.” That is course material to confirm in your definition, not a default you should assume is already configured.

### Where security requirements hide

A requirements line such as “payroll specialists can see the bonus override” is not a business process step. It is a **domain** policy. Workday’s Ask example for that field is: which domain controls Bonus Plan Override, which groups have View, and how to update it. In Workday’s illustration the domain is Worker Data: Compensation Explicit and the role is missing View. Your tenant may differ. Edit the domain policy and activate it. The business process definition will not grant that view.

## What the agent will get wrong if you let it design alone

| Failure | What to do |
| --- | --- |
| It proposes a new business process type | Reject it. Configure a delivered type. |
| It names a security group that is not on the policy | The step cannot use that group for a secured action. Edit the policy first. |
| It ignores a superior organization’s definition | Walk inheritance: organization, then superior, then default. Skip definitions that are in error or inactive. |
| It designs in Production chat | Deployment Agent is not a conversational assistant in Production. Design in Implementation or Sandbox. |
| It cites a condition you cannot find | Open **Maintain Step Conditions**. Delivered entry conditions are not all editable. |
| The workshop treats the chat as the signed design | Copy the definition name, effective date, and step list into the project record the same day. |

BP Optimize Agent is a separate Workday-built agent. The catalog says it analyzes current processes and recommends improvements with steps. It is not Deployment Agent, and this guide does not describe its setup. Do not assume it is active because Ask is.

## Frequently asked questions

### Can I paste a requirements document into Deployment Agent and get a definition?

You can paste one requirement and ask for the delivered type, the steps, and the groups, with “in my tenant.” As documented, you still edit the definition. A long document in one thread will be summarized. Split it.

### Do domain security and business process security do the same job?

No. Domains secure tasks, reports, and data. The business process security policy secures actions on that process type. Both have to allow the person you named in the requirements note.

### Should every country get its own definition?

Only when the steps differ. Otherwise use the default, or a rule-based definition, and keep one copy to test. The course warns that the right definition is easy to miss when many copies exist.

### When is the design “done”?

When the definition you expect is the one inheritance selects, the groups are on the policy, pending security changes are activated, a test event fires the conditions you care about, and the project record names the definition and its effective date. An Ask answer is not that moment.

## Sources checked

Public Workday course and admin-guide topics listed above, fetched 2026-11-16. Workday does not publish a business-requirements-document object on those pages.

## Sources checked

-   [Overview of Workday HCM Core Concepts](https://doc.workday.com/workday-education/en-us/course-manuals/hcm-core-for-administrators/overview-of-workday-hcm-core-concepts.html)
-   [Business Process Framework](https://doc.workday.com/workday-education/en-us/course-manuals/hcm-core-for-administrators/business-process-framework.html)
-   [Setup Considerations: Business Processes](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-process-framework-concepts/khy1593557050505.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)
-   [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)

## 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 Business processes and security

[All 27 guides](https://kiweely.com/guides#business-processes)

-   [Benefits Life-Event Intake That Starts the Right Workday Process](https://kiweely.com/guides/benefits-life-event-intake-workday-business-process)
-   [How do I document Workday configuration and business processes from a live tenant?](https://kiweely.com/guides/document-workday-configuration-and-business-processes)
-   [How to Run Role-Boundary Security Tests Across Employee, Manager, and HR Partner Personas](https://kiweely.com/guides/workday-role-boundary-testing-employee-manager-hr-partner)
-   [Aligning Workday Session Timeouts with External OAuth Access Token Lifetimes](https://kiweely.com/guides/workday-anonymous-vs-authenticated-session-timeout-oauth)
-   [How Workday Terminations and Job Transfers Affect Active OAuth Grants](https://kiweely.com/guides/workday-revoke-oauth-tokens-terminated-transferred-workers)
-   [Configuring Workday Pre-Hire Security So New Employees Can Complete Tasks Before Day One](https://kiweely.com/guides/workday-pre-hire-onboarding-access-before-day-one-security)
-   [Tuning Workday Business Process Notifications When Using External Mobile or Chat Approvals](https://kiweely.com/guides/workday-notification-delivery-settings-suppressing-duplicate-emails)
-   [Workday Time Off vs. Leave of Absence: Helping Employees Pick the Right Request Type](https://kiweely.com/guides/workday-leave-of-absence-vs-time-off-employee-request-routing)

### From the blog on Business processes and security

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

-   [Preparing Workday Domain and Business Process Security Policies for a SOX Audit in Hours, Not Weeks](https://kiweely.com/blog/auditing-workday-segregation-of-duties-before-sox-review)
-   [The Anatomy of a Production-Safe Workday Change: Propose, Approve, Execute One by One, Read Back](https://kiweely.com/blog/anatomy-of-a-production-safe-workday-change)
-   [Why Workday Condition Rules Pass in Sandbox and Fail in Production](https://kiweely.com/blog/why-workday-condition-rules-fail-in-production)

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