2.5: Submission Checklist
- Page ID
- 49212
\( \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{\ket}[1]{\left| #1 \right>}\)
\(\newcommand{\bra}[1]{\left< #1 \right|}\)
\(\newcommand{\braket}[2]{\left< #1 \vphantom{#2} \right| \left. #2 \vphantom{#1} \right>}\)
\(\newcommand{\braopket}[3]{\left< #1 \vphantom{#2}\vphantom{#3} \right| #2 \vphantom{#1}\vphantom{#3} \left| #3 \vphantom{#1}\vphantom{#2} \right>}\)
\(\newcommand{\qmvec}[1]{\mathbf{\vec{#1}}}\)
\(\newcommand{\op}[1]{\hat{\mathbf{#1}}}\)
\(\newcommand{\expect}[1]{\langle #1 \rangle}\)
\(\newcommand{\dfn}[1]{\emph{\textbf{#1}}}\)
Submission Checklist – UCMS Project Charter
Deliverable: UCMS Project Charter
Use this checklist before you submit. You are responsible for ensuring your work is client-ready.
Document Structure & Completion
- Header Section – Project title, your name, date, and version number included
- Purpose / Objective – Explains UCMS’s core problem and what the chartered work aims to achieve
- Business Context and Alignment – Clearly ties the project to UCMS’s mission, strategic drivers, or pain points
- Scope Overview – Clearly outlines what’s included in the planning effort and what’s excluded
- Project Constraints – Lists and ranks key constraints (e.g., timeline, compliance, scope) with justification
- Success Criteria – Contains 3–5 specific, measurable outcomes that define success
- Stakeholders and Roles – Names real people (from the memo), titles, and clearly defines their role and influence
- Risks and Assumptions – Identifies at least two real risks and two assumptions with neutral language
- Deliverables and Timeline – Includes a table with 3+ key deliverables and target dates
- Approval Section – Table created with columns for name, title, signature, and date (signatures may be placeholder text)
Writing, Formatting & Professional Tone
- Client-appropriate tone – Written for UCMS stakeholders, not academic instructors
- Clear organization – Uses headings, white space, and tables to improve readability
- Narrative + structure – Each section flows with context, not just bullet points
- No filler or vague phrases – Avoids phrases like “to improve operations” without specifics
- Document is polished – No spelling, grammar, or formatting issues
- File format is correct – .docx or .pdf, named UCMS_Project_Charter_YourLastName.docx
Best Practice Integration
- Anchored in Purpose – Charter opens with a compelling “Why now?”
- Named Constraints – Constraint priorities are declared and explained
- Defined Success – Measurable indicators are listed and contextualized
- Stakeholder Intelligence – Stakeholders are real, named, and described accurately
- Risks + Assumptions Surfaced – Charter includes realistic risk and assumptions section
- Clear Story with Structure – Entire document reads like a plan, not a form
Final Sanity Checks
- Would I be confident submitting this to the Dean of UCMS?
- Does this document define a project clearly enough that my team could begin planning immediately?
- Does this charter build trust?
- Have I gone beyond filling in a template—and actually made decisions?
File Submission Info
- File name format: UCMS_Project_Charter_YourLastName.docx
- File type: .docx or .pdf
- Upload to: [Specify location: Team Drive, LMS, etc.]
- Due date: [Insert milestone due date]