Finance & Budgeting Free · self-study ~60 min

Post-SteerCo Cost Forecast Variance Review

After a steering committee flagged a cost forecast discrepancy, the Program Director requests a focused one-on-one with the reporting lead to assess data integrity and governance robustness before deciding on escalation. The discussion prioritizes clarifying root causes and corrective actions over technical tool audits.

 Level

What you’ll be able to do

Dialogue

Beginner version

Marcus Thorne
Hello Elena. Thank you for coming. We are here to talk about one problem. There is a difference between the old cost number and the new cost number. I want to tell you why this happened. I also want to tell you what we are doing to fix it.
Elena Vance
Good. I need to understand this clearly. I do not want to know every small detail. I want to know: can we trust the numbers we use to make big decisions? Is this a small mistake, or is there a big problem with how we work?
Marcus Thorne
Okay. The number changed because of three things that did not match. First, there is the cost list in the Verolane Group. Second, there is the cost data from our computer system. Third, there is the report we showed to the managers. The problem was only in one part of the project. The total budget is still okay.
Elena Vance
You said 'one part.' I need to understand this. Is it just a few small work items, or is it a bigger group of costs?
Marcus Thorne
It is about some engineering services. These services help many projects at the same time. In the Verolane Group, we write these costs in a big general group. We do not write them in small detailed groups. The problem is that our plan said costs would match the detailed work. But that is not true for these shared services.
Elena Vance
So the system expected detailed numbers, but the real data is not detailed?
Marcus Thorne
Yes, that is right. The plan has good detail. But the costs are put together in one big group. This is okay for daily work. But when we make a cost forecast, we need a clear rule about how to split these costs. We had a rule, but we did not use it the same way every time in the reports.
Elena Vance
That is a problem. Why did nobody see this mistake before?
Marcus Thorne
The difference was small before. Our checks said it was okay. But then the project got bigger. More work happened. The costs went up. The difference got bigger too. So we saw the problem now, not before.
Elena Vance
So the problem was always there, but it was small. It got big when the project got bigger.
Marcus Thorne
Yes. But I want to say something important. The whole cost plan is not wrong. Only one rule was not written down clearly. That rule said these costs go up the same way as the planned work. But that is not true.
Elena Vance
But if the rule was not written down, is that not a problem with how we manage the project? Important rules must be written down.
Marcus Thorne
I agree. At the start, the plan was new and simple. We did not write every rule. Now the project is bigger. We need better rules. So now we are writing them down properly.
Elena Vance
I need to know clearly. Is this a one-time fix, or do we need to change the forecast plan?
Marcus Thorne
We need to change the plan a little. The data in the computer system is correct. The budget in the Verolane Group is still the same. But we need to change how we use the data to make forecasts.
Elena Vance
Okay. So the numbers are correct, but the story we told about them was not complete.
Marcus Thorne
Yes. The forecast used old rules. Those rules are not right for the project today. The project is bigger now.
Elena Vance
Good. Now, who is responsible for this problem? Is it the computer system, the cost team, or the reporting team?
Marcus Thorne
It touches all three areas. But the main responsibility is mine. I manage the project system design. The cost team followed the rules. The report team showed what the system said. The problem was that nobody checked if the rules still worked as the project grew.
Elena Vance
Thank you for saying that clearly. Now tell me your plan to fix this. Keep it simple. I do not need every detail.
Marcus Thorne
We have two types of actions. First, the fast actions. We changed the rule for how we share these engineering costs. This changes the forecast number, but it does not change the budget or the old cost data. You can see this change clearly.
Elena Vance
Did this change cause the difference in the numbers we saw?
Marcus Thorne
Yes. The difference appeared because we fixed a hidden problem. The cost team and the finance team both checked this change. The change stays inside the budget we already have.
Elena Vance
And what is the plan for the future?
Marcus Thorne
For the future, we will write down the cost rules properly. We will check these rules every time we do a forecast. We will also make sure the Verolane Group data and the reports use the same dates and the same version of the numbers.
Elena Vance
Good. But how do we stop this problem from happening in other parts of the project?
Marcus Thorne
We will do two things. We will check all cost groups that use shared services. We will also add a new check. This check will look at the rules and ask: are these rules still correct?
Elena Vance
So before, we checked if the numbers were entered. Now we also check if the numbers mean the right thing.
Marcus Thorne
Yes. That is exactly right.
Elena Vance
One more question. At the big manager meeting, this problem was a surprise. How do we stop surprises like this in the future?
Marcus Thorne
We will give better information before problems become big. If a rule looks like it may have a problem, we will say so in the report. Then the managers will understand why a number changes later.
Elena Vance
That is important. For managers, a surprise is very bad, even if the problem is small.
Marcus Thorne
I agree. And I want to say clearly: if I thought this was a serious problem, I would have told you immediately. I looked at the data carefully. I do not think this is a serious problem.
Elena Vance
Okay. I will not take this to the senior managers now. But I need a short written note. It must explain the problem, what we did, and what we will change. No technical words. One page only.
Marcus Thorne
I will write it before the end of this week. It will be simple and clear. I will focus on what this means for decisions, not on technical details.
Elena Vance
Good. Marcus, you did this well. The problem is not so bad. But I care more about how you found it and what you did. Keep working like this.
Marcus Thorne
Thank you, Elena. I will make sure we learn from this. We will not treat it as just a one-time fix.
Elena Vance
Good. That is what I wanted to hear. We can stop now.

Intermediate version

Marcus Thorne
Thanks for finding time for this, Elena. I want to take you through the cost forecast issue that came up at the Steering Committee. I'll explain what caused the variance, separate the data problems from any issues with the cost logic itself, and cover the steps we're taking to address it. Hopefully that gives you enough to decide whether you need to escalate.
Elena Vance
That's exactly what I need from this conversation. My main concern isn't the technical detail, it's whether we can rely on the financial data we use for strategic decisions. If this is just a data entry error, that's manageable. But if it points to a deeper problem with our cost logic or governance, that's a different matter. So, what triggered this in the first place?
Marcus Thorne
To give you the key picture: the variance between the previous forecast and the updated Estimate at Completion doesn't reflect a general cost overrun, and it wasn't caused by late scope changes. It came from a mismatch between three things, the cost structure in the Verolane Group, the actual cost data coming from the ERP, and how those figures were combined in the executive BI reports. The problem was limited to one area and didn't affect the overall cost baseline.
Elena Vance
When you say 'one area,' I need to be more specific. Are we talking about a small number of work packages, or a wider cost category that wasn't estimated well enough?
Marcus Thorne
It's a cluster of indirect engineering services that support several projects at once. In the Verolane Group, these costs are recorded at a high-level code rather than broken down by the individual planning activities they relate to. The Estimate to Complete logic assumed there was a direct link between planned work and cost capture, but that assumption doesn't work for shared services.
Elena Vance
So the system was set up to expect a level of detail that doesn't actually exist in how we operate?
Marcus Thorne
Exactly. The planning data is detailed enough, but the cost data was deliberately kept at a higher level to keep things manageable. That's a reasonable design choice, but it means you need a clear allocation rule when forecasting. That rule existed in the Verolane Group, but it wasn't being applied consistently in the BI reports used for the Steering Committee.
Elena Vance
That's a concern. Why didn't our governance process pick this up sooner?
Marcus Thorne
The variance stayed within acceptable limits until the most recent closing period. The problem only became visible when actual costs increased significantly. As the project scaled up, the gap widened. The underlying logic had a weakness, but it only showed up under greater volume.
Elena Vance
So there was a hidden weakness that only became apparent when the project grew.
Marcus Thorne
That's right. But I want to be clear, this doesn't mean the whole cost model is unreliable. It means one specific assumption wasn't formally documented or checked. That assumption was that indirect costs would grow in line with planned work, which isn't actually how these costs behave.
Elena Vance
Let me push back on that. If the assumption wasn't documented, isn't that a governance failure? Important assumptions should be visible and traceable.
Marcus Thorne
I take that point. The reason it was left undocumented is that the cost model was still being developed at the time, and we didn't want to add unnecessary complexity too early. But as the project has grown, what was acceptable before is no longer good enough, which is why we're now formalising this rather than just treating it as a data fix.
Elena Vance
I need a clear answer here. Are we just making a one-time correction, or does the forecast model itself need to be restructured?
Marcus Thorne
Honestly, this has led to a structural improvement. The underlying data is fine, the actual costs from the ERP are accurate and the baseline in the Verolane Group hasn't changed. What we need to improve is the method we use to turn that data into forecasts and management information.
Elena Vance
That's an important distinction. So the figures themselves aren't wrong, but the picture they painted was incomplete.
Marcus Thorne
Precisely. The forecast was working on its original assumptions, but those assumptions no longer match how costs actually behave at this stage of the programme.
Elena Vance
Understood. Now, who owns this issue? Is it a problem with the project management system, with cost control, or with how we report?
Marcus Thorne
It involves all three areas, but the accountability is clear. From a governance perspective, this is a PMIS design issue, and that's my responsibility. Cost control was following the established rules, and reporting was reflecting what the logic produced. The gap was in keeping all three aligned as the programme developed.
Elena Vance
I appreciate you being straightforward about that. Now walk me through your remediation plan, I don't need every detail, just the key thinking.
Marcus Thorne
We're working on two levels, short-term and longer-term. In the short term, we've corrected the cost allocation logic for the indirect engineering services in a controlled way. This adjusts the Estimate to Complete but leaves the baseline and historical actuals untouched. The impact is clearly visible and trackable.
Elena Vance
Was it this adjustment that caused the variance we saw in the first place?
Marcus Thorne
Yes. The variance reflects us bringing a previously hidden element into the open. Both cost control and finance have reviewed and signed off on the change. It also falls within the contingency budget approved at portfolio level.
Elena Vance
And what's the longer-term plan?
Marcus Thorne
Over the longer term, we're converting allocation rules from informal practice into formally governed protocols. That means clear documentation, checks built into forecast cycles, and version control. We're also aligning cut-off dates and data versions between the Verolane Group and the BI tools to avoid timing mismatches that cause confusion.
Elena Vance
That sounds sensible. But how are you making sure this kind of issue doesn't appear in other areas too?
Marcus Thorne
We're doing two things. First, we're reviewing all cost categories that involve shared services or pooled resources. Second, we're adding a governance check that focuses specifically on assumptions during major forecast updates, not just checking whether the data has been entered correctly.
Elena Vance
So the governance focus is shifting from 'have the numbers been entered?' to 'do the numbers still reflect what we actually intended?'
Marcus Thorne
Exactly. That's the step forward in maturity we're making.
Elena Vance
One last question. At the Steering Committee, this came as a surprise. How do we avoid that kind of situation in future?
Marcus Thorne
By improving the narrative we provide. Going forward, if an assumption starts showing signs of risk, even before it becomes a real problem, we'll flag it as an emerging risk. That way, leadership can understand why a forecast might change, rather than being surprised when it does.
Elena Vance
That matters a lot. At this level, how something is communicated can be almost as important as the issue itself.
Marcus Thorne
I completely agree. And I want to be direct: if I had believed this was a genuine control failure, I would have escalated it myself. Based on our analysis, I'm confident we're in a manageable position.
Elena Vance
Alright. Based on what you've told me, I won't escalate this for now. But I do need a short written summary, root cause, actions taken, and governance changes. No technical language, one page, written for senior management.
Marcus Thorne
Understood. I'll have it ready by the end of the week. I'll keep the focus on the decision-making implications rather than the system mechanics.
Elena Vance
Good. And Marcus, you've handled this well. The issue itself worries me less than whether it was caught and managed properly. Keep this level of transparency.
Marcus Thorne
Thank you, Elena. I appreciate the feedback. We'll make sure we take the right lessons from this and treat it as an opportunity to improve, not just a one-off fix.
Elena Vance
That's exactly the right approach. Let's leave it there.

Advanced version

Marcus Thorne
Thank you for making the time, Elena. I appreciate you joining me for this focused discussion. As you know, the purpose of this meeting is to address the specific concern raised during the Steering Committee. I want to walk you through the root causes of the variance in the cost forecast, clearly distinguishing between data integrity issues and fundamental cost logic problems, and outline the corrective actions we are implementing. This context should help you determine whether escalation is warranted.
Elena Vance
That is precisely my objective. I need absolute clarity. I am not interested in a granular technical audit for its own sake. What is critical to me is the reliability of the financial data underpinning our strategic decisions. If this is merely a data entry anomaly, that is one scenario. However, if it points to a flaw in our cost logic or governance framework, that is a far more serious matter. So, let us begin at the source. What precipitated this change, and why?
Marcus Thorne
Understood. To provide a high-level overview, the variance you observed between the previous forecast and the new Estimate at Completion (EAC) does not stem from a general cost overrun, nor did we uncover late-stage scope changes. The discrepancy arises from a misalignment between three elements: the cost structure within the Verolane Group, the actual cost data flowing from the ERP system, and the aggregation methodology used in the BI reports presented to executives. This issue was isolated to a specific segment and did not compromise the overall cost baseline.
Elena Vance
When you refer to a 'specific segment,' I need to be certain. Are we discussing a handful of work packages, or a broader cost category that was inadequately estimated?
Marcus Thorne
It pertains to a specific cluster of indirect engineering services. These services support multiple projects concurrently. Within the Verolane Group, these costs are captured at a high-level cost code, rather than at the granular level of the planning activities they support. The root cause was that the Estimate to Complete (ETC) logic assumed a direct correlation between planned work and cost capture. This assumption does not hold true for shared services.
Elena Vance
So, the system was expecting a level of granularity that does not exist in our operational reality?
Marcus Thorne
Precisely. The planning data possesses sufficient detail. However, the cost data was intentionally aggregated to streamline operations. This design choice is pragmatic. Nevertheless, it necessitates a clear protocol for allocating costs during forecasting. While such a protocol existed partially within the Verolane Group, it was not consistently applied in the BI reports utilized for the Steering Committee.
Elena Vance
That is concerning. Why did our governance checks fail to identify this discrepancy earlier?
Marcus Thorne
That is a valid question. The variance remained within acceptable thresholds until the most recent closing cycle. The issue only surfaced when actual costs escalated. As volumes increased, the gap became more pronounced. In essence, the underlying logic was fragile, but the weakness only manifested as the project scaled.
Elena Vance
So, we had a latent vulnerability that only revealed itself under pressure.
Marcus Thorne
That is accurate. However, I must emphasize: this does not invalidate the entire cost model. It indicates that one specific assumption was not explicitly documented or governed. That assumption posited that indirect costs would increase linearly with planned work. In reality, that is not how these costs behave.
Elena Vance
Let me press you on that. If this assumption was not explicitly documented, does that not constitute a governance failure? Critical assumptions should not remain opaque.
Marcus Thorne
I concur with your perspective in principle. The reason it was accepted at the time is that the cost model was still in its nascent stages. We also sought to avoid overcomplicating the system initially. However, as the project matures, what was once acceptable is no longer sufficient. This is why we are now formalizing this logic, rather than treating it as a simple data correction.
Elena Vance
I need absolute clarity. Is this merely a one-time correction, or does the forecast model itself require structural changes?
Marcus Thorne
The candid answer is that this incident has triggered a structural improvement. The underlying data is sound. The actual costs from the ERP are accurate, and the baseline in the Verolane Group remains unchanged. What requires modification is the methodology we use to leverage this data for forecasting and decision-making.
Elena Vance
That is a crucial distinction. So, the numbers are not erroneous, but the narrative they conveyed was incomplete.
Marcus Thorne
Exactly. The forecast functioned based on its initial assumptions, but those assumptions no longer align with the current scale and cost behavior of the program.
Elena Vance
Understood. Let us discuss accountability. Who owns this issue? Is it a PMIS design flaw, a cost control oversight, or a reporting deficiency?
Marcus Thorne
It sits at the intersection of all three, but accountability is clear. From a governance standpoint, this is a PMIS design responsibility, which falls to me. Cost control adhered to the established rules. Reporting accurately reflected what the logic dictated. The challenge was maintaining alignment among these components as the program evolved.
Elena Vance
Thank you for your transparency. Now, outline your remediation plan. I do not require an exhaustive list. I need to understand your strategic thinking.
Marcus Thorne
We are addressing this across two time horizons: immediate actions and long-term enhancements. In the short term, we have adjusted the cost allocation logic for indirect engineering services in a controlled manner. This modifies the ETC but leaves the baseline and historical actual costs intact. The impact is transparent and easily trackable.
Elena Vance
And did this adjustment create the variance we observed?
Marcus Thorne
Yes. The variance stems from bringing a previously obscured element into the light. This change has been reviewed and approved by both cost control and finance. It also remains within the contingency budget approved at the portfolio level.
Elena Vance
And what about the long-term strategy?
Marcus Thorne
For the long term, we are transitioning allocation rules from informal assumptions to formal, governed protocols. This entails clear documentation, checks during forecast cycles, and version control. We are also synchronizing cut-off dates and versions between the Verolane Group and BI to eliminate timing discrepancies that cause confusion.
Elena Vance
That sounds promising, but how do we prevent this from recurring in other areas?
Marcus Thorne
We are implementing two measures. First, we are auditing all cost categories that utilize shared services or pooled resources. Second, we are introducing a governance check focused on assumptions during major forecast updates, rather than solely verifying data completeness.
Elena Vance
So, governance is shifting from 'are the numbers entered?' to 'do the numbers still reflect our intended meaning?'
Marcus Thorne
Precisely. That is the maturity step we are taking.
Elena Vance
One final question. During the Steering Committee, this issue felt abrupt. How do we prevent that sensation in the future?
Marcus Thorne
By enhancing our narrative. In the future, when assumptions begin to show signs of risk, even before they materialize, we will flag them as emerging risks. This allows leadership to comprehend forecast changes rather than being caught off guard.
Elena Vance
That is significant. At this level, perception is nearly as important as reality.
Marcus Thorne
I completely agree. And to be unequivocal: if I had perceived this issue as a genuine loss of control, I would have initiated escalation myself. Based on our analysis, I am confident that is not the case.
Elena Vance
Very well. Based on your explanation, I will not escalate this at present. However, I require a concise written note outlining the root cause, actions taken, and governance changes. No technical minutiae. One page, executive language.
Marcus Thorne
Understood. I will prepare it by the end of the week, focusing on decision impact rather than system details.
Elena Vance
Good. And Marcus, you handled this effectively. The issue itself concerns me less than how it was identified and managed. Maintain this level of clarity, and we will remain in control.
Marcus Thorne
Thank you, Elena. I appreciate the direct feedback. I will ensure we learn from this and treat it as more than a one-time incident.
Elena Vance
That is precisely what I wanted to hear. Let us conclude here.

Check your understanding

1. According to Marcus Thorne, what were the three system layers whose misalignment contributed to the forecast deviation?

Show answer
The three layers are: 1) the cost structure within the Verolane Group, 2) the actual cost data flowing from the ERP system, and 3) the aggregation methodology used in the BI reports presented to executives.

2. Which specific category of costs was primarily affected by the issue, and why was it more vulnerable than others?

Show answer
The affected category was indirect engineering services. They were more vulnerable because they support multiple projects concurrently and are captured at a high-level cost code rather than at the granular level of planning activities. This aggregation meant the system expected a direct correlation between planned work and cost capture, which does not hold for shared services.

3. Why did the forecast deviation only become visible at this stage of the program rather than earlier?

Show answer
The variance remained within acceptable thresholds until the most recent closing cycle because the underlying logic was fragile but only manifested as the project scaled. As volumes increased, the gap between the assumed linear correlation and actual cost behavior became more pronounced.

Grammar practice (mixed)

Prepositionsself-check

The variance does not stem ______ a general cost overrun, nor did we uncover late-stage scope changes.

Show answer & why
from · 💡 The verb 'stem' is consistently followed by the preposition 'from' when indicating the origin or cause of something.
Conjunctions

If this is merely a data entry anomaly, that is one scenario; ______, if it points to a flaw, it is a far more serious matter.

Show answer & why
however · 💡 The conjunction 'however' is used to introduce a statement that contrasts with or seems to contradict the previous one.
Conditionalsself-check

______ the data integrity issues are resolved, we can proceed with the financial audit.

Show answer & why
Provided · 💡 'Provided' is a conjunction used to introduce a condition that must be met for the main clause to happen.
Modals

You ______ be absolutely clear about the root causes before presenting the findings to the board.

Show answer & why
must · 💡 The modal 'must' expresses strong obligation or necessity, which fits the context of requiring absolute clarity in a business report.
Prepositionsself-check

The report is based ______ the actual cost data flowing from the ERP system.

Show answer & why
on · 💡 The phrase 'based on' is the standard collocation used to indicate the foundation or source of information.

Discussion (practise speaking)

How can organizations ensure that governance checks effectively identify discrepancies before they escalate to leadership levels?

🤔 Think about a time when a governance check failed in your work. What could have been done differently?

Show sample answer
  • Regular audits of shared services and pooled resources can catch issues early.
  • Clear protocols for allocating costs during forecasting prevent misalignment.
  • Documentation of assumptions ensures transparency and accountability.

Ask Phil: Practise explaining a governance failure to a senior manager using the Pickle AI tutor.

What steps should be taken to transition from informal assumptions to formal, governed protocols in cost management?

🤔 Consider how your team handles assumptions. Are they documented and reviewed regularly?

Show sample answer
  • Implement clear documentation for all cost assumptions.
  • Introduce checks during forecast cycles to verify assumptions.
  • Use version control to track changes in protocols.

Ask Phil: Practise outlining a plan to formalize cost assumptions with the Pickle AI tutor.

How can leadership be kept informed about emerging risks in forecasts without causing unnecessary alarm?

🤔 Think about how you communicate risks to stakeholders. Is it clear and timely?

Show sample answer
  • Flag risks early as they appear, even if they do not materialize.
  • Provide clear narratives that explain forecast changes.
  • Focus on decision impact rather than system details.

Ask Phil: Practise communicating emerging risks to a steering committee using the Pickle AI tutor.

What is the difference between a data entry anomaly and a fundamental flaw in cost logic, and how should each be addressed?

🤔 Reflect on a time when you had to distinguish between a simple error and a systemic issue. How did you handle it?

Show sample answer
  • Data entry errors are fixed with corrections, while logic flaws require structural changes.
  • Governance checks should distinguish between the two to apply the right solution.
  • Clear protocols help identify the root cause of discrepancies.

Ask Phil: Practise explaining the difference between data errors and logic flaws to a colleague using the Pickle AI tutor.

Vocabulary

cost forecast
reveal definition An estimate of future project expenses. “I want to walk you through the root causes of the variance in the cost forecast, clearly distinguishing between data integrity issues and fundamental cost logic problems, and outline the corrective actions we are implementing.”
↗
data integrity
reveal definition The accuracy and consistency of information. “I want to walk you through the root causes of the variance in the cost forecast, clearly distinguishing between data integrity issues and fundamental cost logic problems, and outline the corrective actions we are implementing.”
↗
cost logic
reveal definition The reasoning behind how expenses are calculated. “I want to walk you through the root causes of the variance in the cost forecast, clearly distinguishing between data integrity issues and fundamental cost logic problems, and outline the corrective actions we are implementing.”
↗
corrective actions
reveal definition Steps taken to fix a problem. “I want to walk you through the root causes of the variance in the cost forecast, clearly distinguishing between data integrity issues and fundamental cost logic problems, and outline the corrective actions we are implementing.”
↗
financial data
reveal definition Monetary information used for business decisions. “What is critical to me is the reliability of the financial data underpinning our strategic decisions.”
↗
cost baseline
reveal definition The approved budget for a project. “This issue was isolated to a specific segment and did not compromise the overall cost baseline.”
↗
cost code
reveal definition A unique identifier for a budget category. “Within the Verolane Group, these costs are captured at a high-level cost code, rather than at the granular level of the planning activities they support.”
↗
cost allocation
reveal definition The process of distributing expenses. “In the short term, we have adjusted the cost allocation logic for indirect engineering services in a controlled manner.”
↗
governance framework
reveal definition The system of rules and procedures for management. “However, if it points to a flaw in our cost logic or governance framework, that is a far more serious matter.”
↗
contingency budget
reveal definition Funds set aside for unexpected costs. “It also remains within the contingency budget approved at the portfolio level.”
↗

Key phrases (useful expressions from the dialogue)

More Finance & Budgeting lessons

Annual Financial Review and Strategic Planning

Elena, the Financial Controlling Manager, conducts a virtual annual financial review with the CFO to analyze t…

Derivative Trading Risk and Compliance Review

An auditor meets with a trading department head to review derivative strategies, risk management, and regulato…

Explaining Budget Variances and Corrective Actions

A management controller presents a detailed budget variance report to a regional operations manager, discussin…

Negotiating EBITDA Adjustments in M&A Due Diligence

Alex Vance reviews Caldmere Systems's financial data and raises concerns about revenue sustainability, invento…

Post-SteerCo Cost Forecast Reconciliation

After a steering committee meeting, a senior leader requests a private discussion to verify the integrity of a…

Q3 Financial Results and Cost Variance Analysis

A finance manager presents Q3 results to the executive committee, highlighting revenue growth and profit margi…

Keep going

Practise this scenario live with Phil, and get a personalised lesson built from your own mistakes. Interactive in the browser, with a booklet to keep.

Book a lesson with Phil