A lot of trades businesses run projects as if they were big work orders. That works — right up until the project blows past its budget in week three, and you don't notice until you send the final invoice two months too late.

Project management isn't a complex discipline reserved for big construction firms. It's a set of simple routines for staying in control as you go — not just at the end.

In short

  • A project differs from a work order in having a budget, a timeline and enough complexity to need ongoing follow-up.
  • The three critical control points are budget (spend vs. plan), progress (done vs. plan) and the SHA plan when several parties are involved.
  • Most project overruns are caught too late because nobody compared actual spend with the budget along the way.
  • Project reporting doesn't have to be complicated: a weekly check of hours and materials against budget is enough for most SMB projects.

What's the difference between a work order and a project?

A work order is a single job of limited scope — a repair, an installation, a service check. It's opened, carried out and closed.

A project is more complex: it stretches over time, has a defined budget, may involve several trade teams or subcontractors (underentreprenør), and needs a plan for what gets done when.

The practical distinction: if you need to track spend against a budget, sequence the activities, and coordinate with others — it's a project.

The three control points in a project

1. Budget. What did we estimate, and what have we spent so far? Most overruns aren't caused by one big thing going wrong — they're caused by lots of small things that never got recorded as they happened. Hours that go missing, materials that don't get invoiced, extra work done without a change order (endringsordre).

Check: Compare accumulated hours and materials against the budget weekly, not just at month-end.

2. Progress. Are we where we should be by this date? A project programme (progress schedule / fremdriftsplan) is a tool for seeing whether you're ahead of or behind plan — and for catching delays early enough to do something about them.

Check: What was supposed to be finished by today? What's actually finished?

3. Changes. In almost every project, change work crops up — the customer spots something, conditions differ from what the drawings showed, a mistake from the design phase has to be fixed. Changes that aren't handled as change orders (endringsordre) with a new price are lost revenue.

Check: Is all the extra effort today documented with a written change order approved by the customer?

The SHA plan in projects with several parties

If the project involves several parties carrying out work (subcontractors, parallel trade teams), the Construction Client Regulations (byggherreforskriften) trigger a requirement for an SHA plan and a coordinator (koordinator). For more on this, see HSE plan vs SHA plan: what's the difference?.

For practical purposes: if there's more than one business on the site, there should be an SHA plan and a clear coordination responsibility — even on projects that look simple.

Partial invoicing: paid as you go, not just at the end

One of the most important tools for cash flow on projects is partial invoicing (delfakturering) — billing work as it's completed, not only at the end of the project.

Typical models:

  • By progress: invoice 30%, 60%, 90%, 100% of the contract price at agreed milestones (milepæl)
  • By spend: invoice monthly based on the hours and materials actually incurred
  • Up-front payment: the customer pays X% at the start (common for material costs)

Projects without partial invoicing tie up capital for a long time and expose you to customer default. Settle the invoicing model in the contract — not afterwards.

Documentation during the project phase

Good project documentation isn't just tidy — it's the only basis for winning a dispute with a customer over what was included in the price.

Minimum documentation on a project:

  • Signed contract with prices and a description of the work
  • Change orders — all of them, approved in writing
  • Timesheets per week, linked to the project number
  • Materials list with purchasing documentation
  • Progress update per period
  • Handover documentation delivered to the construction client (byggherre)

For more on self-inspection and technical documentation, see Self-inspection and quality assurance (KS) for tradespeople.

What are the typical project mistakes?

No change order routine. "We'll sort it at the end" is the last thing you want to say to a customer. Change work is documented there and then, with the customer's approval — not argued over on the final invoice.

Hours with no project reference. The technician (montør) logs time, but not the project number. The result is that you don't know whether the project is over- or under-spent.

Budget follow-up only at the end. If you don't see the overrun until the project is finished, you can't do anything about it. A weekly check of spend against budget is the minimum.

Materials invoiced at purchase, not at use. The customer should be billed for what they actually use — not everything you ordered.

Project management in practice for SMBs

You don't need an enterprise project management tool to run projects well. The minimum is:

  1. Project number and name — everything is tied to this
  2. Budget for hours and materials — visible in the system
  3. Weekly spend report — hours and materials this week vs. plan
  4. Change order log — every extra not in the contract is documented

Field Ops has a project module with budget, milestones, partial invoicing and document storage — connected to work order management. Start free and see what your projects look like with full oversight.

Frequently asked questions

Do we need project management for projects under kr 500,000?

The threshold depends on complexity, not size. A project with two trades, five weeks and subcontractors needs project management even if it's small in kroner. A single large delivery of a standard installation may not.

What's a good project profit?

It's industry-dependent, but for Norwegian service and installation businesses 8–15% operating margin (driftsmargin) is considered normal. Under 5% is a sign that the project management isn't working. Calculate the project margin per job — not just overall.

Can we run projects in an accounting system like Tripletex?

Tripletex has a project module that covers time registration and invoicing per project. It doesn't cover the dispatch calendar, work order management in the field or the SHA plan. For service businesses it's typically an order management system that sends data to Tripletex, not the other way around.

Summary

Project management for trades businesses comes down to three things: keep the budget visible and up to date, catch delays early with a weekly progress check, and document every change with a written customer order. Partial invoicing protects cash flow as you go. Good documentation is the only basis for winning a dispute. You don't need complicated tools — you need discipline and a system where the hours are tied to the project number.

See also: From hours and materials to invoice · EHF invoicing for tradespeople

Sources