Readiness guide / No fabricated score
See where IT ownership is clear-and where it disappears.
This assessment is a conversation guide, not an automated grade. Use it to prepare internally or bring the answers to a scope conversation.
Read this page in FrenchPeople and access
Who handles joiners, leavers, account recovery, permissions, and recurring access friction? Is there one intake path, and can the team use it in its working language?
Devices and applications
Can you identify the devices people depend on, their working condition, and who owns routine upkeep? Which business applications need vendor coordination?
Microsoft 365
Who is responsible for licensing, tenant hygiene, configuration decisions, and changes that affect mail, Teams, identity, or collaboration?
Vendors and escalation
When an issue crosses internet, line-of-business software, hardware, and Microsoft 365, who carries the context between providers? See how vendor coordination works
Leadership decisions
Are technical risks and project choices translated into decisions with an owner, timing, cost, and clear next action?
How to use the result
Look for orphaned responsibilities.
A “no” is not a failure and there is no public benchmark behind this guide. It simply points to work whose owner, context, or decision path may be unclear.
Bring the unclear areas to a scope conversation. They are more useful than a generic request for “better IT.”
Build a copyable service map →Team service map
Build your team service map.
Identify the language, workplace pattern, systems, and recurring friction to cover. The map creates a discussion list in your browser; nothing is submitted.
Your next step
Never send passwords, recovery codes, API keys, or other secrets in your message.
Next step
Prepare the responsibilities before contacting a provider.
The service map turns your context into a short, copyable list: people, devices, Microsoft 365, vendors, and decisions to clarify.
Build the service map