{"id":300,"date":"2026-09-09T15:30:00","date_gmt":"2026-09-09T07:30:00","guid":{"rendered":"https:\/\/oribridge.org\/blog\/?p=300"},"modified":"2026-09-08T09:36:58","modified_gmt":"2026-09-08T01:36:58","slug":"attendance-not-course-delivery-record-china","status":"publish","type":"post","link":"https:\/\/oribridge.org\/blog\/attendance-not-course-delivery-record-china\/","title":{"rendered":"Attendance Is Not a China Course Delivery Record"},"content":{"rendered":"

An attendance export answers a narrow question: which accounts, or which names, appeared to enter a scheduled session? It does not answer whether a learner could watch the replay, received the promised materials, completed a task, or needed help. For a China-facing course, those are separate operational facts.<\/p>\n

This distinction matters whenever an overseas team reports a pilot to a partner. \u201cTwenty-two people attended\u201d sounds complete. It may actually hide a broken replay link, a missing worksheet, or a login failure affecting three of the people who were counted. The responsible record is not a bigger attendance number. It is a short chain of evidence with each layer labelled.<\/p>\n

The four layers<\/h2>\n

Attendance.<\/strong> Record the session, scheduled time zone, participant identifier as displayed by the system, join and leave information where available, and any stated attendance rule. Do not turn a display name into verified identity. Tencent Meeting documentation describes participant and check-in surfaces; it does not independently verify who was sitting behind an account.<\/p>\n

Replay access.<\/strong> Record whether a replay was created, when it became available, who was given access, and whether a controlled test account could open it. A replay file is an asset, not proof that every learner received or used it. ClassIn\u2019s LTI material separates historical recordings and reports from other classroom data. That separation is useful precisely because it prevents one field from doing several jobs.<\/p>\n

Task or material receipt.<\/strong> Record the worksheet, reading, prompt, or submission expected after the session, plus the delivery channel and timestamp. \u201cThe slide deck was uploaded\u201d is not the same as \u201cthe learner received the deck.\u201d If the programme promised no task, write \u201cnot in scope\u201d rather than inventing a completion field.<\/p>\n

Support and exception.<\/strong> Record access errors, missing links, language questions, schedule conflicts, or content corrections separately. A support event should have a status, owner, next action, and closure time. It should not silently overwrite the attendance result.<\/p>\n

A practical delivery card<\/h2>\n

Use a row per session or cohort, not one celebratory sentence:<\/p>\n

\n\n\n\n\n\n\n\n\n
Layer<\/th>\nEvidence to retain<\/th>\nSafe wording<\/th>\n<\/tr>\n<\/thead>\n
Attendance<\/td>\nexported participant list and session window<\/td>\n\u201c22 displayed participants joined.\u201d<\/td>\n<\/tr>\n
Replay<\/td>\nURL or platform record plus controlled open test<\/td>\n\u201cReplay was available to the test account at 16:20.\u201d<\/td>\n<\/tr>\n
Task<\/td>\nmaterial name, destination and submission state<\/td>\n\u201cWorksheet sent; 9 submissions recorded.\u201d<\/td>\n<\/tr>\n
Support<\/td>\nticket, category, owner and resolution<\/td>\n\u201c3 access incidents; 2 closed, 1 pending.\u201d<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

This card is deliberately unglamorous. It gives a reviewer enough information to ask the next question without pretending that a dashboard metric is a learning result. ClassIn 5.0 describes activities, progress and capability indicators as distinct product surfaces. That is a strong design clue for operators: keep the fields distinct in your own report.<\/p>\n

Illustrative scenario<\/h2>\n

Imagine a two-hour workshop for a China-facing cohort. Twenty-two accounts appear in the sign-in export. Eighteen can open the replay. Nine submit the exercise. Three report that the login route fails on their device. The honest summary is: \u201c22 displayed participants joined; replay access was confirmed for 18; 9 submissions were recorded; 3 access incidents were logged.\u201d<\/p>\n

That sentence is more useful than \u201c22 learners completed the workshop.\u201d It tells the delivery team where to investigate and lets a buyer decide which obligation has actually been met. It also preserves uncertainty: the export does not prove that all displayed names were the intended learners, and a submission does not prove mastery.<\/p>\n

The counterexample: when attendance is enough<\/h2>\n

There are cases where attendance is the only promised deliverable. If a contract says \u201ca two-hour briefing will be hosted for invited participants,\u201d a valid attendance export may be sufficient evidence that the briefing occurred. The mistake is not using attendance. The mistake is extending it to claims the scope never covered: replay consumption, task completion, skill acquisition, or business impact.<\/p>\n

Write the narrow commitment beside the metric. \u201cBriefing hosted; attendance export retained\u201d is defensible. \u201cTraining completed successfully\u201d is a different claim and needs different evidence.<\/p>\n

What this record cannot prove<\/h2>\n

Even a carefully completed delivery card cannot prove identity authenticity, teaching quality, certificate validity, learning outcomes, platform reliability beyond the tested moment, or compliance with every privacy rule. Those questions require their own evidence and, where appropriate, specialist review. Chinese platform documentation describes interfaces and capabilities; it does not convert a product feature into a legal or educational conclusion.<\/p>\n

For a broader path test, see End-to-End Access, Payment and Delivery Test Script<\/a>. For the distinction among a room, broadcast and replay surface, read China-Facing Live Cohort Room, Broadcast and Replay<\/a>. The evaluation logic behind buyer, problem, alternative and delivery is set out in Buyer\u2013Problem\u2013Alternative\u2013Delivery Worksheet<\/a>.<\/p>\n

A small operating rule<\/h2>\n

Before reporting a China-facing delivery, ask four questions: What was attended? What could be opened? What was received or submitted? What went wrong and who owns it? If a question is out of scope, mark it out of scope. A trustworthy record is allowed to contain blanks, pending items and exceptions.<\/p>\n

If you need a scoped review of the evidence your course would require in China, submit a validation request<\/a>. It is a request for assessment, not a promise of platform access, eligibility or commercial outcome.<\/p>\n

Sources and evidence boundary<\/h2>\n