The Scenario Builder describes a role in a real situation, shapes its flow and evidence, and is honest about every assumption it makes along the way.
A Role-based Scenario captures who a person is, the circumstances that prompt them to act, and what they must produce or achieve: for example, a chartered quantity surveyor on a BIM-enabled project who must derive model-based quantities to give reliable cost certainty. The Builder turns that idea into a structured, reviewable scenario with a record of every assumption behind it, a flow of stages and Action Statements, the evidence for each, and a report you can publish.
The Builder runs the full width of the window in three columns: the scenario's sections on the left, the section you are working on in the middle, and the assistant on the right. Below 1024 pixels the columns stack and the sections become a menu.
The header names the scenario, its status in words and whether it is saved. Its one main button is the next step, such as "Next: check assumptions", which opens that step's section; when a change to the brief has made the flow out of date it reads "Next: regenerate the flow" and saves and regenerates it, and once every step is done it publishes or shares the report. Under it, the progress track shows the six steps (Describe, Assumptions, Flow, Evidence, Guidance, Share): green with a tick when done, amber with what waits for you ("1 to check"), or outlined with what it waits for ("after the report"). Each step opens its section, and the one you are looking at is underlined. Making a target pathway-ready, sending for verification and publishing the report are in More and in their sections. On a narrow screen one button names what needs you and opens the steps.
The sections, in the order you meet them:

Tell the BIMei Assistant about the role in your own words; it drafts the structured scenario and asks one question at a time. Recommended for most people.
Fill in the Story section's form directly, field by field, when you are translating an existing written brief.
To continue a saved scenario, open one you can access from More, then Load. Downloads require sign-in.
Start in the Scenario Builder chat and review the extracted scenario before continuing. Drafting is public; chat actions, downloads and saves show their own sign-in requirements. Saving to an organisation also requires membership, permission and feature availability.
The Story section opens with the scenario in one sentence, then its details in a two-column form: the basics first, and the rest behind Show all fields.
What success looks like holds one outcome, up to ten acceptance criteria of up to 140 characters each, a horizon and what is out of scope. A criterion box appears once the one before it is filled.
When the scenario has a story in your words, it follows the form. Each highlight in it is a detail traced to your words: select one to check, confirm or edit it.
Assumptions to check lists what is still needed and what the assistant assumed, each with Review, Confirm or a suggested value.
Scenario fields carry recorded provenance states. Use them to review supplied, inferred, ambiguous and missing details:
In the scenario sentence, a bracketed phrase is inferred, ambiguous or otherwise unresolved: hover it for the status. When nothing has been flagged, the Builder says there are no recorded assumptions and that the scenario is not yet verified, rather than claiming it is correct.
Confirm accepts an inferred or ambiguous value you can vouch for: one click, recorded with your name and the time, with the earlier status kept for audit. Review opens the field so you can supply or correct the value; missing items only offer Review, because there is nothing to confirm.
The assistant sits beside your work in one of two positions. Docked, it has its own column that never covers the page, and you can drag its edge to make it wider or narrower. Floating, it is a window you move by its header and resize from its corner, also with the keyboard. Close it, and the Assistant button in the header brings it back where it was.
When the assistant proposes a change, it arrives as a card: what it would set, the value before and after, and why. Nothing changes until you accept it.
When it proposes several changes at once, they come as a batch: tick I have reviewed these, then Accept all. Accept all without the tick applies nothing. You can still accept or reject each card on its own.
Every accepted proposal can be undone while the scenario still holds the accepted value, and a field changed by a proposal says so beside its label. Once you change that field yourself, Undo steps aside so it never overwrites your work.
Once a scenario is saved, Generate AFD turns it into real draft entities: a Role, its headline Action Statement and a staged flow. Before anything is created, the assistant proposes Information Uses and further statements, each with a rationale, a confidence and a source citation where the corpus supports one. You choose what to include.
A generated flow opens as a canvas page: the stages and their statements in an outline on the left, the diagram in the middle, and an inspector on the right for the part you select. Edit a stage's text, order, lane or decision points on the canvas, then Save flow: the diagram, the stages and the report are composed again together. While the canvas is in view the inspector takes the assistant's column; open the assistant from the header to swap them, or float it.
Select a statement in the outline to review it in the inspector: its wording for this scenario and the stages and Information Uses it is linked to. With nothing selected, the inspector shows the flow: its statements to accept as one reviewed batch, and what was generated.
The result is labelled Generated on the maturity ladder: an indicative starting point. After editing the scenario, regenerate its draft Role and flow before sending them for verification.

The Evidence section shows where each element of the scenario stands on source evidence. Filter it by what needs your review or blocks the report; approve, challenge or waive each link; or select several checked citations and approve them together after a confirmation. Requests for missing sources go to the curators.
Practical guidance holds a brief for each stage (its purpose, inputs, outputs and completion criteria) and recommended Learning Units. Save a draft, or mark it reviewed, to include it in the report.
The Readiness section and the Report track the same conditions: they must be met before the report can call itself client-ready, and every condition not yet met has a Fix that opens the section, and the field, where it is fixed.
Where an organisation uses RPF Wayfinder, a resolved scenario is also a target that practitioners' pathways are drawn from. Its section sets each statement's required levels, places each statement on the stages of the flow, and links each stage to the success criteria it advances. The assistant proposes placements, levels and criteria links in batches; each batch needs your tick before Accept all, and each can be undone.
An organisation admin can freeze a saved scenario's structure. The Builder then says who froze it, when and why, and the structural fields, regenerating, and editing the flow are switched off, each with that reason. Wording, documents, practical guidance and the pathway-ready work stay editable.
For scenarios set in Ireland, the Builder checks the scenario's facts against the official CWMF public-sector BIM adoption timeline, the phased 12-milestone schedule. It checks, in order:
Every finding carries a reason, its effective date and the official source: CWMF: Public Sector BIM Adoption Timeline →
Draft and refine without an account. Sign in to download or print. Saving to an organisation workspace requires membership, permission and scenarios enabled. Opening, renaming and deleting saved scenarios depend on access, permissions and the scenario's state.
A scenario can be published as a public report or shared through a private link, from the Report and share section. Check the intended audience and version before sending either link.
Publishing, re-publishing and revoking an organisation's report needs the organisation publish permission: owner, admin or content editor. If you cannot send a scenario for verification, publishing its report is the header's next step once the scenario is generated.
The Builder tells you what it cannot do. The current list: