This is an operating playbook for someone hired into a Workday account in an FDE-style seat (industry term—not a Workday job product). It sequences work Workday actually documents.
Days 1–5: Inventory without changing Production
- List Extend apps in App Hub / App Manager and their promotion levels.
- List Studio collections/CLARs and which Cloud environment each targets (Studio docs: you are responsible for deploying to the right environment).
- Export or screenshot Platform Consumption Console Overview: balance, agents consuming credits, alert recipients.
- Confirm UMSA / Flex Credits policy status with the customer’s Workday owner.
Days 6–15: Make testing possible
- Confirm proxy access policy exists for non-Production (Start Proxy / Stop Proxy; Production out of scope).
- Create or locate employee/manager test workers for persona runs.
- For each critical Studio assembly, note whether AUnit tests exist; if not, capture one golden input/output pair before edits.
- For Extend, confirm WDCLI/Developer Agent entitlement if the account uses Extend Professional.
Days 16–25: Fix the operating gaps
- Name credit owner, agent operator, and builder for every Production custom agent.
- Add console custom budgets for high Rate Card skills (for example recruiting rediscovery at 750 credits per unique requisition on the public card).
- Write the deactivate-at-100% runbook—Workday will not stop the offer for you.
- Separate personal consumer AI from client work in the firm’s written policy.
Days 26–30: First outcome, narrowly
Ship one bounded outcome (one Extend fix with deploy+proxy proof, or one Studio defect with AUnit+Process Monitor)—not a platform rewrite.