Access these three tabs from within any form under Exam Management, Exams, your exam, Exam Forms, your form. Together they control the form's identity, its item structure, and how it's scored.
Known issue: unsaved changes can be lost when switching between these three tabs. Click Update before navigating away from one you've edited.
The Draft status badge shown throughout this page reflects the form status lifecycle described at the end of this article.
Summary Tab
Holds the form's identity: what it's called, what template it's built from, and which languages it's available in.
- Form Template and Form Template Type (Live or Beta): read-only, set at creation.
- Form Name and Description: editable here after creation.
- Translated Languages table: each language has an Active checkbox ("used for form selection") and a delete icon. English is active by default.
❓ What does "Active" mean for a translated language here?
This determines whether the language is one candidates can choose when selecting a form to take. Marking a language active makes it selectable at booking; deactivating it hides that language option without deleting any translated content underneath.
Delivery Tab
Reveals the form's structural hierarchy and is where items get assigned.
Structure: Form, then Test Part, then Section, each collapsible. Every level shows a Pre-test and Scored item count, plus an Item Selection count for Test Parts and Sections.
❓ What's the difference between a Test Part and a Section?
A Test Part is a major division of the exam. Most single format exams like this one have just one. A Section is a subdivision within a Test Part, used to organize items further. Item selection happens at the Section level: this is where accepted items from your pool get assigned into the form.
❓ What's the difference between a Pre test and a Scored item?
Scored items count toward the candidate's actual result. Pre test items appear on the exam but aren't scored: they're being trialed to gather performance data (difficulty, discrimination) before being promoted to scored status on a future form. This is a common way certification programs quietly validate new items using real candidates without any risk to those candidates' results.
Section Settings
Clicking a Section's name opens a settings panel:
- Name: the section's label.
- Items Per Page: how many items display per screen during delivery.
- Display Screen: dropdown, defaults to "None."
- Shuffle: dropdown controlling item order randomization, default is Items.
- Item Selection: dropdown, defaults to "All."
- Section Outcomes: a band system for reporting subscores, starting at "Total Bands: 0" with an Add Band button.
❓ What is a "Band" in Section Outcomes?
A band groups score ranges into named outcome categories for reporting, for example a "Low Score," "Proficient," and "Advanced" band on a section's results. The platform's own guidance recommends always including a "Low Score" outcome when adding bands, likely because reporting logic needs a defined floor category to categorize any result that doesn't meet a higher band.
Assigning Items to a Section
Use Manual Item Selection or Automated Item Selection next to any Section. Both open the same modal with three tabs: Search, Upload File, and Automated Selection, freely switchable regardless of which button you clicked.
Search tab, for manual picking:
- Search by Item Name/s, Question Text, or Tags.
- Results grid shows Item Name, Pretest (a checkbox marking whether this item should be added as a pretest rather than scored item), Topics, Question Stem, and Enemies.
- Footer tracks Scored Items and Pretest Items counts as you check items.
- Click Add Items to commit your selection, or Cancel to back out.
❓ How do I decide whether to mark an item as Pretest here?
Check Pretest for items you want candidates to see but that won't count toward their score, typically newer items still being validated with real candidate data. Leave it unchecked for items that should count toward the result. This matches the Pretest versus Scored distinction on the Delivery tab overview: a section can mix both types.
Automated Selection tab, filter-driven, a three-step wizard: Settings, Items per Topic, Review Items.
Step 1, Settings:
- Number of Items on Form: total item count to pull, for example 50.
- Delivery Status filters: Unassigned, Untested, Operational, Pretested, Beta Tested.
- Item Quality filters: Green, Yellow, Red, Undetermined, the same quality flag visible as a column filter in Item Management.
- Enemy Items: Not Allowed or Allowed. This is where enemy item enforcement (see the AI Automated Enemy Detection guide) actually gets applied at form assembly time.
- Tags filter.
- Include Items and Exclude Items: manual override fields to force specific item codes in or out regardless of the filters above.
❓ Why would Available Items show 0 for every topic?
This almost always means your Step 1 filters exclude the status your items currently hold. New items that haven't yet been through a delivery cycle typically sit at Item Quality: Undetermined and Delivery Status: Unassigned or Untested. If Step 1's filters only include Green or Yellow quality and Operational, Pretested, or Beta Tested status, a brand new pool will show zero available items everywhere. Broaden the Step 1 filters to include Undetermined quality and Unassigned or Untested status to surface a first time item pool.
❓ Why would I choose "Allowed" for Enemy Items?
Almost never, for a live scored form. Allowing enemies risks placing two items that test the same content on the same form, undermining the exam's coverage. "Allowed" might be useful in a narrow case like a small pretest pool where excluding all enemy pairs would leave too few items to fill the form. Default to Not Allowed unless you have a specific reason otherwise.
Step 2, Items per Topic, shows a per-topic breakdown table:
- Available Items: how many items in your pool currently match the Step 1 filters, per topic. Displays in red when zero.
- Weight: the topic's blueprint weight, carried over for reference.
- Items: an editable field for how many items to pull from this topic, with a warning icon whenever the requested count exceeds what's available.
A running Target Number of Items and Total track your progress against the overall form size set in Step 1.
After Adding Items, Manual or Automated
Once items are assigned to a Section, the Delivery tab updates to show them directly:
- A Select All Items checkbox and a Hide/Show Items toggle, on by default, sit above the list.
- Every level of the hierarchy - Form, Test Part, Section- shows updated Pretest and Scored counts, and the Item Selection label reflects the real count.
- Each individual item row shows its Item Name, Topic, and a per-item Scored/Pretest dropdown, meaning you can reclassify an individual item between Scored and Pretest at any time after adding it, without removing and re-adding it.
❓ Can I change an item from Scored to Pretest after adding it?
Yes. Each item in the populated list has its own Scored/Pretest dropdown, independent of how it was originally added. This is useful if you decide after the fact that a newer item should gather performance data as a pretest item before counting toward candidates' scores.
Once a form has at least one Scored item, a Preview button appears in the header alongside Approve, letting you preview the form as a candidate would see it before approving it.
Scoring Tab
Sets how the form determines pass or fail.
Platform note, shown directly on this tab: "Live forms must include a Pass/Fail Type and a Passing Score. Beta forms typically do not have a score until a cut score is established, so for Beta forms these fields should remain blank."
- Pass/Fail Type: dropdown, defaults to "None." Live forms need this set. Percent and Raw are the documented types.
- Passing Score: manual entry field.
- Scaled Scoring: an off-by-default toggle, plus a CSV Match Table upload for a custom score conversion table.
- Test Part Scoring: a repeated Pass/Fail section per Test Part, letting you set scoring independently at that level as well.
❓ Why does the platform treat Live and Beta forms differently here?
A Live form is scored and delivered to real candidates, so it needs a real passing score to determine outcomes. A Beta form exists to pilot new items and collect performance data before a cut score has been established through standard setting. Scoring it prematurely would be meaningless, since the passing threshold hasn't been determined yet.
❓ How do I pick a passing score?
Ideally from standard setting data, not a round number. The Angoff estimates collected on every item during writing and review exist precisely to inform this: the average difficulty of a form's items suggests a defensible cut score. A flat default, such as 70 percent, is a reasonable starting point for low stakes programs; high stakes certifications should involve a psychometrician before committing to a number.
Looking ahead: Certiverse has an in-progress AI Standard Setting feature that will auto-calculate and pre-populate a suggested passing score directly from each item's Angoff data, and will warn you at approval time if your entered score differs from that calculated value. Not yet live. This page will be updated when it ships.
Form Status Lifecycle
A form moves through three states:
- Draft: being built; items and scoring still editable freely.
- Approved: finalized and ready; requires the Active checkbox to actually be delivered.
- Active, a checkbox rather than a separate status label: the form is live and delivering to test takers.
Approving a form triggers a confirmation modal explaining the consequence: once approved, a form must be made Active before it reaches test takers, and once a test taker has actually been delivered the form, its status can never return to Draft. It can still be made Inactive at any time to stop further delivery.
❓ Can I undo an approval?
Yes, but only up to a point. A form can be moved back to Draft via the "Back to Draft" button as long as no test taker has yet been delivered the form. Once even one test taker has taken it, Draft is permanently off the table. The form can still be deactivated, moved to Inactive, to stop further delivery, but its content and scoring history are locked in place for audit purposes.
Updated
Comments
0 comments
Please sign in to leave a comment.