7.4: Submission Checklist
- Page ID
- 52247
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\( \newcommand{\dsum}{\displaystyle\sum\limits} \)
\( \newcommand{\dint}{\displaystyle\int\limits} \)
\( \newcommand{\dlim}{\displaystyle\lim\limits} \)
\( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)
( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\id}{\mathrm{id}}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\kernel}{\mathrm{null}\,}\)
\( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\)
\( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\)
\( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)
\( \newcommand{\vectorA}[1]{\vec{#1}} % arrow\)
\( \newcommand{\vectorAt}[1]{\vec{\text{#1}}} % arrow\)
\( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vectorC}[1]{\textbf{#1}} \)
\( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)
\( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)
\( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\(\newcommand{\longvect}{\overrightarrow}\)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)🎯 Purpose of This Checklist
This checklist serves as a final validation guide for your submission. It ensures that all deliverables are:
-
Fully developed and populated with meaningful, traceable data
-
Consistent with your previous milestones (especially Milestone 4)
-
Designed for actual execution, not just academic completion
-
Usable by a project manager, stakeholder, or QA lead in a real project environment
This checklist also reinforces professional readiness—your submission should function as a leadership toolkit, not just a set of templates.
✅ SECTION 1 – Budget Tracking Log
| ✔ | Criteria |
|---|---|
| ☐ | All cost categories from Milestone 4 are included (labor, non-labor, contingency if used) |
| ☐ | Each category includes: Planned Budget, Actual to Date, Remaining Budget, % Burned |
| ☐ | Status field clearly flags On Track / At Risk / Over Budget |
| ☐ | Notes column is used for updates, source references, or explanations |
| ☐ | All formulas (Remaining, % Burned) are functioning and correct |
| ☐ | Formatting aids readability (tables aligned, currency symbols used, color coding optional) |
✅ SECTION 2 – Variance Analysis Table
| ✔ | Criteria |
|---|---|
| ☐ | Planned vs. Actual spend shown side-by-side per category |
| ☐ | Variance ($ and %) calculated and displayed |
| ☐ | Each variance includes a Direction: Over / Under / On Target |
| ☐ | Root causes or triggers are described briefly and clearly |
| ☐ | Action Taken field describes how issue was resolved or mitigated |
| ☐ | Language used is clear, professional, and execution-oriented |
✅ SECTION 3 – QA Acceptance Criteria Checklist
| ✔ | Criteria |
|---|---|
| ☐ | Includes at least 3–5 major deliverables from project scope or WBS |
| ☐ | Each deliverable has clearly stated SMART quality criteria |
| ☐ | QA method is defined (e.g., peer review, test, walkthrough, approval) |
| ☐ | Reviewer/approver roles are specified (internal or client-facing) |
| ☐ | Status field shows current acceptance state (Pending, Accepted, Rework Needed) |
| ☐ | Due dates and tracking notes included where applicable |
| ☐ | Matches terminology from previous milestones |
✅ SECTION 4 – Defect Log / QA Tracker
| ✔ | Criteria |
|---|---|
| ☐ | Each defect or issue is uniquely identified (e.g., DEF-001) |
| ☐ | Deliverable or scope area is referenced |
| ☐ | Severity is classified (High, Medium, Low) |
| ☐ | Owner is assigned for follow-up |
| ☐ | Status column used consistently (Open, In Progress, Resolved, Deferred) |
| ☐ | Resolution date and actions taken are documented |
| ☐ | Optional: Sorting/filtering enabled, visual aids (color codes, icons) used effectively |
✅ SECTION 5 – Quality Escalation Process (Optional but Recommended)
| ✔ | Criteria |
|---|---|
| ☐ | Triggers for escalation are clearly defined (e.g., repeated rejections, unresolved issue) |
| ☐ | Escalation levels shown with decision owners (Team → PM → Sponsor) |
| ☐ | Timeline expectations for each escalation level included |
| ☐ | Matrix, table, or flow diagram is clearly structured and easy to follow |
| ☐ | Linked to quality tracker (or references it in application) |
| ☐ | Scenario examples (even hypothetical) are used to validate its function |
✅ FORMATTING & PRESENTATION
| ✔ | Criteria |
|---|---|
| ☐ | All components are labeled clearly and presented in professional layout |
| ☐ | Consistent headers, fonts, and alignment used throughout |
| ☐ | Tables are cleanly structured (no broken columns or unclear labels) |
| ☐ | No placeholder text or empty fields remain |
| ☐ | Units (e.g., $USD, hours, %) are used consistently |
| ☐ | Document includes page numbers, title section, and version/date footer (optional) |
✅ SUBMISSION LOGISTICS
| ✔ | Criteria |
|---|---|
| ☐ | File type submitted as PDF, DOCX, XLSX, or Google Doc/Sheet (as assigned) |
| ☐ | File name uses correct format: Milestone6_BudgetAndQualityControls_TeamName |
| ☐ | All components submitted together or in clearly labeled attachments |
| ☐ | Submitted to the correct platform/location by the deadline |
| ☐ | All team member names listed on title page or first section |
🔁 Final Self-Check Questions
-
Would your QA Tracker be helpful during a stakeholder review or product demo?
-
Could your Budget Tracking Log support a conversation about financial health with your sponsor?
-
Are all deliverables and budget categories traceable to Milestones 3–5?
-
If asked to explain one over-budget item or quality escalation, would your documentation support that answer?
-
Would your tools still be usable by someone taking over your project midstream?

