Back to the employee interview

ROLE GUIDE 05

Project Controls Connect scope, schedule, cost, and jobsite conditions so teams can make informed decisions early

  • Headquarters
  • Multiple Projects
  • Scope + Progress + Cost
Colleagues at headquarters reviewing project summaries

Based on the day-to-day work of a Project Controls employee at headquarters. The interview has been anonymized.

The people shown are fictional images created for privacy.

PROJECT CONTROLS

Project Controls explains what the numbers mean for the work

Project Controls establishes a baseline from the contract and execution scope, then monitors progress, cost, revenue, and changes against that plan.

The job is not simply to compile reports. It explains why performance diverged from the plan, works with project teams to define a response, and verifies whether that response improved the outcome.

CLOSED-LOOP WORKFLOW

Plan, monitor, respond, and verify

Each review builds on the one before it, creating a stronger baseline for the next decision.

  1. Set the baseline

    Define scope, target progress, schedule, and planned cost from the contract and execution plan.

  2. Update actuals

    Bring progress, cost, and change data to the same reporting date.

  3. Analyze the variance

    Trace the gap to schedule, cost, scope, procurement, or project execution.

  4. Define the response

    Agree on the action, priority, owner, and timing with the responsible teams.

  5. Verify the result

    Recheck the data and jobsite conditions after the action, then document any remaining risk.

READ THE GAP

If progress is 70% but cost is 80%, ask why

Project Controls looks beyond each figure to understand the operational cause of the variance.

Illustrative example · Not actual project data
Progress
70%

Share of the planned work completed to date

Cost incurred
80%

Share of planned cost committed or spent to date

Cost variance vs. progress

10 pts Cost is running ahead of physical progress. Before recommending action, the team checks change orders, material timing, jobsite conditions, and operational efficiency.

DECISION TRACE

A useful report shows how the decision was made

The record ties together the current status, analysis, action, and follow-up so stakeholders can see what changed and why.

  1. Status

    Bring progress, cost, and scope data to one reporting date.

  2. Issue

    Define the difference that requires management attention.

  3. Cause

    Compare the data with input from jobsite teams to locate the source of the variance.

  4. Expected impact

    Assess the likely effect on schedule, profitability, and downstream work.

  5. Response

    Define practical options, priorities, owners, and the next review date.

  6. Follow-up

    Verify the result and document any remaining variance for the next decision.

Meeting-room presentation of project status and response options
Presenting project status, impact, and response options
Cross-functional teams reviewing project information in an office
Reconciling field updates with project data

ONE VIEW, MANY INPUTS

Different teams contribute to one project view

Project Controls reconciles each team’s timing, assumptions, and source data so decisions are based on a consistent picture.

Field Operations
Confirm actual progress, constraints, changes, and executable next steps.
Procurement & Materials
Review purchase and delivery timing, material cost, and supply risk.
Finance & Accounting
Align revenue and cost recognition with billing and closeout timing.
Trade Partners
Confirm scope, completed quantities, changes, and supporting documentation.
Leadership
Review material variances, expected impact, and decision options.

CAPABILITIES

Turn project data into action

The role combines analytical tools with field context, communication, and judgment.

  1. Financial and schedule analysis

    Read baselines, timing, relationships, and trends—not just totals.

  2. Field awareness

    Understand which operational change produced the number in front of you.

  3. Data fluency

    Reconcile information from multiple sources and streamline recurring reviews.

  4. Communication

    Translate different team perspectives into a shared objective and clear action.

  5. Problem solving

    Identify the cause, define a response, and establish how the result will be verified.

GROWTH PATH

Grow from project reporting to portfolio-level decisions

As your experience grows, so do the number of projects you review and the time horizon of the decisions you support.

  1. Report progress and actuals

    Maintain the baseline and explain current performance accurately.

  2. Analyze cost and change impact

    Trace the cause of a variance to its likely schedule and cost effects.

  3. Judge profitability and risk

    Support earlier responses and decisions across multiple projects.

ANONYMOUS VOICE

A number only makes sense when you understand what changed in the work

Dohyeon Hwang (pseudonym) · Project Controls interview at headquarters

“A spreadsheet cannot explain a variance by itself. We compare the data with input from jobsite teams and turn the analysis into a decision the project can act on.”