Build an assessment template
Author the questionnaire itself: the questions, their routing, and the metadata that makes them scoreable.
Who this is for
Anyone who writes the content of an assessment. You need the
survey_templates.create and survey_templates.modify permissions; the Account
Administration policy carries them, and the Campaign Management policy carries only
survey_templates.view, because authoring one is account configuration rather
than campaign operations.
Where a template sits in the work
A template is the questionnaire. An assessment is a template attached to a campaign with a deployment key, a status and a window. The two are separate on purpose: one template can serve several campaigns, and a campaign can carry several assessments.
This page covers the template. Attaching one to a campaign, previewing it and publishing it is Publish and preview an assessment; moving one between accounts as a file is Import and export templates as JSON.
Open the library
Assessments in the sidebar, at /<accountId>/dashboard/assessments. The page
is headed Assessment templates.
The table lists the account's own templates plus any global templates that have been distributed to the account. Filter by Scope (All scopes / Local / Global) and Lifecycle status (All statuses / Draft / Active / Archived), or search by name. Each row shows the scope, status, version, how many statement bindings and custom fields it carries, and when it was created and last touched.
Row actions, left to right: edit (a pencil), Clone template, Export JSON, Replace from file…, Lock template, Delete template. The last three are hidden on a global row, because a tenant cannot change one.
To start something new, choose New template in the page header or, from an empty library, Build your first template.
The builder
Both New template and the pencil open the Assessment Template Builder at
/<accountId>/dashboard/assessments/build (or …/build/<id>).
The Studio puts the template name, Check, downloads and Save Template above six workspaces:
| Workspace | Use it for |
|---|---|
| Questions | Add and arrange questions in the SurveyJS designer; edit their properties. Open Item library to reuse an existing item, Action Statements to link sources, or AI Assistant for reviewable suggestions. |
| Preview | Try the questionnaire and its branching without saving responses. |
| Logic | Set conditions and routing between questions and pages. |
| Traceability | See live coverage: how many questions score, why others were dropped, the Domain x Tier heatmap, and which Action Statements each question measures. |
| JSON | Edit a staged copy of the questionnaire source, then apply it to the designer. |
| Details | Set the description, lifecycle, version, team fields and template-level statement bindings. |
The header shows lifecycle, version, question count and whether changes are unsaved. Autosave is off: applying JSON, accepting an AI suggestion or editing a field changes your working copy only. Choose Save Template to store it.
The Studio and SurveyJS controls follow the app's light/dark theme and English or French interface language. This does not translate question content. Use the translation workspace for that.
Details and team fields
Change the template name in the header. In Details:
- Description explains what the questionnaire is for.
- Lifecycle status is Draft, Active or Archived. Active means ready for use; it does not publish an assessment.
- Version is a positive whole number maintained by the author. It cannot be decreased on an existing template, and saving does not automatically increase it or replace an active assessment's pinned version.
- Team fields are administrative metadata, not respondent questions. Add a label, key, type and required flag; choice fields also take one option per line. Supported types are Text, Number, Date, Single choice, Multiple choice and Yes / No.
- Bound Action Statements lists governed template-level bindings. Saving
derives them: every statement a question names as its primary
(
asrStatement) is bound, as is one a matrix row or a choice names (each action in SS-ADM's plan is a choice naming its statement), plus any bound directly. A primary is marked Question primary and cannot be unbound while a question still names it. Clearing a primary does not unbind it, so remove it here if needed.
Check before saving
Check reports errors and warnings with their location in the source. It checks question names and structure, expression syntax, and known metadata formats. Duplicate question names, malformed expressions and an empty questionnaire are examples of errors. Unknown question extensions, scales and unresolved expression references are warnings because they may belong to a custom or legacy questionnaire. Checks also warn about unknown BIMMaS scoring labels and choice values that do not match the declared scale.
A Draft can retain incomplete content. Saving a questionnaire as Active requires its authoring errors to be resolved. Warnings do not block saving, and a clean check is not proof that routing, scoring, uploads or a campaign journey work. Check every branch in Preview and use a test assessment before publication.
Edit JSON safely
The JSON workspace is a staged editor with Format, line wrapping, copy and download controls. Apply JSON copies valid source into the designer; it does not save the template. The Studio refuses an application that would drop unsupported elements during the editor's load/serialization step.
While JSON edits are unapplied, saving is disabled. Apply them or choose Discard JSON edits. After applying, inspect the checks and Preview. Undo last applied change can restore the previous questionnaire after an applied JSON or source/AI change; this is not a complete version-history browser.
Downloads and sharing
Open Downloads and sharing in the header:
- Questionnaire JSON downloads the current designer questionnaire, including applied unsaved changes. It does not include template details or separately stored translations. The JSON workspace's own download instead uses the valid text currently in that editor, including unapplied edits.
- Saved template package downloads the stored template, details, and available questionnaire and team-field translation overlays. It excludes unsaved work and is available only after the first save. Use this package for the JSON import/export workflow.
- Copy account link shares the saved template's editor address. It does not grant access, publish a respondent link or share unsaved changes; colleagues still need the appropriate account access.
- Translations opens the account translation workspace.
- Export PDF uses the current designer questionnaire and the selected orientation and paper size, set in the same type and cards a respondent sees. PDF is an export, not an interactive assessment or a publication action.
Leaving with unsaved changes
Nothing on this page saves itself, so every way out of it asks first. Clicking away in the sidebar, reloading the tab, closing it, and the browser's own back and forward buttons all raise Leave without saving?, with Leave and discard and Stay on this page. Staying keeps the work exactly as it is and the back button still works afterwards: you are not stuck on the page. Leaving discards the edits and takes you where you were going, in the one press; a reload or a close falls to the browser's own confirmation, which looks different because it belongs to the browser rather than to Assessor.io. The back gesture was the exception until September 2026: it used to discard unsaved authoring with no prompt at all.
Action Statements
In Questions, open Action Statements to search the statements available to your account. The list shows 20 results at a time; Show 20 more reveals the next batch. Choose a Working question and use Link to record a source on it. Linked to this question filters the list to its sources.
A question source and its primary statement are different. Every linked source
is recorded on the question (sourceStatementIds) as a free list of sources.
The first statement you link to a scored question (role item or no role) also
becomes its Primary: the one statement its answer measures (asrStatement).
Make primary switches it to another linked statement. Unlinking the primary
clears it.
Saving binds the template to each question's primary. In an account, only statements from locked, distributed statement sets can be bound. A primary outside those sets stays on its question and is still reported against, but the save reports it as not bound instead of failing. Global templates can bind any global statement. Neither sources nor primaries change how a question is scored.
The BIMei AI Assistant
In Questions, open AI Assistant for a sidebar that helps while you author. It never changes the template on its own: each request comes back as a proposal card showing what would change, and nothing happens until you choose Accept. Edit lets you adjust the proposal first; Discard drops it. Proposals stay in the sidebar's history, oldest first, for the rest of the session.
Pick what you want from the action chips. The line under them says what the assistant is working on, for example "3 selected question(s) · page Planning". Select questions in the designer, or tick several in the sidebar's Questions list.
| Action | What you give it | What it proposes |
|---|---|---|
| Draft a section | Action Statements you search for and tick (up to 12), an optional page title | One page with one question per statement. A library item or earlier template question that already measures the statement is reused as it is, with its origin shown; a reused library item also keeps its registered scale, and the proposal says so when its scale is not registered, or when the item's options are not that scale's codes, so you can choose one. The rest are drafted with a question type, a registered scale (its choices come from the scale, not the AI) and Domain/Tier/Thread labels, and each question measures its statement. Add it as a new page or to the current one, and untick any question you do not want. |
| Assign metadata | Up to 10 selected questions | Labels, a registered scale and the Action Statement each question measures, each shown before and after. Tick the parts to apply. Replacing a question's answer choices with the scale's own options is a separate tick: it starts ticked when the question's current choices are not the scale's, and the card says why: either some current choices are not on the scale, so answers to them could not be read on it, or every current choice is on the scale but the scale adds options the question lacks, such as N/A. It starts unticked when they already match. You can change it either way. Edit shows the statement alternatives with the assistant's confidence. |
| Delivery rule | A sentence such as "only for information managers in the design phase", for the selected questions or the current page | A SurveyJS visibility condition and a plain-language restatement. Rules use what the platform already knows about a respondent (discipline, lifecycle phase, organisation size, province) where it can, or the answers to your existing questions. Anything the sentence asks for that the template cannot express is listed rather than guessed. Tick Keep the current rule too to require both. |
| Explain coverage gaps | Nothing: it reads the numbers the Traceability tab shows | A short explanation of what is covered and what is not, with buttons that open Assign metadata for the questions that need it or start Draft a section with a search for an empty area. |
| Improve wording | One selected question, optional instructions | Clearer wording for the question and its choices. The type, the number and order of choices, their values, logic, metadata and translations are kept. |
When a respondent's discipline, lifecycle phase, organisation size or province is not known to the platform, a delivery rule built on it still shows the question to them, and the card says so. Add a qualifier question that asks for it and the rule uses the answer instead. The rule is written so it never hides a question from everyone whose value is unknown.
An accepted proposal is one step in the designer's own undo and redo, and the header also offers Undo last applied change. If you change a question after the assistant proposed something for it, the card is marked as changed and cannot be applied; ask again. Accepting never saves: check, preview and Save Template as usual. Any Action Statement a question comes to measure is bound to the template on save when your account's statement sets allow it, and recorded on the question otherwise.
The assistant needs account authoring access (survey_templates.modify) and
configured AI service access. It can only use the statements, items, templates,
scales and labels available to your account, and a suggestion that refers to
anything else is refused and shown as an error instead. AI does not validate
factual accuracy, evidence, routing or scoring. Review each suggestion and test
the result before saving it as ready for use.