6.4: Submission Checklist

Purpose of This Checklist

This checklist is your final quality assurance tool. It ensures that your submitted Control Toolkit is:

• Complete and properly structured
• Internally consistent with earlier milestones (scope, WBS, milestones, budget)
• Designed for real-world use during project execution
• Ready to support weekly reporting, issue tracking, and status reviews

You are not just submitting templates—you are submitting tools of leadership.

SECTION 1 – Scope Control Register

✔	Criteria
☐	Includes all Level 2 and major Level 3 deliverables from WBS
☐	Each deliverable includes owner, due date, and status field
☐	Status indicators used consistently (e.g., Not Started, In Progress, Completed)
☐	Optional: Includes % complete or blocker notes
☐	Includes scope change flag (Yes/No) and explanation field
☐	Reflects current status and scope change history (if any)

SECTION 2 – Schedule Progress Tracker

✔	Criteria
☐	Task or milestone names are consistent with WBS/schedule from Milestone 3
☐	Includes planned vs. actual start and finish dates (if available)
☐	Includes status field (RAG indicator, % complete, or tracking label)
☐	Notes or blockers documented for items at risk or delayed
☐	Tracker is organized by owner, date, or phase
☐	Visual clarity: status color, symbols, or formatting aid scan-ability

SECTION 3 – Change and Escalation Protocol

✔	Criteria
☐	Clearly explains when and how issues are escalated
☐	Identifies escalation thresholds (e.g., delay >3 days, unplanned task added)
☐	Shows escalation flow: task owner → PM → Sponsor
☐	Includes a change log format or example
☐	At least one sample issue or change is documented
☐	Written in a concise, usable format (procedure or diagram)

SECTION 4 – Control Dashboard (Lite Version)

✔	Criteria
☐	One-page status overview designed for stakeholder communication
☐	Includes project name, date, and high-level health status
☐	Lists at least 2–3 current milestones and their status
☐	Provides summary progress metric (e.g., % complete, tasks done)
☐	Top 2–3 issues or risks are flagged with owner and status
☐	Includes recent or pending scope changes
☐	Lists next actions or upcoming deadlines
☐	Designed for scan-ability (colors, icons, tables, formatting)

FORMATTING & PRESENTATION

✔	Criteria
☐	All tables are clean, labeled, and legible
☐	Consistent language used across all documents (e.g., “Complete” vs. “Done”)
☐	No placeholders, incomplete rows, or missing columns
☐	Fonts, dates, headings, and field types are consistent
☐	File is named correctly and saved in requested format
☐	Final version is spell-checked and professionally formatted

SUBMISSION LOGISTICS

✔	Criteria
☐	All four required tools (Scope Register, Schedule Tracker, Escalation Protocol, Dashboard) are included
☐	Submitted as one document or clearly labeled separate files
☐	File type matches instructions (.docx, .pdf, .xlsx, Google link, etc.)
☐	File name follows naming convention: Milestone5_ControlToolkit_TeamName
☐	Submitted to correct location on time
☐	Team member names and date listed on cover page or top of submission

Final Self-Check Questions

• Would your team use these tools to track work next week?
• Would a sponsor or stakeholder understand your dashboard without a walkthrough?
• Are there decisions that could be made from this information?
• Is your change escalation process practical, or just decorative?
• Have you shown actual progress and possible friction—not just status symbols?