QTI 3 procurement evaluation worksheet
Longsight | Updated September 14, 2026
Companion guide: https://www.longsight.com/guides/qti-3-procurement-requirements/

Use one copy per supplier. Agree on mandatory requirements and expected results
before testing. Use synthetic or approved content without learner data.
Complete this worksheet with your procurement and technical teams. Keep detailed
technical test reports with the evidence for each requirement.

Evaluation scope

Institution and assessment program:
Supplier and product:
Product release and configuration:
Purchased functions (authoring, item bank, delivery, scoring, reporting):
Source systems and versions:
Required destination systems and versions:
QTI version and required features:
Evaluation environment:
Evaluators and requirement owners:
Test date and time zone:
Person authorized to approve acceptance:

Certification evidence

Required application role and certification level/profile:
Mandatory at award, required by an agreed date, or optional:
Supplier's stated status:
Certified product name and scope:
Registration number and current directory URL:
Directory check date and reviewer:
Evidence that the certification covers the proposed release:
Required features outside the certified scope:
If certification is absent, record the requirement as unmet. A future
commitment is not a current certification. Record any approved exception:
Person approving the exception:
Deadline and retest date:
Action to take if the supplier misses the deadline:

Requirement record (repeat for every requirement)

Requirement ID and description:
Mandatory or optional:
Function, feature, and versions in scope:
Supplier status (available / partial / planned / unsupported):
Evidence type (directory listing / supplier test / institutional test):
Evidence URL or saved file location:
Sample questions, saved assessment package, and list of included files:
Test steps and configuration:
Expected result:
Actual result:
Outcome (meets / partly meets / does not meet / not tested):
Limitation, data loss, or manual repair:
Requirement owner and reviewer:
Decision (accept / reject / approved exception / pending evidence):
Person responsible for fixes, deadline, and retest result:

Evidence checklist

For each row, complete a requirement record above. Check the evidence against
the expected result before marking a requirement as met.

[ ] Application roles and supplier responsibilities are documented.
[ ] QTI version, certification profile, and required features are explicit.
[ ] The current certification claim has been checked against its listing.
[ ] Source content, media, metadata, identifiers, and scoring are inventoried.
[ ] The import report identifies missing or changed content and known limits.
[ ] Required authoring changes preserve content, media, and accessibility data.
[ ] An exported package includes the agreed items, test structure, and assets.
[ ] Technical reports separately cover file format, question behavior, scoring, and security.
[ ] The intended destination imports the export using recorded versions.
[ ] Known responses produce the expected scores in the destination.
[ ] Each conversion loss or manual repair has an acceptance decision.
[ ] Accessibility evidence names product version, scope, and known exceptions.
[ ] Keyboard and assistive-technology tests cover required user workflows.
[ ] Required accommodations survive import, editing, export, and delivery.
[ ] Launch, identity, roster, and grade-return integrations pass agreed tests.
[ ] Connection loss, recovery, duplicate submission, and deadline tests pass.
[ ] Scoring corrections preserve original responses and reviewable history.
[ ] Capacity evidence describes workload, environment, duration, and failures.
[ ] Hosting, patching, monitoring, incidents, and backup recovery have owners.
[ ] Data locations, access controls, retention, and recovery targets are agreed.
[ ] Exit exports separately cover QTI packages and required operational records.
[ ] Export formats, destination tests, transfer rights, fees, and support are agreed.
[ ] Tests to repeat after a system change are recorded.

Exchange test record

Original assessment package and saved location:
Item and asset counts:
Required scoring cases and expected outcomes:
Required accessibility and accommodation cases:
Import report and preserved source location:
Authoring changes made during the test:
Exported assessment package and saved location:
Technical test reports, including tools and QTI versions used:
Destination product, version, configuration, and import result:
Expected versus actual scores and test-taker experience:
Losses, workarounds, manual repairs, and evidence locations:
If destination testing could not run, record it as not tested:

Acceptance and exit decision

Mandatory requirements met:
Mandatory requirements unmet or untested:
Optional requirements and evaluation weights:
Approved exceptions, people responsible for fixes, deadlines, and retests:
Technical decision (accept / reject / pending):
Procurement decision owner and date:
Saved evidence location and person responsible:
Pre-launch tests and acceptance date:
Next review date and triggers:
Exit record types and documented export formats:
Exit destination and acceptance test:
Transition owner, support period, fees, and deletion conditions:

Standards sources

1EdTech QTI procurement guidance:
https://www.1edtech.org/standards/qti/rfp-procurement-agreements
1EdTech QTI conformance and certification:
https://www.1edtech.org/standards/qti/conformance
1EdTech QTI accessibility:
https://www.1edtech.org/standards/qti/accessibility

Public test items or supplier tests alone do not establish certification,
destination acceptance, or accessibility of the complete assessment platform.