The scope register, called the Requirements registry in the app, is the project's agreed baseline: what is in scope, what is out, and what you are assuming. It sits under the Scope entry of the project menu and is part of the Professional plan.
What it is for
- Holding the scope baseline in one list, by domain and workstream.
- Recording exclusions, assumptions, constraints and dependencies next to the requirements, so nobody has to dig through the statement of work.
- Seeing at a glance how much of the baseline is approved, and how many change requests have been raised against it.
How to add a requirement
- Open Scope
In the project, select Scope. The first tab is Scope.
- Start one
Select Create requirement. The form is "Add to scope register".
- Describe it
Type the Title and the Detail (what is included, excluded or assumed).
- Classify it
Choose the Category: In scope, Out of scope, Assumption, Constraint or Dependency. Set the Priority (Must have, Should have, Nice to have), the Status, the Workstream and the Module.
- Mark its origin
Leave Part of original baseline (not from a change request) ticked for baseline scope. Untick it for scope that came from a change.
- Save
Select Add scope item.
Reading the register
- The cards at the top show Total scope items (with the share approved), Functional, Non-functional and Pending approval.
- The Domains list on the left filters by area: Technical architecture, Security & compliance, Financial operations, Logistics & supply, People and HR, Integration points and Cross-functional. Each shows a count.
- Scope health gives the share of the baseline that is approved and a line such as "2 approved change requests, 1 awaiting a decision".
- Three views sit above the list: Primary baseline, Change requests and Archived. Search by title or ID with "Search requirements...".
- The list shows 8 items at a time. Select Load 8 more to see the next ones.
Statuses
Counts as approved
- Approved: agreed and part of the baseline
Waiting or set aside
- Pending review: waiting for a decision
- Deferred: held for later
- Removed: taken out of scope, also listed under Archived
Good to know
- Only In scope items count in the baseline, the domains and the totals. Out of scope items, assumptions, constraints and dependencies are listed under Archived, with removed items.
- Functional and non-functional are worked out from the workstream. Technical and cross-functional workstreams, such as Basis, Security, Integration, Data migration, Testing and Cutover, count as non-functional. Items with no workstream count as non-functional.
- Pending approval counts in-scope items that are Pending review or Deferred.
- Raise changes to the baseline as change requests on the Change requests view with Add CR. See Change requests. The budget impact of approved change requests is added to the project's budget at completion (BAC).
- If you cannot edit scope, the form opens read only with "You have read-only access to this scope item."
- Custom objects to build belong in the WRICEF register, on the next tab.
Who can do this
Admins and project managers can add and edit scope items. Admins, project managers, functional leads, technical leads and change managers can raise change requests. Everyone on the project can view the register.