1. Choose your workspace
Use the active-team switcher to pick a workspace.
- A team: you see only that team's BRDs.
- Just me: you see only the BRDs you created personally.
There is no combined "all my teams" view. Whatever you create is stamped with the workspace you are in. Under Just me, new BRDs are personal and visible only to you.
2. Create an engagement
- Open the Engagements view and create a new engagement.
- Enter the client, target release, edition(s), market segment, region, vertical, phase, and status.
- Save it, then select it to work on its requirements.
The edition, region, and target release matter because they drive the fit-gap results later.
3. Add requirements
- With an engagement selected, open Requirements.
- Add a requirement and fill in its ID, title, description, priority, source, effort, and status.
- Save it. The Disposition field is filled in by the app, so you can't edit it.
Deleting a requirement deactivates it rather than permanently removing it.
4. Map requirements to the catalog
- Open a requirement's line-mapping drawer.
- Find the Blueprint capabilities that match, and map one or more to the requirement.
- Add a coverage note (for example, "covers 80%, gap on multi-currency") and, optionally, a coverage percentage.
Once you save a mapping, the app derives its disposition and updates the requirement's overall disposition.
5. Read the fit-gap results
Each mapped line is compared with the engagement's edition, region, and target release. The requirement shows the most severe outcome across its lines.
| Disposition |
Meaning |
| Standard |
In the client's edition, license included, and available by the target release. |
| Standard - additional license/cost |
In scope, but the license is optional, so there may be added cost. |
| Edition gap |
The capability is outside the engagement's edition or region. |
| Version gap |
The capability isn't available until a release later than the client's target. |
| Customization |
No catalog line is mapped to the requirement. |
A line with no edition or region restriction counts as in scope everywhere. Open the Fit-Gap Dashboard for a rollup across the selected engagement.
6. Discuss a requirement
- Open a saved requirement.
- In the discussion thread, add a comment. You can attach files such as documentation or flow diagrams.
- Reply to a comment to continue a thread, or react to a comment with an emoji (click again to remove your reaction).
- Deleting a comment also removes its replies.
Comment threads appear only on requirements that have already been saved.
7. Browse and maintain the catalog
- Open the Catalog view.
- Search by text, or filter by process area, module, edition, and region. Results are paged.
- Use the needs scope filter to find lines that lack edition, region, or license data, then use the scope editor to complete them.
8. Review AI-proposed catalog updates
AI-extracted proposals appear in the Candidates view. Each one shows its proposed action, a confidence score, a source citation, and a short excerpt from the release notes.
- Open Candidates and review each proposal against its citation and excerpt.
- Promote the ones you approve to the catalog.
- Set Available From records the release in which an existing catalog line first becomes available. It needs a matched catalog line.
- Create New Line adds a new catalog line from the proposed details.
- Promoted candidates are marked Promoted, with the reviewer recorded.