daBongo LMS AI Training Courses

Copilot as a Review and Quality Assurance Partner

Lesson 3: Building Custom Review Checklists

Lesson Objectives

By the end of this lesson, students should be able to:

  • Build a custom review checklist for any recurring work product type
  • Design checklists that catch both common errors and role-specific risks
  • Implement the checklist review habit sustainably
  • Refine checklists based on what errors they actually find in practice

Lesson Content

Why custom checklists beat general review guidance.

General quality advice ("be clear, be accurate, be relevant") is not actionable in practice. A checklist built around your specific work products, your audience's expectations, and the most common errors in your area produces consistent, measurable improvement.

Building a review checklist with Copilot.

"I frequently produce [work product type] for [audience and purpose]. Build me a review checklist that catches the most common errors and gaps in this type of work. Organize it into categories: (1) content quality, (2) structural integrity, (3) audience appropriateness, (4) factual accuracy requirements, and (5) common professional errors in this type of document. For each item, write it as a specific yes/no question I can answer about my own document."

The yes/no question format.

"Is the executive summary clear and present?" – yes/no, immediately actionable. "Is the document good?" – not actionable.

Every checklist item should be a specific yes/no question with an action-forcing answer. If the answer is no, the item identifies exactly what needs to be fixed.

Role-specific risk items.

Add items for the risks specific to your role and context:

For a financial analyst: "Have all figures been verified against the source data within the last 24 hours?" For a hiring manager: "Does this job posting use any language that could constitute disparate impact under employment law?" For a project manager: "Are all dependencies explicitly stated and do they match the project timeline?"

These role-specific items catch the expensive errors in your specific professional context.

Implementing the checklist as a habit.

Build the habit by: applying the checklist to a work product you are about to finalize, noting which items caught actual errors, and removing items that never catch anything after three months of use. A checklist that is too long to use consistently is worse than a shorter checklist used every time.

Refining based on real use.

Every six to eight weeks: "Here is my current checklist [paste]. I have been using it for [time]. These items consistently catch problems: [list]. These items have never caught anything: [list]. Help me refine the checklist to keep the effective items, improve the ineffective ones, and add any gaps I am likely missing based on the type of work I described."

Log in and enroll to access lesson quizzes.

Scroll to Top