Exempt or Not? Preparing an FLSA Classification Review With AI

Nonprofit Status Confers No Exemption, and the Coverage Question Is Narrower Than It Sounds

The single most common misconception in this area is that charitable organizations get some accommodation under wage and hour law because of their mission or their tax status. They do not. The Department of Labor has been explicit that its regulations governing the executive, administrative, and professional exemptions have never contained special rules for nonprofit or charitable organizations, and that employees of those organizations are subject to the same salary level, salary basis, and duties tests as everyone else. Being a 501(c)(3) is a federal tax determination. It has no bearing on whether your program manager is owed overtime.

What does require care is the prior question of whether the FLSA reaches a given employee at all, because here nonprofits genuinely sit in a different position from commercial employers. The statute reaches employees two ways. The first is enterprise coverage, which generally applies to businesses with annual gross volume of sales made or business done of at least $500,000. The Department's guidance on nonprofit organizations and the FLSA explains that nonprofit charitable organizations are not covered enterprises unless they engage in ordinary commercial activities that result in sales made or business done, such as operating a gift shop or providing services for a fee, and that where such activities exist, enterprise coverage reaches only the activities performed for a business purpose rather than the organization's charitable activities.

The second route is individual coverage, and this is where the apparent relief disappears. An employee of an organization that is not covered on an enterprise basis is still protected if that individual is engaged in interstate commerce or in the production of goods for interstate commerce. The Department's examples of qualifying activity include making or receiving interstate telephone calls, shipping materials to another state, and transporting people or property across state lines. Read that list against any real nonprofit job. A development coordinator who emails out-of-state funders, a program assistant who orders supplies from a national vendor, a case manager who calls a federal agency, and an administrator who processes credit card donations through an out-of-state processor are all plausibly engaged in interstate commerce on an ordinary Tuesday.

The practical consequence is that a nonprofit which concludes it is outside enterprise coverage should not conclude it is outside the FLSA. For most organizations with any meaningful operation, the safer working assumption is that nearly every employee is covered one way or the other, and that the real analysis is about exemptions rather than coverage. Coverage questions, especially for organizations with a mix of charitable and commercial activity such as a social enterprise or a thrift operation, are precisely the kind of thing to put on the list for counsel rather than settle internally. The National Council of Nonprofits maintains a useful plain-language overview of a nonprofit's obligation to pay overtime that is worth reading alongside the Department's own material.

The Duties Tests, Element by Element

Clearing the salary gate gets an employee to the second gate, not past it. Each exemption has its own duties test built from specific elements, and the employee must satisfy all of that exemption's elements. This is where almost every misclassification happens, and it is also where a structured review pays for itself, because the discipline of writing out each element and answering it separately surfaces problems that a holistic impression of a role will hide.

The concept that runs through all of them is primary duty, which means the principal, main, major, or most important duty the employee performs. It is not a pure stopwatch test under federal law, although time spent is significant evidence, and an employee who spends the majority of the week on non-exempt work will have a hard time establishing that exempt work is the primary duty. The other factors include the relative importance of the exempt duties, the employee's freedom from direct supervision, and the relationship between their salary and the wages paid to others for the non-exempt work they perform. That last factor is quietly important in nonprofits, where an exempt program coordinator may be paid barely more than the non-exempt staff doing the same frontline work alongside them.

The executive exemption requires that the primary duty be managing the enterprise or a customarily recognized department or subdivision, that the employee customarily and regularly direct the work of at least two or more other full-time employees or their equivalent, and that the employee have authority to hire or fire, or that their recommendations on hiring, firing, advancement, or promotion be given particular weight. The two-employee element is a frequent failure point in small nonprofits, where a person with a director title may supervise one part-time staffer and a rotating pool of volunteers. Volunteers are not employees, and a single part-time report is not two full-time equivalents.

The administrative exemption is the one nonprofits lean on most heavily and understand least well. It requires that the primary duty be office or non-manual work directly related to the management or general business operations of the employer or its customers, and that the primary duty include the exercise of discretion and independent judgment with respect to matters of significance. Both halves matter. Work that produces the organization's output, delivering the program itself, is generally production work rather than general business operations, and following established procedures competently is not the exercise of independent judgment on significant matters. A grants administrator who decides which opportunities to pursue and negotiates terms looks different from one who completes forms against a checklist, even where the titles are identical.

The professional exemption splits into two. The learned professional branch requires advanced knowledge in a field of science or learning, customarily acquired by a prolonged course of specialized intellectual instruction, and work that is predominantly intellectual in character requiring the consistent exercise of discretion and judgment. The creative professional branch covers work requiring invention, imagination, originality, or talent in a recognized artistic or creative field. Nonprofits should be careful with the learned professional branch, because the requirement is a specialized academic credential that is a standard prerequisite for the work, not simply that the person holds a degree. Plenty of nonprofit roles are filled by people with master's degrees in jobs that do not require one.

The computer employee exemption applies to specified roles such as systems analysts, programmers, and software engineers performing enumerated kinds of work, and it carries its own compensation route allowing an hourly rate at or above a specified level in place of the weekly salary. Its most important feature for nonprofits is how narrow it is. The person who maintains your donor database, troubleshoots laptops, and manages vendor relationships is doing valuable work that does not obviously match the enumerated duties, and help desk and general technical support roles frequently fall outside this exemption entirely. Finally, the highly compensated employee route offers a relaxed duties analysis for employees above the total compensation figure who customarily and regularly perform at least one of the exempt duties of an executive, administrative, or professional employee. It is useful mainly for senior leadership, and at nonprofit salary levels it will rarely be the relevant path.

The Nonprofit Traps Worth Looking At First

Some positions carry so much more risk than others that a review should start there. The clearest is the program director or program manager who spends most of the week doing direct service. This is the single most common nonprofit misclassification pattern and the easiest to understand once the elements are in front of you. The role is titled as leadership, described in the job posting as strategic, and in practice consists of carrying a caseload, running groups, covering shifts when staff call out, and doing the actual work of the program with a few hours of administration squeezed in at the end of the day. The administrative exemption requires that the primary duty be work directly related to management or general business operations, and delivering the program is usually not that. The executive exemption requires genuine management of a department as the primary duty plus two full-time equivalent reports. A person whose week is mostly frontline service may satisfy neither.

Development and fundraising staff are the second cluster, and they are harder to reason about because the work varies enormously. A development director who sets strategy, decides where the organization will invest effort, negotiates with funders, and commits the organization to positions is exercising discretion and independent judgment on matters of significance. A development associate who maintains the donor database, prepares acknowledgment letters from templates, assembles mailing lists, and completes grant application forms against instructions is doing important work that does not clearly match the elements. Event coordinators sit in the same ambiguous space, and they have the added feature of working extraordinary hours in the weeks before an event, which is precisely when a misclassification becomes expensive.

Part-time salaried roles deserve separate attention because the trap is arithmetic rather than conceptual. The salary threshold is not prorated for part-time work. An employee working twenty-five hours a week must still receive at least the full weekly salary figure to meet the salary level test for the white collar exemptions, so a part-time position paid a salary that annualizes well below the threshold cannot be exempt on that basis regardless of how senior the duties are. Nonprofits create these positions constantly, often to accommodate a valued employee's schedule, and put them on salary because it simplifies payroll. The simplification is the problem.

A fourth pattern is the small-shop generalist, the person in a six-person organization who does bookkeeping, HR paperwork, scheduling, communications, and reception. Breadth is not the same as discretion, and a role that touches everything while deciding nothing of significance is a weak fit for the administrative exemption. A fifth is the role that was classified correctly at the time and drifted. Someone hired to run a department whose staff have since left is now doing the work themselves, and the classification that was sound three years ago may not be sound today. Reviews should look at the current reality, not the hiring memo. These patterns sit inside the broader HR compliance picture we cover in our overview of AI across nonprofit HR functions, and for seasonal programs they interact with the scheduling pressures described in seasonal staffing optimization.

What Getting It Wrong Actually Costs

The exposure from a misclassification is not a fine for a paperwork error. It is unpaid wages, and the structure of the remedy is what makes it dangerous for a small organization. If an employee was misclassified as exempt, they were entitled to overtime for every hour over forty in every affected workweek, and the organization owes that money. The ordinary limitations period for recovering back pay under the FLSA is two years, extending to three years where the violation is found to have been willful, which means the arithmetic runs across years rather than months.

On top of the back wages sits liquidated damages, which under the statute are generally equal to the unpaid amount. In effect the back pay doubles unless the employer can persuade the court that it acted in good faith and on reasonable grounds for believing it was in compliance. The Department's own overview of back pay recovery describes the routes available, which include the Wage and Hour Division supervising payment of back wages and the Secretary of Labor bringing suit for back wages and liquidated damages. Private suits can also recover attorney's fees and costs, and because classification decisions apply to positions rather than to individuals, one employee's claim tends to implicate everyone else in the same role.

There is a second, quieter cost that organizations consistently underestimate. Calculating what is owed requires knowing how many hours each misclassified employee actually worked, and an organization that treated them as exempt has no timekeeping records. Where the employer's records are inadequate, the employee's reasonable recollection can carry considerable weight, which means the organization ends up litigating against an estimate it cannot contradict. The absence of records is not protective. It is the opposite.

Beyond the direct liability sit consequences that matter to a nonprofit more than to a commercial employer. A wage and hour finding is a governance and funder problem, surfacing in audits, in grant compliance reviews, and in the kind of questions a major donor's advisor asks. It is a story a local reporter will cover, and a charity underpaying its own frontline staff is a story with a particular sting. Staff trust takes a direct hit, since the people affected are usually the lowest-paid employees in the organization. The good news is that the good faith defense gives real credit to employers who looked at the question seriously, which is an argument for running the review now and documenting it properly rather than hoping nobody asks. Related compliance habits are covered in our articles on audit preparation with AI and on employment law exposure in automated hiring.

Reclassification Is a People Problem Before It Is a Payroll Problem

Suppose the review concludes, with counsel, that four positions have been misclassified and need to move from exempt to non-exempt. The legal analysis is now the easy part. What follows is a change that affects how people are paid, how their work is tracked, and how they understand their own standing in the organization, and it lands on employees who did nothing wrong and who will reasonably wonder what else the organization has gotten wrong about them.

Start with the pay design, because it has to be settled before anyone is told. Converting a salary to an hourly rate is not arithmetic with one right answer. Dividing the annual salary by 2,080 hours keeps base pay flat only if the person works forty hours, and someone who has been working fifty will see their total compensation rise once overtime applies. Some organizations set the hourly rate so total expected compensation including overtime approximates the old salary, which protects the budget but can read as a pay cut on the base rate. Others hold the base rate and absorb the overtime cost, which is cleaner to explain and more expensive. There are also non-exempt salary arrangements where a salary covers a set number of hours with overtime paid on top. Each has consequences, each has to work with your actual hours data, and the choice has legal implications that belong in the same conversation with counsel.

The morale dimension is the part leaders consistently handle badly, usually by being vague. Many employees experience exempt status as a marker of professional standing and autonomy, and hearing that they must now record their hours and get approval before working late can feel like a demotion even when it comes with more money. The communication has to do several things at once: explain clearly what is changing and when, be honest that this reflects a legal requirement rather than a judgment about the person's value or performance, state explicitly that it is not a demotion and that title and responsibilities are unchanged, set out exactly what the new timekeeping expectations are, and name a specific person who will answer questions individually. A model drafts this well, including the manager talking points and an anticipated question list, and the tone work matters as much as the content. What a model should not do is send it. Each affected employee should hear this in a conversation with their supervisor before any written notice arrives, and the written version should follow the same day.

Then there is the operational consequence, which organizations plan for least and feel most. A newly non-exempt employee has to track time accurately, which may be a first for them, and the organization has to decide what happens when the work genuinely exceeds forty hours. If the answer is that overtime must be pre-approved, then workloads have to shrink or budgets have to grow, because an instruction to finish the work without recording the hours is a wage violation being created on purpose. This is the moment where unrecorded off-the-clock work starts, and it has to be addressed directly in training for supervisors as well as staff. Handling reclassification well is also a retention question, since the people affected are often long-tenured and committed, a dynamic explored in our article on employee retention in nonprofits. The resulting policy changes should be written into your handbook rather than communicated once by email, which connects to our guidance on building a nonprofit employee handbook with AI.

A Practical Sequence for an Organization Starting From Nothing

If none of this has ever been reviewed, the temptation is to do it all at once or not at all, and not at all usually wins. A better approach is to run the inventory first, because it is cheap, mechanical, and it tells you how large the problem is. Pull payroll, the org chart, and every job description you can find, consolidate them into one table, and flag every position that matches one of the high-risk patterns described earlier. Many organizations find that the real exposure sits in four or five positions rather than across the whole staff, which makes the rest of the work tractable.

Work through the flagged positions in order of risk, building the duties description and the element worksheet for each. Do the state research in parallel, since it affects which positions are flagged in the first place. Review the salary basis practices across the whole organization at the same time, because that is a single policy question rather than a per-position one and a bad practice there can undermine otherwise sound classifications. When the flagged set is prepared, take the file to counsel in one engagement rather than asking questions piecemeal. Then implement whatever changes are required with the pay, communication, timekeeping, and workload planning settled in advance.

Finally, make it recurring, because classification drifts with every departure, every title change, and every annual state threshold adjustment. Put a date in the calendar, assign a named owner, and define the triggers that require an out-of-cycle look: a new position, a material change in someone's duties, a promotion, the loss of a direct report, a hire in a new state, and any change in the federal or state threshold. A review that happens once produces a snapshot. A review that recurs produces the good faith record that is worth having, and a conversation with staff about hours and workload that is honest rather than overdue. For leaders working out where this fits among other AI priorities, our guide for nonprofit leaders getting started with AI offers a way to sequence it.