HKSM

A checklist is a structured list of steps, criteria, or items used to ensure completeness and consistency in project work. Teams use checklists to prevent omissions, promote quality, and support audits across processes such as risk, quality, safety, and procurement.

Definition

See the short definition above.

Key Points

• Simple, low-cost tool that improves reliability and repeatability.
• Tailored to the project context, deliverables, and lifecycle phase.
• Useful across predictive, hybrid, and agile approaches.
• Supports compliance, quality control, and readiness reviews.
• Items should be clear, actionable, and testable.
• Maintain version control and traceability to standards.

Purpose

• Ensure critical steps are not missed during planning and execution.
• Standardize acceptance criteria and definition of done for deliverables.
• Enable consistent audits, inspections, and handoffs.
• Accelerate onboarding by making tacit know-how explicit.
• Provide evidence of compliance to organizational and regulatory standards.

Field Definitions

• ID - Unique identifier for each checklist item.
• Category or Process - Area of work or process step the item supports.
• Item or Check - Specific action or condition to verify.
• Acceptance Criteria or Standard - Measurable condition that defines done.
• Owner or Role - Person or role responsible for completing the check.
• Status - Not started, In progress, Done, or N/A.
• Evidence or Reference - Link or artifact proving completion.
• Date Checked - When the item was verified.
• Frequency - When to apply the item (per deliverable, per iteration, per phase).
• Comments or Lessons - Notes, issues found, and improvement ideas.

How to Create

1. Define the scope and objective of the checklist (process, deliverable, or review).
2. Gather inputs from standards, organizational process assets, regulations, and lessons learned.
3. Co-create items with SMEs and the team to ensure practicality and buy-in.
4. Write clear, binary checks with measurable acceptance criteria and required evidence.
5. Group items by category or process step and assign owners or roles.
6. Pilot the checklist on a small activity, collect feedback, and refine wording.
7. Baseline the checklist, apply version control, and publish location and update cadence.

How to Use

• Introduce the checklist during planning and working sessions; align with definition of done.
• Use in readiness reviews, quality control, risk identification, and procurement evaluations.
• Facilitate a read-check-act flow: read each item, perform or verify, mark status, capture evidence.
• Log defects or nonconformities, create follow-up actions, and track to closure.
• Monitor completion rates and recurring misses to drive process improvements.
• Update items through change control and integrate updates into team ceremonies.

Ownership & Update Cadence

• Owner: project manager or process owner; SMEs maintain content accuracy.
• Contributors: team members who apply the checklist and suggest improvements.
• Cadence: baseline in planning, review at phase gates, per iteration, or monthly as needed.
• Trigger updates after audits, incidents, regulatory changes, or lessons learned.
• Version and communicate changes; archive prior versions for traceability.

Example Rows

• 01 - Planning - Stakeholder list validated - Criteria: all key roles identified and ranked - Owner: PM - Status: Done - Evidence: stakeholder register - Frequency: once per phase.
• 02 - Requirements - Acceptance criteria defined - Criteria: testable conditions per user story or requirement - Owner: BA - Status: In progress - Evidence: backlog or RTM - Frequency: per item.
• 03 - Quality - Peer review completed - Criteria: checklist signed by reviewer, no open high defects - Owner: Developer - Status: Done - Evidence: review record - Frequency: per deliverable.
• 04 - Risk - New risks screened - Criteria: at least one pass through risk prompts - Owner: Team - Status: Done - Evidence: risk log update - Frequency: per iteration.
• 05 - Procurement - Supplier deliverable accepted - Criteria: meets spec and acceptance tests - Owner: QA - Status: N/A - Evidence: test report - Frequency: per delivery.
• 06 - Transition - Handover complete - Criteria: docs stored, training delivered, access transferred - Owner: PM - Status: Not started - Evidence: handover record - Frequency: once per project.

PMP Example Question

A team frequently skips small but critical steps during handoffs, causing rework. What should the project manager implement first to reduce recurrence without adding heavy bureaucracy?

1. Create a more detailed WBS with additional work packages.
2. Implement a lightweight checklist with explicit acceptance criteria for handoffs.
3. Increase testing hours to catch issues earlier.
4. Escalate to the sponsor to request more budget for oversight.

Correct Answer: B — Implement a lightweight checklist with explicit acceptance criteria for handoffs.

Explanation: A checklist standardizes critical steps and criteria, reducing omissions with minimal overhead. Other options do not directly address the behavior causing missed steps.