zahra_

Paycom

Designing Smart Automation for Timecard Correction Requests

Platform
Web
Mobile
Time Clock Kiosk
My Role
Lead Product Designer
Team
2 Designers
1 Product Manager
1 Researcher
3 Developers
Timeline
4 Months

Overview

Automating Timecard Correction Requests at Scale

Managers were manually reviewing 65M+ timecard correction requests (TCRs) every year, delaying approvals and creating payroll bottlenecks. I designed a dashboard and decisioning tool that let clients automate approvals and denials using custom rule logic.

Impact

From manual effort to automated decisions at scale

Automation eliminated the friction of manual timecard decisions, with careful attention to transparency, control, and fairness. Accuracy improved too, cutting pay disputes and retroactive corrections.

  • 60%Requests resolved without manager intervention
  • 39M+Requests auto-decided annually
  • 45%Reduction in manager handling time
  • $45MEstimated annual labor cost savings

Beyond the quantitative results, the feedback revealed something important: users valued having control over the automation.

One retail area manager described the experience this way:
“It’s like I trained the system to think like me.”
An HR administrator expressed a similar sentiment:
“We trust it more because we built the logic ourselves.”

Problem

A two-minute correction could become a much bigger payroll problem.

  1. Employee

    Imagine an employee who forgets to clock out after a shift.

    They submit a timecard correction request. It's a routine issue, but the request enters the same approval process as more complicated cases.

  2. Queue

    Their manager is managing schedules, staffing, and daily operations. The request sits in a queue.

  3. Delay

    By the time it's reviewed, the payroll processing window may have passed.

  4. Payroll

    What started as a simple time correction can now require additional payroll adjustments, administrative work, and potentially a delayed or incorrect paycheck.

At the scale of 60 million decisions annually, this isn't just an inconvenience. It's a systemic operational challenge.

The existing experience

  1. Employee Submits correction
  2. Queue Waits for review
  3. Manager Manually decides
  4. Delay Payroll cutoff risk
  5. Payroll Rework required
Illustrative workflow showing how delayed approvals can increase downstream payroll work.

The core issue wasn't that managers were making bad decisions.

It was that the system treated every decision as if it required the same level of human attention.

Research

We Listened to the People Behind the Punches

To design automation that people would actually trust, we needed to go beyond business logic, we had to understand human logic.

HR admin

NeedsTranslate organizational policies into consistent, enforceable rules.

Asks“How do I know the system is making the right decisions?”

HR admin

Design opportunityGive administrators control over automation criteria, exceptions, and policy changes.

Manager

NeedsResolve exceptions quickly without reviewing every routine request.

Asks“What actually needs my attention today?”

Manager

Design opportunitySeparate automated decisions from pending actions and surface urgent exceptions.

Employee

NeedsAn easy way to correct time entries and know whether the issue has been resolved.

Asks“Will my correction be reflected in my pay?”

Employee

Design opportunityMake submission effortless and request status transparent.

How might we automate routine timecard corrections without sacrificing policy control, decision transparency, or employee trust?

Solution

Designing for Trust, Speed, and Scale

The proposed solution connects the employee's attendance record, manager approval, and HR's payroll review in one transparent workflow.

Employee submits timecard correction Request details and supporting context
Policy evaluation engine Checks eligibility, rules, and exceptions
Meets Policy
Automatically approved Decision logged and employee notified
Needs Judgment
Routed to manager Manager reviews and resolves exception

The important design decision was to avoid automating every approval blindly. The system should validate requests and escalate discrepancies while preserving configurable approval policies, employee protections, and payroll compliance.

1. HR admin experience

Approval Rules Setup: The Decision Criteria

This multi-step flow is where HR admins configure the core logic behind how timecard correction requests are auto-approved or denied.

Walkthrough of the five-step approval rule setup

Approval Rules Dashboard

This is where HR admins add and manage rules that automatically approve timecard correction requests, check which employees each rule covers, and identify overlapping rules or gaps in employee coverage.

Walkthrough of the Approval Rules dashboard

2. Manager experience

Timecard Correction Requests Dashboard

The new dashboard provides a real-time, unified view of all TCRs—auto-approved, manually reviewed, and flagged exceptions.

Walkthrough of the Timecard Change Requests dashboard

Manager Mobile Review

The Manager on the Go app gives managers instant access to timecard correction requests—both pending and completed—with just enough context to take action confidently if needed.

Also, for flagged or ambiguous cases, the system routes requests to managers with context-rich decision support.

Walkthrough of the manager mobile review screens

3. Employee experience

Employee TCR Dashboard

This is where employees track, review, and manage all their submitted timecard correction requests.

Walkthrough of the employee request dashboard

Employee TCR Flow

The employee experience for submitting timecard correction requests, designed to reduce confusion, increase transparency, and guide users toward successful submissions.

Walkthrough of the employee request flow

Trade-offs

Navigating The Hard Design Decisions

Trade-off 1

Efficiency vs. control

Automating more decisions could reduce manual effort, but overly broad rules might create compliance or payroll risks.

The design approach

Give HR administrators explicit eligibility conditions, exception handling, and visibility into automated outcomes.

Trade-off 2

Transparency vs. information overload

Managers needed to understand automated decisions without being distracted by hundreds of requests that required no action.

The design approach

Make pending exceptions the primary focus while keeping automated decisions accessible for oversight.

Trade-off 3

Simplicity vs. complex policy logic

HR policies can include thresholds, eligibility criteria, organizational differences, and edge cases.

The design approach

Progressive disclosure—keep common configuration tasks simple, while allowing access to advanced conditions when necessary.

Reflection

Automation Only Works When It Understands People First

Automation in HR software isn't about replacing people, it's about scaling their best decisions.

Transparency Earns Trust
If the system makes a decision, it has to explain why, especially in a sensitive domain like payroll.
Design is Negotiation
Balancing legal, technical, and business needs while keeping the experience clean shaped nearly every decision.
Control Builds Trust
Even the most skeptical managers adopted the tool when they felt they had control.
Complexity Demands Configuration
Every client had different thresholds, policies, and cultural expectations. We needed something configurable, not one-size-fits-all.
Overview