Skip to main content
Engineering LibreTexts

Chapter 4: 3 Slide Check-In

  • Page ID
    116283
  • \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \( \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{\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}\)

    Guidelines for Preparing a 3-Slide Weekly Check-In for Mechanical Engineering Capstone Projects

    The purpose of a 3-slide check-in is to maintain project momentum, provide updates to your advisors or stakeholders, and receive feedback. Below are detailed instructions on creating and presenting these slides.


    Slide 1: Recap of the Plan from Last Week

    Purpose: Show how you planned to progress since the last check-in.

    Content Suggestions:

    • Title: "Recap of Last Week’s Plan"
    • Key Elements to Include:
      • Objectives or milestones planned for last week.
      • Tasks assigned to each team member.
      • Specific deliverables or outputs expected.
    • Visuals:
      • Gantt chart snippet showing progress and schedule.
      • Diagram of the workflow or planned system.
      • Photos/screenshots of designs, CAD models, or schematics from the planning phase.

    Notes Section:

    • Provide a detailed description of each point in bullet form.
    • Mention who was responsible for each task and whether it was on track.

    Primary Contact for This Slide:

    • Indicate which team member is responsible for the plan and will answer questions related to this slide.

    Slide 2: Work Done This Week and Results

    Purpose: Highlight the team’s accomplishments and show tangible progress or results.

    Content Suggestions:

    • Title: "Work Completed and Results This Week"
    • Key Elements to Include:
      • Summary of tasks accomplished (e.g., designs finalized, prototypes built, tests conducted).
      • Quantifiable results or progress (e.g., test data, calculations, or simulations).
      • Challenges encountered and how they were addressed.
    • Visuals:
      • High-quality images or videos of prototypes, experiments, or models.
      • Graphs or charts summarizing data.
      • Screenshots of simulation results, CAD renders, or FEA outputs.

    Notes Section:

    • Provide additional context and technical details for each result.
    • Explain any challenges, how they were resolved, and any deviations from the plan.

    Primary Contact for This Slide:

    • Specify who led the work presented and will address related questions.

    Slide 3: Preliminary Plan for Next Week

    Purpose: Present a roadmap for the upcoming week, highlighting priorities and deliverables.

    Content Suggestions:

    • Title: "Plan for Next Week"
    • Key Elements to Include:
      • High-level goals for the coming week.
      • Specific tasks for each team member.
      • Deadlines or milestones.
      • Any resources, materials, or assistance needed.
    • Visuals:
      • Updated Gantt chart or timeline showing next steps.
      • Annotated design iterations or schematics of planned work.
      • Flowchart outlining the next stages of the process.

    Notes Section:

    • Elaborate on the specific steps for each task.
    • Mention potential risks and contingency plans.
    • List any questions or decisions that require feedback from advisors or stakeholders.

    Primary Contact for This Slide:

    • Identify the team member responsible for coordinating the next week’s tasks.

    General Presentation Tips

    1. Slide Design:
      • Keep slides visually appealing and uncluttered.
      • Use bullet points and limit text on the slides themselves.
      • Ensure all visuals are relevant, labeled, and clear.
    2. Notes Section Usage:
      • Treat the notes section as an extended narrative or script.
      • Provide detailed explanations and technical information that may not fit on the slide.
      • Anticipate possible questions and address them in the notes.
    3. Presentation Delivery:
      • Practice as a team to ensure a smooth flow.
      • Each team member should be prepared to present their assigned slide.
      • Be concise but thorough in your explanations.
    4. Be Prepared for Discussion:
      • Anticipate technical and logistical questions about your progress and plan.
      • Have backup data or additional visuals ready in case they are requested.
    5. Professionalism:
      • Dress professionally or as required for the presentation setting.
      • Ensure all team members are engaged and attentive during the discussion.

    Checklist Before the Check-In

    • Are all visuals (figures, schematics, videos) ready and clear?
    • Are the notes sections filled with detailed explanations?
    • Has each team member rehearsed their slide and is ready to discuss it?
    • Is the contact person for each slide clearly indicated?
    • Has the presentation been proofread for typos and clarity?

    By following these guidelines, your team will deliver a polished and professional weekly check-in that highlights your progress and demonstrates your organization and teamwork.


    This page titled Chapter 4: 3 Slide Check-In is shared under a CC BY-NC-ND license and was authored, remixed, and/or curated by Joshua P. Steimel.

    • Was this article helpful?