Every batch Tamitu delivers is verified against the Tamitu Verified framework, a documented quality standard aligned to Quality Matters (QM) rubric criteria. When your accreditor asks how you ensure online course quality, the answer is this document.
When a vendor delivers 40 courses and says it's done, and then your team finds broken LTI links and missing PDFs: you have no way to know whether anyone checked anything. In regulated environments, "we trusted the vendor" is not an answer that survives audit. The QA Evidence Pack gives your team the documented, batch-level verification record: what was checked, against what criteria, with what results, and who accepted it.
Procurement and audit defense: The pack is the record your team points to when a delivery gets questioned. It documents the checklist applied, the criteria each course was measured against, and the sign-off from your designated reviewer.
Compliance documentation: For regulated training, evidence of quality checks is not optional. The pack provides that evidence at the batch level: what was verified, what exceptions were flagged, and how each was resolved.
Vendor continuity: When teams change, the next vendor or hire needs to know what was delivered, to what standard, and where the exceptions are. Every batch has its own summary, checklist results, and exception log.
Accreditation documentation: When regional accreditors ask how your institution ensures online course quality, a subjective claim is not sufficient. A Tamitu Verified evidence pack maps every course to QM-aligned criteria and gives your accreditation team a citable, dated record.
Note: Numbers are representative of real batch deliveries. Course names and client identifiers are redacted for confidentiality.
The full checklist maps to the Definition of Done agreed during standards lock. Every item is binary (pass or exception) so there is no ambiguity about what was verified.
Checklist criteria are aligned to Quality Matters (QM) Standard references where applicable.
Every exception is classified and assigned.
Integration: depends on a third-party system or client IT action.
Content: requires SME input or source material that was not provided.
Scope: falls outside the agreed Definition of Done and requires a change order.
“Batch 02 is accepted against the Definition of Done. Exceptions listed above are acknowledged and scheduled.”
What sign-off means: Sign-off formally accepts a batch against the agreed Definition of Done.
Warranty: Defects within the acceptance criteria that surface within 30 days are fixed without a separate negotiation.
A full 5-page version of the QA Evidence Pack: cover page, batch summary, Definition of Done checklist, exception log, and sign-off record. Client name and identifiers are redacted.