Scope of Work Template for Nonprofit

A scope of work (SOW) defines what you will deliver, when, and what is not included—before a Nonprofit project starts. For US freelancers and agencies, a clear SOW reduces scope creep, supports milestone invoices, and gives accounts payable a document to match against your bills. This page lists typical deliverables and exclusions for Nonprofit engagements plus a template to draft your own SOW.

Why Nonprofit projects need a written SOW

Nonprofit work often involves multiple stakeholders, revision cycles, and third-party dependencies. Without a written scope, "small tweaks" accumulate into unpaid labor. The SOW attaches to your master contract and becomes the baseline for change orders.

Clients use SOWs internally for budget approval. When your invoice line items mirror SOW deliverables, payment moves faster.

Typical deliverables for Nonprofit projects

• Grant-aligned project plan
• Donor-facing campaign assets
• Annual report design/content sections
• Volunteer toolkit documents
• Board presentation summary
• Impact metrics template

Customize counts, formats, and acceptance criteria for each client. Name the decision-maker and feedback window (for example, five business days for consolidated comments).

Timeline and milestones

Align milestones to grant reporting dates and board meetings. Consider reduced nonprofit rates in SOW fee section.

Align payment milestones to these dates or deliverable approvals. Invoice when triggers occur, not only at project end.

Common exclusions to list explicitly

• Grant writing and submission fees
• Donation processing setup
• Event venue and catering
• Paid media spend

Listing exclusions prevents assumptions that hosting, licensing, rush fees, or extra revision rounds are included. When clients request excluded work, issue a change order with fee and schedule impact.

Connecting SOW to contracts and invoices

The master contract holds legal terms; the SOW holds project specifics. Reference the SOW on every milestone invoice. When scope changes, amend the SOW or attach a signed change order before doing extra work.

Learn more in our guide SOW vs proposal vs contract. Draft your document with the Scope of Work template.

Sample SOW email to your client

Subject: Scope of work — [Project Name] for review

Hi [Name],

Attached is the scope of work for [Project Name] listing deliverables, timeline, exclusions, and acceptance criteria. Please review and sign so we can align the contract and first invoice to these milestones.

Reply with consolidated feedback by [Date]. Thank you,
[Your name]

Related documents for Nonprofit projects

• Freelance proposal — sell the approach before detailed SOW
• Freelance contract — legal terms that govern the SOW
• Change order — when scope expands mid-project
• Invoice template — bill each SOW milestone

Acceptance criteria for Nonprofit deliverables

Define objective acceptance tests: format, quantity, performance benchmarks, or stakeholder sign-off within a fixed review window (often five business days). Silence or vague feedback should not trigger unlimited rework—state that consolidated comments are required and extra rounds are billable.

For Nonprofit work, tie acceptance to specific artifacts: approved wireframes, staged URLs, draft copy in the client CMS, or exported files in agreed formats. "Looks good" emails count as approval when your SOW says they do.

Change orders when Nonprofit scope expands

When clients request features, assets, or meetings outside the SOW, pause and issue a change order with fee and schedule impact. Verbal yeses without updated documents are the primary cause of unpaid overtime on Nonprofit projects.

Track change requests in email threads and link them to numbered change orders so finance can see why the final invoice exceeds the original estimate.

Client responsibilities on Nonprofit projects

List what the client must provide: brand assets, logins, content, feedback within X days, and a single decision-maker. Delayed client inputs push timelines—your SOW should say schedule shifts when inputs are late.

Third-party vendors (hosting, stock licenses, printers) should be named with who pays and who manages the relationship.

Payment milestones aligned to Nonprofit SOW phases

Match invoice triggers to SOW sections: deposit at signing, payment at wireframe approval, payment at beta launch. Avoid a single final invoice for multi-month Nonprofit engagements unless the client has a strong payment history.

Repeat payment terms from the master contract on every milestone invoice. Reference SOW section numbers or deliverable titles on line items.

Legal and IP notes for Nonprofit SOWs

The SOW typically references the master agreement for IP transfer, confidentiality, and liability. Work product often transfers upon full payment—state that in the contract, not only the SOW.

Pre-existing tools, frameworks, and stock assets remain yours unless the SOW explicitly assigns them. List licensed third-party components the client must purchase.