A nonprofit consulting contract should spell out what you'll deliver and what you won't, the timeline, your fee and payment terms, how changes get handled, how you'll communicate, who owns the work, and how either side can end it. Below is what to include in each section, the lessons I learned the hard way, and what to check in a template.
This post is educational, not legal advice. Have a lawyer review any contract before you use it.
What's a contract?
A consulting contract is a written agreement between you and your client. Here's how I set mine up. First, I send a proposal that lays out the project and the fee. Once the client says yes, I send an agreement with a statement of work attached. The agreement covers the legal terms, like payment, confidentiality, and termination. The statement of work covers the details of the project: the scope, timeline, and fee.
Why every nonprofit consultant needs a contract
In nonprofit consulting, it's easy to start from trust. The client is kind, the mission matters, and the need feels urgent. Then the project grows in small, reasonable-sounding ways. A quick question becomes ongoing support. One draft becomes three rounds of edits. Payment slows down because the organization is juggling too much.
Usually no one is trying to take advantage. The expectations just were never written down. A contract puts them in writing before the work starts, so you both agree on what's being delivered, when, and for how much.
What to include in a nonprofit consulting contract
A good contract doesn't need to be long. It needs to be clear.
Scope of work and deliverables
This section carries the most weight.
I learned this on one of my first projects, a CRM migration for a small nonprofit moving from Excel spreadsheets to a donor management platform. I quoted $3,500 to clean up donor records, move contact information, organize gift history, and get them set up in the new system. Halfway through, they sent two more spreadsheets with more contacts and gift history that weren't in the count I had priced from. Because I hadn't defined what was included, I absorbed it: another 10 to 15 hours I didn't charge for. The client wasn't taking advantage of me. I just hadn't protected the project.
Now my scope of work names:
What's included, down to the numbers (for a CRM migration, the number of spreadsheets or records, imports, cleanup rounds, and training calls)
What's not included
What the client needs to provide, and by when
What happens if new work gets added after the project starts
Timeline, milestones, and responsibilities
Nonprofit timelines shift, often for reasons no one controls. List the start date, end date, and key milestones. Then say what happens if feedback or materials come in late. My statement of work says that delays in client review may adjust the timeline, so a late approval doesn't turn into a rush job for me.
Fees, invoicing, and payment terms
Payment problems usually come from unclear terms, not bad intentions. State your fee, when you'll send invoices, when they're due, and what happens if a payment is late.
Your terms can change from client to client. For projects, I often ask for a deposit when the agreement is signed and the rest at final delivery. Sometimes I ask for the full fee upfront. For retainers, I invoice monthly. If you'll have expenses, like travel, say which ones the client covers and which need their approval first.
If you're a fundraising consultant, don't tie your fee to the money raised. The Association of Fundraising Professionals' Code of Ethical Standards says members shouldn't accept compensation based on a percentage of contributions. My agreements say directly that my fees aren't connected to any money the organization raises.
Changes to scope
Your contract should spell out how changes to the scope work. Keep it simple: the client puts the request in writing, you send a written quote with the new timeline, and the work starts only after they approve it. My statement of work says any new deliverables need a revised statement of work.
Communication expectations
Early in my consulting career, I worked with a small nonprofit whose executive director expected me to be available around the clock: nights, weekends, and last-minute requests that were always urgent. I had never said up front how and when I'd be available.
Now I name communication expectations at the start: the main way we'll communicate, how quickly I'll respond, and how often we'll meet. My statement of work includes a communication plan, like biweekly check-ins on Zoom, progress updates by email, and shared documents in Google Drive.
For more on this, read how to set boundaries with nonprofit clients.
Confidentiality and data handling
Nonprofit consulting often involves sensitive information, like donor data, program records, and internal documents. Your contract should say how you'll keep that information confidential, how files will be shared and stored, and what happens to them when the work ends.
Intellectual property and ownership
Ownership gets confusing when your deliverables include training materials, templates, or frameworks you use with other clients. Say who owns the final deliverables once they're paid for, and which materials stay yours because you created them before the project. You can also ask permission to mention the work in your portfolio, without confidential details.
Independent contractor status
Include a section that says you're an independent contractor, not an employee. That means you aren't eligible for the organization's benefits, and you handle your own taxes. The IRS says worker classification depends on the facts of the relationship, not just the label, so make sure the way you work matches what the contract says.
Termination and offboarding
Projects sometimes end early. Priorities change, budgets shift, and leadership turns over. Your contract should say how much notice either side has to give, what fees are owed, what you'll hand over, and how offboarding will work. In my retainer agreements, either side can end the work with written notice, and the client pays for the work done through the end date.
Using a contract template: What to check first
A template can save you time, but it won’t fit your work out of the box. Wherever yours comes from, check it against this list before you send it:
Scope: what’s included, down to the numbers, and what isn’t
Timeline: milestones, plus what you need from the client and when
Fees: the amount, when each payment is due, and how you’ll invoice
Changes: how new requests get approved and priced
Communication: how you’ll stay in touch, how fast you’ll respond, and how often you’ll meet
Confidentiality: how donor and program data is shared, stored, and returned
Ownership: who owns the final deliverables, and what stays yours
Contractor status: that you’re an independent contractor, not an employee
Ending the work: notice, fees owed, and what you’ll hand over
If you’re a fundraising consultant: your fee isn’t a percentage of the money raised
Then have a lawyer review it once, so you can reuse it with confidence.
About the author
Catalina "Cat" Parker is the founder of Relatable Nonprofit. She has a master's in nonprofit management from Columbia, her business has generated nearly $1 million in revenue, and 100+ nonprofit professionals have joined her Mentorship program. Read her story.
Want help scoping your offers?
In the Mentorship, we work together for six months on your offers, scopes, and client boundaries, along with your marketing, sales, and operations.