Keep logs of recordings.

Keep logs of recordings. — real work, not an imagined feature: named inside 7 evidenced career tasks. Below are four ready AI prompts for it, one per height of help: do it, make it easier to accept, decide when you are stuck, and change the pattern for good.

7career tasks name it
4prompt heights

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
The events team needs the recording log for legal and archive. Send the Recording Log spreadsheet…
The events team needs the recording log for legal and archive. Send the Recording Log spreadsheet to Lucy in Events and to our compliance officer, Naveen, with a request to confirm timestamps and participant lists by Tuesday. Before sending, ensure each entry has filename, start and end time, host, consent status, and storage location verified.

Improve — make it easier to accept

+
Before sharing the master recording log with compliance, make it easy for them to approve…
Before sharing the master recording log with compliance, make it easy for them to approve retention: add a top-line summary of recordings older than retention threshold, make consent status column prominent, flag recordings missing signed consent, and insert a quick link to the storage folder so reviewers can spot-check audio without hunting across drives.

Decide — diagnose the stuck moment

+
I found a meeting recording where the consent column says unknown, and the host insists verbal…

One recording shows 'unknown' for consent status.

I found a meeting recording where the consent column says unknown, and the host insists verbal consent was given but has no signed form. Compliance will want a definitive record. What are the most defensible steps to verify consent now, which logs or emails should I inspect, and what wording should I add to the spreadsheet so it accurately reflects our position if compliance questions it?

Become — change the pattern

+
Across events I often leave consent verification until an audit or request, which forces frantic…

I repeatedly scramble to confirm consent for recordings before audits.

Across events I often leave consent verification until an audit or request, which forces frantic searches for emails and wrecks our retention schedule. What routine and what specific field to add to the log will make consent check a near-automatic part of recording capture so audits stop creating fire drills?

Where the evidence lives

Who was seen doing this, and what people really ask.

Software tasks in the LLOS Work Atlas come from evidence, never a feature list: careers attested to do the work, real job descriptions, and the questions people actually ask (with their view counts). Facets — feature, workflow, troubleshoot, administer, deploy, scale — are open metadata: the work decides, not a taxonomy.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.