Engagements. Create and select a client engagement. Each records the client, target NetSuite release, edition(s), market segment, region, vertical, phase, and status.
Team workspaces. You always work in exactly one workspace, either one of your teams or Just me. New BRDs belong to whichever workspace is active.
Requirements. Record each requirement with an ID, title, description, priority, source, effort, and status.
Catalog mapping. Map a requirement to one or more Blueprint catalog lines, with a coverage note and optional coverage percentage.
Catalog browser. Search the Blueprint catalog and filter by process area, module, edition, and region. Use the needs scope filter to find lines missing edition, region, or license information, and the scope editor to fill them in.
Automatic fit-gap. Each requirement gets a disposition based on its mapped lines, the engagement's edition and region, and its target release. A Fit-Gap Dashboard summarizes the results per engagement.
Threaded comments. Discuss a requirement in threads, with replies, emoji reactions, and file attachments.
AI release-note candidates. Review AI-proposed catalog updates drawn from release notes, and promote the ones you approve into the catalog.