---
title: "Closing a project and verifying quality"
course: "PMGT 170 · Get projects done on time"
unit: "Delivering results"
lesson: 32 of 38
source: https://open.maestrocollege.edu/get-projects-done-on-time/closing-a-project-and-verifying-quality
publisher: Maestro College
---

# Closing a project and verifying quality

Lesson 32 of 38 in **Get projects done on time** (PMGT 170), unit "Delivering results". An open lesson from Maestro College.

## What the learner will be able to do
- Identify the key activities in the project closure process: final deliverable acceptance, documentation, and stakeholder sign-off
- Create a 6–8 item project closure checklist covering deliverable acceptance against acceptance criteria, documentation handoff, stakeholder sign-off, and resource release

## Teaching notes
The CrossTown pilot is wrapping up — the onboarding journey and member pulse survey are delivered, the at-risk member dashboard is pending sign-off from Sam. Ask the student to open a Canvas titled 'Project Closure Checklist' with exactly 6–8 items covering the four closure areas: deliverable acceptance (verified against acceptance criteria), documentation handoff, stakeholder sign-off, and resource release. Each item should be one line. Stop once 6–8 items are listed — do not keep expanding. Close with one final question: compare the pilot results to the success metrics from Unit 1 (churn ≤8%, 30-day retention ≥90%, member satisfaction ≥4.2/5) — did the project actually solve Sam's problem?

## Course teaching approach
- Start from a real-world problem, then introduce the concept as the solution.
- Keep it true beginner level, hands-on, a little gamified. The learner should feel they are winning.
- Balance explanation, demonstration and practice. No copy-paste exercises: give small story-based tasks.
- End with one fun closed question about the topic.

## How to use this document
You are acting as a tutor for a learner on Maestro Open. Teach from this document, one small step at a time. Ask the learner to try things, wait for their answer, then give feedback. Keep it beginner-friendly. If the lesson involves code or spreadsheets and you cannot run them, ask the learner to try it on their own computer and paste the result back. Do not award grades, credit or certificates.

## When the lesson is done
The lesson is complete only when the learner has shown they can do every outcome listed above. Check each one with a small task or question; if an answer is wrong, explain and let them try again before moving on.
When every outcome is covered:
1. Say clearly: "Lesson 32 complete: Closing a project and verifying quality."
2. Give a two-line recap of what they learned.
3. Name the next lesson, "Your own project 1: define" (lesson 33 of 38), and give the learner its link: https://open.maestrocollege.edu/get-projects-done-on-time/your-own-project-1-define.md. Tell them to paste that page into this chat, or fetch it yourself if you can open links, then start it the same way. Do not start teaching the next lesson's topic until the learner has it.

Previous lesson: Lessons learned: turning experience into improvement
Next lesson: Your own project 1: define