Microsoft 365 case management: You probably already manage cases. You just might not call them that.
Incidents, enquiries, requests, investigations, complaints and referrals. Different names, but often the same underlying challenge: coordinating people, information, actions and outcomes through a structured process.
When someone mentions “case management”, what comes to mind?
Perhaps a customer service desk. Complaints. Legal matters. Social care. Maybe an IT support system.
But look around almost any organisation and you'll find people managing cases, even though nobody calls them that.
A customer raises an issue that needs investigating. A data protection concern needs reviewing. A property repair involves several people and external contractors. An employee raises a request that needs handling confidentially. A compliance incident needs evidence, actions and a documented outcome.
The terminology changes.
The underlying requirement often doesn't.
Someone needs to capture something, take ownership of it, understand the context, coordinate activity, manage deadlines and ultimately reach an outcome.
That's a case.
And in many organisations, the case-management system isn't really a system at all.
It's Outlook, Excel, Teams, SharePoint and the people who know how everything fits together.
What actually makes something a case?
Not every task or process needs case management.
If somebody needs to perform a simple action and tick it off, a task-management tool may be perfectly adequate.
Casework tends to become different when there is a combination of:
an owner responsible for progressing it
a lifecycle, rather than a single action
different stages or statuses
other people or organisations involved
emails, conversations and communications
related documents and evidence
actions, decisions and deadlines
service levels or escalation requirements
a requirement to understand what happened and when
an eventual resolution, closure or outcome
The more of those characteristics a process has, the less comfortably it tends to fit into a spreadsheet or shared inbox.
And that's where an informal workflow can quietly become a case-management requirement.
Seven examples you might not think of as case management
Consider some of the operational processes happening around a typical organisation.
Customer and service enquiries
An enquiry arrives by email. Someone needs to take ownership, gather information, involve colleagues, communicate with the customer and eventually resolve it.
That's a case.
Incidents and compliance issues
An incident may need to be categorised, assessed for severity, assigned, investigated, documented and potentially escalated.
There may also be regulatory requirements, evidence or deadlines involved.
That's a case.
Complaints
A complaint isn't simply an email to answer. It can have a complainant, context, supporting information, correspondence, investigation, internal decisions, timescales and an eventual outcome.
That's a case.
Property and facilities issues
A problem is reported at a property. There may be tenants or occupants, contractors, correspondence, appointments, documents, inspections, costs and follow-up actions before the issue can be closed.
That's a case too.
Internal employee requests
Some internal processes require information from several people, approvals, documents, deadlines and sometimes greater confidentiality than ordinary operational work.
Again, the underlying pattern looks remarkably like a case.
Investigations
Whether the subject is operational, financial, compliance-related or customer-facing, an investigation brings together evidence, people, activities, findings, decisions and outcomes over time.
Very definitely a case.
Specialist operational processes
This is perhaps the most interesting category.
Organisations frequently have processes that don't fit neatly into an off-the- shelf application at all.
They might call them referrals, assessments, engagements, applications, reviews, jobs, enquiries or something specific to their sector.
The name isn't particularly important.
The lifecycle is.
When does a workflow need Microsoft 365 case management?
There's nothing inherently wrong with managing work using the Microsoft 365 tools you already have.
In fact, that is usually how a new process starts.
An email arrives in Outlook.
Someone records it in Excel.
Documents are saved in SharePoint.
Colleagues discuss it in Teams.
Dates go into calendars. Tasks and reminders are added. Someone maintains a spreadsheet showing which items are still open.
For twenty cases, that might work perfectly well.
At 200, things can start looking rather different.
Which spreadsheet is current?
Who owns this?
Where's the latest document?
Did somebody reply to that email?
When is the next action due?
Why has this been open for three months?
What happened before the person who normally deals with it went on holiday?
The problem isn't necessarily the individual tools. It's that the process exists between them.
Nobody has one place where the case itself exists as a complete operational record.
One platform doesn't have to mean one process
One of the reasons organisations end up with numerous separate systems is an understandable assumption:
Different processes need different software.
Sometimes they do.
But different processes don't necessarily require different applications.
This is where Microsoft 365 case management can offer a different approach. Cases, the configurable case management and operational workflow module within the So365 One platform, is designed to support different types of operational work without forcing them all into the same process.
A compliance incident shouldn't necessarily follow the same process as a customer enquiry.
An internal service request may have very different information, stages and service levels from a property issue.
A sensitive case may have completely different access requirements.
Cases is designed to support multiple case types within the same platform, while allowing those processes to have their own fields, stages, service levels and operational rules. Our updated Cases experience demonstrates how different teams and processes can operate from the same configurable environment rather than being forced into one generic workflow.
Different processes. One platform.
The lifecycle matters more than the label
This is where case management becomes more than simply creating a record.
Consider an incident.
Initially you might need to record:
what happened
when it happened
who reported it
its category and severity
But that's only the beginning.
The incident might then need assigning. People may need to be contacted.
Documents collected. Tasks completed. Deadlines monitored. Decisions recorded. The case could move through several stages before eventual resolution.
A different type of case might have a completely different journey.
That's why configurable lifecycles matter.
The current Cases proposition supports multiple case types and configurable workflows alongside stakeholder management, service levels, reporting and governance, rather than restricting an organisation to one standard case process.
What about the information surrounding the case?
This is another area where informal processes often become difficult.
A case rarely exists in isolation.
It might relate to:
People. Customers. Suppliers. Properties. Projects. Documents. Emails. Tasks. Previous cases.
If all of that context has to be manually reconstructed whenever somebody picks up the work, you're spending time finding information before you can actually act on it.
That's particularly relevant to the way Cases sits within So365 One.
Cases can operate alongside CRM and Projects on a shared Microsoft 365 foundation, connecting operational casework with related customers and active projects rather than treating support or operational activity as an isolated system.
That can become particularly valuable as the relationship or process gets more complex.
Do you need another disconnected cloud platform?
It's worth asking.
Organisations have become used to solving each new operational requirement by buying another SaaS application.
Sometimes that's absolutely the right answer.
But every additional platform can also introduce another place for people to work, another set of permissions, another data store, another integration requirement and another subscription.
Cases takes a different approach.
As part of So365 One, Cases is designed around the Microsoft 365 environment organisations are already using and supports working with SharePoint, Teams and Outlook while keeping organisational data within the customer's Microsoft 365 environment.
For organisations already invested in Microsoft 365, that can make the question rather different.
Instead of:
“Which new case-management system should we buy?”
it's worth asking:
“Could we manage this process properly using the Microsoft 365 platform we already have?”
Five questions to ask about your own workflows
Take a look around your organisation and choose one operational process.
Then ask:
Where is the definitive record?
Could somebody unfamiliar with the case find its current status and history without searching across inboxes, spreadsheets and folders?
Is ownership clear?
Can you immediately see who is responsible and what needs to happen next?
Can you see the complete lifecycle?
Can you understand how something progressed from initial enquiry or incident through to resolution?
Are deadlines and service levels managed systematically?
Or do they depend on Outlook reminders, spreadsheet columns and individuals remembering to chase them?
Could another person pick it up tomorrow?
If the usual owner disappeared for two weeks, could somebody else understand the case and continue working on it confidently?
If several of those questions produce uncomfortable answers, you may not have a problem with Outlook, Excel, Teams or SharePoint.
You may have a process that's outgrown the way you're using them.
What could Cases support for you?
We're currently working with clients using Cases around real operational processes, and those conversations keep reinforcing the same point.
Almost every organisation has casework. They just use different names for it.
Incident.
Enquiry.
Request.
Investigation.
Referral.
Complaint.
Job.
Assessment.
Review.
Or something entirely specific to your organisation.
So perhaps the most useful question isn't:
“Do we need case management software?”
It's:
“What are we currently managing through a combination of email, spreadsheets, Teams and shared folders that would benefit from becoming a properly managed process?”
That might be a very good place to start.
Comments