Freelance Isn't Free Act: NYC nonprofit compliance rules

If your organization retains a covered freelance worker for compensation, the same basic protections can apply even when the work is funded by a grant, supports a small community program, or is performed by a consultant who has worked with the nonprofit for years.

That matters because nonprofit operations often depend on flexible, project-based labor: grant writers, teaching artists, facilitators, interpreters, designers, evaluators, photographers, technology specialists, and event producers. Mission-driven work does not remove the administrative obligation to document the relationship, pay on time, and preserve a reliable record of what the organization agreed to do.

I read the Freelance Isn’t Free Act as an operational rule with a straightforward purpose: reduce the legislative friction between a completed service and the payment that should follow it. The difficult part for nonprofits is rarely understanding the principle. It is building that principle into procurement, program management, finance, and the many informal arrangements that make up a community organization’s daily ecosystem.

Why NYC nonprofits generally fall within the Act

The Freelance Isn’t Free Act was enacted as Local Law 140 of 2016 and took effect on May 15, 2017. It protects covered freelance workers’ rights to:

• A written contract when the statutory threshold is met.
• Timely and full payment for completed work.
• Freedom from retaliation for exercising rights under the law.

The statute excludes government entities, including the United States government, New York State and its entities, New York City and its entities, other local governments, municipalities or counties, and foreign governments. Nonprofit organizations are not included in that list of exclusions. A nonprofit’s tax-exempt status, charitable mission, or dependence on philanthropic funding does not, by itself, create an exemption.

That distinction is central to NYC nonprofit freelance law compliance. A nonprofit may have a very different financial model from a private company, but the organization is still a hiring party when it retains a covered freelancer for compensation. A grant agreement may shape how the nonprofit budgets for the work, and a government contract may determine when reimbursement arrives, but those funding arrangements do not automatically change the organization’s obligations to the person who completed the services.

A nonprofit mission may explain why the work matters; it does not, by itself, change when the freelancer must be paid.

This does not mean that every person who performs work for a nonprofit is covered by the Act. The legal relationship must be examined as it actually operates. A person may be an employee, an independent contractor, a volunteer, an intern, a vendor, or a professional falling within a statutory exclusion, and those categories should not be treated as interchangeable.

The Act also excludes certain freelance workers, including sales representatives covered by New York Labor Law section 191-a, qualifying attorneys, and licensed medical professionals. Work performed under a collective bargaining agreement that defines the workers as employees is generally outside the Act’s application as well. Those exclusions are specific; they should not be expanded into a general assumption that professional or mission-related services are outside the law.

The $800 threshold is about the relationship, not just one invoice

The most important starting point for a nonprofit is the written-contract threshold. A written contract is required when the contract value is $800 or more, either under a single contract or when contracts between the same hiring party and freelance worker are aggregated during the immediately preceding 120 days.

That means a nonprofit should not look only at the value of one purchase order or one invoice. A series of smaller assignments may reach the threshold when considered together. This is particularly relevant to organizations that engage the same consultant for recurring workshops, monthly communications work, evaluation support, translation, or short-term program deliverables.

The confirmed statutory threshold is $800. Proposed legislation and Council activity have included discussion of a lower threshold, including a proposed $250 figure, but that proposal should not be presented as the current statutory rule unless and until the law changes. For present compliance purposes, the organization should work from the $800 threshold and the 120-day aggregation period.

A practical intake process should therefore ask:

• Has this freelancer performed or been engaged to perform other work for the nonprofit during the previous 120 days?
• Do the assignments involve the same nonprofit as the hiring party, even if different departments or programs are managing them?
• Is the combined value of the contracts $800 or more?
• Is the individual actually performing freelance services, or is the relationship more accurately treated as employment or another legal category?
• Does a statutory exclusion apply to this person and this work?

The invoice, purchase order, grant budget, or vendor setup form may be useful internal records, but none should be assumed to satisfy the written-contract requirement automatically. The document needs to contain the required information, and the safest practice is to have a signed agreement before the work begins or, at minimum, before the nonprofit relies on the arrangement operationally.

What the written contract must contain

The contract must identify the parties and describe the bargain with enough clarity that neither side has to reconstruct it later from email fragments, calendar invitations, or an accounting system.

At a minimum, the written contract should include:

• The names and mailing addresses of the nonprofit and the freelance worker.
• An itemization of the services to be provided.
• The value of the services.
• The rate and method of compensation.
• The payment date, or a mechanism for determining when payment is due.

For nonprofits, “itemization of services” deserves more attention than it often receives. “Consulting services” may be too vague to guide a dispute about what was delivered, especially when a grant-funded project involves several stages. A stronger agreement might identify the number of workshops, the evaluation deliverable, the communication products, the meetings included, the revision process, or the specific reporting responsibilities.

The payment provision also benefits from precision. “Payment upon receipt of funding” is not the same as a clear payment date or a mechanism that allows the freelancer to determine when payment is due. A nonprofit may need to coordinate its cash flow carefully, but a funder’s reimbursement schedule should not be treated as an automatic permission to delay payment unless a separate legal source supports that arrangement.

Here is the operational difference between the documents nonprofits commonly use:

A nonprofit independent contractor agreement in New York should be treated as part of the organization’s compliance infrastructure, not as a form that disappears into a shared drive after signature. Program staff, finance staff, and the person with contracting authority should be able to locate the agreement and understand which deliverables trigger payment.

Payment deadlines do not wait for grant reimbursement

The Act requires the hiring party to pay for completed work on or before the payment date stated in the contract. If the contract does not specify a payment date, payment is due within 30 days after the freelance worker completes the work.

That default rule is easy to overlook because nonprofit finance systems often operate through monthly payment runs, board approval schedules, reimbursement cycles, or funder reporting periods. Those internal processes may be necessary for responsible stewardship, but they do not necessarily alter the worker’s payment deadline.

The key word is “completed.” A contract should define completion in a way that corresponds to the actual work. If payment depends on a deliverable, the agreement should explain what the deliverable is, when it is due, and what happens if the nonprofit believes it is incomplete or requires correction. Without that detail, a routine revision request can become an open-ended reason to hold payment.

A sound payment workflow usually has four connected parts:

1. The program lead confirms the scope. The staff member managing the project identifies what the freelancer is expected to produce and what counts as completion.

2. The contract establishes the payment point. The agreement states the payment date or gives the parties a workable method for determining it.

3. Finance receives a complete approval package. The signed contract, invoice, completion confirmation, and payment instructions are stored together rather than scattered across email and accounting systems.

4. Someone monitors exceptions. If a payment is delayed, the organization records the reason, communicates with the freelancer, and escalates the issue before the deadline passes.

This is not merely a matter of administrative neatness. A delayed payment can produce statutory damages, including double damages in appropriate circumstances, as well as injunctive relief and reasonable attorney’s fees and costs. The individual claim may arise from one unpaid or late-paid engagement, while a recurring breakdown in the same payment process can create a broader pattern of risk.

The safest response to a payment problem is not silence. If the nonprofit discovers that a payment will not be made when promised, the responsible staff should identify the contractual deadline, confirm the amount owed, communicate clearly with the freelancer, and involve organizational leadership or counsel as needed. A difficult funding situation is easier to manage when it is surfaced early; it becomes substantially more serious when the organization continues to accept work while avoiding a known obligation.

Records are part of the compliance system

The law requires hiring parties to preserve contract records. For a nonprofit, recordkeeping should extend beyond the signed agreement itself because the organization may later need to show what services were assigned, what was delivered, when the work was completed, and when payment was made.

I recommend preserving one coherent file for each engagement, containing:

• The signed contract and any amendments.
• The freelancer’s name and mailing address.
• The statement of work or service description.
• Approved changes to scope, rate, or timing.
• Invoices and payment confirmations.
• Evidence of delivery or completion.
• Communications about revisions, disputed work, or payment timing.
• Any classification analysis or internal escalation concerning the relationship.

This does not require nonprofits to create an elaborate compliance department. It does require them to decide who owns the file. In a small organization, the program director may initiate the engagement, the executive director may sign it, and the bookkeeper may process payment. If no one is responsible for retaining the complete record, each person may hold a fragment while the organization holds no reliable account of the transaction.

The record should also make it possible to identify repeat engagements within the 120-day aggregation period. That may require coordination across departments. A freelancer hired by the education program and later engaged by development may still be working for the same hiring party: the nonprofit itself. Separate budgets do not necessarily mean separate legal relationships.

What happens if a freelancer files a complaint

A freelance worker may file a complaint with the New York City Department of Consumer and Worker Protection within two years after the alleged violation. The City’s complaint process requires the hiring party to respond, and the stated response period is 20 days.

That timeline should be treated as an immediate organizational matter. A complaint should not sit in an individual inbox while staff try to determine whether it is “really legal” or whether the amount involved is too small to justify attention. The organization should preserve relevant records, identify the person responsible for responding, and obtain appropriate legal guidance where the facts or exposure are disputed.

The complaint process is not a substitute for legal advice, and the filing of a complaint does not automatically determine liability. It does, however, create a formal point at which the nonprofit must respond to the allegations and organize its account of the relationship.

Individual violations can expose a hiring party to statutory damages, double damages, injunctive relief, and reasonable attorney’s fees and costs. Where there is reasonable cause to believe that a hiring party has engaged in a pattern or practice of violations, the Corporation Counsel may bring a civil action seeking a civil penalty of up to $25,000.

The enforcement record also shows why organizations should not dismiss these rules as theoretical. On February 24, 2026, DCWP reported that since the Act took effect it had received 4,832 complaints, closed 4,394 cases, and helped freelancers recover more than $3,526,572. The same announcement described a $528,817 settlement involving Splashlight and 350 freelancers. That information does not mean that every nonprofit faces the same facts or outcome, but it does demonstrate that payment and contracting practices are being examined at scale.

The greatest exposure usually begins as a process defect: one missing contract, one undocumented scope change, or one payment that nobody owns.

Do not confuse freelance compliance with worker classification

The Act’s contract and payment rules are important, but they do not answer the separate question of whether a person has been properly classified as a freelancer in the first place.

A nonprofit may call someone a “consultant” because that is the label used in a budget or grant proposal. The label does not settle the legal analysis. Classification depends on the actual facts and work arrangement, including how the work is controlled, how integrated it is into the organization’s operations, the degree of independence, and the terms under which the person performs services.

That distinction matters in both directions. Some people described as contractors may be employees with rights under other employment laws. Others may be genuine freelancers covered by the Freelance Isn’t Free Act. A volunteer is not simply an unpaid freelancer, and an organization should not use volunteer language to avoid paying someone who was retained to perform compensated services.

The same caution applies to vendors. If a nonprofit contracts with a company that provides a fully staffed service, the legal analysis may differ from an agreement with an individual who personally performs the work. But the organization should examine the actual arrangement rather than relying on a category selected for convenience during onboarding.

When classification is uncertain, the practical next step is to gather the facts before the engagement expands:

• Who controls the manner and schedule of the work?
• Is the person providing a defined project or performing an ongoing organizational function?
• Can the person work for other clients?
• Who supplies the tools, workspace, and supervision?
• Is the person paid for a completed result, for hours, or through a recurring salary-like arrangement?
• Does the person personally perform the work, or does an independent business provide a team or service?

No single question decides every case. The point is to prevent the organization from treating a title as an analysis.

A compliance route that works for smaller nonprofits

The most useful response is not to add another disconnected policy to the organization’s manual. It is to connect the legal requirement to the decisions staff already make.

A small nonprofit can begin with a modest workflow:

1. Create a single engagement trigger

Require a written agreement before a person begins compensated freelance work whenever the engagement is expected to reach $800 or more, or when the person’s contracts with the nonprofit may aggregate to that amount within 120 days.

The trigger should apply across departments. A central log or shared intake form can help identify repeat engagements that a program-by-program process might miss.

2. Use a contract that reflects actual nonprofit work

The form should have space for concrete services, deliverables, rates, payment method, payment date, mailing addresses, and amendments. Avoid relying on a generic “services as requested” clause when the project can be described more clearly.

If the work is grant-funded, identify the program context internally, but do not make the freelancer’s payment dependent on an uncertain reimbursement event unless counsel has reviewed the arrangement and the legal basis for it.

3. Assign payment ownership

Someone should be accountable for confirming that the invoice corresponds to completed work and reaches finance in time. “Finance handles it” is not an ownership model if finance does not know when the work was completed or which contract governs the payment.

4. Preserve the full record

Keep the signed agreement, scope changes, invoices, completion confirmation, and payment record together. Ensure that staff turnover does not erase the history of the engagement.

5. Review recurring relationships

At least periodically, look for individuals who appear repeatedly in accounts payable, program budgets, or consultant lists. Recurring engagements are where aggregation, classification, and payment problems often become visible.

6. Prepare a complaint response protocol

Identify who receives a DCWP notice, who preserves records, who communicates with the freelancer, and when counsel is engaged. The 20-day response period makes this a governance issue, not merely an administrative preference.

Advocacy belongs in the same conversation

Compliance is the immediate responsibility, but policy advocacy is also part of how nonprofit organizations improve the ecosystem in which they operate. Many community organizations are both hiring parties and advocates for workers, artists, educators, and independent professionals whose labor supports civic life.

That dual role calls for practical advocacy rather than broad statements detached from operations. Nonprofits can document how payment timing interacts with grant reimbursement, how small organizations manage contract administration, and where public procurement rules create avoidable delays. They can also distinguish clearly between current law, proposed legislation, and policy recommendations.

For organizations tracking broader nonprofit legal updates, the useful questions are concrete:

• Would a lower contract threshold materially change onboarding practices?
• Which public or philanthropic funding terms create payment delays?
• What technical assistance would help small nonprofits comply without diverting resources from programs?
• Do community-based freelancers experience barriers in filing complaints or recovering payment?
• Which contract templates and procurement practices could be shared across the sector?

As of the available enforcement information reported on February 24, 2026, the current confirmed NYC threshold remains $800, not $250. The sources reviewed also do not establish a separate NYC nonprofit safe harbor, a nonprofit-specific compliance protocol, or a New York State-wide version of these protections based solely on City materials or proposed Council resolutions. Those distinctions should remain visible in any policy paper, board briefing, or advocacy campaign.

The strategic takeaway for nonprofit leaders

The Freelance Isn’t Free Act does not require a nonprofit to abandon flexible project work. It requires the organization to make that flexibility legible: who is being hired, for what services, at what rate, with what payment date, and under which documented relationship.

I would begin with three actions. First, review every recurring freelance engagement and identify contracts that reach the $800 threshold through the 120-day aggregation rule. Second, compare the organization’s current agreements with the required contract elements rather than assuming that invoices or purchase orders fill the gaps. Third, test the payment process against a real project: can staff show when the work was completed, who approved it, when payment became due, and when it was made?

That review will not resolve every classification question or predict every enforcement outcome. It will, however, give the nonprofit a usable route through the bureaucratic maze and a stronger foundation for conversations with freelancers, funders, auditors, board members, and community stakeholders.

The larger principle is simple. A nonprofit’s credibility is built not only through the services it delivers to the public, but also through the way it treats the people whose labor makes those services possible. In NYC’s nonprofit ecosystem, clear contracts and timely payment are not separate from mission. They are part of responsible mission practice.