What the month's log can say

Lesson map

Lesson 20 published. Map, example, EX074.

flowchart TD
  N["One leaving note"] --> E{"Is the sentence backed by a log line or a counted output?"}
  E -->|Yes| K["The note may say it, with that limit"]
  E -->|No| R["The note names the gap instead of filling it"]
  R --> G["Next course: data governance, for retention"]

Twenty lessons meet a planning minimum. They do not close the case file.

Logical drawing

the note may carry
    personal accounts, the three repaired computers, twelve files closed
    phone-back still in force, backup results already logged, card pinned
the note may not carry
    a new share total, a dated fresh list, next month's restore
    a dated locum disable this book never supplied
    "the clinic is secure" or "the exercise is closed"

Learning outcomes

After this chapter, you should be able to:

1. Separate sentences the change log supports from sentences that would invent a result.
2. Leave stated gaps as gaps, including where an earlier lesson taught the action but did not date it.
3. Name data governance as the next course for retention, without calling this book a finished qualification.

20.1 A leaving note is a reading of the file

Sofia can leave one note for the person who opens the log next month. The note is allowed to say what the file already shows. Personal accounts replaced the shared reception login. Second factors started with Dr. Moss and the office team, then everyone else over two weeks, and two nurses have security keys because they declined phone apps. The eight client files and four finance files were taken off open links. The phone-back rule stopped one fraudulent request and remains in force. The separate email-and-files backup has a failed mailbox restore and a later success, both logged, into a test area. The incident card is on the wall. The three computers that had updates off had a newer driver and then had updates switched on.

The note is not allowed to improve the file. Chapter 7 left the counted open total at the seed-2 print until a new export. Chapter 10 left the urgent-call list without a dated print. Chapter 11 left next month's restore row empty. Chapter 8 taught that the locum account is disabled and the date written; the exercise still begins from a log that has not recorded that date, and this note does not invent one. Chapter 12 refused a nine-computer patch census. Chapter 17 held a blanket link shutdown. None of those blanks become ticks because the course has reached its twentieth lesson.

20.2 Worked example

Lesson table; scroll horizontally to read all columns →

Synthetic case. Reaching the planning minimum of 20 lessons is not a qualification and does not close technical, language, source, or accessibility review.

Errors and limits

The next course is the data-governance rapid book, because Dr. Moss's next question is how long old client records are kept. That question is not answered by ISO/IEC 27000:2026's three goals, and this chapter is not legal advice. Another language edition is not published by the existence of these English lessons. There is no maximum: a later lesson is added when a new decision needs teaching, not to decorate the count.

Apply

• EX074 — What may the note say? Using only the file this book has already fixed, accept or reject each claim: the seed-2 open total may be replaced by 35; the locum disable already has a date; next month's restore already passed; the clinic is secure because twenty lessons exist. Then name the next course and the question it is for.
  Show marking criteria

  Rubric: 3 = reject all four claims; the next course is data governance; the question is retention of old client records; twenty lessons meet the planning minimum and do not finish review;; 2 = reject the four claims and name data governance;; 1 = one part;; 0 = none.