Getting Started

Requio is a modern replacement for the traditional Business Requirements Document (BRD). Instead of a Word document that gets emailed around, edited in parallel by different people, and goes stale the moment a decision changes, Requio gives your organisation one governed, AI-assisted system for defining, reviewing, and approving requirements — the Digital Requirements Pack, or DRP.

The problem Requio exists to solve is a familiar one: requirements gathered informally, spread across documents and email threads, discovered to be incomplete or contradictory only after delivery has already started. That gap between what was actually agreed and what a delivery team builds from is where rework, scope drift, and missed deadlines come from.

• A single source of truth — every DRP is built from the same set of structured modules (Business Objectives, Solution Scope, Requirements, RAID Log, and more), so nothing is missing and every pack looks and reads consistently, project to project and analyst to analyst.
• AI assistance at every stage — from drafting module content grounded in your own project and knowledge base, to surfacing gaps, ambiguity, and conflicts before they reach delivery, to generating diagrams and traceability automatically instead of by hand.
• Built-in governance — formal review and approval workflows, full version history, an audit trail, and a Reference Data library that keeps terminology and standards consistent across every project in the workspace.
• A finished, professional output — once a DRP is complete, it generates as a fully formatted, branded .docx document in one click, ready to share securely with stakeholders or delivery teams who don't even need a Requio account to view it.

The result is requirements work that creates real, shared understanding early — so what a delivery team builds is what the business actually agreed to, not a guess reconstructed from a stale document three sprints too late.

Every user in a workspace holds one or more roles. Roles control what you can see and do, and drive what your dashboard shows you.

• Workspace Admin — looks after the workspace itself: settings, billing, which modules are bought and enabled, and managing users. Not a project job — a Workspace Admin does not appear on project teams.
• Lead Analyst — runs the work. Creates and configures projects and DRPs, writes content, decides who reviews and approves, and manages users.
• Analyst — creates and edits DRPs, modules and requirements within the projects they are assigned to. Cannot configure a project — with one deliberate exception: Analysts can set the AI knowledgebase terminology, because the people writing the DRPs are the ones who know the right terms.
• Reviewer — reviews DRP modules (the Requirements module included) and generated DRP versions, and leaves comments, without authoring or approval rights.
• Approver — approves or rejects DRP modules and generated DRP versions, giving formal sign-off. Requirements are signed off together, when the Requirements module is approved, not one by one.

A person can hold more than one role at once — for example, a Lead Analyst who is also an Approver. When a workspace is first created its founding user holds both Workspace Admin and Lead Analyst, so a new workspace works out of the box; the two can be split across different people later.

The dashboard is role-specific — both the stat tiles at the top and the quick-action cards below them change based on your role:

• Lead Analyst — Total/Assigned Projects, Pending Reviews, Needs an approver, Items Approved (modules that have been signed off), plus Archived Projects and Archived DRPs — each opens a list you can restore from. Quick actions cover Projects, DRPs, Reference Data, External Documents Triage, Audit, and Users.
• Analyst — Assigned Projects, My DRPs, My Drafts and Pending Reviews. Quick actions cover Projects, DRPs, the Audit Log, the Requirements module, and Reference Data.
• Reviewer — Pending Reviews and Reviewed Today, both counted just for you. One quick action opens your review queue directly.
• Approver — Assigned/Total Projects, Pending Approvals, and Reviewed Today. Quick actions cover Approvals, Projects, and DRP Requirements.
• Workspace Admin (and nothing else) — no project tiles, because there is no project work to show. Quick actions go straight to Workspace Settings, Users and the Audit Log.

Your dashboard follows one of your roles, so somebody who holds several sees the dashboard for one of them. A Reviewer or Approver dashboard still shows an Audit Log card if another of your roles lets you open the Audit Log — for example, an Approver who is also an Analyst.

"Needs an approver" counts reviews that have lost their approver — usually because that person was taken off the project, lost the Approver role, or was deactivated. The review is not thrown away: it waits, with every sign-off given so far, until somebody names a new approver on that section or DRP.

Lead Analysts and Analysts see a "Getting started" card at the top of the dashboard. It lists the four steps from an empty workspace to a finished pack, and ticks each one off as it really happens:

1. 1Create and configure your project — set up your team, choose the modules you need, and decide how work gets reviewed.
2. 2Create your first DRP — a pack lives inside a project, and a project can have several.
3. 3Complete DRP modules — work through each module and finish it. Solution Scope and Business Objectives are the usual place to start.
4. 4Generate your complete DRP — once every required module is finished.

"Show me" on the next step opens a short guided tour on the real screen, pointing at each thing to press in turn — for example, it takes you to Projects, shows you where a new project starts, then walks you through naming it and giving it a code. "Take me there" skips the tour and goes straight to the right page. A step that is somebody else's job says who does it — "A Lead Analyst sets this up" — rather than offering a button you could not use.

"Hide" folds the card away and "Show" brings it back; your choice is remembered. Reviewers, Approvers and Workspace Admins see a short note in its place instead of the checklist — for example, a Reviewer with nothing yet is told that work reaches them by email and in their Review queue once an Analyst sends a module for review.

1. 1A Lead Analyst creates a project — the container that a DRP and its requirements live under.
2. 2An Analyst (or the Lead Analyst) creates a DRP inside the project and works through its modules, drafting content with AI assistance.
3. 3Requirements are drafted and linked into the DRP. The Requirements module, like any other module that needs sign-off, is reviewed by a Reviewer and approved by an Approver as a whole.
4. 4Once every required module is finished — and approved, where it needs sign-off — the DRP is generated as a polished, fully formatted .docx version. That version then goes through its own review and is approved by the approver named on the DRP.
5. 5The finished DRP can be shared with stakeholders or delivery teams via a secure, passphrase-protected link — no Requio login required for the recipient.

Signing in requires three things: your workspace code, your email address, and your password. The workspace code identifies which workspace to check your email and password against — the same email can belong to more than one workspace, each with its own separate account.

Forgotten your workspace code or your password? Both have a self-service recovery link on the sign-in page. Forgot workspace code sends an email listing every workspace your email address belongs to. Forgot password needs your workspace code plus your email, and emails you a reset link. Forgotten your email address itself? There's no way to look that up — contact Support.

A brand new account has to confirm its email address before it can sign in. If you try first, the sign-in page says the address is not verified and offers "Resend verification email". If the confirmation never arrived because the address was mistyped when the workspace was created — say, jane@acme.co instead of jane@acme.com — choose "Typed the wrong address when you signed up?", enter the address you meant, and press "Send confirmation". It uses the workspace code, address and password you typed, and nothing changes until you open the email sent to the corrected address. This only works before an account has been verified.