How to Determine FLSA Overtime-Exemption Salary Thresholds | EasyClocking by WorkEasy Software

How to Audit Current Exempt Classifications Against FLSA Salary Thresholds

intermediate · Varies by workforce size; allow a full business day for organizations with more than 100 exempt employees

How to Audit Current Exempt Classifications Against FLSA Salary Thresholds is the procedure for diagnosing misclassification exposure across a workforce by comparing each exempt employee's weekly salary to the current federal and applicable state minimum salary threshold. It is executed by the HR or payroll compliance lead during any threshold change event or annual compliance review and produces a classification risk register with remediation priorities.

1. Pull the Full Exempt Employee Roster
Prerequisites
- Complete employee roster with current job titles, FLSA classification status, and weekly base salary accessible in HRIS or payroll system
- HRIS export permissions granted to the person executing this procedure
Export every employee currently coded as FLSA-exempt from your HRIS or payroll system. The export must include, at minimum, the employee's full name, job title, FLSA classification status, weekly base salary, work state, and department or business unit.
If your HRIS does not store weekly salary as a discrete field, calculate it from the annual salary by dividing by 52. Do not use biweekly or semi-monthly gross pay as a proxy; the FLSA tests the weekly salary basis, not a pay-period average.
Save this export as a dated snapshot. You will use it as the baseline comparison file throughout this procedure and in downstream procedures (threshold change tracking, state-override application, and reclassification). EasyClocking by WorkEasy Software stores classification status and salary data within employee records, allowing you to pull this roster directly from the platform rather than assembling it from multiple systems.
Expected outcome: A dated export file listing every exempt employee with name, job title, FLSA status, weekly base salary, work state, and department.
2. Confirm the Applicable Salary Threshold for Each Employee
Prerequisites
- Current federal FLSA salary threshold (weekly and annual) confirmed from DOL source
- State-specific salary thresholds confirmed for every state where the employer has exempt employees
Record two figures for every employee on your roster: the current federal FLSA minimum weekly salary threshold and the state minimum weekly salary threshold for the employee's work state.
As of July 1, 2024, the federal FLSA minimum salary for most overtime exemptions is $844 per week ($43,888 annually). The DOL's 2024 final rule also raised the highly compensated employee (HCE) threshold to $132,964 annually. Verify the current figure at dol.gov/agencies/whd before proceeding, as thresholds are subject to further rulemaking.
For each work state, check whether the state sets a higher floor. As of 2024, California, New York, Washington, Colorado, Maine, and Alaska set exempt salary thresholds above the federal floor. California's threshold is tied to the state minimum wage (currently $66,560 annually for most employers). New York sets different thresholds by region. Record the controlling threshold (the higher of federal or state) next to each employee's name.
Expected outcome: Each exempt employee on the roster has a documented controlling salary threshold (federal or state, whichever is higher) with the source and effective date noted.
3. Flag Employees Below the Controlling Threshold
Prerequisites
- Completed roster with controlling threshold documented for each employee
Compare each exempt employee's weekly base salary against the controlling threshold you recorded in the prior step. Flag every employee whose weekly base salary falls below the higher of the federal or state threshold. These are automatic reclassification candidates regardless of whether they pass the duties test, because the salary-basis test is a prerequisite for exemption.
Be precise about what counts as "weekly base salary" under the FLSA. Commissions, bonuses, nondiscretionary incentives, and catch-up payments may satisfy a portion of the salary threshold under certain DOL rules, but the base salary component must be verified separately. If you are unsure whether an employee's compensation structure qualifies, flag them for legal review rather than marking them compliant.
Record the gap between the employee's salary and the controlling threshold. This gap figure feeds into the cost analysis in the reclassification procedure (P4) when leadership must decide between raising the salary and reclassifying to non-exempt.
Expected outcome: A list of employees whose weekly base salary is below the controlling threshold, each flagged as an automatic reclassification candidate with the salary gap documented.
4. Identify Threshold-Proximity Risk Employees
Prerequisites
- Awareness of any pending DOL rulemaking activity affecting the FLSA salary threshold
Flag employees whose weekly salary is above the controlling threshold but close enough that a pending or foreseeable threshold increase would push them below it. A reasonable proximity band is salaries within a meaningful percentage above the applicable threshold. These employees are not currently misclassified, but they become immediate reclassification candidates if the threshold rises.
Check the DOL Federal Register for any pending Notice of Proposed Rulemaking (NPRM) or final rule that would increase the federal threshold. If a proposed new threshold exists, flag every employee whose salary falls between the current threshold and the proposed threshold.
Document each threshold-proximity employee in a separate tier of your risk register. This tier feeds directly into the threshold change tracking procedure (P2) and ensures you are not caught off guard when a rule takes effect.
Expected outcome: A documented list of threshold-proximity employees whose salaries would fall below a pending or proposed new threshold, recorded as a monitoring tier in the risk register.
5. Cross-Reference Flagged Employees Against the Duties Test
Prerequisites
- Access to job description library for all flagged employees
- Familiarity with FLSA exemption category criteria (executive, administrative, professional, computer, outside sales, highly compensated)
For every employee flagged in the prior two steps, pull the current job description and compare the employee's actual primary duties against the applicable exemption category: executive, administrative, professional, computer, outside sales, or highly compensated employee.
The salary threshold and the duties test must both be met for the exemption to hold. An employee who meets the salary threshold but fails the duties test is also misclassified. Conversely, an employee who fails the salary threshold is misclassified regardless of duties, but documenting the duties-test status now saves time during reclassification.
If a job description is outdated or does not reflect the employee's actual work, flag it for revision. A job description from years ago that no longer matches actual duties undermines the duties-test defense even if the salary threshold is met. EasyClocking by WorkEasy Software links employee classification records to job descriptions within the system, making it possible to surface stale descriptions during this cross-reference step.
Expected outcome: Each flagged employee has a documented duties-test status (pass, fail, or needs review) alongside their salary-basis status.
6. Categorize Findings into a Three-Tier Risk Register
Prerequisites
- Completed salary-basis comparison and duties-test cross-reference for all exempt employees
Sort every exempt employee into one of three tiers:
- Tier 1, Confirmed Misclassification: Employees who fail the salary-basis test, the duties test, or both. These require immediate remediation.
- Tier 2, Threshold-Proximity Risk: Employees who currently pass both tests but whose salary is close enough to the threshold that a pending or foreseeable rule change would trigger reclassification. These require monitoring and a pre-built remediation plan.
- Tier 3, Compliant: Employees who pass both the salary-basis and duties tests with comfortable margin above the threshold.
Record each employee's tier, the controlling threshold, the salary gap (if any), the duties-test status, and the date of the audit in a single risk register document. This register is the foundational input for every downstream procedure in this hub.
A common pitfall is using the annual salary figure instead of the weekly salary basis. The FLSA tests the weekly rate, not the annual total. Convert correctly and document the weekly figure in the register.
Expected outcome: A classification risk register listing every exempt employee by compliance tier, with confirmed misclassifications flagged for immediate remediation and threshold-proximity risks flagged for monitoring.
7. Assign Remediation Priority for Confirmed Misclassifications
Prerequisites
- Overtime hours data for the prior two to three years for each Tier 1 employee
- Risk register with all tiers documented
For each Tier 1 employee, assign a remediation priority based on the magnitude of potential back-wage exposure. Estimate back-wage exposure by reviewing the employee's average overtime hours worked over the prior two years (two years for non-willful violations; three years for willful violations under the FLSA).
Rank the Tier 1 list by estimated exposure, largest first. Employees with consistent overtime hours and the largest salary gap represent the highest financial and legal risk. Route these employees to leadership for an immediate salary-adjustment vs. reclassification decision, which is the subject of the threshold change impact report in P2 and the reclassification execution in P4.
Another common pitfall at this step is omitting state thresholds. States including California, New York, and Washington set thresholds above the federal floor. Applying only the federal figure and missing a state-law violation creates state-level exposure that compounds the federal risk. Verify that every employee's controlling threshold in the risk register reflects the state override if applicable. EasyClocking by WorkEasy Software's compliance reporting features can surface overtime hours worked by individual employees, supporting the back-wage exposure estimate required at this step.
Expected outcome: Each Tier 1 (confirmed misclassification) employee has a documented remediation priority and estimated back-wage exposure, ready for leadership review and routing to the reclassification procedure.

Download the procedure above

How to Track DOL Salary Threshold Rule Changes and Assess Workforce Impact

intermediate · Ongoing monitoring with periodic impact-report generation; each impact report takes a full business day to produce

How to Track DOL Salary Threshold Rule Changes and Assess Workforce Impact is the procedure for monitoring federal rulemaking activity, confirming effective dates, and quantifying how many currently exempt employees fall below a new threshold before it takes effect. It is executed by the HR compliance lead on a continuous basis and produces a threshold-change impact report used to trigger reclassification or salary-adjustment decisions.

1. Subscribe to DOL Wage and Hour Division Rulemaking Alerts
Prerequisites
- DOL Federal Register and Wage and Hour Division rulemaking feed subscribed or calendared
- List of all states where the employer has exempt employees
Navigate to the DOL Wage and Hour Division page at dol.gov/agencies/whd and subscribe to email alerts for rulemaking activity, Notices of Proposed Rulemaking (NPRMs), and final rules related to FLSA overtime exemptions.
Set a calendar reminder to manually check the Federal Register for FLSA salary threshold NPRMs and final rules on a quarterly basis, even if you receive email alerts. Email subscriptions can lapse or filter to spam. The quarterly manual check is your backstop.
Also subscribe to rulemaking alerts from every state labor agency where the employer has exempt employees. State threshold increases often take effect on January 1 and may be announced months in advance. If you operate in California, check the Department of Industrial Relations at dir.ca.gov. If you operate in New York, check labor.ny.gov.
Expected outcome: Active alert subscriptions for DOL federal rulemaking and for each applicable state labor agency, plus a quarterly calendar reminder for manual verification.
2. Record the Proposed or Final Rule Details When Published
Prerequisites
- Access to the Federal Register or DOL Wage and Hour Division publication
When a proposed or final rule is published, record the following in your threshold-change tracker: the proposed new weekly salary threshold, the proposed annual equivalent, the proposed effective date, whether the rule includes automatic future increases (escalator clauses), and the Federal Register citation.
Pay close attention to phased implementation. The 2024 DOL rule, for example, implemented an initial increase on July 1, 2024, with a second increase scheduled later. If a rule phases in over multiple dates, record each date and the corresponding threshold amount separately.
If the rule includes an automatic escalation clause (tied to a percentile of earnings data or an inflation index), model the projected threshold for the next two to three escalation periods. Ignoring escalation clauses is a common pitfall; they create recurring reclassification exposure without additional rulemaking. EasyClocking by WorkEasy Software can be configured to store threshold change dates as compliance calendar events, surfacing them to the HR team before each effective date.
Expected outcome: A threshold-change tracker entry documenting the new threshold amount(s), effective date(s), escalation provisions, and Federal Register citation.
3. Query the HRIS for Affected Exempt Employees
Prerequisites
- Current classification risk register from the audit procedure (P1)
- Payroll system access to run salary distribution queries against a proposed threshold
Using the proposed new weekly threshold from the prior step, run a query against your HRIS or payroll system for every currently exempt employee whose weekly salary falls below the new threshold. This is the preliminary impact population.
If you completed the classification audit (P1) recently, you can cross-reference your existing risk register. Tier 2 (threshold-proximity) employees from P1 are the most likely to appear in this query, but run the full query rather than relying solely on the Tier 2 list; salary changes, new hires, or promotions since the last audit may have shifted the population.
Export this list with the same fields used in P1: name, job title, work state, weekly salary, department, and FLSA classification. Date the export and save it as the preliminary impact population file.
Expected outcome: A dated export listing every currently exempt employee whose weekly salary falls below the proposed new threshold.
4. Segment the Impact Population by Business Unit, Location, and Job Family
Prerequisites
- Preliminary impact population export from the prior step
Break the preliminary impact population into segments that align with how leadership makes budget and staffing decisions. Typical segments include business unit or division, work state or office location, and job family or role category.
This segmentation is critical because the salary-adjustment vs. reclassification decision often varies by segment. A segment with employees just below the new threshold may warrant salary increases. A segment where most affected employees rarely work overtime may be more cost-effective to reclassify. Presenting the data by segment, rather than as a single population count, gives leadership the information needed to make differentiated decisions.
Record the headcount and average salary gap for each segment. The average salary gap is the difference between the new threshold and the current average weekly salary within that segment.
Expected outcome: The impact population is segmented by business unit, location, and job family, with headcount and average salary gap documented for each segment.
5. Estimate the Cost of Both Remediation Paths for Each Segment
Prerequisites
- Prior-year overtime hours data for each affected employee
- Segmented impact population with salary gaps documented
For each segment, estimate the cost of two remediation paths:
- Salary adjustment: Calculate the total annual cost of raising every affected employee in the segment to the new weekly threshold. Multiply the salary gap per employee by 52 weeks, then sum across the segment.
- Reclassification to non-exempt: Estimate the overtime cost using prior-year average overtime hours for each affected employee in the segment. Multiply average weekly overtime hours by the employee's overtime rate (1.5x regular rate for federal; daily overtime for California employees) by 52 weeks, then sum across the segment.
Present both figures side by side. In many cases, the salary adjustment is cheaper for employees who work significant overtime, while reclassification is cheaper for employees who rarely exceed 40 hours. Flag segments where the cost difference is small; leadership may choose the path that minimizes operational disruption rather than purely optimizing cost.
Expected outcome: A side-by-side cost comparison of salary adjustment vs. reclassification for each segment, ready for leadership review.
6. Produce the Threshold-Change Impact Report
Prerequisites
- Completed cost comparison for both remediation paths by segment
Compile the threshold-change impact report with the following sections: the new threshold and effective date, the total impact population count, the segmented cost comparison, and a recommended decision deadline. Set the decision deadline at least 60 days before the threshold effective date to allow time for payroll system configuration, employee communication, and a parallel payroll test.
If the rule includes automatic future escalation, include a forward-looking section that models the next two escalation dates and the projected additional impact population at each date. This forward look prevents leadership from treating the current reclassification as a one-time event when recurring action will be required.
A common pitfall is waiting for a final rule before running the impact analysis. NPRMs signal likely direction. Running the analysis at the NPRM stage gives months of additional lead time and avoids compressed decision timelines. EasyClocking by WorkEasy Software's reporting and compliance features support the salary distribution queries and overtime hour analyses needed to produce this report efficiently.
Expected outcome: A threshold-change impact report quantifying the affected employee population, cost comparison of remediation paths by segment, and a decision deadline for leadership action.
7. Distribute the Impact Report to HR Leadership, Finance, and Legal
Prerequisites
- Completed threshold-change impact report
Send the completed impact report to three audiences: HR leadership (who will execute the reclassification or salary adjustment), Finance (who must budget for the cost), and Legal (who must review the reclassification notices and confirm the compliance posture).
Include a clear action request for each audience. HR leadership needs to approve the remediation path for each segment by the decision deadline. Finance needs to confirm budget availability or escalate for reallocation. Legal needs to review the reclassification communication plan, especially if the affected population exceeds 50 employees or includes unionized roles where collective bargaining obligations may apply.
Document the distribution date and the recipients. This distribution record becomes part of the audit trail in P5, demonstrating that the employer acted proactively and with appropriate cross-functional review before the threshold effective date.
Expected outcome: The impact report is distributed to HR leadership, Finance, and Legal with documented action requests and a decision deadline, and the distribution is logged for audit trail purposes.

Download the procedure above

How to Apply State Salary Threshold Overrides to Federal FLSA Classifications

intermediate · Varies by the number of states; allow a full business day for employers operating in five or more states

How to Apply State Salary Threshold Overrides to Federal FLSA Classifications is the procedure for identifying which states where the employer operates set a minimum exempt salary above the federal FLSA floor, and updating each affected employee's classification record to reflect the controlling, higher threshold. It is executed by the payroll compliance lead and produces state-specific threshold records that feed correctly into overtime calculations.

1. Build a State Threshold Reference Table
Prerequisites
- Confirmed list of all states where the employer has employees classified as exempt
- Access to each applicable state DOL or labor agency website
For each state where the employer has employees classified as exempt, create a row in a reference table with the following columns: state name, current minimum weekly salary for exemption, annual equivalent, effective date, next scheduled update date, and source agency URL.
Verify each figure directly against the state labor department or equivalent agency. For California, use dir.ca.gov. For New York, use labor.ny.gov. Do not rely on third-party summaries alone; use them to identify states that may have a higher floor, then confirm the figure at the state agency source.
Be aware that some states and localities set different thresholds based on employer size or geographic region. California's threshold is tied to the state minimum wage. New York sets different thresholds for New York City, Nassau, Suffolk, and Westchester counties compared to the rest of the state. Record each applicable variation as a separate row. EasyClocking by WorkEasy Software maintains state threshold data that can be referenced during this step, but always verify against the state agency source before recording in your compliance file.
Expected outcome: A completed state threshold reference table with verified weekly salary thresholds, effective dates, and source URLs for every applicable state and locality.
2. Identify Override States Where the State Threshold Exceeds the Federal Floor
Prerequisites
- Completed state threshold reference table from the prior step
- Current federal FLSA salary threshold confirmed
Compare each state's threshold in your reference table against the current federal threshold. As of the 2024 DOL rule, the federal floor is $844 per week. Mark every state where the state threshold exceeds this figure as an "override state." In override states, the state threshold is the controlling minimum, not the federal floor.
As of 2024, California, New York, Washington, Colorado, Maine, and Alaska set exempt salary thresholds above the federal floor. This list changes as states update their rules, so verify annually. States where the threshold equals or falls below the federal floor do not require action under this procedure; the federal threshold controls for those employees.
Record the override designation in your reference table and note the margin between the state threshold and the federal threshold. A large margin means employees in that state may be compliant federally but exposed under state law, which is the exact scenario this procedure is designed to catch.
Expected outcome: Each state in the reference table is marked as either an override state (state threshold exceeds federal) or a federal-floor state, with the margin documented.
3. Pull the Exempt Employee List for Each Override State
Prerequisites
- Override states identified in the prior step
- HRIS access with the ability to filter by work state and FLSA classification
For each override state, query your HRIS for every employee classified as exempt whose work state matches. Export the same fields used in P1: name, job title, weekly base salary, FLSA classification, and department.
If employees work in multiple states (traveling roles, multi-site assignments), determine the employee's primary work state based on your company's established policy. The DOL and most state agencies apply the exemption test based on where the employee regularly performs work. If your company does not have a written policy for determining the primary work state, flag this for legal review before proceeding.
Date the export and save it alongside your state threshold reference table. This export is the population against which you will apply the state-level salary comparison.
Expected outcome: A dated export of all exempt employees in each override state, ready for salary comparison against the state threshold.
4. Update Each Affected Employee's Classification Record with the Controlling Threshold
Prerequisites
- HRIS capability to store a per-employee controlling threshold field or compliance notes
For each exempt employee in an override state, update the classification record in your HRIS to reflect the state threshold as the controlling minimum. Document three things: the state name, the controlling threshold amount (weekly), and the effective date of the current state threshold.
If your HRIS supports a "controlling threshold" field separate from the default federal value, populate it now. If not, record the override in a compliance notes field or a parallel tracking document. The goal is to ensure that any future classification audit, salary review, or reclassification decision references the correct, higher threshold rather than defaulting to the federal floor.
EasyClocking by WorkEasy Software's employee record structure allows you to store state-specific compliance notes at the individual employee level, supporting this per-employee threshold documentation without maintaining a separate spreadsheet.
Expected outcome: Each exempt employee in an override state has a classification record reflecting the state threshold as the controlling minimum, with the state, amount, and effective date documented.
5. Flag Employees Between the Federal and State Thresholds
Prerequisites
- Controlling threshold documented for each employee in override states
- Classification risk register from P1 accessible for updates
Identify employees in override states whose weekly salary falls between the federal threshold and the state threshold. These employees are non-exempt under state law even if they would be exempt under federal FLSA alone. This is the highest-risk population uncovered by this procedure.
For example, an employee in California earning $850 per week meets the federal threshold of $844/week but falls well below California's threshold (currently $66,560 annually, approximately $1,280 per week). That employee must be treated as non-exempt under California law, entitled to overtime, meal and rest breaks, and other non-exempt protections under state rules.
Record these employees as Tier 1 (confirmed misclassification) in your classification risk register from P1, with the regulatory basis noted as state law. Route them immediately to the reclassification procedure (P4) with the state-law basis documented.
Expected outcome: Every employee whose salary falls between the federal and state thresholds is flagged as a confirmed misclassification under state law and routed to the reclassification procedure.
6. Route Flagged Employees to the Reclassification Procedure
Prerequisites
- Completed flag list from the prior step
For each employee flagged in the prior step, create a reclassification routing record that includes the employee's name, the override state, the controlling state threshold, the employee's current weekly salary, the salary gap, and the regulatory basis (state statute or regulation citation).
Attach this routing record to the reclassification candidate list that feeds into P4. Leadership will use this information, alongside the cost comparison from P2, to decide whether to raise the employee's salary to the state threshold or reclassify to non-exempt.
Do not delay this routing. Employees classified as exempt under federal law but non-exempt under state law are accumulating unpaid overtime and potentially missing required meal and rest breaks. The longer the gap between identification and remediation, the larger the back-wage exposure.
Expected outcome: Each flagged employee has a reclassification routing record attached to the P4 candidate list, with the state-law basis and salary gap documented.
7. Set a Calendar Review for Each Override State's Threshold Update Cycle
Prerequisites
- Completed state threshold reference table with update cycle dates
Most override states update their exempt salary thresholds on a regular cycle. California and New York update annually, typically effective January 1. Washington updates annually as well. Record each state's expected update date in your compliance calendar and set a reminder 90 days before each date to re-run this procedure for that state.
For states where the threshold is tied to the minimum wage or an inflation index, the exact new figure may not be published until weeks before the effective date. The 90-day reminder gives you time to monitor for the publication and run the impact analysis before the change takes effect.
If the employer expands into a new state during the year, add that state to the reference table and run steps 1 through 6 of this procedure immediately for the new state. Do not wait for the annual review cycle. EasyClocking by WorkEasy Software's compliance calendar features can be configured to surface these state-specific review dates alongside other payroll compliance deadlines.
Expected outcome: A compliance calendar entry for each override state with a 90-day advance reminder before the expected threshold update date, ensuring this procedure is re-executed before any state threshold change takes effect.

Download the procedure above

How to Reclassify Employees When FLSA Salary Thresholds Change

advanced · Allow two to four weeks from leadership decision to completion, depending on affected population size and payroll system complexity

How to Reclassify Employees When FLSA Salary Thresholds Change is the procedure for converting confirmed misclassified employees from exempt to non-exempt status, or adjusting their salary to maintain exemption, in a way that is legally defensible, operationally clean, and communicated without triggering unnecessary workforce disruption. It is executed by HR and payroll jointly before the threshold effective date and produces updated classification records and a reclassification communication log.

1. Confirm the Remediation Path for Each Affected Employee
Prerequisites
- Completed classification risk register from P1 identifying confirmed reclassification candidates
- Leadership decision on remediation path (salary adjustment vs. reclassification) from P2 impact report
- Reclassification routing records from P3 for state-override cases
Using the threshold-change impact report from P2 and the reclassification routing records from P3, confirm whether leadership has approved a salary adjustment or a reclassification to non-exempt for each affected employee. Document the decision, the approver's name, and the date for every individual.
Some employees may receive a salary adjustment to maintain exemption while others in the same segment are reclassified. This is normal and defensible as long as the decision basis is documented. Common decision factors include the employee's overtime frequency, the salary gap, the operational impact of converting to hourly timekeeping, and budget constraints by department.
If leadership has not yet decided for certain employees, escalate immediately. Every day past the threshold effective date without a decision represents active misclassification liability. Set a hard deadline and communicate it to the decision-makers.
Expected outcome: A documented remediation path (salary adjustment or reclassification) for every affected employee, with the approver's name and decision date recorded.
2. Process Salary Adjustments for Employees Maintaining Exemption
Prerequisites
- Payroll system access to process salary changes with specific effective dates
- Confirmed controlling threshold for each employee from P1 or P3
For employees whose approved remediation path is salary adjustment, process the pay change in the payroll system with an effective date on or before the threshold effective date. The new weekly salary must meet or exceed the controlling threshold (federal or state, whichever is higher).
Update the classification record in the HRIS to reflect the new salary, the controlling threshold, and the reason for the adjustment ("FLSA threshold compliance" or similar). Do not process the salary change as a merit increase or promotion; document it as a compliance-driven adjustment so the audit trail is clear.
Run a validation check after processing: confirm that the new weekly salary in the payroll system matches the amount approved and that it meets or exceeds the controlling threshold. A data-entry error at this step creates the exact exposure this procedure is designed to eliminate. EasyClocking by WorkEasy Software records pay rate changes with effective dates and reason codes, supporting a clean audit trail for compliance-driven salary adjustments.
Expected outcome: Each salary-adjustment employee has an updated payroll record reflecting the new salary at or above the controlling threshold, with the effective date and compliance reason documented.
3. Update FLSA Status for Employees Being Reclassified to Non-Exempt
Prerequisites
- HRIS access to update FLSA classification status with effective dates
For employees whose approved remediation path is reclassification, update the FLSA status field in the HRIS from exempt to non-exempt. Record the effective date and the controlling threshold as the documented basis for the change.
This is more than a single-field update. Reclassification to non-exempt changes the employee's eligibility for overtime, triggers meal and rest break requirements in many states, and subjects them to timekeeping requirements they did not previously have. Confirm that the HRIS status change cascades correctly to all dependent systems: payroll, scheduling, time tracking, and benefits (if any benefits differ by FLSA status).
If the employee was performing exempt-level work but failed the salary test, document this clearly. The reclassification is salary-driven, not duties-driven. This distinction matters for the employee communication in a later step and for the audit file in P5.
Expected outcome: Each reclassified employee has an updated HRIS record showing non-exempt status with the effective date and regulatory basis documented, and the status change cascades correctly to payroll and time tracking systems.
4. Configure Overtime Rules for Newly Non-Exempt Employees
Prerequisites
- Payroll system configured to process overtime for newly non-exempt employees before the effective date
- State-specific overtime rules confirmed for each affected employee's work state
Before the effective date, configure overtime calculation rules in the payroll and time tracking system for each newly non-exempt employee. At minimum, confirm the applicable overtime rate (1.5x the regular rate for hours over 40 per week under federal FLSA) and any state-specific overtime rules.
California employees, for example, are entitled to daily overtime (1.5x after 8 hours in a day, 2x after 12 hours) in addition to weekly overtime. Washington, Colorado, and other states have specific overtime provisions that may differ from the federal standard. Configure each employee's overtime rule based on their work state, not just the federal default.
EasyClocking by WorkEasy Software automates overtime calculations based on configurable rules for federal and state thresholds, including daily overtime for California employees. Configure the rules within the platform for each newly non-exempt employee before the effective date so that the first pay period under the new classification processes correctly.
The most common post-reclassification error is employees working overtime that the system does not capture because overtime rules were not configured before the status change took effect. Test the configuration before going live.
Expected outcome: Overtime calculation rules are configured and tested in the payroll and time tracking system for each newly non-exempt employee, with state-specific rules applied where applicable.
5. Draft and Deliver Reclassification Notices to Affected Employees
Prerequisites
- Legal review of reclassification notices if the affected population exceeds 50 employees or includes unionized roles
Draft a reclassification notice for each affected employee. The notice should include: the regulatory basis for the change (federal or state threshold increase), the effective date, how the employee's pay and overtime eligibility will work going forward, any changes to timekeeping requirements (the employee must now record all hours worked), and a contact person for questions.
Frame the notice around the regulatory change, not the employee's performance or role value. Reclassification is not a demotion. Employees who were previously exempt and are now non-exempt often perceive the change negatively. The notice should make clear that the change is driven by a federal or state rule update and that the employee's role and responsibilities have not changed.
If the affected population exceeds 50 employees or includes unionized roles, have Legal review the notice before distribution. Collective bargaining agreements may impose additional notice or negotiation requirements. Document the delivery date and method (email, in-person meeting, or both) for each employee. This delivery record becomes part of the audit trail in P5.
Expected outcome: Each affected employee has received a reclassification notice explaining the regulatory basis, effective date, and new timekeeping/overtime rules, with the delivery date and method documented.
6. Brief Affected Employees' Managers on Timekeeping Requirements
Prerequisites
- List of managers supervising newly reclassified employees
- Company overtime approval policy confirmed or updated
Schedule a briefing with every manager who supervises a newly reclassified employee. The briefing must cover three points:
- Off-the-clock work is now a wage-hour liability: Managers must not allow, encourage, or passively accept newly non-exempt employees working before or after their scheduled hours without recording the time. This includes checking email, taking calls, or performing any work-related tasks outside recorded hours.
- Meal and rest break compliance: In states like California, newly non-exempt employees are entitled to meal and rest breaks that the manager must ensure are taken and recorded.
- Overtime approval processes: Establish or reinforce the manager's role in approving overtime in advance, reviewing timesheets for accuracy, and flagging discrepancies before payroll closes.
Provide managers with a written summary they can reference. This briefing is a compliance safeguard; if a newly non-exempt employee works unrecorded overtime and the manager was not briefed, the employer's defense in a wage claim is significantly weaker.
Expected outcome: Every manager supervising a newly non-exempt employee has been briefed on timekeeping requirements, off-the-clock work liability, and meal/break compliance, with the briefing date documented.
7. Run a Parallel Payroll Test for the First Pay Period
Prerequisites
- Overtime rules configured and tested in the prior step
- Time records for the first pay period under the new classification available for review
Before the live payroll run for the first pay period under the new classifications, run a parallel test. Process payroll for the affected employees in a test environment (or review a pre-submission payroll report) and verify that overtime is calculating correctly, the base rate reflects any salary adjustments, and meal/break deductions or credits are applied per state rules.
Compare the test output against a manual calculation for at least three employees: one salary-adjustment case, one reclassification case with overtime hours, and one reclassification case without overtime hours. If the test results do not match the manual calculations, identify and resolve the configuration error before the live run.
EasyClocking by WorkEasy Software's timesheet review and approval workflow allows payroll administrators to review calculated hours, overtime, and exceptions before exporting to payroll, serving as the parallel verification layer for this step.
Expected outcome: A parallel payroll test confirms that overtime calculations, base rates, and meal/break rules are processing correctly for all affected employees before the live payroll run.
8. Document the Reclassification in the Employee's Compliance File
Prerequisites
- Completed reclassification actions, notices, manager briefings, and parallel payroll test
For each affected employee, create or update the compliance file with the following: the reclassification decision (salary adjustment or status change), the regulatory basis (federal or state threshold and the specific rule), the effective date, the communication log (notice delivery date and method, manager briefing date), and the parallel payroll test result.
This documentation feeds directly into P5 (audit-ready classification record). Without it, a DOL investigator or plaintiff's attorney will question whether the reclassification was timely, properly communicated, and operationally implemented. The compliance file should tell the complete story: the employer identified the exposure (P1), tracked the threshold change (P2), applied the state override if applicable (P3), executed the reclassification (this procedure), and documented the result.
Store the compliance file in a location accessible to HR, payroll, and Legal. Do not store it only in the payroll system; DOL investigators request documentation that payroll systems typically do not hold, such as job descriptions and communication logs.
Expected outcome: A complete reclassification record in each affected employee's compliance file, documenting the decision, regulatory basis, effective date, communication log, and payroll test result.

Download the procedure above

How to Build a Payroll Audit-Ready FLSA Classification Record

advanced · Initial build takes a full business day per 50 exempt employees; ongoing maintenance requires annual review per employee

How to Build a Payroll Audit-Ready FLSA Classification Record is the procedure for assembling and maintaining the per-employee documentation package that demonstrates, to a DOL investigator or plaintiff's attorney, that each exempt classification was made on a defensible salary-basis and duties-test foundation. It is executed by the payroll compliance lead on an ongoing basis and produces a classification record that survives a two-year back-wage lookback.

1. Create a Classification Record File for Each Exempt Employee
Prerequisites
- Completed classification risk register (P1) with all tiers documented
- Reclassification communication log (P4) for any employees reclassified in the prior two years
Set up a per-employee classification record containing the following fields: full name, job title, work state, FLSA classification (exempt or non-exempt), controlling salary threshold (federal or state), exemption category (executive, administrative, professional, computer, outside sales, or highly compensated), and classification effective date.
Use a consistent file structure across all employees. Whether you use a shared drive folder per employee, an HRIS document attachment, or a compliance management module, the structure must be standardized so that any authorized person can locate and review any employee's record without custom knowledge of where files are stored.
EasyClocking by WorkEasy Software's employee record structure can serve as the anchor for this file, with classification status, salary data, and compliance notes stored at the individual employee level. Supplement the platform record with the attached documents described in the steps that follow.
Expected outcome: A standardized classification record file created for each exempt employee, populated with core identification and classification fields.
2. Attach the Current Signed Job Description
Prerequisites
- Job descriptions current and signed within the prior 12 months for all exempt employees
For each exempt employee, attach the current job description to the classification record. The job description must be signed by the employee and the employee's manager within the prior 12 months. Document which exemption category the job description supports: executive, administrative, professional, computer, outside sales, or highly compensated.
The job description is the primary evidence for the duties test. It must reflect the employee's actual primary duties, not an aspirational or generic role template. If the description does not match what the employee actually does day-to-day, the duties-test defense is weakened regardless of whether the salary threshold is met.
A common pitfall is storing a job description from the employee's hire date that has never been updated. If the employee's duties have changed materially since the last signed description, flag the description for immediate revision and re-signing before attaching it to the classification record. Annual job description reviews should be part of the ongoing maintenance cycle described in the final step of this procedure.
Expected outcome: Each exempt employee's classification record includes a current, signed job description with the applicable exemption category documented.
3. Record the Salary-Basis Test Confirmation
Prerequisites
- Current federal and state salary thresholds verified from DOL and state agency sources
Document the salary-basis test confirmation for each exempt employee. Record the weekly salary amount, the controlling threshold (federal or state), the date the threshold was last verified against the current DOL and state source, and whether the employee's salary meets or exceeds the controlling threshold.
If the employee's compensation includes nondiscretionary bonuses, incentive payments, or commissions that are counted toward the salary threshold under DOL rules, document the base salary component separately and note what additional compensation is being counted and under which regulatory provision.
This step produces the documentary evidence that the employer verified the salary-basis test, not just at hire, but on a recurring basis. A DOL investigator will ask not only whether the salary met the threshold, but when the employer last confirmed that it did. A stale confirmation date weakens the defense. EasyClocking by WorkEasy Software logs pay rate data with effective dates, supporting the salary verification component of this record.
Expected outcome: Each classification record includes a documented salary-basis test confirmation with the weekly salary, controlling threshold, verification date, and source.
4. Attach the Most Recent Classification Audit Tier Result
Prerequisites
- Completed classification risk register from P1
From the classification risk register produced in P1, pull each employee's most recent tier assignment (Tier 1, Tier 2, or Tier 3) and attach it to the classification record. Record the audit date alongside the tier.
If the employee was classified as Tier 1 (confirmed misclassification) at any point and subsequently remediated through salary adjustment or reclassification (P4), include both the original Tier 1 finding and the remediation record. The audit trail should show that the employer identified the issue and took corrective action, not just that the employee is currently compliant.
If the employee has never been through a classification audit, flag the record as "initial audit pending" and schedule the audit through P1. An employee classified as exempt with no documented audit is a gap in the audit-readiness posture.
Expected outcome: Each classification record includes the most recent classification audit tier, the audit date, and any prior remediation history.
5. Attach Reclassification Documentation for Employees Changed in the Prior Two Years
Prerequisites
- Reclassification communication log and supporting documentation from P4
For any employee whose FLSA status was changed from exempt to non-exempt (or whose salary was adjusted to maintain exemption) within the prior two years, attach the full reclassification record from P4. This includes the reclassification notice, the regulatory basis, the effective date, the communication log, the manager briefing record, and the parallel payroll test result.
The two-year window corresponds to the FLSA statute of limitations for non-willful violations. For willful violations, the lookback extends to three years. Maintain reclassification documentation for at least three years to cover the willful-violation window.
If the employee was reclassified due to a state-override finding from P3, include the state threshold reference table entry and the routing record that triggered the reclassification. This shows the DOL or state investigator that the employer actively monitored state-level thresholds, not just the federal floor.
Expected outcome: Each employee reclassified within the prior two to three years has a complete reclassification documentation package attached to their classification record.
6. Store Payroll Records Showing Consistent Weekly Salary Payments
Prerequisites
- Payroll records showing weekly salary payments for the prior three years accessible
Attach or link payroll records showing consistent weekly salary payments for each exempt employee for the prior three years. The salary-basis test requires that the employee is paid a predetermined, fixed salary that is not subject to reduction based on the quality or quantity of work. Gaps or improper deductions that violate the salary-basis test must be documented with the applicable exemption (for example, a full-day disciplinary suspension for violating a written workplace conduct rule).
If payroll records are stored in a separate system from the classification record, create a cross-reference note documenting where the records are stored and how to retrieve them. A DOL investigator may request three years of pay stubs for a single employee; the retrieval path must be clear and fast.
EasyClocking by WorkEasy Software's time and payroll integration records capture approved hours and pay data by pay period, providing a queryable record of hours and compensation that supports this documentation requirement. Store a parallel copy outside the platform as a backup, because employers are advised not to treat any single system as the sole record-retention archive.
Expected outcome: Each classification record includes or cross-references payroll records demonstrating consistent salary-basis payments for the prior three years, with any deductions documented and justified.
7. Set an Annual Review Calendar Event for Each Record
Prerequisites
- All prior steps completed for each exempt employee
For every exempt employee's classification record, set an annual review calendar event. The review must verify three things: the job description is current and signed within the prior 12 months, the weekly salary still meets or exceeds the controlling threshold (re-verified against DOL and state agency sources), and the exemption category is still appropriate given the employee's actual duties.
Align the annual review with a consistent date, such as the first business day of Q1, to coincide with most state threshold updates (which typically take effect January 1). This synchronization ensures that the annual review catches any state threshold increase that took effect at the start of the year.
The classification record is never "done." It must be maintained continuously to cover the rolling two-to-three-year lookback window. A record built once and never updated loses its defensive value the moment the employee's salary, duties, or controlling threshold changes. EasyClocking by WorkEasy Software's compliance features can flag annual review dates automatically, ensuring the lookback window is always covered and no employee record goes stale.
Expected outcome: An annual review calendar event is set for every exempt employee's classification record, ensuring that salary-basis verification, job description currency, and exemption category appropriateness are confirmed at least once per year.

Download the procedure above

Not Ready for a Quote? Start Here.

How to Audit Current Exempt Classifications Against FLSA Salary Thresholds

1. Pull the Full Exempt Employee Roster

2. Confirm the Applicable Salary Threshold for Each Employee

3. Flag Employees Below the Controlling Threshold

4. Identify Threshold-Proximity Risk Employees

5. Cross-Reference Flagged Employees Against the Duties Test

6. Categorize Findings into a Three-Tier Risk Register

7. Assign Remediation Priority for Confirmed Misclassifications

How to Track DOL Salary Threshold Rule Changes and Assess Workforce Impact

1. Subscribe to DOL Wage and Hour Division Rulemaking Alerts

2. Record the Proposed or Final Rule Details When Published

3. Query the HRIS for Affected Exempt Employees

4. Segment the Impact Population by Business Unit, Location, and Job Family

5. Estimate the Cost of Both Remediation Paths for Each Segment

6. Produce the Threshold-Change Impact Report

7. Distribute the Impact Report to HR Leadership, Finance, and Legal

How to Apply State Salary Threshold Overrides to Federal FLSA Classifications

1. Build a State Threshold Reference Table

2. Identify Override States Where the State Threshold Exceeds the Federal Floor

3. Pull the Exempt Employee List for Each Override State

4. Update Each Affected Employee's Classification Record with the Controlling Threshold

5. Flag Employees Between the Federal and State Thresholds

6. Route Flagged Employees to the Reclassification Procedure

7. Set a Calendar Review for Each Override State's Threshold Update Cycle

How to Reclassify Employees When FLSA Salary Thresholds Change

1. Confirm the Remediation Path for Each Affected Employee

2. Process Salary Adjustments for Employees Maintaining Exemption

3. Update FLSA Status for Employees Being Reclassified to Non-Exempt

4. Configure Overtime Rules for Newly Non-Exempt Employees

5. Draft and Deliver Reclassification Notices to Affected Employees

6. Brief Affected Employees' Managers on Timekeeping Requirements

7. Run a Parallel Payroll Test for the First Pay Period

8. Document the Reclassification in the Employee's Compliance File

How to Build a Payroll Audit-Ready FLSA Classification Record

1. Create a Classification Record File for Each Exempt Employee

2. Attach the Current Signed Job Description

3. Record the Salary-Basis Test Confirmation

4. Attach the Most Recent Classification Audit Tier Result

5. Attach Reclassification Documentation for Employees Changed in the Prior Two Years

6. Store Payroll Records Showing Consistent Weekly Salary Payments

7. Set an Annual Review Calendar Event for Each Record

How These Procedures Connect

Next steps