Build (Lifecycle Activity) Explained (ITIL® 5)
Preparing for the ITIL® 5 Foundation exam? Build is the fourth activity in the ITIL® Product and Service Lifecycle, and it's the point where a design actually becomes something real. This guide explains what it covers and where it ends.
Quick Answer
Build is the lifecycle activity focused on coding, configuring, assembling, and testing the components acquired for a solution — turning a design and its sourced resources into a working product or service component. It comes after Acquire has obtained what's needed, and before Transition moves the finished work into live use.
What Is the Build Activity?
Build is the construction phase of the lifecycle. It's where the people, technology, and other components obtained during Acquire actually get put together — writing code, configuring systems, assembling components, and testing that all of it works as intended.
Build isn't finished the moment something technically runs. Testing is part of Build itself, not a separate afterthought — confirming the assembled solution actually behaves the way Design specified, before it's ready to move toward live use.
Where Build Ends and Transition Begins
Build produces a solution that has been assembled and tested, typically in a development or test environment. Transition is the separate activity that takes that finished, tested work and moves it into live use. The distinction matters: something can be "built and tested" without yet being "transitioned into production" — those are two different activities with two different sets of risks.
Real-World Example
Once the SMS gateway and developer are in place from Acquire, Build is where the actual notification feature gets coded: the trigger logic, the integration with the SMS gateway, and the in-app display. The team writes automated tests to confirm notifications fire correctly and don't duplicate or drop messages.
Only once that code has been built and has passed testing in a development environment does the work move on to Transition, where it's deployed into the live production system customers actually use.
Why This Matters
Understanding Build matters because:
- It clarifies that testing belongs inside Build, not as a separate bolt-on step
- It draws a clear line between "assembled and tested" and "actually live," which Transition handles separately
- It's where design and sourcing decisions get proven out — or exposed as flawed — before real customers are affected
Common Exam Mistakes
The most common mistake is assuming Build ends the moment code is written, without testing. In the Product and Service Lifecycle, testing the assembled components is part of the Build activity itself.
A second mistake is confusing Build with Transition. Build produces a working, tested solution in a development or test environment. Transition is the separate activity that moves that finished work into live use — they are not the same step.
Memory Trick
Think:
Acquire gets the pieces.
Build puts them together and proves they work.
Transition moves the proven thing into the real world.
If you're coding, configuring, assembling, or testing, you're in Build.
Key Takeaways
- Build is the lifecycle activity focused on coding, configuring, assembling, and testing the components obtained during Acquire.
- Testing is part of Build itself, not a separate step that happens afterward.
- Build sits between Acquire (obtaining resources) and Transition (moving finished work into live use).
- Something can be fully built and tested without yet being transitioned into production — those are distinct activities.
- This activity is part of the eight-activity ITIL® Product and Service Lifecycle, a frequently tested area of the ITIL® 5 Foundation syllabus.
One Practice Question
Which statement best describes the Build lifecycle activity?
- It is the activity where a solution is moved into live production use.
- It is the activity focused on coding, configuring, assembling, and testing the components needed for a solution.
- It is the activity where suppliers and technology are obtained.
- It only refers to writing code, and does not include testing.
Show Answer
Correct Answer: B
Build covers coding, configuring, assembling, and testing the components sourced during Acquire, producing a working, tested solution ready to move into Transition.
Frequently Asked Questions
Does testing happen during Build, or is it a separate activity?
Testing happens within Build itself. Build covers coding, configuring, assembling, and testing the components of a solution, all as part of the same activity.
How is Build different from Transition?
Build produces a solution that has been assembled and tested, typically in a development or test environment. Transition is the separate activity that moves that finished, tested work into live use.
Can something be "built" without being live yet?
Yes. A solution can be fully built and tested in a development environment without yet being transitioned into production — those are two distinct activities with different risks.
Is this topic tested on the ITIL® 5 Foundation exam?
Yes. The eight lifecycle activities, including Build, are part of the Product and Service Lifecycle, a significant and frequently tested area of the ITIL® 5 Foundation syllabus.
Ready to Test Yourself?
Now that you understand what Build covers, the next step is seeing how it connects to Transition and the rest of the lifecycle. Take our free diagnostic quiz at PassTheFoundation.com to test yourself, or continue exploring the other ITIL® 5 lifecycle activity guides.