SharePoint consulting for mission-driven organizations
Board members, committee volunteers, programme volunteers and funders all need to reach something — and none of them hold a staff seat. That single constraint is what makes a nonprofit intranet a different build from a generic one: grant files structured by award and grant cycle rather than by year, a board and committee library that guests can reach without opening the rest of the tenant, volunteer access that does not quietly require a full licence, and retention on grant records that starts when the award closes. Sized around whatever Microsoft 365 Nonprofit licensing your tenant actually carries. One written fixed fee, typical delivery in 2–4 weeks, 30 days of hypercare included.
Representative dashboard — sample data
What we configure
Each of these is configuration of tools already inside your Microsoft 365 tenant — scoped in writing before anything is built.
A library per award, laid out by stage — proposal, agreement, budget, expenditure evidence, interim report, closeout — with funder, program and award period as columns, so the reporting deadline is a view rather than a memory.
Directors and treasurers who hold no staff mailbox still get the board packet — signed in as themselves, in the one site where external sharing is deliberately on, with finance and governance committees kept separate from the full board.
Rotas, handbooks and safeguarding policies reachable by people who are not on payroll, drawn as a deliberate boundary rather than a shared link that leaks — and an honest line about where a guest stops and a licensed seat starts.
Grant and donor records kept for the period your funder agreement or finance lead requires, with the clock starting at grant close rather than at upload, and a named person confirming before anything is destroyed.
Donor records, participant case notes and HR files sit in their own sites with their own membership, instead of inheriting the permissions of whichever shared folder they were dropped into when the organization was smaller.
The next grant site comes from a provisioning template, not from us. Group-based access, named site owners and written runbooks, because in most nonprofits the person who inherits this also runs finance or communications.
How it works
A free consultation covers which awards you hold and what each funder requires you to keep, how the board pack is assembled and circulated today, who on the board or committees is not a staff member, which volunteers need to reach what, and what licensing your tenant already carries. We reply with a written scope, one fixed fee and a delivery date.
We configure a single award library and a single committee site first, invite a test guest, and try to reach everything else from that guest account — before any donor record, case note or funder agreement is moved in.
Remaining awards, programs and committees move in agreed waves with funder and period metadata applied on the way in. Your staff are trained to spin up the next grant site from the template themselves, and we stay on for 30 days of included hypercare.
This is the line that separates a nonprofit build from every other one we do. In a clinic, a law firm or a contractor, almost everyone who opens a document is on the payroll and holds a licensed account; the design problem is which staff see which files. In a nonprofit, the board that approves the budget is unpaid and works elsewhere, the finance committee may be three volunteers with day jobs, the programme is delivered by people who are rostered rather than employed, and the funder may ask to see expenditure evidence directly. A structure that assumes a licensed staff account behind every reader falls apart on contact with that reality — usually into a habit of emailing PDFs around, which is how last quarter’s board pack ends up being the one a director is reading.
So the boundary gets drawn first, not last. We separate the tenant into what staff work in, what the board and its committees work in, and what a guest may ever reach, then build outward from there. That ordering matters because Microsoft’s external sharing documentation (opens in new tab) notes that external sharing is turned on by default across a new SharePoint and OneDrive environment, that the setting exists at both organization and site level with the more restrictive value winning, and that guests sign in under their own identity rather than through an anonymous link. Left at the default, a small team that shares generously ends up with donor records and HR files one link away from a volunteer. Configured deliberately, the board site is the place sharing is allowed and the rest of the tenant is the place it is not.
This is the translation table we scope against. Your build takes the rows that match how the organization runs — a two-grant community group and a multi-program agency with a grants manager land in different places on several of them — but the conversation is the same every time.
| What the organization calls it | What it becomes in SharePoint | Why the shared-drive version stops working |
|---|---|---|
| The grant file | One library per award with a stage-based structure and funder, program, award period and report-due dates as columns | A folder named after the funder and the year cannot tell you which of eleven awards has a report due next month |
| Board packet | A board site whose meeting sets hold agenda, minutes, finance papers and resolutions, reachable by guests signed in as themselves | Emailed PDFs mean the version a director reads is whichever attachment they opened, and nothing is retrievable later |
| Finance or governance committee papers | A separate site with its own membership, not a folder inside the board site | Folder permissions inherit downwards, so a committee folder is visible to the whole board by default |
| Bylaws, conflict-of-interest and safeguarding policies | A published policy library carrying owner, approving body, effective date and next-review date | Nobody can tell an approved policy from a draft when both are documents in the same folder |
| Donor and funder records | A restricted development site with its own membership, deliberately outside general staff reach | Major-donor correspondence in a shared folder is readable by everyone who was ever added to it |
| Participant or client case files | A program site with unique permissions, sharing off, and access requests routed to the program lead | Case notes filed under a program folder inherit whatever access that program folder accumulated |
| Volunteer handbook and rota | A single volunteer-facing site that guests may reach, holding only what volunteers should see | Sharing individual files one by one produces a permission map nobody can audit or revoke |
| Grant reporting calendar | A due-date column driving a filtered view and a scheduled reminder to the named owner | The deadline lives in the grants lead’s calendar and leaves when they do |
| Record retention for grant records | Purview retention labels with the clock keyed to award close, plus disposition review before deletion | Nothing about a folder changes when a grant closes, so a period measured from closeout never starts |
| “Ask whoever set it up” | A site provisioning template, named site owners, group-based access and a written runbook | An undocumented structure in an organization with no IT staff decays the moment that one person leaves |
Read this before you scope anything, because it moves the design and not just the invoice. Microsoft operates its own grant and discount programs for eligible nonprofit organizations, with eligibility assessed and registration handled by Microsoft and the current terms published on Microsoft’s nonprofits page (opens in new tab). We are an independent consultancy and not a reseller of those grants, so we will not quote you an offer, a seat count or an approval outcome — those are Microsoft’s to state and yours to check.
What we can say is what the answer does to the architecture. Granted and discounted seats are finite and are allocated by the organization to the people it decides need them, which in practice means the staff who create and manage content. Everyone else in the orbit of a nonprofit — the board, the committees, the volunteers, sometimes the funder — sits outside that pool. Once you accept that, the design question stops being “where does this file go” and becomes “which of these four audiences reaches it, and through what”. Build it the other way round, as an internal intranet that later has guests bolted on, and you get the pattern we are usually called in to unpick: a dozen individually shared links, no idea who still holds one, and a board member who lost access when their personal email changed.
| Who needs to reach something | What they actually need to do | How it gets built | What that implies about licensing |
|---|---|---|---|
| Staff and programme managers | Create, edit and own content; run the grant and program sites day to day | Member or owner of the staff sites, in groups by function rather than named one at a time | Licensed seats — the population your granted and discounted allocation is for |
| Board directors and treasurer | Read the packet before a meeting, occasionally upload a paper or a signed resolution | Guests on the board site, signed in as themselves; sharing deliberately enabled on that site only | Not staff accounts — but confirm the guest terms for your tenant during scoping, not afterwards |
| Finance or governance committee | Work on papers the wider board should not see until the committee has finished | A separate committee site with its own membership, not a subfolder of the board site | Same guest route as the board, but membership is drawn narrower on purpose |
| Volunteers | Read a rota, a handbook, a safeguarding policy; sometimes submit a form | A single volunteer-facing site holding only volunteer content; form submissions land in a staff site | Depends on the task — reading is a guest question, staff-equivalent work is a licensed one |
| Funder or independent auditor | Inspect expenditure evidence for one award, for a defined period | Time-boxed guest access to that award’s library only, granted for the review and removed after | Nothing standing — the access is created for the audit and expires with it |
| Contract bookkeeper or grant writer | Work inside your files the way staff do, but they are not on payroll | Scoped like staff, in the sites their engagement covers and nothing wider | Usually a licensed seat — the honest answer, even when it is not the one hoped for |
We do not decide any of this for you and we do not administer your grant application. What we do is check what your tenant actually carries before designing anything, and tell you plainly when something you were hoping to avoid paying for cannot be avoided. If the licensing conversation is broader than SharePoint, our comparison of Microsoft 365 Business Premium against E3 covers the ground beneath it.
Ask a grants lead where the evidence for a 2023 award is and you will usually get a route rather than a location: the proposal is in the folder named after the funder, the signed agreement is in an email, the receipts are in the finance drive by month, and the interim report is on somebody’s desktop. Nothing is lost, but reassembling it for a funder review takes a fortnight the organization does not have. The fix is to make the award, rather than the calendar year, the thing the structure is built around, and to record funder, program, award period and report-due date as real columns. Where several programs share a vocabulary of funders and award types, managed metadata term sets (opens in new tab) keep those values consistent across sites instead of re-typed differently in each one.
Retention is the second half, and it is the half most small organizations cannot enforce, because enforcement on a shared drive means a person deleting files on purpose and nobody wants to be that person. Microsoft’s documentation on retention policies and labels (opens in new tab) draws the distinction that decides this design: a retention policy applies the same settings across a site, while a label applies to an individual item, and only labels can start the retention period from an event rather than from creation or last modification, and only labels support disposition review before permanent deletion. For grant records that is the whole point — the obligation in a funder agreement typically runs for a period after the award closes, not after a receipt was scanned, and only an event-based label can express that.
What we will not do is tell you what those periods are. Retention obligations for a nonprofit come from your funder agreements, federal and state requirements, your auditor and your own counsel — a mix we are not qualified to resolve and would not put in a scope document. Bring the schedule your board or finance lead has approved; we configure the tenant to enforce it and document exactly how, so the next person can see what was set and why.
Most of our nonprofit engagements have no full-time IT staff on the other side. The tenant is administered by a finance manager, an operations lead or a communications officer who took it on because somebody had to, and often by a board member with a technical background who helps out on evenings. That changes what a good deliverable looks like: a structure that only its designer can extend is a liability in that environment, however elegant it is.
So the self-service part is the deliverable, not a bonus. The next grant, the next program, the next committee is provisioned from a template rather than assembled by hand — SharePoint site templates and site designs (opens in new tab) apply a consistent set of lists, libraries, columns and settings to a new site automatically, which is what stops year three looking nothing like year one. Access runs on groups, so adding a new board member is one membership change rather than a hunt through individual permissions. Every site has a named owner who is a person and not a role nobody filled. And the runbooks are written for the person who actually holds the job, covering the handful of things that will genuinely come up: onboarding a director, removing a volunteer who has left, opening a new award, closing an old one. During the 30 days of hypercare we would rather watch your staff do each of those once than do them for you.
Three shapes cover most requests from mission-driven organizations. Every fee is fixed and put in writing after your free consultation — the table shows scope and typical timeline, because an honest number needs to see your document volume, your board and volunteer access requirements and your current licence position first.
| Engagement | What is configured | Typical timeline | Fee |
|---|---|---|---|
| Board and committee portal | A board site with meeting sets for agendas, minutes, finance papers and resolutions, separate committee sites with their own membership, guest access configured and tested, and a runbook for onboarding and offboarding directors | About 2 weeks | Fixed fee — scoped after your free consultation |
| Grant and program document management | The award library structure and grant-cycle metadata, reporting-deadline views and reminders, a restricted development site for donor records, a volunteer-facing site, and the permission model and external sharing settings behind all of them | 2–3 weeks | Fixed fee — scoped after your free consultation |
| Whole-organization intranet and handover | The above across every program and committee, retention labels including event-based clocks and disposition review, migration of agreed content off the existing drive with metadata applied in flight, site provisioning templates, and admin runbooks written for a non-IT owner | 3–4 weeks | Fixed fee — scoped after your free consultation |
We publish no price list, because the number depends entirely on the scope agreed after your consultation. The wider drivers behind a SharePoint fee — number of sites, volume of content to migrate, how much structure has to be designed rather than moved — are broken down on our SharePoint intranet cost page, the fixed-fee model itself is explained on how it works, and if the timeline is what worries you, our SharePoint intranet in 30 days walkthrough sets out what a short build can and cannot include.
Small and mid-sized US nonprofits — community and social service agencies, foundations, arts and cultural organizations, faith-based charities, associations and volunteer-led groups — already paying for or granted Microsoft 365, and still running documents off a shared drive with a board packet that goes out by email. The trigger is usually one of five things: a funder review or independent audit on the calendar, a grants lead leaving and taking the filing logic with them, a new executive director asking who can see the donor list, a board that has started meeting on personal email attachments, or a shared drive that has outgrown whoever set it up. It is a poor fit for organizations that have not yet decided who owns the board packet and the grant file, because a structure built on an undecided owner has to be rebuilt.
Two neighbouring pages are worth being explicit about, because the overlap is real. This is document management and access, not reporting: if the need is grant burn, restricted-fund balances, donor retention and a board pack of numbers, that is a different engagement and our Power BI consultant for nonprofits page is the right one — it is the natural analytics next step once documents carry consistent funder and program metadata, because the reporting layer can then read them. And this page is the nonprofit-shaped child of our wider SharePoint intranet and document management consulting, which covers the same engineering standards without an industry vocabulary; what differs here is the guest-heavy audience, the grant-cycle structure and the licensing reality, not the build quality. The equivalent for a sector where nearly every reader is on payroll is our SharePoint consultant for healthcare engagement, which is a useful contrast if you are deciding which shape you actually have. If the files are still on an in-house server, our file server to SharePoint migration playbook explains why the structure gets designed before anything moves, and the reporting deadlines and reminders behind a grants calendar are automated reminder and approval workflows rather than a spreadsheet someone checks on Fridays. We work with organizations in all US states remotely from our Orange County, CA base.
Related services
The wider fixed-fee service: intranets, document management, migration and governance across any industry.
Grant burn, restricted funds, donor retention and the board pack of numbers — the analytics next step.
A written read on sharing settings, guest access and admin roles before donor and case records move anywhere.
Further reading
Hand-written guides from our article library.
The step-by-step playbook for moving documents off a server share without carrying the mess across.
What a short, tightly scoped build actually delivers — and which decisions have to be made first.
The factors that move a fixed fee up or down on an intranet and document management project.
FAQ
Microsoft runs grant and discounted licensing programs for eligible nonprofit organizations, and both eligibility and the number of granted seats are decided by Microsoft, not by us. We are not a reseller and will not promise you an offer or an outcome. During scoping we look at what your tenant already carries and design around it.
Yes, as guests. A board member signs in under their own email address rather than being given a staff account, and the board site is the one place where external sharing is deliberately allowed. Committee sub-sites keep their own membership, so finance committee papers are not visible to the whole board.
It depends entirely on what they need to do. Reading a rota, a handbook or a safeguarding policy can usually be handled by guest access to one site rather than a staff account. Anything closer to staff work needs a licensed seat. We separate those two during scoping rather than assuming the cheaper answer stretches.
By award and by stage, not by the year somebody happened to save the file. Each grant gets its own library with the proposal, agreement, budget, expenditure evidence, interim reports and closeout in named places, and the funder, program and award period recorded as columns rather than typed into filenames.
Yes, with retention labels. Microsoft Purview retention policies apply the same settings across a site, while labels apply per item and can start the retention period at an event such as an award closing. Labels also support disposition review before deletion. Your finance lead or board sets the periods; we configure them.
You do, and the design assumes it. New grant and program sites come from a provisioning template instead of being built by hand, access runs on groups rather than one-off grants, and you get written runbooks plus 30 days of hypercare, so the first real change after handover is made with us alongside.
Book a free consultation
Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.
The fastest way to reach us is the form — tell us the task and we’ll reply within one business day.