Everything you need to run a project in RequirementsHub.

RequirementsHub is a structured workspace for business analysis. You and your team capture the moving parts of a project — objectives, stakeholders, requirements, risks, systems, decisions, constraints — and the platform analyzes that knowledge model against BABOK, SAFe, and Lean Six Sigma practice to surface gaps, broken traceability, and missing artifacts.

It's like having a senior Business Analyst sitting beside your team: every finding is grounded in your real entities and points to the exact rule or technique it came from.

1. 01

   Sign in

   Magic-link email — no password to manage.

2. 02

   Create or join a workspace

   Workspaces are how teams collaborate. Owners invite members by email.

3. 03

   Create a project

   Each project has its own objectives, stakeholders, requirements, risks, systems, decisions, and constraints.

4. 04

   Capture or import context

   Add entities directly, or upload documents (BRDs, transcripts, decision logs) to extract them.

5. 05

   Link entities

   Requirements link to objectives they support, risks they mitigate, and systems they touch — with typed relationships.

6. 06

   Run Intelligence

   The analyzer scores readiness, surfaces gap findings, and produces a repair plan.

7. 07

   Coach & generate

   On paid tiers, run Coaching activities and BA Techniques to produce real deliverables.

8. 08

   Export & share

   Download the report, evidence trails, scorecards, and generated artifacts.

Sign in

1. 01

   Go to sign-in

   Open /sign-in and enter your work email.

2. 02

   Click the magic link

   We email you a one-time link. Click it from the same device. No password to remember.

3. 03

   Land on your account

   You'll arrive on /workspaces. If you have no workspaces yet, you'll be prompted to create one.

Create your first workspace

1. 01

   Open Workspaces

   Go to /workspaces.

2. 02

   Click ‘New workspace’

   Give it a name that maps to your team or program — e.g. ‘Payments Modernization’ or ‘Acme Internal BA Team’.

3. 03

   Invite teammates (optional)

   Add member emails now or later. Invitees are automatically added as members the moment you send the invite — they see the workspace as soon as they sign in.

What a workspace is

A workspace is the container for everything your team works on: projects, members, shared decisions, and the audit trail of who did what. Each member sees every project in the workspace.

Invite a member

1. 01

   Open the workspace

   Click your workspace name from /workspaces.

2. 02

   Open ‘Members’

   From the workspace sidebar, choose Members.

3. 03

   Click ‘Invite’ and enter an email

   Pick a role (Owner, Editor, Viewer). Owners can invite and remove others; Editors can change project data; Viewers are read-only.

4. 04

   Send

   We email the invitee a link. They're added as a member immediately — if they already have an account, the workspace shows up the next time they sign in. New users are added on sign-up.

Revoke an invite or remove a member

• Open Members → click the row → ‘Revoke invite’ (pending) or ‘Remove member’ (active).
• Removing a member does not delete anything they created — entities stay with the workspace.

Create a project

1. 01

   Open the workspace

   From /workspaces, choose the workspace.

2. 02

   Click ‘New project’

   Name it after the initiative, not the team — e.g. ‘Payment Portal Modernization’.

3. 03

   Set the stage

   Pick the current BA stage: Discovery, Elicitation, Analysis, Solution Design, or Delivery Readiness. The analyzer adapts its checks to the stage.

What lives inside a project

The project sidebar

Every project has a left-hand sidebar with one tab per entity type plus Activity (audit log) and Intelligence(the analysis report). Switch tabs freely — your work is auto-saved.

Add an objective

1. 01

   Open Objectives

   From the project sidebar.

2. 02

   Click ‘New objective’

   Give it a short title and a measurable outcome. The analyzer flags objectives that have no measure.

3. 03

   Link supporting requirements

   Open the objective → ‘Supported by’ → add requirements. Unlinked objectives surface as orphaned_objective findings.

Add a stakeholder

1. 01

   Open Stakeholders

   From the project sidebar.

2. 02

   Add name, role, and authority

   Authority is used to detect missing decision-makers and to power the stakeholder map.

3. 03

   Tag ‘missing voice’ if needed

   If you know a role should be represented but isn't, add a placeholder stakeholder so the gap is explicit.

Log a decision

• Open Decisions → ‘New decision’.
• Record: what was decided, who decided it, when, and the rationale.
• Link the decision to the requirements, risks, or objectives it affects so traceability is preserved.

Add a requirement

1. 01

   Open Requirements

   From the project sidebar.

2. 02

   Click ‘New requirement’

   Pick a type: Business (BR), Functional (FR), Non-Functional (NFR), Technical (TR), Quality (QR), Shared (SHR), or Compliance.

3. 03

   Write a clear statement

   Use ‘The system shall …’ phrasing. Add acceptance criteria — the analyzer flags requirements without them at Delivery Readiness.

4. 04

   Link supports / risks / systems

   Use the context picker to attach objectives, risks, and systems. Each link captures a typed relationship — see next section.

The Requirement Context Picker

When you link a risk or system to a requirement, the picker now asks you to pick a relationship type. This is what feeds the intelligence report — vague links produce vague findings.

Risk relationship types

System interaction types

Add a risk

• Open Risks → ‘New risk’. Give it an ID like RSK-001 and a short title.
• Set severity (Low / Medium / High / Critical) and likelihood.
• Add a mitigation owner if known. Risks without mitigating requirements are flagged.

Add a system

• Open Systems → ‘New system’. Give it an ID like SYS-001 and a short description (purpose, vendor, status).
• Mark it as in-scope or supporting. Systems with no requirement linking to them surface as a system_coverage finding.

Edit a relationship type

1. 01

   Open the requirement

   From the Requirements tab, click the row.

2. 02

   Open the linked risk or system

   Scroll to the ‘Risks’ or ‘Systems’ section.

3. 03

   Change the type inline

   The dropdown next to each link is editable — pick a new type and it saves immediately.

Run an analysis

1. 01

   Open the project

   From the workspace.

2. 02

   Click ‘Intelligence’ in the sidebar

   Or visit the Intelligence tab directly.

3. 03

   Click ‘Run analysis’

   The analyzer reads every entity and edge in the project and produces findings, scores, and a repair plan in seconds.

4. 04

   Re-run any time

   Free includes one analysis per project. Pro includes unlimited re-runs — useful after adding entities or fixing findings.

What the analyzer checks

• Traceability — every requirement supports an objective; every objective has supporting requirements.
• Coverage — every in-scope system is touched by a requirement; every risk has at least one mitigating requirement.
• Quality — requirements are SMART and have acceptance criteria when the stage demands it.
• Authority — decisions have owners; stakeholders cover the required roles.
• Stage-fit — the artifacts present match what's expected at the project's current stage.

Where findings live

Findings appear on the project's Intelligence tab, grouped by severity (Critical → High → Medium → Low). Each finding shows the rule it came from, the entity it points to, why it matters, and the recommended next action.

Common finding types

The repair plan

The repair plan turns findings into ordered, sized actions grounded in BABOK knowledge areas, SAFe artifacts (Epic, Feature, Story, BDD, PI, DoD), or Lean Six Sigma tools (VOC, SIPOC, CTQ, DMAIC). Each action names a stakeholder, system, objective, or gap from your project — never a generic template.

Project Coaching Workspace

Coaching takes a finding and walks you through resolving it: what to do next, who to involve, and what artifact to produce. Each activity is grounded in BABOK, SAFe, or Lean Six Sigma and scoped to your project's current stage.

BA Techniques

A library of applied techniques — SIPOC, CTQ trees, stakeholder maps, RACI, BDD acceptance criteria, story slicing, traceability matrices, and more. Run any technique against your project and we generate a deliverable pre-filled with your real entities, evidence, and gaps rather than a blank template.

How to run one

1. 01

   Open Intelligence

   From the project sidebar.

2. 02

   Open the side panel

   Choose Coaching or BA Techniques.

3. 03

   Pick an activity

   We suggest the most relevant ones first, based on your current findings.

4. 04

   Generate

   The output appears under the project's Artifacts tab, ready to download or hand off.

• Full report PDF — full formatted report with findings and scorecards.
• Evidence trail — per-finding source citations.
• Scorecards export — per-discipline grades.
• Repair plan export — actions sized for your tracker.
• Generated deliverables — outputs from BA Techniques and Coaching.
• Raw data export (ZIP) — all entities and findings as JSON.

For anything not listed, email hello@requirementshub.ai with your workspace, project name, and the screen you were on.

Free vs. Pro

Free covers workspace foundations — capture requirements, invite collaborators, and run one Intelligence analysis per project. Pro unlocks unlimited projects, unlimited re-analysis, the full Project Coaching Workspace, BA Techniques, and generated deliverables across your whole portfolio.

The two tiers

See current pricing on the Pricing page. Payment is via Stripe; receipts are emailed automatically. For invoices or VAT details, contact hello@requirementshub.ai.

You own everything you create

• Your workspaces, projects, entities, and reports are private to your account and workspace members.
• We do not train models on your content.
• Every action below is self-service — no tickets, no waiting.

Export everything

1. 01

   Open the Data Control Center

   Go to /account/data.

2. 02

   Click ‘Export Everything’

   We package every workspace and project you own — metadata, entities, relationships, findings, scores, and artifacts — into a single ZIP.

3. 03

   Save the ZIP

   Browser downloads requirementshub-export-YYYY-MM-DD.zip. One folder per project, plain JSON files inside.

Delete a single project

1. 01

   Open Data Control Center

   Scroll to ‘Delete a Project’.

2. 02

   Click ‘Delete’ on the project

   A confirmation dialog opens with the exact project name.

3. 03

   Type the project name

   ‘Delete Permanently’ only activates on an exact match.

4. 04

   Confirm

   We remove the project, every entity, every relationship, every finding, and any generated artifact. Irreversible.

Delete your account

1. 01

   Export first (recommended)

   After deletion there is nothing to restore.

2. 02

   Open ‘Delete My Account’

   On /account/data, scroll to the red card.

3. 03

   Type DELETE

   Type DELETE in uppercase. The final button only activates on an exact match.

4. 04

   What gets removed

   Every workspace you own, every project, document, entity, finding, score, generated artifact, and your account profile. Any active subscription is cancelled.

Quick reference

Privacy & security

Visit the Trust Center for our Privacy Policy, Security, Data Handling, Subprocessors, DPA, and Incident Response details.