Item type coverage

Show the coverage table, not a generic claim.

The packet should include an item-type matrix with examples, QTI export notes, accessibility fields, and any current limitations. That is the artifact evaluators expect when an RFP asks about authoring coverage.

Item family Coverage Status
Selected response Single choice, multiple choice, multi-select, true/false In build for launch
Text entry Short answer, numeric entry, constructed response metadata In build for launch
Matching and ordering Associations, ordering, categorization, sequence evidence In build for launch
Media-rich prompts Images, audio, video, captions, transcripts, alt text, long descriptions In build for launch
Rubric-scored work Rubric metadata, scoring status, reviewer workflow, export notes Planned
QTI package fidelity Source package, preserved XML, conversion warnings, export validation Ready
Workflow

A reusable item is only useful if the workflow protects it.

01

Import

Bring in QTI, IMSCC, Moodle XML, GIFT, and Aiken content with original source preserved.

02

Normalize

Map content into the QFlowLearn item model without hiding warnings or unsupported transformations.

03

Review

Approve fidelity, metadata, accommodations, standard alignment, and scoring before release.

04

Assemble

Build assessment forms from reusable items and publish immutable versions for delivery.

Authoring evidence

Put item bank coverage in the RFP packet.

The authoring packet should include item type coverage, metadata fields, revision history, standards alignment, source preservation, and clean QTI export samples.