Stop 8 of 8 · Weekly
Dr. Salma's week
The Monday digest, the guidance watch and the monthly drafts run on a timer, the policy refresh across nine clients goes to Cowork, and the capstone is one facility from walkthrough to signed report.
What runs without her
After eight stops the individual jobs are fast. The week is still full, because nine clients generate a background hum of due dates, guidance changes and monthly reports that has nothing to do with skill and everything to do with counting. That part comes off her desk.
| Routine | When | What it returns |
|---|---|---|
| Client digest | Monday, seven | Corrective actions due in a fortnight, by client code |
| Guidance watch | Weekly | Documents that appear to have moved, with the pages to open |
| Monthly drafts | First of the month | A draft administrator memo per client, from the register |
Every one of those returns a draft or a list. None of them sends anything, and none of them touches a person's record.
Cowork, when the job is volume
Chat is a conversation. Cowork is a delegation: hand over a folder and a brief and it works through the steps. The policy refresh after new guidance is the case. Nine clients, three facility types, one policy subject: that is a folder of documents and a comparison to run against each one, and Dr. Salma wants the change tables on her desk, not the afternoon it takes to make them.
Start Cowork in the mode that asks before every action, and leave anything that sends where it is.
Every Monday at seven, go through the findings registers in my client Projects and give me one list: every corrective action with a target date inside the next fortnight, grouped by client code, with the owning role and how many days are left. Then a second short list of anything whose date has already passed. Use client codes only. Do not email anybody and do not mark anything as complete.
Once a week, check whether the guidance documents and survey protocols listed in my Project files have been revised, superseded or reissued. Return only what appears to have changed, with the document, what the change seems to be in one line, and the exact page for me to open. Do not summarise the new requirement as settled and do not tell me which of my clients it affects.
Work through the policy folder for [ASC-4] one document at a time. For each policy that touches [reprocessing of reusable instruments], compare it against the guidance PDF I have put in the folder and produce a clause by clause change table: what the guidance requires, what the policy says with its section, and the gap as silent, weaker or conflicting. Do not rewrite any policy. Return one table per document and a single list at the end of every requirement you were unsure applied.
The capstone
One facility, walkthrough to signed report, in one sitting.
- De-identify the walkthrough notes with the four moves from stop one.
- Group them into ranked findings and get the candidate standards with a verify list.
- Open every source on that list and delete the candidates that do not survive.
- Build the corrective action table with roles and dates.
- Draft the two page administrator memo with the risk paragraph carrying your own numbers.
- Write the in-service outline for the one finding that needs training.
- Read the whole thing against your notes and cut anything you cannot point to.
If step three deletes nothing, you did not open the documents.