Signing with a new IT provider is only the start. What happens in the following month determines whether you've actually improved your position, or just moved the same problems to a new name on the invoice. Here's what a proper onboarding looks like.
Week One: Discovery and Access
The first week is almost entirely about establishing a full picture of your environment - not assuming the previous provider's documentation is accurate or complete. Expect:
- A full hardware and software inventory, often using remote monitoring tools that scan the network automatically
- Admin access set up and tested across Microsoft 365, firewalls, servers, and any line-of-business systems
- A review of backup configuration, including confirming the last successful restore, not just the last successful backup job
- Baseline security checks - MFA coverage, patch status, endpoint protection deployment
If you switched providers, this is also when access transferred during the handover gets rotated and confirmed. See our guide on switching managed IT providers without disruption for what that handover should have covered.
Week Two: Findings and Quick Wins
By the end of week two, you should receive a written summary of what's been found - not a sales pitch, an actual technical assessment. This typically includes immediate risks (unpatched systems, MFA gaps, expired licences) alongside lower-priority items that don't need urgent action. Low-risk, low-effort fixes usually get actioned in this window without needing a separate approval process.
Week Three and Four: Documentation and Process Setup
This is where the provider builds their own internal documentation for your environment - network diagrams, standard operating procedures for common requests, and an escalation path for after-hours emergencies. This is also typically when helpdesk processes get properly established: how to submit a ticket, what response times to expect, and who to call for a genuine emergency.
What Should Be Flagged, and What Shouldn't Be a Surprise
A thorough onboarding often turns up things the previous provider missed or never mentioned - an unpatched server, backups that were never actually tested, admin accounts without MFA. This isn't unusual, and it isn't a sign the new provider is exaggerating problems to justify their fee. It's a sign the assessment is being done properly. What should raise concern is the opposite: a new provider who reports no findings at all after 30 days, which usually means the review was superficial.
What Good Onboarding Communication Looks Like
You shouldn't have to chase updates during this period. Expect a short kickoff call in week one, a written findings summary by week two, and a wrap-up covering what's fixed, what's planned, and what's still needed from your side by the end of week four. If communication goes quiet after the contract is signed, that's a pattern worth watching closely - it tends to continue.
Red Flags in the First 30 Days
- No documentation or findings summary provided at all
- Admin access still not fully confirmed by week two
- Backups not tested with an actual restore, only confirmed as "running"
- Every conversation steering toward upsells rather than the findings themselves
Frequently Asked Questions
Should I expect changes to be made in the first 30 days, or just observation?
Both. Low-risk fixes - an unpatched server, MFA gaps, an expired SSL certificate - typically get actioned straight away. Larger changes, like a firewall replacement or a platform migration, get documented and proposed with a plan, not pushed through immediately without your sign-off.
Will my staff notice anything different in the first month?
Mostly not, beyond a new helpdesk contact and possibly a monitoring agent installed on their devices. A good onboarding is designed to be invisible to end users - most of the work happens at the infrastructure and admin level.
What if the new provider finds something seriously wrong?
This happens more often than businesses expect - an unpatched vulnerability, backups that were never actually tested, or MFA not properly enforced. A good provider raises it immediately with a clear remediation plan, not as a way to make the previous provider look bad, but because it needs fixing regardless of who's at fault.
How do I know if onboarding is going well versus poorly?
You should receive a written summary of findings within the first two weeks, a clear list of what's been fixed versus what's planned, and responsive communication if you have questions. Radio silence for the first month, or vague reassurance with no documentation, are both warning signs.
Every new client gets a documented 30-day onboarding - full environment review, written findings, and a clear plan before anything major changes.
Managed IT Services →Want to know what we'd find in your environment?
Call 0433 087 091 - our free IT health check covers the same ground as a 30-day onboarding review, with no commitment required.
Book a Free IT Health CheckFor related reading, see our guides to what happens during a free IT health check and switching managed IT providers without disruption.