Global Pattern · Everest Design System

Record List Template

Standardizing CRUD workflows across 32 product teams—one template, two experiences

The Problem

Every team building their own CRUD

Dayforce is built around lists of records. Employee lists. Payroll entries. Time cards. Benefits enrollments. Every product area needed to Create, Read, Update, and Delete records.

But each of the 32 teams had built their own patterns.

Recruiting Team

Edit in modal dialogs

Payroll Team

Inline editing in cells

Time & Attendance

Separate edit pages

Benefits Team

Side panel drawers

Solution

One template, two experiences

Instead of prescribing a single CRUD pattern, we recognized two distinct user archetypes and built the Record List Template to serve both.

Employee Experience

Side Panel Editing

For occasional users who need focus and clarity. View and edit one record at a time.

→ Click row to open side panel

→ Form-based editing experience

→ Clear labels, validation, guidance

→ Save/Discard actions

Admin Experience

Inline Editing

For power users who need speed and efficiency. Edit multiple records without context switching.

→ Click cell to edit in place

→ Tab through fields quickly

→ Bulk actions and selection

→ Row action menus

Visual Comparison

Employee Version

Side panel slides in. Form-based editing. Clear save/discard actions. Focused experience for occasional users.

Admin Version

Click to edit cells. Tab through fields. Row actions. Bulk operations. Speed-optimized for power users.

⟷

← Employee (Side Panel) | Admin (Inline) →

Impact

Platform-wide standardization

80%

Product surfaces using template

Teams standardized on pattern

27.6K+

Weekly component insertions

Consistency

Users learned CRUD once, applied everywhere. No more relearning patterns per product.

Efficiency

Teams ship CRUD in days, not weeks. No rebuilding flows from scratch.

Next Project

Notification Framework →