The choice of an IT service model directly affects your costs, the pace of work, and the company's resilience to outages. In this article we explain IT offboarding — a safe separation procedure without jargon — so the board, the CFO and the owner have concrete arguments in hand to make a decision.
An employee leaving = risk. Close it with a procedure.
Closing accounts
This section frames the topic "Closing accounts" in the context of IT offboarding — a safe separation procedure. We approach it from the business side — what concrete value or risk it brings to the company.
What you gain
- Predictable monthly cost instead of irregular spend on hardware, people and training.
- Access to a team of specialists (network, cloud, security) under a single contract.
- Faster response to incidents thanks to defined processes and ticketing tools.
Most common mistakes
- A contract without a precisely defined SLA (response time ≠ resolution time).
- No clauses on knowledge and password transfer at the end of the engagement.
- "All-in" pricing without an hour cap — extra fees for every larger project later.
Hardware return
This section frames the topic "Hardware return" in the context of IT offboarding — a safe separation procedure. We approach it from the business side — what concrete value or risk it brings to the company.
What you gain
- Predictable monthly cost instead of irregular spend on hardware, people and training.
- Access to a team of specialists (network, cloud, security) under a single contract.
- Faster response to incidents thanks to defined processes and ticketing tools.
Most common mistakes
- A contract without a precisely defined SLA (response time ≠ resolution time).
- No clauses on knowledge and password transfer at the end of the engagement.
- "All-in" pricing without an hour cap — extra fees for every larger project later.
Data backup
Backup is not "copy a folder to an external drive". It is a defined process that specifies what, how often, where and for how long is copied — and how quickly it can be restored.
How many copies and where to keep them
- At least three copies of the data on two different media,
- one copy off-site (another office, cloud, colocation),
- one copy offline or immutable (ransomware-proof and safe from accidental overwrites),
- zero errors during the restore test.
That last point matters most — a backup that was never tested statistically fails to restore in 30–40% of cases at the critical moment. Quarterly restore tests are the standard we recommend to every client.
MFA revocation
Modern IT security works in layers. No single solution protects a company 100% — only a full set of layers (identity, endpoints, network, data, people) provides real effect. In the context of IT offboarding — a safe separation procedure it is worth starting with the basics:
- MFA on all accounts (no exceptions for the board — the most common gap).
- EDR/XDR instead of classic antivirus — it detects behaviour, not just signatures.
- Backups in several locations, including an offline or immutable copy — ransomware cannot encrypt them.
- Patches within 14 days of the vendor's release.
- Anti-phishing training at least quarterly, with simulations.
Key takeaways
- Predictable monthly cost instead of irregular spend on hardware, people and training.
- A contract without a precisely defined SLA (response time ≠ resolution time).
- Treat the topic of "IT offboarding — a safe separation procedure" as a project, not a one-off purchase — the best results come from a step-by-step approach.
Frequently asked questions
Considering IT outsourcing for your company?
Book a free 30-minute consultation. We will walk through your current IT service model, point out the weak spots and show what working with MAD System would look like — with no commitment.