Skip to content
KiweelyKiweelyKiweely

Designing Manager Time-Off and Timecard Approvals in Teams and Slack That Show Team Coverage

Managers ignore bare chat approval cards (‘Approve 24 hours of PTO for Alex?’) because a yes/no button without team overlap, accrued balance, or timecard exception context forces them to open Workday anyway. Combining live WQL coverage reads with businessProcess v1 approvals solves it in one tap.

  • By Kiweely
  • 6 min read
On this page

Managers ignore bare Workday approval pings in Microsoft Teams and Slack—“Approve 24 hours of Vacation for Alex Rivera, Dec 21–23?”—because clicking Approve blindly risks leaving a shift, customer desk, or on-call rotation unstaffed. To achieve genuine one-tap completion in chat, the approval view must query Workday live under the manager’s OAuth token and render who else in the Supervisory Organization is already out or pending, the employee’s projected remaining balance, and—for timecards—scheduled vs. reported hours and overtime exceptions right above the Approve and Send Back buttons.

Every HRIS team has watched the same pattern unfold: IT deploys an integration bot that mirrors My Tasks items into Slack or Microsoft Teams as two-button cards. In week one, managers click a few cards. By week three, pending approvals pile up again because every card forces a mental pause—“Wait, didn’t Sam and Priya already book that Friday off?”—followed by opening a browser tab, signing into Workday, navigating to the Team Absence calendar or Edit and Approve Time report, and approving there instead.

Bare Chat Bot Card vs. Context-Complete Approval Screen

The difference between a notification ping and an actual decision screen comes down to the four data points a manager checks before saying yes:

Decision Question Bare Chat Bot Card Coverage-Aware Approval Screen Workday Source Queried Live
Decision QuestionWhat is being requested? Bare Chat Bot Card"Request Time Off: Alex Rivera (24 Hours)" Coverage-Aware Approval ScreenExact calendar dates, daily units (8h / 8h / 8h), plan name (PTO - US Exempt), and requester comment. Workday Source Queried LivebusinessProcess/v1/eventSteps/{ID} + WQL allTimeOffs
Decision QuestionWho else on the team is out? Bare Chat Bot CardMissing. Manager must open Workday Team Absence calendar. Coverage-Aware Approval ScreenInline overlap strip: “2 of 7 direct reports out Dec 22 (Sam Chen — Approved; Priya Patel — Pending)”. Workday Source Queried LiveWQL allTimeOffs + scheduleShiftsBetweenStartDateAndEndDate
Decision QuestionDoes the worker have the balance? Bare Chat Bot CardMissing. Coverage-Aware Approval ScreenProjected balance as of Dec 23: 44h Available -> 20h Remaining (0h Unpaid). Workday Source Queried LiveGET /absenceManagement/v5/balances?effective=2026-12-23
Decision QuestionAre there timecard alerts or OT? Bare Chat Bot Card"Enter Time: 44.5 Hours" Coverage-Aware Approval ScreenScheduled (40.0h) vs. Reported (44.5h), 4.5h Overtime, and any missed-punch or meal-break warnings. Workday Source Queried LivetimeTracking/v7/workers/{ID}/timeTotals + WQL allTimeBlocks

Assembling Live Team Coverage Without Caching Org Trees

In a stateless pass-through architecture, you do not sync absence calendars into an external database. When a manager opens an approval card inside a Teams tab, Slack modal, DingTalk, or Lark view, their user-delegated Workday OAuth token naturally constrains WQL queries to the workers in their Supervisory Organization (and subordinate orgs if permitted by their constrained Manager security group).

Step 1: Fetch the Pending Approval Step

Query the awaiting Event Record from Workday’s My Tasks and businessProcess/v1 APIs to confirm the step is still Awaiting Action and retrieve the parent event ID, requester, and step permissions.

Step 2: Query Overlapping Team Absences via WQL

Run a targeted WQL query against allTimeOffs filtered to the requested date window (2026-12-20 through 2026-12-24, adding a one-day buffer on either side so managers spot Thursday-to-Monday bridge gaps):

sql
SELECT
  worker,
  timeOffDate,
  timeOffType,
  approvedUnits,
  pendingUnits,
  unitOfTime,
  timeOffEntryStatus
FROM allTimeOffs
WHERE timeOffDate >= '2026-12-20'
  AND timeOffDate <= '2026-12-24'
ORDER BY timeOffDate ASC, worker ASC

Because the WQL request executes with the signed-in manager’s bearer token—and allTimeOffs respects Workday’s domain security (Worker Data: Time Off constrained to the manager’s supervisory hierarchy)—Workday returns only the time-off entries for workers that manager is authorized to supervise. Notice two details that prevent bad staffing calls:

  1. Include Both approvedUnits and pendingUnits: If three employees submit December 24 off within ten minutes of each other, showing only Approved requests hides the other two unapproved requests sitting in the same manager’s queue. Surfacing Pending overlaps alongside Approved overlaps lets the manager evaluate all three together.
  2. Respect Privacy on Leave Reasons: A manager needs to know that Sam Chen has an approved absence on Tuesday (8 Hours — Out), not any protected medical leave detail that Workday’s segmented security withholds from line managers. Relying on the manager’s own Workday security token guarantees clinical orHR-restricted leave fields never leak into the coverage strip.

Step 3: Check Projected Balance as of the Request End Date

Managers routinely ask whether a request dips into negative carryover or triggers unpaid time off. Calling GET /absenceManagement/v5/balances with effective set to the final date of the request returns Workday’s exact future-dated balance projection, accounting for Start of Period vs. End of Period accruals and year-end carryover caps.

Designing Timecard Approvals That Respect Workday Time Tracking Rules

Approving weekly or biweekly timecards (Enter Time / Submit Time) has a different failure mode than PTO: rubber-stamping exceptions. In Workday’s desktop Edit and Approve Time report, Workday intentionally splits direct reports into two buckets:

  • Workers with Alerts: Employees whose reported time blocks contain critical errors, missed check-outs, unapproved overtime thresholds, or custom Time Validations.
  • Workers without Alerts: Clean timecards where reported hours match the Work Schedule Calendar or clean clock punches.

A well-designed Teams or Slack timecard approval view mirrors that exact split instead of flattening every worker into identical “Approve 40h” cards:

  1. Clean Timecards (Fast Batch or One-Tap Approve): Display Scheduled: 40.0h | Reported: 40.0h | Overtime: 0.0h | Alerts: None, allowing immediate approval via Workday’s step-approval API.
  2. Exception Timecards (Highlighted Delta + Inline Send Back): Highlight the exact day where reported hours diverge from scheduled hours (for example, Tue Nov 10: Missing Check-Out or Fri Nov 13: +3.5h Unscheduled Overtime). Give the manager an inline Send Back button that fetches valid target steps from GET /businessProcess/v1/values/sendBack/to/ and posts POST /businessProcess/v1/eventSteps/{ID}/sendBack with a clear correction note (reason) to the employee.
json
{
  "id": "a3f5b554007d20e98360015c5e6daf6",
  "to": {
    "id": "d9e4108c446c11de98360015c5e6daf6"
  },
  "reason": "Missing Thursday clock-out punch on Warehouse 4 evening shift—please update punch time and resubmit."
}

Handling Comment Validations and Concurrency Cleanly

Two Workday API nuances trip up naive chat approval integrations:

  • comment Requirements Differ by Action and Tenant Setup: On POST /businessProcess/v1/eventSteps/{ID}/approve and /deny, Workday’s REST schema marks comment as required (A181: Specify a comment), unless your tenant or individual Business Process Security Policy has Disable Comments checked (A1573: You can't comment on this business process type). Always inspect policy behavior in Sandbox so an optional comment box in Teams neither fails with A181 on an empty string nor fails with A1573 when comments are suppressed.
  • Graceful Handling of Already-Completed Steps (A212): When Retain Access to Delegated Tasks within My Tasks is enabled or a step routes to a multi-person Manager role group, another authorized approver may complete the task first. Catch HTTP 400 error code A212 and update the chat card state cleanly to “Already approved in Workday” rather than displaying a raw JSON stack trace.

Building Coverage-Aware Approval Views in Kiweely Leaf

With Kiweely Leaf (coming next), HRIS admins do not need React engineers or bot framework specialists to replace bare chat pings with coverage-aware manager approvals. You describe the approval view in plain English—for example, “Show leave approvals in Microsoft Teams with a 7-day team overlap calendar, projected remaining PTO balance, and Approve / Send Back actions”—and Kiweely Leaf’s AI agents inspect your tenant’s absence plans and business process definitions, wire the live Workday REST and WQL calls under each manager’s own Workday OAuth token, and host the experience with zero employee HR data stored at rest—ready inside Microsoft Teams, Slack, DingTalk, Feishu, Lark, the browser, or the Kiweely Leaf phone app, with no Workday Extend license required.

Frequently asked questions

Why do managers still open Workday even when chat approval notifications are enabled?

Standard notification cards show only the requester's name, plan, and total hours. Before clicking Approve, a responsible manager needs to verify whether two other peers in the same Supervisory Organization or shift are already off on those dates—forcing a context switch back into Workday's Team Absence calendar.

Which Workday APIs assemble a coverage-aware time-off approval card?

Pair GET /businessProcess/v1/eventSteps/{ID} (for the awaiting approval step) with WQL queries on allTimeOffs or scheduleShiftsBetweenStartDateAndEndDate scoped to the manager's supervisory organization, plus GET /absenceManagement/v5/balances for projected remaining balance.

Can managers approve Workday timecards from Teams or Slack without missing overtime or meal-break alerts?

Yes, provided the approval screen surfaces reported vs. scheduled hours, overtime totals, and Time Tracking validation warnings—separating clean timecards eligible for one-tap approval from workers with critical or warning exceptions.

What happens if two co-managers or a delegate try to approve the same step in chat?

Workday's businessProcess/v1/eventSteps/{ID}/approve endpoint enforces atomic state transitions on the Event Record. The first valid submission completes the step (HTTP 201), while any subsequent click receives HTTP 400 validation code A212 ('This event step is not awaiting your action').

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.