Lesson Content

The recurring deliverable problem.

Every professional has recurring deliverables – documents, reports, presentations, or outputs they produce repeatedly in the same format for similar audiences. Each one should meet the same quality standard. But without a system, quality depends entirely on how thorough and focused the author happens to be on any given day – which varies significantly.

Custom review checklists create a quality floor. They do not guarantee excellence – but they prevent the systematic omissions and errors that occur when important steps are left to memory and individual energy.

Building a custom checklist with Gemini.

"I regularly produce [deliverable type] for [audience] at [frequency]. Help me build a comprehensive review checklist for this deliverable. The checklist should cover: (1) required content elements – what must always be present, (2) quality standards for each element – what does 'good' look like vs. 'just present', (3) common errors and omissions for this type of document – things I might miss under time pressure, (4) format and presentation requirements, and (5) a final pre-submission check – the last things to verify before sending. Structure this as a checklist I can run through in under 10 minutes."

Review the generated checklist and add:

• Any organization-specific requirements (approvals needed, formats required, routing steps)
• Any recurring errors from your own experience ("I always forget to attach the supporting data file")
• Any audience-specific requirements that vary from the generic standard

Refining checklists based on use.

A checklist that never changes is a checklist that stops being used. After using any checklist for 4-6 weeks, update it:

"I have been using this checklist [paste checklist] for [time period]. Here is what I have observed: (1) these items consistently pass and may no longer need checking every time: [list], (2) these items I still regularly miss: [list], (3) I have discovered new error patterns not currently on the list: [describe]. Revise the checklist based on this feedback."

Checklists that are refined based on actual use become progressively more accurate to your specific error patterns – and more efficient to apply.

The pre-submission confirmation.

The most critical function of a checklist is the final pre-submission confirmation – the 5-minute review before clicking send that catches last-minute errors. Build a dedicated pre-submission section:

"For [deliverable type], what are the 5-7 most critical final checks – the things that, if wrong when the document is submitted, would cause immediate problems regardless of how good the rest of the document is?"

Examples typically include: correct recipient address, correct attachment, current version (not a draft from last week), correct date and period references, and signature or approval present.

The living checklist principle.

A checklist is a hypothesis about what matters for quality – updated by experience. The best checklists are not perfect on first generation; they become valuable through iteration. Treat every near-miss and every "I wish I had checked X" as a checklist update opportunity. A checklist that has been used and refined 20 times is more valuable than one generated perfectly from scratch.