IAI SP1
More study resources
Cheat sheet
Keep the key ideas within reach.
ExploreKey terms
Get comfortable with the vocabulary.
ExploreStudy plan
Give each week a clear focus.
ExploreCommon mistakes
Understand the traps and how to avoid them.
ExploreCase studies
Put your knowledge to work in context.
ExploreExam-day guide
Prepare for the day ahead.
ExploreAbout this exam
SP1 (Systems Practice 1) is a certification offered by the International Association for Innovation (IAI) for people who apply systems engineering and systems thinking in practice, whether as systems engineers, requirements analysts, architects, integrators or technical leads moving into a systems role. It tests judgement as much as recall: how you frame a problem, bound a system, engage stakeholders, turn needs into verifiable requirements, shape a conceptual design, evaluate trade-offs, and carry a system through integration, verification, validation and lifecycle governance. The eight published domains are weighted unevenly, with foundations, systems thinking, requirements, and architecture carrying the most weight, so plan your study proportionally rather than reading everything once. Preparation works best in layers: first build a shared vocabulary and a mental model of the whole lifecycle, then practise applying it to a realistic system you know well, then work through scenario-style multiple-choice questions where two answers look plausible and only one respects the systems context. Expect the questions to describe situations rather than ask for definitions, and expect to justify choices under constraints. The official body publishes current administrative details; check its site before booking.
What you'll study
About IAI SP1 preparation
What is the SP1 exam format?
It is delivered as multiple-choice questions covering the eight published domains. The official body publishes the current item count, delivery method and any scheduling details, so confirm these on its website before you book rather than relying on forum posts, which drift out of date.
How hard is SP1?
The difficulty is conceptual rather than mathematical. Most candidates find the vocabulary manageable but the scenario questions demanding, because several options are defensible in isolation and only one fits the stated system boundary, lifecycle phase or stakeholder context. Practising contextual reasoning matters more than memorising lists.
How much time should I plan for preparation?
There is no published preparation requirement. A practical approach is to budget study time proportional to domain weight: foundations, systems thinking, requirements and architecture together account for roughly sixty percent of the syllabus, so they deserve the largest share of your schedule, with the remaining domains covered at working depth.
What happens if I fail, and can I retake?
Retake rules, waiting periods and any fees are set by IAI and change over time. The official website is the only reliable source for the current policy. Do not assume a free immediate retake; check the terms before your first attempt so a failure does not disrupt your plans.
In what order should I study the domains?
Start with foundations and systems thinking, because they supply the vocabulary used everywhere else. Then move to stakeholder engagement and requirements, followed by architecture and modelling, where trade-off reasoning depends on good requirements. Finish with integration, verification and validation, then lifecycle governance, which ties the earlier material together.
Do I need to memorise standards and frameworks?
You need working familiarity with lifecycle concepts, requirement quality attributes, verification versus validation, and traceability, not clause-by-clause recall. Questions test whether you can apply a concept to a described situation. If a question hinges on a specific standard's wording, treat that as a signal to check the official syllabus.
What are common failure modes?
Candidates often answer from habit rather than from the scenario: choosing the most rigorous option when the context calls for a proportionate one, confusing verification with validation, or ignoring the stated stakeholder or boundary. Read the whole stem, identify the phase and constraint, then eliminate options that violate them.
How are the domains weighted?
The published weights are 15 percent each for foundations, systems thinking, requirements and architecture; 10 percent each for stakeholder engagement, modelling and trade-offs, integration and verification, and lifecycle governance. Use these proportions to allocate revision time and to decide which weak areas to fix first.
Is SP1 recognised by employers?
Recognition varies by sector and region. Treat SP1 as evidence of structured systems practice knowledge that complements demonstrated project experience, and check job advertisements in your target market. This page is independent study material and is not affiliated with or endorsed by IAI.