NFP Website Brief Checklist: What to Tell Your Agency Before You Start

You’ve just been handed the job of getting your nonprofit a new website. Maybe the board finally signed off on the budget, maybe the old site hasn’t been updated since 2016, or maybe a well-meaning volunteer built the last one and it shows. Whatever brought you here, here’s the thing most people don’t tell you: the biggest reason nonprofit website design projects go wrong has nothing to do with the agency you hire or the platform you choose. It comes down to the brief you hand them before work even begins.

A poorly written brief wastes money, derails timelines, and creates tension between your board, your team, and your agency. A well-written one does the opposite. It protects your budget, keeps the project aligned with your mission, and forces the important conversations that would otherwise blow up halfway through the build.

In this guide, you’ll get a practical, beginner-friendly checklist covering everything from stakeholder sign-off and donor journey mapping to CRM integration, accessibility requirements, and content ownership. Work through it before you approach a single agency, and you’ll be in a much stronger position from day one.

Why the Brief Is the Most Important Part of Your Website Project

Most NFP website projects don’t fail because the agency did a poor job. They fail because the project started without a clear brief. When hard questions are skipped before work begins, the consequences show up as scope changes, budget pressure, and missed deadlines.

A well-written brief does two things at once. It is a project document, yes, but it is also a governance document. It forces the questions that boards and leadership teams tend to defer: Who has approved this budget? Who has final sign-off authority? What are we actually trying to achieve? When these questions surface mid-build instead of before it, they cause delays, disagreements, and cost overruns that could have been avoided entirely.

The Council of Nonprofits identifies board approval and formal documentation of significant expenditures as a core governance practice. A website build is a significant expenditure. Your brief is that documentation. It is the record that shows the decision was considered, approved, and scoped responsibly before any agency was engaged.

From an agency perspective, a specific brief changes everything. It allows faster scoping, more accurate pricing, and proposals that actually match your needs. Vague briefs produce vague quotes. Agencies fill the gaps with assumptions, and those assumptions become disputes later.

This checklist is written for the person who has never commissioned a website before. If that is you, you are in the right place. Each section explains not just what to include, but why it matters. Before you craft your website brief and submit it to an agency, work through every section here. It will save you time, money, and a great deal of frustration.

Stakeholder Sign-Off: Who Needs to Agree Before You Start

Before a single agency sees your brief, you need to know who actually has the authority to make decisions, and who is just along for the ride.

Name one project owner. This is the person with board-delegated authority to approve scope, budget, and agency selection. Not a committee, not a shared inbox. One named person. Without this, every review point becomes a negotiation, and projects stall.

Separate input rights from approval rights. A useful way to map this:

• The board sets the budget ceiling
• The CEO approves the brief
• A program manager reviews content for accuracy
• The project owner gives final sign-off on design

Everyone else provides feedback. Only one person approves. Write this down and share it with your team before the project begins.

Get board approval in writing before you approach any agency. BoardSource’s governance guidance is clear that boards carry fiduciary responsibility for significant expenditures, and the Council of Nonprofits recommends documenting all board decisions in meeting minutes as a basic governance practice. Documented board approval protects the project lead and satisfies fiduciary requirements.

Map stakeholder availability now. Agency timelines are built around client review windows. If your board chair is unavailable for six weeks mid-project, that delay falls on your timeline, not theirs. Check availability across five key milestones: discovery, wireframes, design, content review, and launch.

Agree on a conflict resolution process. If the board chair and CEO disagree on a direction mid-build, who has the final word? Define this before it becomes a problem, because mid-project is a costly time to find out.

Budget and Scope: Be Honest About What You Can Afford

Once you have your sign-off structure sorted, the next conversation to have internally is about money, and it needs to be an honest one.

Tell your agency your actual budget range. This is the single most common mistake NFPs make. Withholding your budget does not protect you from being overcharged; it produces a proposal scoped to guesswork, and everyone wastes time. A range is fine. “We have between $25,000 and $35,000 for the build” gives an agency everything they need.

Split your budget into two distinct pots: capital and ongoing. The capital budget covers the build. The ongoing budget covers hosting, software licences, maintenance, security updates, and content support after launch. Many NFPs fund the launch and then find nothing is left to keep the site running. If you are uncertain what ongoing costs look like, our website design and development resources cover typical cost structures in plain language.

Write down your must-haves and your nice-to-haves before the brief goes out. Scope creep almost always starts when “it would be great to also have…” gets added after work has begun. Separating essential features from desirable ones in writing keeps the project anchored.

Ask for a phased quote. If the full scope exceeds your current budget, a good agency can stage the build across financial years. This is common practice in nonprofit website development and a sensible way to manage cash flow.

Finally, build in a contingency buffer. Content always takes longer than expected, integrations reveal surprises, and revision rounds add up. Our guide to website costs in Australia breaks down where budget typically goes before you brief anyone.

Your Mission, Your Audiences, and What You Need the Website to Do

Once budget is settled, the next question is deceptively simple: what does this website actually need to do, and for whom?

Start with a plain-English mission summary. Two or three sentences that any visitor could read and immediately understand. Then list your primary audiences: donors, volunteers, service recipients, referral partners, government funders. These groups often want completely different things from the same website. A donor wants to know their money is well spent. A service recipient wants eligibility criteria, not an impact report. Rank these audiences in order of priority so your agency knows whose needs take precedence when trade-offs arise.

Set goals you can measure. Vague goals produce vague websites. Research from NP Tech for Good shows 94% of donors form their first impression from your website design, which means performance targets matter. Write down two or three specific outcomes: increase online donations by 20%, reduce inbound phone enquiries by 30%, improve volunteer sign-up conversion. These numbers give your agency something to design toward.

Be honest about what is broken. What do visitors complain about? What does your team dread updating? What does the site fail to communicate about your programs? Check your Google Analytics for pages with high exit rates and short time-on-page. That data tells you where the current experience falls apart.

Map your critical user journeys. A first-time donor discovering your organisation, a returning volunteer logging hours, a service recipient finding program eligibility. Write each journey as a short sequence of steps. These journeys should drive every design decision your agency makes.

Finally, share any brand guidelines, tone-of-voice documents, or style guides upfront. If these do not exist, flag it now. Brand development may need to be scoped into the project, and that affects both timeline and budget. You can request a quote that includes brand work if that is where you are starting from.

Mapping the Donor Journey Before Design Begins

Once you’ve defined your audiences and website goals, the next piece to document is how your donors actually move through your site, because a website built without this picture almost always needs expensive fixes later.

The donor journey is the sequence of touchpoints that takes someone from first hearing about your organisation to completing a gift. Your site needs to be designed around that path from the start.

Document your current donation funnel first. How do donors find you today? Search, social media, a referral? What page do they land on, and where do they leave without giving? Your existing website analytics will show you this. If you don’t have analytics set up, flag that in your brief too.

Be specific about your donation types. A one-off gift, a regular monthly giving program, an in-memory donation, peer-to-peer fundraising, and a bequest enquiry all require different page structures and different calls to action. List every giving type your organisation accepts. An agency cannot design the right flows without knowing this upfront.

Define the emotional job of each key page. Your impact page needs to answer one question: “Does my gift actually make a difference?” Your donation page needs to do two things at once, build trust and remove friction. Write down what each page must make a visitor feel or believe before they act. This is more useful to a designer than a paragraph describing your programs.

Confirm your payment gateway before the brief goes out. Whether you use a platform like GiveNow, Stripe, or something else, this is a technical dependency that shapes both the design and the development scope. Poor donor retention undermines any gains from new acquisition, which is exactly why getting the journey right at the brief stage matters so much.

CRM Integration and Third-Party Systems: Get This on the Brief Early

Once your donation platform is confirmed, the next question your agency will ask is: what else does your website need to talk to?

Make a list of every system your website will need to connect with before you write your brief. Common platforms in the NFP sector include Salesforce and Salesforce NPSP; your organisation may use others. Your list will also typically include your email marketing platform, volunteer management tool, event booking system, and any government reporting databases tied to your funding agreements.

For each system on that list, try to answer one critical question: how will the connection actually work? Some platforms have a native, plug-and-play connector. Others require a custom API build. Some organisations use a middleware tool like Zapier to bridge the gap. This distinction matters enormously to your budget. Integration complexity that surfaces mid-project, rather than in the brief, can add significant cost to your scope.

You also need to confirm who holds the login credentials and administrative access for each connected system. Agencies need access during development, and handover arrangements need to be agreed before launch, not after.

In your brief, describe what data needs to move between your website and your CRM: new donor records, email opt-ins, event registrations, volunteer applications. You do not need to map every field yourself; detailed data mapping is a discovery task. But signalling the complexity early helps your agency scope accurately.

If you do not currently have a CRM, say so clearly in your brief. A good agency will factor CRM selection into the project rather than building a website that cannot connect to a future system.

If you are ready to scope your integrations properly, submit a brief to our team and we can walk through the options with you.

Accessibility Requirements: Not Optional for Nonprofits

Once your integrations are mapped, there is one more item your brief must address clearly, and it is one that NFPs sometimes treat as a design preference rather than what it actually is: a legal obligation.

Under the Disability Discrimination Act 1992, providing inaccessible digital services to people with disability can constitute unlawful discrimination. Over 4 million Australians live with disability, and NFP audiences are more likely than most to include people using assistive technologies, older adults, or individuals with cognitive or sensory differences. Accessibility is not a bonus feature. It belongs in your brief as a baseline requirement.

Set the standard in writing. Specify WCAG 2.1 AA compliance as the minimum deliverable. This is the benchmark endorsed by the Australian Human Rights Commission and referenced by most government funding bodies. Australia has also formally adopted WCAG 2.2 Level AA as the national standard — ask any agency whether they build to this updated benchmark.

Ask agencies how they test for it. A credible agency will describe a three-part process: automated tool validation, manual keyboard navigation testing, and screen reader testing. If an agency cannot explain their testing methodology clearly, accessibility is probably a checkbox for them rather than a discipline.

Think beyond the baseline. Consider whether your specific audiences need anything further:

• Older donor cohorts may benefit from larger text and higher colour contrast
• Service recipients with cognitive disability may need plain-language content and simple page structures
• CALD communities may require multilingual support

Bring your history to the brief. If your current website has received accessibility complaints or been through an audit, include those findings. They give an agency a concrete starting point and signal that your organisation is serious about this.

Check your funding agreements. Some government grants and funding contracts require digital assets to meet specific accessibility standards as a compliance condition. Confirm this before scoping begins so the requirement is built in, not bolted on later.

Content Ownership: Who Writes It, Who Approves It, Who Maintains It

Once accessibility requirements are locked in, content is the next place NFP website projects quietly fall apart.

Here is the honest reality: a capable agency can complete the technical build in a fraction of the total project timeline. In practice, most delays are not technical — they are content, sitting unwritten in someone’s to-do list.

Assign a named person, not a department

Before your brief goes out, map every content type your site will need: service descriptions, program pages, team profiles, board bios, impact stories, policy documents. Against each one, write a person’s name, not “marketing” or “the programs team.” Departments don’t write content; people do. Without a named owner and a deadline, content waits indefinitely.

Be honest about internal capacity

Most NFP staff are already stretched. If your team cannot realistically produce website content alongside their regular work, say so in the brief and ask your agency to include a content writing or content strategy service in their scope. Discovering this gap at the halfway mark is far more expensive than planning for it upfront.

Do a content audit before you brief

Before approaching any agency, review what you already have. Separate existing content into three categories: content that can migrate as-is, content that needs rewriting, and content that needs to be created from scratch. This single exercise saves significant agency time during scoping and keeps your quote accurate.

Define post-launch governance

Who has CMS access after launch? Who approves changes to key pages? How often will content be reviewed for accuracy? These decisions directly shape the CMS recommendation an agency will make, so settle them before the project starts rather than after.

Sort your imagery now

Do you have a bank of approved photography, or will you rely on stock? Authentic images of your people, programs, and community tend to resonate more strongly with nonprofit audiences than generic stock photography. If a dedicated shoot is needed, it is worth budgeting for.

If you are ready to start pulling this together, submit your project brief here and we can help you work through the detail.

Technical Requirements, Hosting, and Security

Content sorted, now for the technical side of things.

This is the area where NFPs most commonly get caught out, and it is almost always because no one asked these questions before the project started.

Know your current hosting situation. Before you brief any agency, find out who your hosting provider is, when that contract expires, and who holds the login credentials. You would be surprised how often an NFP gets partway through a rebuild only to discover that the person who set up the original site left three years ago and took the login details with them.

Note any platform preferences. Some NFP boards prefer open-source platforms like WordPress or Drupal because they protect against vendor lock-in long term. Others need to match a platform their IT provider already supports. Either way, document this preference in your brief so agencies can scope accordingly.

Flag your compliance obligations upfront. If your organisation collects sensitive client data, handles health information, or operates under specific regulatory frameworks, your website’s security architecture needs to reflect this from day one, not be retrofitted after launch. Security measures must match the type and sensitivity of the data you process.

Ask about post-launch support. What happens after the site goes live matters as much as the build itself. Ask each agency how software updates are managed, who handles a broken plugin outside business hours, and what their service level agreement looks like. Get this in writing before you sign anything.

Confirm domain and DNS ownership now. Your organisation should own its domain, not a former staff member or a previous agency. Transferring domain ownership mid-project creates delays; discovering it on launch day creates emergencies. Check this today.

If you are ready to move forward, submit a brief and our team will help scope your project.

What Agencies Actually Need From You to Write a Useful Proposal

Once your technical and hosting details are documented, you’re ready to think about how the brief lands with the agency receiving it.

Agencies invest real time in scoping and proposal writing, often several hours before a single dollar changes hands. The more specific your brief, the more accurately they can price the work and the more confidently they can commit to outcomes. A vague brief produces a vague quote, and that gap almost always causes friction later.

A useful brief covers these eight elements:

• Organisation overview: mission, size, and funding model
• Website goals with measurable outcomes
• Audience profiles
• Integration requirements
• Content responsibilities
• Budget range
• Timeline
• Decision-making process

Be upfront about your timeline drivers. If there is a funding announcement, a gala dinner, or an annual report release creating a hard deadline, say so clearly. Agencies can often work to tight timelines, but only if they know about them from the start.

Tell agencies how you will choose. Are you selecting on price, portfolio fit, sector experience, or the working relationship? Agencies who understand what you value write better proposals, and you make a better decision. This is worth one honest paragraph in your brief.

Ask for case studies showing nonprofit clients — the information architecture, donor psychology, and user needs are genuinely different from commercial projects.

Expect clarifying questions, and answer them quickly. A good agency will come back before finalising their proposal to confirm assumptions or flag ambiguity. How you respond at this stage is a reliable signal of how the project relationship will work on both sides.

If you are ready to put a brief together, submit your project details and our team will help scope it from there.

Your Pre-Brief Checklist at a Glance

Here is everything covered in the preceding sections, distilled into one working reference. Print it, share it with your board, or work through it in a team meeting before you approach any agency.

Governance and sign-off

• Board approval documented in writing
• Single decision-maker named with delegated authority
• Input roles versus approval roles mapped for each stakeholder
• Review availability confirmed across key milestones

Budget

• Capital build cost separated from ongoing hosting and maintenance
• Must-haves and nice-to-haves listed in writing
• Contingency buffer allocated
• Phased delivery considered if full budget is not available upfront

Mission and audiences

• Plain-English mission summary written (two to three sentences)
• Audience priorities ranked, not listed as equals
• Two to three website goals defined with measurable outcomes
• Current website failures documented honestly

Donor journey

• Donation types listed (one-off, regular giving, in-memory, bequests)
• Current funnel documented using existing analytics
• Payment gateway confirmed or flagged as a decision to make
• Emotional job defined for each key page in the giving journey

CRM and integrations

• Every connected system listed with its integration method
• Native connector, custom API, or middleware identified for each
• Data flows mapped between website and CRM
• Login credentials and admin access ownership confirmed

Accessibility

• WCAG 2.1 AA specified as the minimum standard
• Specific audience needs documented (older donors, CALD communities, people with disability)
• Any existing audit findings or complaints included
• Funding agreement compliance requirements checked

Content

• Named owner assigned per content type, not per department
• Existing content audited before the brief is written
• Each piece categorised as migrate, rewrite, or create new
• Post-launch governance defined, including CMS access and review cadence

Technical

• Current hosting provider, contract expiry, and credentials documented
• Platform preferences or IT constraints noted
• Security and data compliance requirements flagged
• Domain and DNS ownership confirmed as sitting with the organisation

If you can tick every item above before your first agency conversation, you are starting from a position of genuine readiness. If gaps appear, that is exactly what this exercise is for. Better to find them now than three months into a build.

Start with the Brief, Not the Budget Conversation

That checklist covers the hard work. Now here is the honest truth about what it represents.

Working through these questions is the single highest-return investment you can make before a website project begins. Not the agency selection, not the platform decision, the brief. As earlier sections show, scope problems almost always begin before the agency is even engaged.

If parts of this checklist revealed gaps, that is exactly the point. No CRM, no named content owner, no accessible brand guidelines, these are better discovered now, on your own time, than after an agency has started billing. Gaps found early cost you a conversation. Gaps found mid-build cost you money, momentum, and goodwill.

A thorough brief also surfaces the governance questions — budget authority, sign-off process — that belong at board level before they become urgent mid-build.

You do not need to have every answer before you speak to an agency. You just need to know which questions are still open.

At Slant Digital, we work with not-for-profit organisations across Australia and we genuinely welcome these early conversations. Before a brief is written is exactly when the right advice makes the most difference. If you are at that stage, we would be glad to help you think it through.

Conclusion

A strong website brief is not bureaucratic box-ticking. It is the foundation everything else is built on. The checklist above gives you a structured way to reach that foundation.

You do not need perfection before you start. You need clarity on what you know, and honesty about what you do not.

If working through this checklist has raised more questions than answers, that is a good sign. It means the right conversations are ahead of you, not behind you. Start them now, while they are still cheap.