Inactive
Helping your business
perform at its best.
perform at its best.
Technology Partners
- AWS
- Google Cloud
- Microsoft
- Apple
Charity SharePoint specialists · Staff resources · Governance documents
Give your charity one understandable place for approved policies, staff guidance and shared working documents. NetMonkeys helps charities plan and implement SharePoint Online around the people who create, approve and use their information.
Start with a staff intranet, trustee document area, volunteer resources or a move from shared drives. We agree a practical scope, assess relevant licensing and prepare the owners who will keep the environment useful.
Design around staff, trustees and authorised contributors rather than a generic template.
Agree publishing and document ownership that fits your charity’s capacity.
Distinguish implementation, content preparation, subscriptions and ongoing assistance.
A charity’s shared information often grows around immediate needs. A policy arrives by email, a volunteer guide is saved in a personal folder and a board pack is assembled from several versions. Over time, staff spend effort locating the right resource instead of using it.
We begin with the people and tasks affected. Staff may need current guidance, trustees may need controlled access to selected papers and publishers may need a simpler way to update resources. Those audiences do not automatically need the same permissions or the same entry point.
Your implementation should reflect the capacity available to maintain it. A smaller, well-owned first release can be more useful than a large intranet with unclear responsibilities. We identify the initial content, the owners and the acceptance tasks needed to make that first release practical.
We can deliver a focused review or a defined implementation, with additional work scoped where it supports your requirements. The proposal identifies the responsibilities your charity must supply alongside the technical delivery.
Review selected sites, libraries and information tasks before buying a wider project. We identify useful existing work, structural issues and unresolved decisions. Findings help prioritise improvements, distinguishing configuration from content preparation, migration or development so your charity can assess the next commitment.
Create an employee destination for policies, contacts, announcements and common resources. We agree navigation and page patterns around the tasks staff need to complete. Initial content and publishing ownership are planned with your team, helping the intranet remain useful after its launch.
Organise approved guidance, working documents and other selected information around their purposes. We scope libraries, useful properties and versioning arrangements, with your owners defining review and access requirements. Representative users check that they can recognise and reach the correct resource.
Assess a defined area for selected trustee papers and governance resources. Your authorised stakeholders decide the audience, publishing responsibilities and required boundaries. We configure and test the agreed approach, while wider identity, device and information handling requirements are identified where relevant.
Consider how authorised volunteers should reach appropriate guidance and resources. We assess the audience, access route and licensing implications before implementation. A staff-only resource, an external participant and a wider public resource can require different approaches rather than one assumed user model.
Plan a move from agreed sources into a useful SharePoint destination. Content owners confirm what is current and what should move. A pilot tests representative information and access, while the transition plan explains where staff should work and who validates the result.
Assess a recurring internal request, review or approval using suitable capabilities. We establish the information needed, decision roles and exception handling before build. Additional Power Platform features, connections and licences are identified where they affect the proposed scope.
Prepare readers, publishers and administrators for their different responsibilities. Guidance can use the delivered environment, keeping examples relevant to the charity. Ongoing assistance is agreed explicitly, with supported activities, availability and request routes distinguished from new development or content ownership.
New starters and established employees often ask similar questions: where is the current policy, who owns a process and which form should be used? We use those journeys to choose navigation and homepage priorities before discussing a large collection of features.
The intranet can bring approved staff guidance together while preserving different department responsibilities. A central resource should not require separate copies for every team. Clear relationships between pages and libraries help employees reach the information without understanding the history of each document.
Publishing needs to fit the people available. We agree who prepares content, who approves important changes and who reviews older pages. Reusable patterns and practical training help contributors maintain consistency alongside their other duties. Your first release should include resources with owners who can keep them current.
Our SharePoint intranet design service covers the related employee experience and publishing decisions.
A trustee document area should be designed around the information and authorised audience involved. Your charity identifies who needs access, who publishes the papers and how updated versions should be recognised. We assess the technical approach against those decisions.
The process surrounding the documents matters. Someone needs responsibility for assembling the current pack, checking the information and withdrawing or replacing material when the business process requires it. SharePoint configuration supports the agreed routine; it does not decide the charity’s governance procedures.
Acceptance can include an authorised participant finding the current papers, a publisher replacing an approved document and the responsible owner managing an agreed access change. Identity, devices and sharing requirements are assessed where relevant, with a clear route for future administration rather than an assumption that the area maintains itself.
Volunteer information should begin with the intended audience and the sensitivity of the material. Some resources may belong within authorised collaboration, while other guidance may be better delivered through a different channel. We assess the requirement rather than assume every volunteer should receive the same access as an employee.
Your team identifies which people contribute, which only need to read information and how participation changes over time. Joining, changing roles and leaving should have an accountable owner. Those practical details affect permissions, licensing and the administration your charity must sustain.
We also consider how contributors find help. An occasional participant may need clearer instructions than an experienced employee. Representative testing should establish whether the intended users can reach the appropriate information and understand what to do next, using the access arrangements agreed for the project.
Tell us who needs the information, where it lives today and the task that is causing extra work. We will discuss a sensible first scope and the decisions needed to prepare a proposal.
Discuss your projectMicrosoft provides nonprofit offers for organisations that meet its current eligibility requirements. Approval and the availability of a particular offer should not be assumed from charity status alone. Your charity should check its validated tenant, subscriptions and applicable user requirements before implementation is committed.
We assess the licensing relevant to the proposed solution and identify dependencies. SharePoint access, external participation, additional Power Platform capabilities and connected services can have different requirements. Implementation fees should be distinguishable from software subscriptions and any ongoing assistance.
Use Microsoft’s nonprofit eligibility guidance and Microsoft 365 offer guidance for the programme information. We scope the project against the environment and permissions your charity is authorised to use, without promising a grant, discount or specific licence entitlement.
Charities can hold different kinds of information with very different audiences. General staff guidance should not automatically share a structure with restricted personnel, beneficiary or other sensitive material. Your designated owners identify the requirements and decide which information belongs within the scoped solution.
We assess libraries, access and the wider dependencies relevant to those decisions. A charity intranet is not automatically a substitute for a specialist case management or donor system. The appropriate location and working process should be established before moving information because a shared platform happens to be available.
Review, retention and disposal decisions remain with your authorised owners. Where related technical configuration is included, the proposal identifies the relevant capabilities and licensing. Your handover explains how changes are approved and who should be involved when a request affects more than routine administration.
We work with the sponsor, IT contact and relevant business owners, identifying the decisions and preparation required at each stage. The plan should fit stakeholder availability and the charity’s capacity to maintain the result.
Identify the information problem, audiences and useful outcome. Establish whether a review is needed before implementation can be scoped.
Propose navigation, libraries and access. Confirm initial content, licensing and the people who approve publishing or information decisions.
Implement the agreed solution and use representative tasks to test access, navigation and any scoped processes. Record findings and required corrections.
Train the agreed audiences, communicate the working arrangements and validate the expected result. Assign outstanding items to responsible owners.
Confirm content, administration and support responsibilities. Assess further requirements as defined work rather than allowing the first release to become an unclear programme.
The move starts by identifying the sources and the people authorised to decide what should happen to the content. Current policies, historical documents and uncertain copies may require different treatment. We help expose those decisions before wider transfer begins.
Destination design comes before mapping. Staff guidance, trustee resources and department working files may need distinct structures and access. A pilot tests representative information and user tasks, revealing preparation or design issues while the migration plan can still be refined.
The transition should explain where staff make changes and which source is authoritative. Validation, exceptions and any source retirement follow the approved plan. Our shared drive replacement guide provides useful questions for your internal owners before a migration discussion.
Scope, source readiness, audience access, migration, development and training affect project cost. A staff resource library differs from a wider intranet, trustee area and connected approval process. We establish what the first release needs to deliver before proposing implementation.
Your quote identifies preparation and acceptance responsibilities alongside the technical work. It separates subscriptions, additional tools and ongoing support where relevant. A defined assessment can come first if the environment or requirements are not yet clear enough to price implementation responsibly.
| Requirement | What we agree with you |
|---|---|
| Initial scope | Selected audiences, sites, libraries and employee tasks. |
| Content preparation | Current resources, approval owners, cleanup decisions and migration. |
| Access and licensing | Staff, trustees, external participants and relevant subscriptions. |
| Launch and maintenance | Training, publishing routines, documentation and ongoing assistance. |
Readers, publishers and administrators need different guidance. Staff need to find and use resources; publishers need to update information; administrators need to understand the agreed structure. We choose examples from the delivered environment where possible so training addresses real tasks.
Your charity keeps business ownership of its information. A technical provider cannot reliably recognise every outdated policy or decide whether a trustee paper should be replaced. Named owners and review routines are therefore part of a maintainable implementation rather than optional extras after launch.
Ongoing support can be scoped for the selected environment. Included activities, availability and request routes are agreed explicitly, distinguishing investigation and administration from additional development. For a hospice-specific brief, explore our SharePoint document management service for hospices.
A charity does not need to publish every historical document to make the first intranet useful. Begin with resources employees repeatedly request and owners who can confirm the current version. That may include staff guidance, contact information and selected forms, with other areas considered once their requirements are understood.
Your project sponsor should identify the problem the first release addresses. A new starter finding the right guidance is a different outcome from trustees reviewing selected papers. Both can be valuable, but combining them without an agreed audience and access model can make the initial implementation unnecessarily difficult to approve and maintain.
We help define the selected content, navigation and responsibilities, then test representative tasks with the intended users. Findings reveal whether an information gap, unclear wording or technical behaviour needs attention. The pilot provides a basis for deciding when the environment is ready for wider use.
Further departments or resources can be assessed after that first result. The charity can use what it has learned about publishing capacity, employee questions and administration to prioritise the next stage. This supports a practical improvement plan without committing the team to an environment it cannot keep current.
People join, change roles and leave a charity, while responsibility for documents and approvals must continue. The design should therefore identify business ownership rather than depend on one employee remembering where information lives. Your charity needs an accountable route for approving changes and maintaining the selected resources.
Publishers require enough guidance to update information consistently. A replacement owner should understand the purpose of a page, the audience it serves and the review routine expected. We can include relevant documentation and training within the scope, with the charity responsible for appointing and supporting the people who carry out those duties.
Technical dependencies also need continuity. Where workflows or connected services are included, the handover identifies their ownership and administration requirements. Your technical team should understand which identities and subscriptions the solution depends on, and the route for investigating a failed process or an authorised change.
Periodic review can then focus on meaningful questions. Are the resources still useful? Do they have active owners? Can the intended users find them? Further specialist assistance can be scoped against the findings, while the charity retains the information decisions that belong to its own designated stakeholders.
Your first release should also make help easy to find. Tell employees where to report an unclear resource, how content corrections are approved and which questions belong with technical support. That simple route helps owners keep the charity’s information useful as working practices change.
It can support staff intranets, approved resources, selected governance documents and collaborative working where appropriate. The implementation should follow your audiences, information requirements and maintenance capacity. We agree a defined first release rather than assume every charity needs the same environment.
Eligible organisations can apply for Microsoft nonprofit offers under the current programme requirements. Approval and specific entitlements should not be assumed. Your validated tenant, subscriptions and user requirements need checking against Microsoft’s current guidance.
No such assumption should be made. Eligibility, offers, subscriptions and user requirements vary. We assess the licensing relevant to the proposed solution and distinguish software costs from implementation and ongoing assistance.
Yes. We scope navigation, initial resources, page patterns and publishing ownership around employee tasks. Representative users test the experience, while training and handover prepare the people who will maintain the information.
We can assess a defined area for selected trustee resources. Your authorised stakeholders decide audience, publishing and information requirements. We configure and test the agreed approach, including relevant identity, access and administration dependencies.
The appropriate route depends on the audience, content and licensing. We assess whether authorised collaboration or another channel fits the requirement. Joining, role changes and leaving need accountable owners and manageable administration.
That should not be assumed. An intranet or document environment serves different purposes from a specialist system. We establish the information requirements and appropriate location before proposing a move or connection.
We can assess selected sources, design the destination and scope a migration. Content owners approve what moves and how it is accessed. The plan includes representative pilot checks, transition arrangements and business validation.
Your named business owners remain responsible for content accuracy and approval. We help agree publishing and review routines and provide the scoped guidance. Technical support does not replace ownership of policies or other charity information.
We translate authorised audience and access decisions into the scoped configuration and test representative roles. Your owners identify sensitive information and approve sharing. Wider identity, device and licensing requirements are considered where relevant.
Scope, content readiness, access, migration, development and training affect cost. We establish deliverables and assumptions before quoting. Subscriptions and ongoing support are distinguished from the initial implementation.
Yes. Start with useful resources, clear navigation and available owners. A contained implementation can establish the publishing approach and user experience before further sites or processes are assessed.
Training can cover readers, publishers and administrators using the delivered environment. The proposal identifies audiences, sessions and guidance included. Handover also explains ongoing content and technical responsibilities.
Yes. Your existing provider can supply context and retain agreed workplace responsibilities while NetMonkeys carries out selected SharePoint work. We establish access, tasks and escalation routes during scoping.
Bring the information problem, intended audiences, current Microsoft environment and available content owners. Include known licensing or access questions and any deadline. The initial discussion identifies the next useful step and further assessment required.
SharePoint can be part of a wider Microsoft and IT engagement. Explore the relevant specialist services, including document management for hospices and support for different locations.
Explore the core planning, intranet and document management service.
Explore service →Discuss specialist capacity, reviews and implementation.
Explore service →Navigation, page patterns and publishing for employees.
Explore service →Clarify platform management and support responsibilities.
Explore service →Implementation, development and ongoing assistance.
Explore service →Coordinate a project involving Manchester-based teams.
Explore service →Explore the wider Scottish consultancy offering.
Explore service →Consultancy and development for Edinburgh organisations.
Explore service →Consulting and intranet development for Welsh teams.
Explore service →Explore the related specialist offering.
Explore service →Explore the related specialist offering.
Explore service →Explore the related specialist offering.
Explore service →Explore the related specialist offering.
Explore service →Use these guides to brief colleagues, identify ownership questions and prepare for a discussion about your own environment. The implementation should follow your requirements and the capabilities included in your scope.
Prepare the move from familiar folders to structured libraries.
Read guide → Guide 02Consider the ownership decisions behind permissions.
Read guide → Guide 03Plan the information employees need to find.
Read guide → Guide 04Explore structured records for requests and activity.
Read guide → Guide 05Organise working documents and project resources.
Read guide → Guide 06Give staff practical background for everyday tasks.
Read guide → Guide 07Understand the preparation behind content transfer.
Read guide → Guide 08Make common employee resources easier to reach.
Read guide → Guide 09Discuss layouts and priorities with content owners.
Read guide → Guide 10Consider the role of ongoing specialist assistance.
Read guide →Bring your staff, trustee or volunteer information challenge and an outline of the current environment. We will help establish the implementation, preparation and support your charity needs for a practical next step.
Book a free SharePoint consultationCore Service Locations: London, Manchester, Birmingham, Nottingham, Leeds, Liverpool, Derby, Bristol, Coventry, Leicester, Glasgow, Edinburgh