Workspace coverage

Six things a serious authoring tool must do.

Unified item authoring

One workspace for the QTI 3 item type surface, metadata, accessibility fields, standards alignment, and review workflow.

Versioned revisions

Every item carries a revision history. You can see what changed, when, by whom, and roll back without losing learner attempt history.

Reusable assembly

Items are first-class. Assessments are assemblies of items with delivery rules, not duplicated content lakes.

Standards metadata

Item-to-standard alignment is captured at authoring time and exported through the QTI manifest.

Portable media

Images, audio, and video stay attached to the item, packaged cleanly on export.

Clean QTI export

Exports produce conformant QTI 3 packages with manifest metadata. No proprietary side-cars.

Versioning

Edits never mutate published work.

When an instructor fixes a bad question after the assessment is live, the published version is not silently rewritten. The fix becomes a new version. Original learner responses stay anchored to the version they took. Re-scoring happens as an overlay, not a rewrite.

This is what lets us tell procurement that nothing in the system can quietly destroy evidence. It is also what makes auditable rescoring tractable.

RFP coverage

Authoring claims need an item bank matrix behind them.

Buyers ask whether the item bank supports item types, standards metadata, DOK, source package preservation, accessibility fields, review workflow, permissions, revision history, and item statistics. The public authoring story should point straight to that matrix.

See the authoring workspace in your context.

Schedule a walkthrough or request the authoring capability matrix for your RFP response.