Capability checklist

Clear status for every claim.

Every line is tagged. Procurement teams can see what we will defend in a contract, what is currently architecture or product direction, and which launch artifacts are being prepared.

Area Public statement Status
Open standard Built around IMS/1EdTech QTI 3. Ready
Item & test exchange QTI 3 packages on import and export. Ready
Migration Importers for QTI 1.2, QTI 2.1/2.2, QTI 3.0, IMSCC, Moodle XML, GIFT, Aiken. Ready
Fidelity review Item-level review with preserved source XML. Ready
Authoring Versioned items, assemblies, standards metadata, clean export. Ready
Item bank Item type coverage, metadata fields, revision history, and review workflow. In build for launch
Delivery operations Cloudflare-native runtime handles clustered launches and deadline submissions. Ready
Concurrent scale Load-tested for thousands of concurrent learners on Cloudflare serverless primitives. Ready
Reconnect / offline IndexedDB-backed local recovery, reload and tab reopen restore, replay on reconnect, and durable receipt coverage. Ready
Immutable versions Published assessment versions are immutable; corrections are new versions. Ready
Re-scoring Auditable scoring overlay; original responses preserved. Ready
Reporting & analytics Standards mastery, item analysis, accommodation evidence, report bundles, learner bundles, and export data dictionaries. Ready
State standards reporting Reports group results by framework, domain, standard, assessment form, cohort, class, and learner. Ready
Accessibility (PNP) PNP and accommodation evidence are snapshotted at launch and carried into reports and CSV exports. Ready
VPAT / ACR Conformance artifact in production. In build for launch
LMS integration LTI 1.3 and Advantage support includes launch, Dynamic Registration, Deep Linking, AGS grade return, and NRPS membership reads. Ready
SIS / rostering CSV and OneRoster CSV provisioning support preview, apply, hierarchy metadata, idempotency, and run reports. Ready
SSO / role boundaries SSO and role mapping stay explicit in the implementation plan and security boundary packet. Planned
Implementation & QA Discovery, migration proof, integration testing, accessibility review, pilot, UAT, and launch support. In build for launch
Security & isolation Tenant isolation, signed launch tokens, audit ledger. Planned
1EdTech certification Held until certification is complete. Not claimed yet
Sample RFP answers

Questions we should be ready to answer every time.

Procurement-safe language you can adapt directly. Each answer maps back to a page on this site and an artifact, status note, or launch artifact in the library.

01

Is the platform built on an open assessment standard?

QFlowLearn is built around IMS/1EdTech QTI 3. Items, tests, accessibility metadata, and results reporting use the QTI 3 interchange formats so institutions retain portability of authoring investment.

02

How does the platform handle synchronized starts and submissions?

Delivery runs on Cloudflare Workers with per-attempt Durable Objects and a durable submit queue. The runtime uses serverless primitives that spin up on demand for launch and submit spikes instead of relying on servers that get overwhelmed as usage spikes. The concept has been load-tested for thousands of concurrent learners, with exact ceilings documented in the evaluator packet.

03

What happens when a learner loses connection mid-attempt?

Responses are journaled locally in the browser and reconciled against the per-attempt authority on reconnect. Per-attempt Durable Objects prevent stale tabs or duplicate sessions from corrupting authoritative state.

04

How are scoring corrections handled?

Published assessment versions are immutable. A correction is a new version with auditable provenance; re-scoring runs as an overlay on raw attempt evidence so original responses are never destroyed.

05

Can administrators report by state standard and export results?

QFlowLearn stores item-to-standard alignment and attempt evidence so reports can break down performance by state framework, domain, standard, assessment form, cohort, subgroup, and learner. The export center provides cataloged CSV artifacts, assessment result bundles, learner bundles, manifest hashes, row counts, and data dictionaries.

06

What does the item bank store?

QFlowLearn item records carry item type, standards metadata, accessibility metadata, source package, preserved XML, review state, revision history, usage, and item statistics. The RFP packet should include the item bank coverage matrix and a redacted item detail example.

07

What is your accessibility support?

QFlowLearn uses QTI 3 PNP and accessibility capabilities end-to-end. Alt text, captions, glossary, color themes, masking, extra time, and screen-reader support are tracked on the support matrix. A VPAT/ACR is in production and will be linked from /evidence when complete.

08

How does the platform integrate with institutional systems?

QFlowLearn names the handoffs directly. LTI 1.3 and Advantage cover launch, Dynamic Registration, Deep Linking, AGS grade return, and NRPS membership reads. CSV and OneRoster CSV provisioning cover roster preview, apply, hierarchy metadata, idempotency, and run reports. QTI import/export and result exports remain explicit parts of the packet.

09

How do you reduce implementation risk?

Implementation is handled as a sequence of proofs: discovery, migration proof, integration proof, accessibility review, pilot, launch support, UAT, and training. Each phase should have an artifact and signoff path in the RFP response.

Request the packet

A person reviews each RFP request.

Tell us about your evaluation timeline, the categories your RFP asks about, and which artifacts you specifically need cited. We assemble the packet, send a single follow-up, and stop there.

  • Capability matrix tied to your RFP categories.
  • Sample answers with citations.
  • Architecture summary and accessibility status.
  • Migration QA report (when relevant).

Checking form protection...

This request is submitted to our Zendesk queue so we can route the right packet and artifacts.