Turn a change into a paid variation
Capture a scope change while it is fresh, price it as a contract variation on your agreed r…
Bli enige om milepælene, fakturer dem etter hvert som de fullføres, og la loven om rettidig betaling som styrer prosjektet starte klokken, slik at en forsinket betaling har en dato, et beløp og en rentesats i stedet for en diskusjon.
5 trinn gjennom plattformen - hva du gjør i hvert og hvorfor det betyr noe.
Record the contract with its price, its payment terms and the milestones that trigger a payment, so what is owed and when is a property of the job rather than a thing two people recall differently.
Hvorfor: A milestone that was never written down cannot be billed without a discussion, and the discussion always happens when you need the money. Written up front, the same milestone is an invoice trigger nobody has to justify.
Raise the payment claim against the milestone as it completes, with the date it went out. Billing late shortens nothing except your own runway, and the submission date is what every subsequent question turns on.
Hvorfor: The statutory clock starts from an event, and on private work that event is usually your claim arriving. A claim you sat on for two weeks is two weeks of interest you will never see, and it is the one part of the timeline entirely within your control.
Pick the prompt payment regime that governs this job, by state and by whether the work is public or private, and start the clock from the claim. The due date is then computed from the statute rather than assumed from habit.
Hvorfor: The periods are genuinely different between states and between public and private work, which is exactly why people guess and guess wrong. Naming the regime turns the due date into something checkable, and it means the same job billed in another state does not quietly inherit the wrong deadline.
Once the due date passes, the interest the regime provides accrues on the unpaid amount and is calculated rather than estimated, so a reminder can carry a figure instead of a complaint.
Hvorfor: Asking to be paid is awkward and easy to defer. Sending a number that grows on a schedule the law set is neither, and it changes what the other side is deciding: not whether to be fair to you, but whether delay is now costing them more than paying.
Reconcile what was billed against what arrived, and keep the ageing rather than clearing it from memory once the money lands.
Hvorfor: A client who pays a month late every time is a financing cost you are carrying without pricing it. Once that is visible per client rather than felt in general, it becomes something you can price into the next bid or decline.
3 / 190 plattformmoduler
Everything in this case follows how construction work is measured, priced and paid for in this market. The forms, the cost breakdown and the payment rules are the ones used there, not a generic version of them.
Standards it follows
You do not have to set any of that up by hand. The first time you open the platform it asks which market you work in. Choose this one and it sets the interface language, loads the matching cost database and records the cost classification, and it adds an example project you can open straight away.
The rule checks for this market come with the platform too. Switch them on once and an estimate that misses something the market expects is flagged while you are still working on it, not after the tender has gone out.
Capture a scope change while it is fresh, price it as a contract variation on your agreed r…
Award a trade package to a subcontractor, place it on a subcontract with a schedule of valu…
Value the work put in place this period against the contract, raise the application with th…