Why Your Projects Look Busy but Bleed Money

The project finished on time. The client was happy. Then the numbers came in, and the margin had quietly disappeared into unlogged hours, extra revisions, and work that never made it onto an invoice.

For an agency, consultancy, studio, or services firm, that is a difficult kind of success. The team delivered what the client needed, but the business earned far less than expected.

A full calendar can hide this problem. Everyone is busy, projects keep moving, and the next deadline takes priority over checking whether the current job still makes commercial sense.

Learning to track project profitability without spreadsheets means bringing the budget, recorded costs, scope changes, and remaining work into a dependable operational view. The aim is to spot a deteriorating forecast while there is still time to act.

Spreadsheets can calculate margin and support regular reviews. The difficulty is maintaining accurate information across several projects, people, and systems. When updates depend on manual consolidation, the warning often arrives after the opportunity to respond has passed.

Illustrative dashboard: project costs become more useful when viewed alongside remaining work and delivery progress.

Key Takeaways

• A fully booked team can still deliver projects with weak or negative margins.
• Costs recorded so far do not tell you the expected profit on a finished project. You also need an estimate of the work and costs remaining.
• Unlogged time, unapproved changes, and rework can make a project look healthier than it is.
• A connected dashboard can shorten the gap between work happening and management seeing its effect, provided the underlying data is complete and current.
• Project margin, utilisation, invoicing, and cash collection answer different questions and should be shown separately.
• Start with a few active projects, clear cost definitions, and a regular review that leads to decisions.

Related: see what belongs in an operations dashboard for a small business and the wider signs you need operational systems.

In this guide:

• Why busy does not mean profitable
• Where project margin disappears
• How to calculate a useful forecast
• A worked project margin example
• What the dashboard should show
• Spreadsheets versus a connected dashboard
• How to put the process in place
• Frequently asked questions
• How OpsMavix can help

1. Busy Does Not Mean Profitable

A full schedule shows that people have work. It does not establish whether the agreed fee covers the cost of delivering it.

A project may have been priced using an optimistic estimate. It may require more senior involvement than planned. The client may request additional rounds of changes, or the team may spend days correcting a misunderstanding that nobody records separately.

Each situation can increase cost without increasing revenue.

Delivery success and commercial success need separate checks

A project manager can report that milestones are on time while the delivery team is using significantly more hours than budgeted.

Both statements can be true. Meeting the deadline may even depend on expensive overtime, additional contractors, or moving experienced staff away from other paid work.

A useful review therefore asks two questions: are we delivering the agreed outcome, and what do we now expect it to cost?

Utilisation needs context

Billable utilisation can help explain how available time is being used. For example, a business might define it as billable hours divided by available working hours, with clear rules for leave and other exclusions.

That measure does not establish margin. A person can spend most of their week on client work that was underpriced. On a fixed-fee project, additional delivery hours can increase workload while reducing the return on the agreed fee.

Show utilisation alongside project economics and capacity. Keep the definitions consistent so managers can compare like with like.

2. Where Project Margin Quietly Disappears

Margin loss becomes harder to detect when the work and its cost are recorded in different places.

Hours are entered late or missed entirely

A short client call, an internal review, and a quick correction may each seem too small to record. Repeated across a project, they can represent a meaningful amount of delivery time.

If that time is missing, the dashboard understates cost. For time-and-materials work, missing eligible hours may also reduce billing. For fixed-fee work, they distort the view of how efficiently the team delivered the agreed scope.

Use a practical time-entry routine with a small number of meaningful categories. Make missing entries visible instead of silently treating them as zero effort.

Scope changes never become commercial decisions

An extra request should have a visible outcome: included in the existing fee, exchanged for something else, quoted separately, deferred, or declined.

The problem is the request that gets completed without anyone making that decision.

Record the change, its estimated effort, the commercial owner, and the approval status. Keep proposed additional fees separate from the approved contract value until the client has agreed them.

Rework is hidden inside normal delivery

Time spent correcting an internal error has a different cause from an approved client change. Combining everything under “project work” makes it difficult to learn why estimates keep being exceeded.

Use categories that help identify the cause without making time entry burdensome. The purpose is to improve estimating, briefing, review, and delivery processes.

External costs arrive after the review

Contractor work, specialist services, travel, and project-specific purchases may not appear in the accounts immediately.

A project can look comfortably within budget if the review includes only invoices already received. Track expected and committed costs alongside recorded actual costs, with clear rules to avoid counting the same item twice.

The reporting gap often comes from missing or disconnected inputs rather than the margin calculation itself.

3. How to Track Project Profitability While Work Is Still Open

For an active project, the central question is: what profit do we currently expect when the agreed work is complete?

Subtracting costs incurred so far from the entire project fee does not answer that question. It leaves out the work still required to earn the fee.

Define the revenue and cost basis

For a fixed-fee management forecast, start with the agreed fee plus approved fee changes. Show unapproved proposals separately.

Then define which delivery costs the project calculation includes. Labour should use an agreed cost rate rather than the customer billing rate. Include relevant external delivery costs and apply the same treatment consistently across projects.

Be explicit about overhead. A contribution figure before company overhead is different from profit after allocated overhead. Label the measure so nobody mistakes one for the other, and avoid allocating a cost twice through both labour rates and a separate overhead charge.

Use a consistent tax and currency basis. The worked example below excludes VAT and uses a simplified project contribution measure before general company overhead.

Combine actual costs with the cost to finish

For this management view:

Forecast total delivery cost = actual delivery cost to date + estimated remaining delivery cost

Forecast project contribution = approved project fee − forecast total delivery cost

Forecast project margin = forecast project contribution ÷ approved project fee × 100

The remaining cost estimate should include outstanding commitments and other expected costs that have not already been included in actuals. Do not add a purchase commitment again if it is already included in the estimate to finish.

The principle of combining actual cost with remaining cost is also used in Microsoft’s project cost tracking documentation. Its documented view concerns labour; your own project model should account for the other delivery costs relevant to your business.

Update the estimate to finish

A budget is the original plan. An estimate to finish is the team’s current assessment of what remains.

If a task was budgeted at 40 hours, has already consumed 35, and still needs another 20, the forecast should reflect 55 hours. Assuming only five hours remain would preserve the budget on paper while hiding the likely overrun.

Ask owners to re-estimate remaining work at meaningful milestones and whenever a material change occurs.

4. A Worked Example: How a Healthy Project Loses Its Margin

Imagine a consultancy delivering a fixed-fee project for £20,000. These figures are illustrative and do not represent a client result or industry benchmark.

The original plan allows £12,000 for delivery labour and £2,000 for external costs. Expected project contribution is £6,000, giving a planned margin of 30% before general company overhead.

During delivery, extra reviews and more complex implementation work increase the expected effort. The fee has not changed.

The forecast cost has increased by £4,000. Expected contribution has fallen by the same amount, even though the team may still be on schedule.

Why actual costs alone give an incomplete picture

Suppose the team has recorded £9,000 of labour and £1,000 of external costs so far. That is £10,000 of actual cost.

Comparing the £20,000 fee with that £10,000 could appear reassuring. But the project still needs £6,000 of labour and £2,000 of external work. The expected final cost is £18,000, leaving the forecast 10% margin shown above.

The remaining-work estimate changes the decision.

What management can do with the warning

The team can investigate whether the increase comes from an estimating error, rework, or additional scope. Each cause calls for a different response.

An estimating error may require a revised delivery plan and better assumptions on the next quote. Rework may call for an earlier quality review. Additional scope may require a conversation about fees, priorities, or replacing an existing deliverable.

As an illustration, if the client approves £2,000 of additional fees and no further costs arise beyond the current forecast, contribution becomes £4,000 on revenue of £22,000: approximately 18.2% margin. That improves the forecast but does not restore the original 30%.

The dashboard should record the decision and revised forecast. An alert only becomes useful when someone owns the response.

5. What a Project Operations Dashboard Should Show

A project operations dashboard should help an owner or delivery lead identify which active projects need attention and why.

Start with a small number of measures that support action.

Show billing and cash separately

The agreed fee, amount invoiced, and cash received are different values.

A deposit can improve cash availability before much work has been delivered. A profitable project can still have an overdue invoice. Neither fact alone establishes project margin.

Use separate fields for the commercial forecast, invoice status, and payment status. If the dashboard also reports recognised revenue or accounting profit, agree those definitions with the finance team instead of inferring them from invoices alone.

Make data freshness visible

“Live” should describe the actual update process. A dashboard that refreshes every few minutes still cannot show time that has not been submitted or contractor costs nobody has recorded.

Show the last successful refresh, outstanding time entries, and the date the remaining-work estimate was reviewed. Mark incomplete forecasts clearly rather than presenting false precision.

Let managers open the detail

When a project falls below its target, users should be able to trace the movement to the relevant tasks, costs, or changes.

A red indicator without an explanation creates another investigation. A useful view links the warning to the information needed for a decision.

6. Spreadsheets vs a Connected Project Operations Dashboard

Both approaches can calculate margin. The practical difference is how much effort it takes to keep the underlying information complete, consistent, and available.

A small team with a well-maintained model may not need to replace it immediately. The stronger signal is repeated delay, conflicting versions, or dependence on one person to assemble the answer.

For the wider reporting picture, see what an operations dashboard should show.

Connected reporting works best when project records, time, costs, and approvals share consistent identifiers and ownership.

7. How to Start Tracking Project Profitability Without Spreadsheets

Start with a manageable group of active projects and a clear review routine. The first version needs to make important decisions easier, not reproduce every report the business has ever created.

Establish a reliable project record

Use one identifier across the estimate, task plan, time records, expenses, changes, and invoicing references.

For each pilot project, confirm the agreed fee, approved scope, delivery owner, original cost budget, and current estimate to finish.

Agree ownership of the inputs

Assign responsibility for time completeness, labour cost rates, external costs, scope decisions, and forecast updates.

A dashboard cannot resolve a disagreement about who should maintain the information. Make those responsibilities part of the delivery process.

Connect the sources that matter first

Time tracking, project planning, and accounting information may already exist in separate tools. Assess whether they can share the necessary data through supported integrations, APIs, or controlled imports.

Confirm how each connection handles corrections and duplicates. A recurring import must not add the same expense twice, and a corrected time entry must update the forecast appropriately.

Pilot a weekly commercial review

For each project requiring attention, ask:

• What has changed since the last review?
• Is the remaining-work estimate still credible?
• Are any costs or hours missing?
• Is additional work commercially agreed?
• What action is needed, who owns it, and by when?

Review sooner when a significant scope or cost change occurs. Match the rhythm to the pace of delivery and the time available to intervene.

Compare outcomes after delivery

At close-out, compare the final result with both the original budget and the forecasts made during delivery.

Use the differences to improve estimating assumptions, staffing, revision allowances, and change control. The value compounds when lessons from completed work improve the next quote.

Frequently Asked Questions

How soon can I tell whether a project will be profitable?

You can create an initial forecast before delivery begins and update it as work progresses. It remains an estimate until the relevant revenue and costs are settled. Confidence improves with complete time records, visible commitments, and realistic estimates of remaining work.

Can spreadsheets track project profitability during delivery?

Yes. The limitation is usually the effort and discipline required to keep them updated across multiple people and systems. A connected process becomes useful when manual maintenance repeatedly delays decisions or produces inconsistent figures.

Do I need a professional services automation platform?

Not necessarily. Options include extending existing tools, adopting a PSA platform, or building a focused custom system. Compare the required workflows, integrations, administration, licensing, training, and ongoing support. Custom software is not automatically cheaper, and an off-the-shelf platform is not automatically too complex.

How do we encourage people to log time accurately?

Keep entry simple, explain which decisions the information supports, and set a clear routine. Show how reliable time data helps improve estimates and workloads. Review missing entries promptly and investigate process problems without encouraging people to hide overruns.

How does this differ for time-and-materials projects?

The revenue forecast depends on expected billable work, agreed rates, caps, approvals, and likely write-offs rather than only a fixed fee. Recording more hours does not guarantee they can be invoiced. Keep delivery cost and billable value distinct.

Can the dashboard connect to invoicing and approvals?

Potentially, depending on the systems, available interfaces, and agreed integration scope. Linking approved work to billing and an invoice approval workflow can reduce duplicate handling, but reconciliation and exception ownership still need to be designed.

What is a good project margin target?

There is no single target that fits every service business or cost definition. Set targets using your pricing model, delivery costs, overhead needs, and commercial priorities. Compare projects on the same basis and review both the margin percentage and the contribution in pounds.

How OpsMavix Can Help

OpsMavix builds custom project operations dashboards that bring project costs, hours, scope changes, and delivery status into a clearer management view.

We start by understanding how your projects are quoted, delivered, changed, and billed. From there, we can help define the data and workflows needed to monitor performance while the work is still open.

That can include:

• Connecting project budgets with time and cost records.
• Making approved and unapproved changes visible.
• Showing forecast margin alongside delivery progress.
• Highlighting missing information and projects needing review.
• Improving the handover between delivery, approvals, and billing.
• Reducing the manual work involved in preparing project reports.

If your team is busy but project margins keep disappointing, book an Operations Leak Audit. Bring a recent project that earned less than expected and an active project whose outcome is uncertain. We can help map where the information is missing and what a more useful view should show.