Project Controlling for Small Businesses: Budget, Time, and Scope

Why do small companies notice too late that a project is going off track?

In many companies, a project is calculated twice: at the costing stage and at the final invoice. In between lies a phase in which everyone is busy and has the feeling things are moving forward. That two thirds of the budget has already been used although only half is finished usually becomes apparent only at the end. Then nothing can be changed anymore, only explained.

Small companies do not need a controlling department for this, but they do need an answer to the guiding question of this article: How does a small company keep an eye on the budget, time, and scope of its projects with little effort, so that deviations show up early enough?

To answer it, we first clarify the terms and the triangle of budget, time, and scope. Then we introduce earned value management as a thinking model, work through it with an example, and weigh how much of it a small company needs. At the end there is a project sheet with four numbers and an answer to the guiding question.

Whoever only compares costs with the budget knows how much money is gone, but not what they got for it.

Budget, time, scope: what does project controlling mean?

Project controlling refers to the continuous comparison of a project with its plan, combined with the decision whether and how to correct course. It is not control in the sense of surveillance but a steering aid, comparable to glancing at the fuel gauge while driving instead of only at the pump.

Three quantities are compared, often shown as the project triangle: the budget, meaning planned costs or hours; time, meaning deadlines and milestones; and scope, meaning the agreed result. The three are connected. If scope grows, costs or duration rise unless cuts are made elsewhere. Whoever tracks only one of the three therefore sees only part of the picture.

The basis for any controlling is a plan with milestones, as described in the article on project planning for small teams. Without milestones, there is nothing to compare progress with. And without realistic planned values, controlling only measures how far reality deviates from an overly optimistic plan.

The thinking model: earned value management

The best-known method for combining budget, time, and scope in one calculation is called earned value management. Elsaid, Nassar, Alqahtani, and Abotaleb (2025) describe it as a widely used method that brings together costs, schedule, and scope and is meant to make deviations recognizable early. It works with three values.

• Planned value: How much budget should have been used by today according to plan?
• Earned value: How much budget corresponds to the work that is actually finished?
• Actual cost: How much has actually been spent?

These three values yield two key figures. The schedule performance index divides earned value by planned value. If it is below 1, the project is behind plan. The cost performance index divides earned value by actual cost. If it is below 1, the finished work costs more than planned. Dividing the total budget by the cost performance index gives a simple forecast of final costs, assuming things continue as before.

The decisive idea is earned value. It answers the question that a mere comparison of costs and budget leaves open: what did we get for the money spent? A project that has used 50 percent of its budget is on plan only if 50 percent of the work is also finished.

Worked example: is the project doing as well as everyone says?

A company with 25 employees is carrying out a customer project with a budget of 60,000 euros and a duration of ten weeks. After five weeks, according to plan, work worth 30,000 euros should be finished. In fact, milestones valued at 24,000 euros in the plan have been reached. So far, 32,000 euros have been spent. The figures are a worked example.

Without earned value, the situation would look harmless. 32,000 euros against a budget of 60,000 euros at the halfway point looks like a slight overrun. With earned value, a different picture emerges: the project is one fifth behind plan, and every euro delivers only 75 cents of planned work. Extrapolated, 20,000 euros are missing, a third of the budget.

After five weeks, there is still time to act: talk to the customer about scope or change orders, change the division of work in the team, or simplify the workflow. After ten weeks, only the explanation remains. What this means for the margin can be quantified with the order’s contribution margin, as described in the article on contribution margin per order.

How much controlling does a small company need? Two perspectives

The first perspective says: formal project controlling is for large projects. Small companies know their projects, the owner sees every day where things are stuck, and every calculation costs time that is missing from the project. There is a lot to be said for this. Elsaid and colleagues (2025) summarize in their literature review that earned value management is considered laborious, complicated, and disputed in its forecasting accuracy. It measures the amount of work done, not directly the delay in time.

The second perspective says: precisely because small companies have no reserves, they need early warning signs. Elsaid and colleagues (2025) compared three variants of the method for forecasting completion dates in 30 construction projects in Egypt. No variant was best in all phases: one was most accurate early in the project, another in later phases. Thiele, Abbasi, and Ryan (2025) showed with six completed projects that ongoing figures can reveal whether forecasts tend to be too optimistic or too pessimistic.

Both studies come from construction and from projects larger than those in most small companies. Nevertheless, I consider one conclusion sound: the full method is too laborious for a small company, but its basic idea is not. Comparing planned progress, actual progress, and costs can be done in a few minutes with three numbers from milestones reached and hours recorded. It does not provide a precise forecast, but it does provide a reliable warning sign.

When scope grows: how do you prevent creeping extra work?

The numbers show that a project is going off track. They do not show why. The most common cause in small companies is one that appears in no costing: scope creep. It means that the scope of a project grows bit by bit without budget or deadlines being adjusted. An extra report here, another variant there, a “Could you also do this while you’re at it?” on the phone.

ElAlem and colleagues (2025) analyzed 50 completed construction projects in Egypt and found delays in execution, poor documentation of agreements with stakeholders, and unexpected site conditions to be the most important factors behind scope creep. Gerona and Ocampo (2023) interviewed five project managers in the IT department of a Philippine financial institution. They named uncontrolled growth in scope, underestimated timelines, and an unfavorable distribution of work as the biggest difficulties. Their remedies were to put other projects on hold, extend deadlines, and work overtime, which the authors classify as unsustainable in the long run.

Both studies are limited to one country and one industry, and the second is based on only five interviews. But their shared finding matches what many small companies know: extra scope arises where agreements are not recorded. The remedy is therefore not a stricter no to the customer but a change log.

• Every request that goes beyond the quote goes onto the project’s change log with a date.
• Each entry includes estimated effort in hours and the effect on the deadline.
• The customer receives the log regularly and decides: order it as a change, swap it for something else, or postpone it.
• Small favors are allowed, but they also go on the log, marked “no charge.”

The log does not start in the project. Many extensions are already set up in sales when commitments are not passed on to the project team. What needs to be recorded at this handover is described in the article on the sales-to-project handover.

The project sheet: four numbers a month

The thinking model and the change log combine into a tool called the project sheet here: one row per project with four numbers, updated once a month in five minutes.

1. Read the planned value

   How much budget should have been used by today according to plan? This follows from the milestones with their dates and values.

2. Count the earned value

   Sum of the planned values of all milestones actually reached. Milestones that have been started count as zero.

3. Enter actual cost

   Recorded hours times hourly rate plus materials and subcontracted work. Without time tracking on the project, there is no actual cost.

4. Add up open changes

   Effort of all change log entries not yet ordered or decided.

5. Set the traffic light and act

   If the schedule or cost index is below 0.9 or open changes exceed ten percent of the budget, the project goes on the agenda of the next meeting, with an action and a name.

The thresholds of 0.9 and ten percent are a suggestion, not a standard. What matters is that they are set before the numbers are known, as also applies to the KPI dashboard. If several projects run at the same time, a row with the sum of deviations belongs on the dashboard. If the deviations keep coming down to a lack of time in the team, the cause is often not the individual project but capacity planning. The article on capacity planning addresses this.

Conclusion: how project controlling works in a small company

We began by asking
a small company keeps an eye on the budget, time, and scope of its projects with little effort so that deviations show up early. The answer: with the basic idea of earned value management in a lean form. Once a month, planned value, earned value, and actual cost are compared based on milestones reached and hours recorded, supplemented by the open entries of a change log.

As shown, the full method is considered laborious and not always accurate in its forecasts, and the studies on it come mostly from larger construction projects. Its core, comparing work done with money spent, is just as valid for small projects. The greatest danger, in any case, lies not in the calculation but in scope that grows unnoticed. This leads to a sober observation: a project rarely goes off track in a single day, but over many small days on which nobody wrote down a number.

How to get started

1. Take your largest running project and assign each milestone a planned value in euros or hours.
2. Count which milestones have actually been reached and calculate the earned value.
3. Compare it with the hours and costs recorded so far and calculate the schedule and cost index.
4. Create a change log and enter all additional requests from recent weeks.
5. Set a monthly appointment of five minutes per project for the project sheet.

At the end of the project, it is worth comparing the forecasts with the result. How to learn from this for the next project is described in the article on project close-out and lessons learned.