Skip to content
KiweelyKiweelyKiweely

Finding Unsubmitted Workday Time Blocks and Project Hours with WQL

Query unsubmitted and unapproved Workday time before payroll cutoff using allTimeBlocks, incompleteTimeBlocks, and projectTimesheetLinesForWorkersWithinDateRange in WQL. Pair each query with explicit data source filters so constrained managers and project leads see every permitted row.

  • Checked against Workday on
  • Applies to Workday Time Tracking & WQL
  • 6 min read
  • Published
  • By Kiweely
On this page

To find unsubmitted or unapproved hours before payroll cutoff in Workday Query Language (WQL), query allTimeBlocks (filtering on isSubmitted, isApproved, and timeBlockStatus), incompleteTimeBlocks (for open clock-ins missing an out time), and projectTimesheetLinesForWorkersWithinDateRange (for project timesheets across any timesheetStatus). Always pass the exact dataSourceFilter matching the caller’s role—supervisory manager, timekeeper, or project manager—so Workday’s constrained security groups return complete, accurate rows without over-granting tenant-wide access.

Pre-payroll time audits fail most often because “missing hours” in Workday span four distinct object states: workers who entered zero time blocks (workersWithNoTimeBlocks), workers who clocked in without clocking out (incompleteTimeBlocks), workers who saved draft hours without clicking Submit (isSubmitted = false), and submitted entries sitting in a manager’s or project lead’s approval queue (isSubmitted = true AND isApproved = false). Treating all four states as a single status filter causes silent payroll underpayments and missed client billing cutoffs.

Which WQL Data Source Matches Each Missing-Time Scenario?

Before writing a WQL statement or exposing a Reports-as-a-Service (RaaS) endpoint, map each pre-cutoff exception to the Workday data source that actually surfaces it:

Pre-Payroll Exception WQL Data Source Alias Primary Business Object filterIsRequired Key Status & Quantity Fields
Pre-Payroll ExceptionSaved draft time blocks (not yet submitted) WQL Data Source AliasallTimeBlocks Primary Business ObjectTime Block filterIsRequiredtrue Key Status & Quantity FieldsisSubmitted, isApproved, timeBlockStatus, reportedQuantity, reportedDate
Pre-Payroll ExceptionSubmitted time blocks awaiting approval WQL Data Source AliasallTimeBlocks Primary Business ObjectTime Block filterIsRequiredtrue Key Status & Quantity FieldsisSubmitted, isApproved, approvalDate, totalHoursTimeTracking, projectForWorkerTimeBlock
Pre-Payroll ExceptionProject timesheet lines in draft, submitted, or sent-back state WQL Data Source AliasprojectTimesheetLinesForWorkersWithinDateRange Primary Business ObjectProject Timesheet Line filterIsRequiredfalse (built-in prompts) Key Status & Quantity FieldstimesheetStatus, timesheetIsApproved, totalHoursInDateRange, totalHoursBillable
Pre-Payroll ExceptionClock-in punches missing an out time WQL Data Source AliasincompleteTimeBlocks Primary Business ObjectIncomplete Time Block filterIsRequiredtrue Key Status & Quantity FieldstimeBlockStatus, reportedDate, startDate, projectForWorkerTimeBlock
Pre-Payroll ExceptionEligible workers with zero entries in period WQL Data Source AliasworkersWithNoTimeBlocks Primary Business ObjectWorker filterIsRequiredfalse (org & date prompts) Key Status & Quantity FieldsWorker reference rows for follow-up reminders

For general WQL syntax rules and REST pagination mechanics, see Workday WQL fundamentals and choosing between RaaS, WQL, and REST.

Querying Unsubmitted and Unapproved Time Blocks on allTimeBlocks

The allTimeBlocks data source covers both reported and calculated time blocks, so Workday marks filterIsRequired as true to prevent unbounded full-tenant scans. Calling SELECT ... FROM allTimeBlocks without a dataSourceFilter fails validation immediately. Worse, picking the wrong filter hides unsubmitted drafts altogether—for example, myTeamsReportedTimeBlocks explicitly filters only for reported time blocks that are already Submitted or Approved.

Compare that trap against a period-scoped filter that retains draft entries:

Fails
-- Fails two ways:
-- 1. Omitting dataSourceFilter on allTimeBlocks triggers a required-filter error.
-- 2. Switching to myTeamsReportedTimeBlocks silently excludes unsubmitted draft blocks!
SELECT
  worker2,
  reportedDate,
  reportedQuantity,
  isSubmitted,
  isApproved
FROM allTimeBlocks(
  dataSourceFilter = myTeamsReportedTimeBlocks,
  organizations = ('817bbf12d6c710000fc644a491ae0015'),
  startDate = '2026-11-01',
  endDate = '2026-11-14'
)
WHERE isSubmitted = false
Works
-- Uses reportedTimeBlocksForWorkersByPeriod or timeBlocksSecuredBySupervisoryOrganization
-- so unsubmitted (isSubmitted = false) and unapproved (isApproved = false) blocks both appear:
SELECT
  worker2,
  supervisoryOrgForWorkerTime,
  reportedDate,
  timeEntryCode,
  projectForWorkerTimeBlock,
  reportedQuantity,
  isSubmitted,
  isApproved,
  timeBlockStatus
FROM allTimeBlocks(
  dataSourceFilter = timeBlocksSecuredBySupervisoryOrganization
)
WHERE reportedDate >= '2026-11-01'
  AND reportedDate <= '2026-11-14'
  AND isReportedTimeBlock = true
  AND (isSubmitted = false OR isApproved = false)
ORDER BY supervisoryOrgForWorkerTime ASC, worker2 ASC, reportedDate ASC

When auditing by Cost Center or Location rather than Supervisory Organization, swap the filter to allTimeBlocksForWorkersByCostCenter (supplying costCenter, startDate, and endDate) or allTimeBlocksForWorkersByLocation. Always include isReportedTimeBlock = true when chasing unsubmitted worker entries so you do not double-count paired calculated rows.

Catching Unsubmitted Project Hours and Cross-Org Security Traps

Project time tracking introduces two classic pitfalls in Workday: filter status blind spots and cross-supervisory security constraints.

First, examine how Workday’s project filter on allTimeBlocks behaves. The reportedTimeBlocksForProjectsProjectHierarchies filter requires projectsAndProjectHierarchies (and accepts startDate, endDate, workers, and includeSubordinateProjectHierarchies), and it surfaces submitted, sent-back, and approved time blocks for project workers. That makes it ideal for finding unapproved (isApproved = false) or sent-back project blocks before billing close, whereas completely untouched unsubmitted project timesheet lines should be queried from projectTimesheetLinesForWorkersWithinDateRange (which returns project timesheet lines in any status):

Works
SELECT
  workerForTimesheetLine,
  supervisoryOrganizationForWorker,
  project_worktag,
  timesheetPeriod,
  timesheetStatus,
  timesheetIsApproved,
  timesheetLineIsBillable,
  totalHoursInDateRange
FROM projectTimesheetLinesForWorkersWithinDateRange(
  startDate = '2026-11-01',
  endDate = '2026-11-14'
)
WHERE timesheetIsApproved = false
ORDER BY project_worktag ASC, workerForTimesheetLine ASC

Second, verify why a Project Manager often gets zero rows for matrixed engineers or consultants outside their own Supervisory Organization:

  1. Missing Project Role Assignment: The reviewer must hold an assigned role on the project or project hierarchy via Assign Roles to Projects (secured to Manage: Project Details in the Project Tracking functional area).
  2. Missing Cross-Org Domain Permissions: To report on project time across supervisory boundaries, grant a constrained role-based security group access to both Reports: Time Tracking (Time Tracking functional area) and Manage: Project Plan (Project Tracking functional area), then run Activate Pending Security Policy Changes.
  3. Accidental Unconstrained Leakage: Never grant unconstrained access to Manage: Project Plan to ordinary project leads. Workday documents that unconstrained access on Manage: Project Plan exposes all time blocks across the entire enterprise. Keep the role-based group constrained to the project/project hierarchy, and apply reportedTimeBlocksForProjectsProjectHierarchies so managers only see projects they own.
  4. Indexed Report Fields Blocking Cross-Org Rows: If you wrap your query in a custom RaaS report instead of raw WQL, remove any indexed report fields from your Custom Report Filter and Group By sections. Indexed worker/supervisory fields force Workday to intersect results with the viewer’s Supervisory Organization, silently dropping matrixed project contributors.

Catching Open Clock-Ins Before Payroll Calculation

Workers using web clocks or mobile check-in with optional out times create Incomplete Time Blocks whenever they forget to clock out. Workday excludes incomplete blocks from time calculations, so calculatedQuantity is zero even though the employee worked a full shift. Always pair your allTimeBlocks check with a query against incompleteTimeBlocks(dataSourceFilter = incompleteTimeBlocksInDateRangeSecuredToSupervisoryOrganization, startDate = '...', endDate = '...') before locking payroll.

Calling WQL Over REST and Handling Post-Cutoff Approvals

Execute your pre-payroll WQL query via GET /wql/v1/data (for queries under 2,048 characters) or POST /wql/v1/data (for queries up to 16,000 characters, such as multi-organization IN lists). Remember to append offset=0 if you need to bypass Workday’s 30-minute WQL result cache during the final hour before payroll lock:

http
POST /ccx/api/wql/v1/{tenant}/data?limit=1000&offset=0 HTTP/1.1
Content-Type: application/json

{
  "query": "SELECT worker2, reportedDate, projectForWorkerTimeBlock, startDate FROM incompleteTimeBlocks(dataSourceFilter = incompleteTimeBlocksInDateRangeSecuredToSupervisoryOrganization, startDate = '2026-11-01', endDate = '2026-11-14')"
}

To use WQL externally, ensure the caller holds View access to the Workday Query Language domain in the System functional area alongside Reports: Time Tracking. And if a manager approves late time entries after an initial pay calculation has already run for the period, run Run Pay Calculation with Smart Calculation or Smart Calculation Based on Events so those newly approved blocks flow into the open payroll result rather than stranding until next period’s retro run (see troubleshooting Time Tracking retro recalculations).

Pre-Cutoff Verification Checklist

Run these four checks in Sandbox before relying on an automated missing-time query in Production:

  1. Test all four states with synthetic entries: Stage one worker with zero entries, one with an open clock-in (incompleteTimeBlocks), one with saved unsubmitted hours (isSubmitted = false), and one awaiting approval (isSubmitted = true AND isApproved = false), and confirm your queries surface all four.
  2. Proxy or sign in as a constrained Project Manager: Confirm the manager sees project time blocks for a worker in a sibling Supervisory Organization, and confirm they cannot see blocks on an unrelated project (Manage: Project Plan constrained, not unconstrained).
  3. Verify Worked Hours Calculation Tags: If cross-checking WQL sums against Workday’s delivered Review Time or Review Project Time reports, inspect Edit Time Approval Template and Edit Project Time Approval Settings to ensure your WQL calculationTags filter matches the exact tags driving the delivered Unsubmitted Time and Submitted Time columns.
  4. Bypass stale WQL cache near cutoff: Pass offset=0 on live cutoff-morning refreshes so blocks submitted five minutes ago do not still show as unsubmitted from a cached WQL page.

If you want managers and project leads to ask for unsubmitted team or project hours directly in Claude, ChatGPT, or Gemini under their own constrained Workday security—or view a clean pre-cutoff coverage grid in the browser or Microsoft Teams—Kiweely Bridge and Kiweely Leaf (both coming next) run live WQL and RaaS queries as the signed-in user with zero employee data stored outside Workday, while Kiweely Vine builds and tests custom WQL and RaaS definitions directly against your tenant today.

Frequently asked questions

Why does my WQL query on allTimeBlocks fail without a dataSourceFilter?

In Workday, the All Time Blocks report data source (allTimeBlocks) enforces filterIsRequired as true. You must supply a valid dataSourceFilter alias inside the FROM clause, such as allTimeBlocksCreatedBetweenADateRange or timeBlocksSecuredBySupervisoryOrganization, along with its required date or organization parameters.

Why are open clock-ins missing from unsubmitted hours totals?

When a worker checks in without recording an out time, Workday creates an Incomplete Time Block and excludes it from standard time calculations until an out time is entered. Query the incompleteTimeBlocks data source separately before payroll cutoff to catch open punches.

Why cannot a Project Manager see project time blocks for workers outside their supervisory organization?

Project managers need an assignable role on the project plus access to both Reports: Time Tracking and Manage: Project Plan domains, and the query or custom report must use a project data source filter such as reportedTimeBlocksForProjectsProjectHierarchies without indexed supervisory report fields blocking cross-org rows.

Does reportedTimeBlocksForProjectsProjectHierarchies return unsubmitted draft time blocks?

No. That specific filter on allTimeBlocks only returns existing time blocks that were approved, sent back, or submitted in the date range. To catch unsubmitted project hours across all statuses, query projectTimesheetLinesForWorkersWithinDateRange or filter allTimeBlocks by supervisory, cost center, or period filters where isSubmitted is false.

Sources checked

Related guides

All guides

Let Workday check the work.

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

Get the next guide in your inbox.

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

We’ll email you once to confirm. Unsubscribe in one click from any issue.