Clear Expectations Matter More Than a Long Service List
A managed IT agreement may look straightforward at first: a monthly fee, a list of services, and a general description of what the provider handles. The details matter when something falls outside the normal routine.
For example, new-user setup may be included, while SharePoint changes, onsite work, after-hours support, or larger system changes are billed separately. That is not necessarily a concern, as long as the agreement makes it clear.
Before signing, you should understand what is included, what may cost extra, and how less common requests are handled. That clarity is one important part of a broader managed IT buying decision, and it helps avoid mismatched expectations once the relationship begins.
When “Fully Managed” Still Leaves Questions
“Fully managed” can mean different things from one provider to another. One agreement may include day-to-day Microsoft 365 administration, user changes, vendor coordination, and onsite support, while another treats some of those as separate project work.
The wording itself is not the problem. What matters is whether the scope is specific enough that your team can tell where regular support ends and additional work begins.
For a charity, that can include less predictable needs such as setting up temporary staff, supporting a short-term program, adding volunteers to shared systems, or making changes around a fundraising campaign. If those situations are likely to come up, it is worth understanding how they are handled and billed before the contract starts.
A good agreement does not need to include everything. It should simply make the boundaries clear enough that your organization can plan around them.
Make Sure Responsibilities Are Actually Assigned
An agreement can say the provider “manages backups” or “handles Microsoft 365,” but that still leaves room for confusion if it does not explain what that responsibility includes.
For example, who checks that backups are completing properly? Who tests whether data can actually be restored? Who approves permission changes, keeps system documentation current, or coordinates with another software vendor when an issue crosses between systems?
These details matter because IT responsibilities are often shared. Your provider may manage the technical side, while someone inside the charity still approves access changes, decides who should see certain information, or authorizes major changes.
The goal is not to spell out every possible scenario. It is to make sure the important responsibilities are clear enough that everyone knows who is expected to do what, especially when something unusual happens. That same clarity should carry into your disaster recovery planning, where recovery responsibilities need to be understood before they are ever needed.
Your Organization Should Still Stay in Control
It is normal for an IT provider to have administrative access to the systems they support. The important question is whether your charity still retains clear ownership and control of those systems.
That includes things like your Microsoft 365 tenant, domain registration, backup platform, security tools, licensing portals, and key administrative accounts. If everything depends on credentials or accounts held only by the provider, changing providers later can become much harder than it needs to be.
The same applies to documentation. Your organization should be able to access important records about how systems are configured, who has administrative access, and what services are in place, rather than relying on one provider to hold all of that knowledge.
This does not mean your team needs to manage those systems day to day. It simply means the relationship should be structured so the provider manages the technology on your behalf without becoming the only party capable of controlling it.
Leaving Should Not Be More Complicated Than It Needs to Be
Most organizations do not choose an IT provider while thinking about how the relationship might eventually end, but the contract should still make that process reasonably clear.
Look at the notice period, renewal terms, any early termination fees, and what transition support is included. It is also worth confirming how your organization would receive administrative credentials, documentation, configuration details, and copies of any data held in provider-managed systems.
Some transition work may reasonably be billable. The key is knowing what that process looks like before you need it.
A good agreement should make it possible for another provider to take over without unnecessary confusion or delay. That usually depends less on having a perfect exit clause and more on making sure your organization’s access, documentation, and ownership are clear throughout the relationship.
Start With a Clear Onboarding Plan
The contract should give you a reasonable picture of what happens between signing the agreement and settling into normal support.
That may include gathering information from your current provider, reviewing devices and Microsoft 365 settings, confirming administrative access, checking backups and security tools, and documenting how your systems are set up. If the provider expects to find and fix older issues during onboarding, it should also be clear which work is included and which may be billed separately.
There should also be some clarity around communication. Your team should know when the new provider officially takes over, where staff go for help, and who is responsible for coordinating any outstanding items during the transition.
A good onboarding process does not need to solve everything in the first few days. It should give both sides a clear starting point. From there, the first couple of weeks should feel organized rather than improvised, which is why it helps to understand what managed IT onboarding actually looks like.
A Clear Contract Makes the Relationship Easier to Manage
By the time you sign an IT agreement, you should understand what is included, what may cost extra, who is responsible for key tasks, and how the relationship will work if your needs change.
The contract does not need to predict every staffing change, new program, or unusual request. It simply needs to give both sides a clear enough framework to handle those situations without confusion.
For a charity, that clarity makes budgeting, planning, and shared responsibility easier. More importantly, it creates a stronger foundation for the working relationship that follows.
