# Scoping requirements, assumptions, risks and constraints

*Omnistudio Consultant Study Guide · Omnistudio Fundamentals · Last updated October 27, 2026 · https://www.certifyforce.com/study-guide/omnistudio-consultant/omnistudio-fundamentals/scoping-requirements-assumptions-risks-and-constraints*

How a consultant turns discovery notes into an Omnistudio design: sorting statements into requirements, assumptions, risks and constraints, mapping each requirement to a component, flagging governor-limit and runtime constraints early, and outlining the plan end to end.

- Certification: Salesforce Omnistudio Consultant
- Exam section: Omnistudio Fundamentals
- Study guide: https://www.certifyforce.com/study-guide/omnistudio-consultant

**Official exam objective:**

> Determine a projects needs by evaluating a customer's requirements, assumptions, risks, and constraints.

## What the exam expects

- Sort a discovery statement into a requirement, an assumption, a risk or a constraint, and say what to do with each.
- Map each requirement to the Omnistudio component that meets it, and spot requirements no standard capability supports.
- Challenge assumptions that a declarative design escapes governor limits or performance testing.
- Surface runtime and designer constraints at discovery (Streaming API data sources, SLDS 2 theme, Omni Analytics, OmniOut).
- Turn the design into an implementation plan that outlines the whole process before building.
- Key terms: **requirement** (what the solution must do); **assumption** (something the plan treats as true without proof); **risk** (an uncertain event that could hurt the project); **constraint** (a fixed limit the design must work within). These four definitions are the exam's working vocabulary (Exam convention); no Salesforce page defines them.

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Integration Procedure fit | No user interaction during execution; one server call; can cache | [Omnistudio Integration Procedures](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_integration_procedures_48334.htm&language=en_US&type=5) |
| Too many data calls in one IP | Risks SOQL limit errors; keep a small group of related functions per IP | [Integration Procedure Best Practices](https://help.salesforce.com/s/articleView?id=xcloud.os_integration_procedure_best_practices_54721.htm&language=en_US&type=5) |
| Async IP from an Omniscript | Continues on Next; stops if the user navigates away from the Omniscript | [Integration Procedure Best Practices](https://help.salesforce.com/s/articleView?id=xcloud.os_integration_procedure_best_practices_54721.htm&language=en_US&type=5) |
| Omniscript size | Try to limit a single Omniscript to a maximum of 750 elements | [Omniscript Best Practices](https://help.salesforce.com/s/articleView?id=sf.os_omniscript_best_practices_8368.htm&language=en_US&type=5) |
| Governor limits | Apply to Omnistudio; debug logs capture usage for Omniscripts, IPs and Data Mappers | [Omniscript Best Practices](https://help.salesforce.com/s/articleView?id=sf.os_omniscript_best_practices_8368.htm&language=en_US&type=5) |
| Streaming API data source | Only with the designer on a managed package | [Set Up a Data Source on a Flexcard](https://help.salesforce.com/s/articleView?id=xcloud.os_configure_a_data_source_on_a_flexcard_35864.htm&language=en_US&type=5) |
| Analytics on Standard Runtime | Omni Analytics works with Google Analytics 4; no Tracking Service | [Supported Features](https://help.salesforce.com/s/articleView?id=sf.os_omnistudio_and_omnistudio_for_vlocity_products_and_features_support.htm&language=en_US&type=5) |
| SLDS 2 | Omnistudio SLDS 2 theme aligns with the org's SLDS and SLDS 2 theme | [Omnistudio Settings](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_settings.htm&language=en_US&type=5) |
| Turbo Extract | No formulas, custom JSON, default values or transformations | [Omnistudio Data Mappers](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_dataraptors_45587.htm&language=en_US) |

## Check yourself

- Why is "the async Integration Procedure always finishes" a risk rather than a safe assumption?
- When should a requirement map to an Integration Procedure?
- What element count should a single Omniscript stay within?
- Why is one Integration Procedure for an entire application a risk?
- Which analytics option should a Standard Runtime design name for Google Analytics 4?

## Sources

- [Omnistudio Integration Procedures](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_integration_procedures_48334.htm&language=en_US&type=5)
- [Integration Procedure Best Practices](https://help.salesforce.com/s/articleView?id=xcloud.os_integration_procedure_best_practices_54721.htm&language=en_US&type=5)
- [Omniscript Best Practices](https://help.salesforce.com/s/articleView?id=sf.os_omniscript_best_practices_8368.htm&language=en_US&type=5)
- [Supported Features in Omnistudio and Omnistudio for Managed Packages](https://help.salesforce.com/s/articleView?id=sf.os_omnistudio_and_omnistudio_for_vlocity_products_and_features_support.htm&language=en_US&type=5)
- [Omnistudio Settings](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_settings.htm&language=en_US&type=5)
- [Set Up a Data Source on a Flexcard](https://help.salesforce.com/s/articleView?id=xcloud.os_configure_a_data_source_on_a_flexcard_35864.htm&language=en_US&type=5)
- [Omnistudio Data Mappers](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_dataraptors_45587.htm&language=en_US)
- [Discover the Omnistudio Digital Suite (Trailhead)](https://trailhead.salesforce.com/content/learn/modules/omnistudio-basics/discover-the-omnistudio-digital-suite)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 10 linked practice questions, and unlimited timed mock exams are included with the Omnistudio Consultant pack (USD $19): https://www.certifyforce.com/practice-exams