Skip to main content
Workforce LibreTexts

7.2.1: Step 1 - Reconnect to Your Approved Budget

  • Page ID
    52308
  • \( \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 Step

    Before you can monitor real-world financial performance, you must re-anchor your work to the approved baseline budget created in Milestone 4.

    This step ensures your budget control system starts from:

    • The original budgeted amounts for labor and non-labor costs

    • The correct categorization of costs

    • A traceable structure that aligns with your WBS and execution phases

    This prevents your tracking system from being disconnected, misaligned, or overly simplified. Your cost control model must reflect the plan that was approved—and what you’re now expected to deliver within.🧱 Step-by-Step Instructions

    🔹 1. Retrieve and Review Your Approved Budget (Milestone 4)

    Start by reopening the full budget you submitted for Milestone 4. This should include:

    • Total labor cost

    • Total non-labor cost

    • Breakdown by role, category, or phase

    • Contingency (if included)

    • Assumptions and narrative rationale

    📘 Tip: If you used a table or visual summary, this becomes your cost control baseline. No new costs should be tracked unless approved via scope or change control.

    🔹 2. Create a Cost Structure Mapping Table

    List the budget line items or categories from your approved budget. These are the elements you will now track and compare to actual spend.

    📘 Example Mapping Table:

    Budget Category Description Budgeted Amount Source
    Labor – Business Analyst 60 hours @ $85/hr $5,100 Task 1.2, WBS Level 2
    Labor – Project Manager 45 hours @ $110/hr $4,950 Admin + Milestone Prep
    Software Licenses 5 seats @ $30/mo × 6 months $900 Training platform access
    Travel – Onsite Kickoff Flights, meals, lodging $1,500 Week 2 kickoff session
    Contingency 8% buffer $1,000 Risk-linked (vendor delay)

    📘 Note: Use the same categories and naming from Milestone 4 to ensure consistency across all milestones and control tools.

    🔹 3. Group Budget Items for Tracking

    Decide how you will group or disaggregate cost items for tracking during execution.

    Options include:

    • By cost type: Labor vs. Non-Labor

    • By role: PM, BA, QA, Developer

    • By project phase: Planning, Build, Test, Launch

    • By WBS workstream: Training, Platform Build, Testing, etc.

    • By client billing type: Billable vs. internal, one-time vs. recurring

    📘 Tip: Don’t overcomplicate—choose a grouping strategy that supports visibility, not just formality.

    🔹 4. Define Units of Measurement

    Make clear what unit of cost tracking you’ll use:

    Category Unit of Tracking
    Labor Hours × Hourly Rate = $
    Licenses Per user, per month
    Travel Per trip or event
    Software/Hosting Monthly subscription (fixed or usage-based)

    Clarify:

    • How frequently you will update this (weekly, biweekly)

    • What documentation will verify actual cost (timesheets, receipts, invoices, effort logs)

    🔹 5. Identify Risk-Prone Budget Areas

    Highlight any categories that are:

    • Historically prone to overrun (e.g., developer time, vendor services)

    • Highly dependent on third parties (e.g., hosting, training vendors)

    • Priced based on assumptions that may change (e.g., usage-based tools)

    Flag these items for closer monitoring or early warning thresholds.

    📘 Example:

    “Cloud Hosting: Assumes base-level instance. Will monitor monthly usage to avoid auto-scaling charges.”

    🔹 6. Establish the Version Control Baseline

    Label your budget control system with:

    • A baseline version date (e.g., “Budget v1 – Approved Apr 1”)

    • A note that all variance will be measured against this version only

    • A reference to your scope change and escalation protocol for any budget revisions

    📘 Tip: Add a header or footer note to your Budget Tracking Log and Variance Table that says:

    “All tracking reflects comparison to Milestone 4 Budget (v1, Approved Week 6). Changes beyond original scope require sponsor sign-off.”

    ✅ Deliverables from This Step

    By the end of this step, you should have:

    ✔️ A complete mapping of approved budget line items
    ✔️ Grouping categories for cost tracking
    ✔️ Defined units of measurement per cost type
    ✔️ Flagged risk-prone cost areas
    ✔️ A clearly defined budget baseline for control comparison

    This sets you up to begin tracking actual spend in Step 2 using your Budget Tracking Log.

     


    7.2.1: Step 1 - Reconnect to Your Approved Budget is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by LibreTexts.

    • Was this article helpful?