The recording is not the class, and pretending otherwise costs everyone

Capture has become routine in almost every teaching room, yet the artefact it produces is still treated as an afterthought. The gap between what a recording is and what people expect it to do explains most of the frustration on both sides of it.

Somewhere in the last two decades, pressing record became the default rather than the exception. The button is now part of the furniture, alongside the lectern and the projector, and it is switched on with roughly the same amount of deliberation as the lights. What comes out the other side is a file: long, unbroken, faithful to the room in the way a security camera is faithful to a corridor. It captures what happened. It does not interpret, prioritise, summarise or select. And that distinction, small as it sounds, is the origin of nearly every argument that institutions have been having about recorded teaching ever since.

The trouble is that everyone downstream treats the file as though it were something else. Students open it expecting a lesson. Coordinators file it expecting a resource. Reviewers point to it expecting evidence of quality. Marketing teams occasionally point to it expecting a product. It is none of those things by default. It is a record of an event, and a record of an event only becomes a learning object when someone does work to make it one. Nobody is usually assigned that work, so it does not happen, and the file sits there being technically available and practically unusable.

This magazine exists to take that gap seriously. Not to argue for or against capture, which is a settled question in most places, but to look hard at the object itself. What is in it. What is missing from it. What a person actually does when they open a long recording at ten o'clock at night with a specific question in mind and thirty minutes to spare. Those questions are more interesting than the ones usually asked, and they are far more answerable than the perennial and largely unwinnable debate about whether recording is good or bad for attendance.

There is a version of this conversation that gets stuck immediately on technology, and we intend to avoid it. Which system, which camera, which settings: these matter less than people think, and they change constantly. The decisions that determine whether a recording is worth anything are almost entirely human and almost entirely cheap. Did anyone say aloud what was about to happen, so a listener could find it later? Did anyone note the moment where the explanation actually landed? Did anyone spend ten minutes afterwards writing three sentences about what the session covered? None of that requires a budget line. All of it requires someone to decide it is their job.

The honest position, which we will return to across these pages, is that a recording is a low value artefact that can be turned into a high value one at modest cost, and that most institutions are paying the storage bill for the low value version without ever making the conversion. The file exists. It is retained. It is occasionally cited in a policy document as evidence of flexibility. It is very rarely made findable, searchable, navigable or current. That is not a technology failure. It is a failure to decide who owns the object once the room has emptied.

So we start from the artefact and work outwards. What a recording is and is not. What happens to a room when everyone knows the session will be available later. What separates a recording somebody can use from one they abandon at the four minute mark. And the harder questions, the ones that get deferred: who consented to being in it, who owns it, how long it should live, and who is doing the unpaid labour of keeping it useful. These are ordinary questions. They deserve better than being ignored until an incident forces the issue.