What the Record Says — Logs, Gaps, and Being Able to Find Anything

What a record is for, what's actually in one, why 'we'll check the logs' so often fails, why time is harder than it looks, how long things are kept and by whose decision, and whether anybody can find anything.

What you'll learn

• Say who a record is written for, name the three jobs it does, and include the human-written records nobody counts as records.
• Read an entry plainly and separate what it shows from the intention, context, and identity people read into it — and notice the field nobody captured.
• Recognise the four kinds of gap, state one plainly, find them before you need them, and handle clock drift, time zones, and what a timestamp really means.
• Set retention from the discovery gap rather than a default, run a timed retrieval test, judge whether a record is dependable or merely suggestive, and never edit one.

Sign in to enrol — you can pay by bKash or Nagad, or apply a promo code.