--- title: "Define project scope" slug: "define-project-scope" tags: ["Task", "RapidValue", "RV"] updated: 2026-03-20T09:55:21Z published: 2026-03-20T17:46:36Z canonical: "docs.staedean.com/define-project-scope" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.staedean.com/llms.txt > Use this file to discover all available pages before exploring further. # Define project scope Define which business processes of the relevant solution are in or out of scope for the implementation project. One of these scenarios is applicable: - No milestones defined Business processes can have these scope indicators: - **Not specified** - No scoping is done for the business process. - **In scope** - Either the business process itself or one of its child business processes is set to In scope. - **Out of scope** - The business process is set to Out of scope. - Milestones defined Business processes can have these scope indicators: - **Not specified** - No scoping is done for the business process. - **[Milestone]** - The business process is in scope for the milestone. - **In scope** - No scoping is done for the business process itself. One of its child business processes is in scope for a milestone. - **Out of scope** - The business process is set to Out of scope. ### Steps 1. Click **Business process implementation**. 2. Click **Define scope**. 3. In the tree, select 'a node'. 4. Click **In scope** to open the drop dialog. 5. In the list, find and select the desired record. 6. Click **OK**. 7. Close the page. > [!NOTE] > Notes > > Scope changes and related notes are stored in the change history of each business process. ## Related - [Assess scope and effort](/assess-scope-and-effort.md) - [Filter business process hierarchy](/filter-business-process-hierarchy.md)