Technical Management, Infrastructure and Platform Management, and Service Continuity Management. These are the backbone practices that answer one fundamental question for a business: ‘How do we keep our essential technology running reliably and get it back quickly when it fails?’ For your ITIL 4 Foundation exam, you need to understand that these practices aren't just about ‘fixing IT’; they are about designing, maintaining, and protecting the very foundation upon which every digital service — from your email to your banking app — is built.
Jump to a section
A simple way to picture Technical Management and Service Continuity Practices
Ever wonder what happens to your favourite online game or banking app when the power goes out or a server crashes?
Think about the building you live in. The building itself is the platform, the physical structure that makes everything possible. The ‘Technical Management’ practice is like the building’s super (superintendent) and their team. They don’t just fix a leaky pipe; they proactively maintain the boiler, inspect the electrical wiring, and replace the roof before it starts leaking. They ensure the entire infrastructure — the foundation, the plumbing, the elevators — is running smoothly, reliably, and securely. Without them, the building falls apart.
Now, imagine a massive storm is coming. The power might fail for days. That’s where ‘Service Continuity Management’ comes in. This is the building’s backup plan. The super doesn’t just hope the power stays on. They have a diesel generator in the basement, tested monthly. They have a stock of bottled water and emergency lighting in the stairwells. They have a laminated plan: what to do if a pipe bursts on the 10th floor, who to call, and how to get the building back to ‘normal’ as fast as possible. This isn’t about just ‘fixing’ the problem during the storm; it’s about having the generator, the plan, and the practised drills ready long before the first raindrop falls. Technical Management keeps the building healthy; Service Continuity Management keeps it alive during a disaster.
Let’s break down these three critically important practices. They are often confused with one another, but each has a distinct, vital purpose.
Technical Management is the broadest of the three. Think of it as the set of skills, roles, and tools responsible for the ‘technical’ bits of IT. This covers everything from managing the network cables in a server room to troubleshooting a failing hard drive. The key here is that Technical Management is about managing the technology itself. It is the practice of planning, implementing, and maintaining a stable technical infrastructure to support the business processes. It is the ‘how to’ of IT. It provides the resources, the knowledge, and the day-to-day expertise. For example, a Technical Management team might include network engineers who manage routers and switches, database administrators who look after the company’s data, and system administrators who manage the servers. They are the experts who know the specific configuration of every piece of hardware and software.
Infrastructure and Platform Management is a more focused practice that sits within Technical Management. While Technical Management is the entire engineering department, Infrastructure and Platform Management is the team that specifically looks after the ‘platform’ where applications run. The ‘infrastructure’ is the physical and virtual components: servers, storage, networking, and data centres. The ‘platform’ is the environment (like an operating system, a database, or a web server) on which applications are built and deployed. This practice is about ensuring that this underlying layer is available, scalable, and secure. It is responsible for things like provisioning new virtual servers in the cloud, managing updates to the operating system, and ensuring the database cluster is highly available. A common example is a cloud platform like AWS or Azure. The Infrastructure and Platform Management team would be the people configuring virtual machines (VMs), setting up load balancers to distribute traffic, and managing the storage for customer data. They don’t write the code for the application; they build and maintain the stage on which the application performs.
Service Continuity Management is entirely different in focus from the first two. It is not about the day-to-day running of technology; it is about planning for disaster. Its official purpose is to ensure that, in the event of a major incident (a cyberattack, a natural disaster, a power outage, a hardware failure), the essential services can continue to operate or be restored within an agreed-upon timeframe. This practice is proactive, not reactive. It asks, ‘What are the biggest threats to our critical services? If they happen, how do we keep running, and how do we get back to normal as fast as possible?’ This involves creating a Business Continuity Plan (BCP) and a Disaster Recovery Plan (DRP). A BCP is about keeping the business running (e.g., staff work from another office, manual processes take over), while a DRP is specifically about recovering the IT systems (e.g., restoring data from backup, spinning up servers in another region).
How they work together: Imagine an online payment service. - Technical Management provides the expert engineers who design and maintain the payment servers and the database. - Infrastructure and Platform Management is the team that configures the cloud servers, sets up autoscaling to handle traffic spikes, and patches the operating system for security. - Service Continuity Management ensures that there is a backup payment server in a different geographic region, that the data is replicated every five minutes, and that the team has practised the procedure to switch over if the main server crashes. The continuity plan is worthless if the infrastructure isn’t set up for it. The infrastructure is worthless if nobody has planned for its failure. All three practices must work in concert.
What does this replace? Before these structured practices, IT management was often chaotic. If a server failed, a panicked admin would try to fix it with no plan. Infrastructure was built ad-hoc. There was no thought about scalability or disaster recovery. These practices bring discipline, reliability, and predictability to the world of technology operations. Instead of a ‘fire-fighting’ culture, you create a ‘preventive and planned’ culture. ITIL 4 formalises these into repeatable, standardised practices that manage risk and ensure services are provided at the right quality.
1. Identify Critical Services
The first step in Service Continuity Management is to identify which services are absolutely critical to the business, like the payment system for a shop or the patient records system for a hospital. This is called a Business Impact Analysis (BIA). Without knowing what is most important, you cannot plan how to protect it.
2. Assess Risks and Threats
Once you know your critical services, you assess what could go wrong. This is a risk assessment. Could a fire take out the server room? Could a cyberattack encrypt the data? Could the internet connection fail? You list these threats and decide how likely they are and how much damage they would cause.
3. Design the Continuity Strategy
Based on the risk assessment, you design a strategy. This strategy defines how you will keep the service running during a disaster. It might involve having a redundant server in another city (a ‘hot standby’), having tape backups to restore later (a ‘cold standby’), or arranging for staff to work from home.
4. Develop and Document Plans
You write down the detailed plans. This includes a Disaster Recovery Plan (DRP) for the IT systems (e.g., step-by-step commands to restore the database) and a Business Continuity Plan (BCP) for the business operations (e.g., who to call, where the alternative office is, what manual process to use). Documentation is critical – a plan in your head is not a plan.
5. Test and Exercise the Plan
You cannot wait for a real disaster to test your plan. You must practise it. This step involves running a ‘tabletop exercise’ (talking through a scenario) or a full ‘failover drill’ (actually switching to the backup systems). Testing reveals flaws in the plan, like a forgotten password or an outdated step, which you then fix.
6. Review and Improve Continuously
After each test or real event, you review what happened and improve the plan. Technology changes, new people join the team, and new threats emerge. Service Continuity Management is not a one-time project but a continuous cycle of planning, testing, and improvement to keep the plan effective.
Let’s follow Sarah, an IT professional at a mid-sized e-commerce company called ‘ShopStream’. Her official title is ‘Infrastructure Lead’, and she lives and breathes these three practices.
Monday Morning - Technical Management in action: Sarah gets an alert that the company’s main customer-facing website is loading slowly. This is a performance issue. She doesn’t just guess. She uses monitoring tools to check the ‘health’ of the technology. She looks at:
- CPU utilisation on the web servers. - Memory usage on the database server. - Network latency. She identifies that the database server is hitting its memory limit. This is a core Technical Management task: diagnosing a technical problem using technical tools and knowledge. She doesn’t just reboot it; she analyses the root cause. She finds that a recent software update has a memory leak. She works with the development team to roll back the update, solving the issue technically.
Tuesday - Infrastructure and Platform Management: ShopStream is launching a huge sale next month. The marketing team expects 10 times the normal traffic. Sarah’s job now shifts to Infrastructure and Platform Management. She must ensure the platform can handle the load. She does the following:
- She logs into the cloud provider’s console (e.g., Amazon Web Services). - She configures an ‘autoscaling group’ for the web servers. This means as traffic goes up, more virtual servers are automatically created. As traffic goes down, they are destroyed. This is a classic platform management task. - She sets up a ‘load balancer’ to distribute incoming traffic evenly across these servers. - She updates the database to a larger, more powerful instance type. She doesn’t write the website code, but she builds the platform to make the code run smoothly and scalably.
Wednesday - Service Continuity Management: A crisis. A major storm is predicted for the city where ShopStream’s primary data centre is located. Sarah executes the continuity plan. She does the following:
- She checks the status of the data replication. Data is being continuously mirrored to a ‘recovery site’ in a different region, 500 miles away, every 15 minutes. This is a key part of the continuity strategy. - She runs a scheduled ‘failover drill’. She and her team simulate the loss of the primary data centre. They switch all traffic to the recovery site. The website stays online. This is the ‘practise’ part of the plan. - She documents the time it took to failover (target was under 1 hour) and notes that the DNS (Domain Name System) change took too long. She updates the Service Continuity Plan to fix this issue. This isn’t about fixing a slow server. It’s about a pre-planned, practised response to a catastrophic event to ensure the business doesn’t go offline.
Thursday - The Integration: Sarah gets a request from the security team. They need a new server to run a security scanning tool. First, she uses Technical Management knowledge to select the right hardware specs (RAM, CPU). Then, she uses Infrastructure and Platform Management to provision that server as a virtual machine in the cloud, applying standard security patches. Finally, she updates the Service Continuity Plan to include this new server, ensuring it is also backed up and included in the failover procedures. Every day, these three practices are not separate tasks; they are interwoven responsibilities.
The ITIL 4 Foundation exam will ask you to distinguish between these three practices. They are a classic ‘trick’ question area because they sound similar. Here is exactly what you need to know and what traps the exam sets.
What the exam explicitly tests: The ITIL 4 Foundation syllabus explicitly lists the purpose of these three practices under point 2.4. The exam will almost certainly include one or two questions that ask for the purpose of one of them. You must know the key phrase for each: - Purpose of Technical Management: To ‘manage and maintain the technology and infrastructure that underpins a service’. The focus is on the technology itself. - Purpose of Infrastructure and Platform Management: To ‘manage the infrastructure and platforms used by the organisation’. The focus is on the platform where applications run. - Purpose of Service Continuity Management: To ‘ensure that the organisation can continue to operate in the event of a disaster or major incident’. The focus is on business survival.
Common Exam Traps: - Confusing Scope: The exam will give you a scenario. For example: ‘An IT engineer is patching the operating system on a server. Which practice is this?’ Many candidates might say ‘Technical Management’ because they hear ‘patching’. But look closer. Patching an OS is a classic Infrastructure and Platform Management task, as it modifies the platform an application runs on. The trap is that Technical Management is broader, so candidates default to it. The correct answer is usually the more specific one. - ‘Disaster’ vs. ‘Incident’: The exam loves to confuse a disaster with a regular incident. If a single server crashes, that is an incident, handled by Incident Management. If a hurricane destroys a data centre, that is a disaster, handled by Service Continuity Management. The continuity practice is only invoked for events that threaten the entire service or business, not a simple hardware fault. - ‘Plan’ vs. ‘Tech’: A question might say: ‘An organisation establishes automated backups of its database.’ Is this Service Continuity Management? Yes, but also partly Infrastructure Management. The exam will expect you to recognise that the act of establishing backups is a continuity measure, but maintaining the backup software is an Infrastructure Management task. They want the highest-level correct answer.
What to memorise: - The core definitions of all three practices (purpose statements). - The relationship: Technical Management is the pool of technical skill; Infrastructure and Platform Management is a specific discipline within that pool. - The key outputs of Service Continuity Management: Business Continuity Plan (BCP) and Disaster Recovery Plan (DRP). - That Service Continuity Management involves proactive planning and regular testing of those plans.
Technical Management is the practice that provides the technical expertise and skills to manage the entire IT infrastructure, including hardware, software, and networks.
Infrastructure and Platform Management is a focused practice within Technical Management that specifically looks after the platforms (like servers and databases) where applications run.
Service Continuity Management is a proactive practice that plans for major disasters to ensure critical business services can continue to operate or be restored quickly.
Service Continuity Management is not triggered by a simple server crash (an incident), but by a catastrophic event like a data centre power outage or a cyberattack.
The key outputs of Service Continuity Management are the Business Continuity Plan (BCP) and the Disaster Recovery Plan (DRP), which must be tested regularly.
The three practices work together: Technical Management provides the expertise, Infrastructure and Platform Management provides the stable environment, and Service Continuity Management provides the safety net.
In an exam scenario, always ask: 'Is this a day-to-day technical task (Technical/Infrastructure Management) or a long-term survival plan (Service Continuity)?'
These come up on the exam all the time. Here's how to tell them apart.
Technical Management
The broad practice encompassing all technology management, including networks, security, and end-user devices.
Focuses on the entire technical landscape and the people with the skills to manage it.
Answers the question: 'Who manages the technology?'
Infrastructure and Platform Management
A specific practice within Technical Management focused on the runtime environment for applications.
Focuses on the platform layer: operating systems, databases, middleware, and cloud services.
Answers the question: 'How do we keep the application environment stable and scalable?'
Business Continuity Plan (BCP)
Focuses on the entire business process, including people, processes, and alternative facilities.
Aims to keep the business operating during a crisis, even if technology is down.
Example: 'Staff will use manual paper forms and work from the backup office.'
Disaster Recovery Plan (DRP)
Focuses specifically on restoring IT systems, data, and applications.
Aims to get the technology back to a working state as quickly as possible.
Example: 'Restore the database from the backup server and switch DNS to the secondary site.'
Incident Management
Handles individual, operational events like a single server crash or a user's forgotten password.
Aims to restore normal service operation as quickly as possible for a specific issue.
Reactive process; triggered when something breaks.
Service Continuity Management
Handles catastrophic events that threaten the entire service or business, like a data centre flood.
Aims to ensure the business survives a major disruption, not just fix a specific problem.
Proactive process; involves planning and testing before any disaster occurs.
Technical Management
Focuses on day-to-day operation and maintenance of technology.
Responsible for keeping the infrastructure running and healthy.
Output includes patched systems, updated hardware, and stable networks.
Service Continuity Management
Focuses on planning for technology failures and major disasters.
Responsible for creating and testing the plans for recovery.
Output includes a Business Continuity Plan and a Disaster Recovery Plan.
Mistake
Service Continuity Management is just about IT backup systems.
Correct
It is a holistic business practice that covers people, processes, and facilities, not just IT backups.
People assume 'IT continuity' means 'backup the data', but ITIL defines it as ensuring the entire business service continues, which includes having staff work from a different office or using manual workarounds, not just restoring a tape.
Mistake
Infrastructure and Platform Management is the same as Technical Management.
Correct
Infrastructure and Platform Management is a specialised subset of Technical Management focused on the runtime environment for applications.
Beginners see both involve 'technology' and think they are synonyms. The exam explicitly tests the distinction: Technical Management is the broader engineering function; Infrastructure and Platform Management is the specific role of managing the platforms and infrastructure that support applications.
Mistake
A single server failure always triggers Service Continuity Management.
Correct
A single server failure is a standard incident, handled by Incident Management. Service Continuity Management is for major disasters that threaten the entire service.
ITIL uses a 'severity' scale. Beginners often label every failure a 'disaster'. The correct understanding is that continuity management is reserved for events that meet the definition of a 'disaster', which generally means a significant loss of service capability beyond the scope of normal incident management.
Mistake
Technical Management is only about fixing things when they break.
Correct
Technical Management is proactive, including designing, maintaining, and optimising the infrastructure to prevent failures.
The term 'management' implies ongoing care, not just reactive repair. People confuse it with 'technical support', which is reactive. ITIL emphasises that Technical Management includes planning, testing, and improvement activities to prevent failures and improve performance.
Mistake
A Business Continuity Plan (BCP) and a Disaster Recovery Plan (DRP) are the same document.
Correct
A BCP covers keeping the entire business running during a crisis, while a DRP specifically focuses on recovering the IT systems.
The terms are used interchangeably in casual conversation, but ITIL defines them as distinct. A BCP might involve using paper and pen, while a DRP involves restoring data from a backup server. The exam expects you to know the difference.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Technical Management is the broad practice of managing all technology, including networks, servers, and end-user devices. Infrastructure and Platform Management is a specific practice within that, focusing solely on the environment (platform) where business applications run, like operating systems and databases.
No. Every business of any size that relies on digital services needs it. A small bakery might need a plan if their credit card machine and online order system go down. The scale is different, but the principle of planning for major disruptions is universal.
Patching a server's operating system is a classic Infrastructure and Platform Management task because it directly modifies the platform on which applications depend. It is a subset of Technical Management, but on the exam, the more specific answer is usually correct.
A Business Continuity Plan (BCP) covers everything needed to keep the business operating during a crisis, including manual processes and alternative work locations. A Disaster Recovery Plan (DRP) is a subset of the BCP that focuses specifically on restoring IT systems and data.
ITIL recommends regular testing, typically at least once a year for a full-scale exercise, but more frequent ‘desktop’ or ‘tabletop’ tests (e.g., quarterly) are common. The key is to test the plan before you need it, not during an actual disaster.
It often includes cloud management, especially if the organisation uses cloud providers, but it also covers on-premises data centres. It is the practice of managing whatever platform your applications run on, whether that is a physical server in your building or a virtual machine in the cloud.
You've finished Technical Management and Service Continuity Practices. Continue through the ITIL4F study guide to build a complete picture of the exam.
Done with this chapter?