InterLAB tools · Before/after · change order

Change request calculator

Load the approved scope from the scope calculator or enter it manually, mark the work progress and describe the changes. The calculator shows affected modules, extra hours, money and weeks, risks and a before/after comparison — and builds a change order without altering the original agreement.

Free, no sign-up

First set the approved scope: load a scope-snapshot file from the scope calculator or enter the modules manually.

From a scope-snapshot file

The file the Scope and cost calculator exports with “Approve the scope”. The scope is locked and becomes read-only.

Enter manually

Modules from the contract or estimate: hours and cost as low and high bounds. If there is a reserve, enter it separately — totals include it.

The document is stored only in this browser. InterLAB rules v1.0 (2026-10-13): rework surcharge +20% (in progress) and +40% (done), credit only for the unfinished share, re-planning when a change exceeds 20%.

How the calculator works

Approved scope
A scope-snapshot file from the Scope and cost calculator, or modules entered manually with hours and cost. Once locked, the scope is read-only, and who approved it and when is always shown.
Work progress
Each module is not started, in progress (with a percentage) or done. The status drives the rework surcharge and the credit for removals.
Requests CR-001, CR-002…
Each request has a title, a reason, who asked and when, and a list of changes: add a module, change a module (± hours or ± %), remove a module.
Impact
Δ hours, money and weeks, a before/after table, affected and dependent modules, risks under published rules and the calculation behind every number.
Approval
Draft → submitted → approved or rejected, with the decision maker and date. An approved request is pinned as a version and cannot be edited; a rejected one stays in the log.

Calculation rules

Change	Rule
Add a module	Hours (low–high) × rate. The rate is entered or the average rate of the approved scope: Σ cost ÷ Σ hours; the derivation is shown
Change a module: ± hours or ± %	A percentage applies to each hour bound of the module. Cost uses the module's own rate (its cost ÷ its hours)
Rework surcharge	On hours added to a module in progress +20%, done +40%: some finished work is redone
Reduce a module	Only the unfinished share is credited: reduction × (1 − done share); a done module credits 0
Remove a module	Credit = module hours and cost × unfinished share. The finished part is not credited and stays in the scope, marked
Reserve	The approved scope's reserve applies to the change — so the scope snapshot stays consistent
Schedule	Δ weeks = Δ hours with reserve ÷ team capacity. Capacity is entered or “hours ÷ weeks” of the approved scope

Add a module

Rule: Hours (low–high) × rate. The rate is entered or the average rate of the approved scope: Σ cost ÷ Σ hours; the derivation is shown

Change a module: ± hours or ± %

Rule: A percentage applies to each hour bound of the module. Cost uses the module's own rate (its cost ÷ its hours)

Rework surcharge

Rule: On hours added to a module in progress +20%, done +40%: some finished work is redone

Reduce a module

Rule: Only the unfinished share is credited: reduction × (1 − done share); a done module credits 0

Remove a module

Rule: Credit = module hours and cost × unfinished share. The finished part is not credited and stays in the scope, marked

Reserve

Rule: The approved scope's reserve applies to the change — so the scope snapshot stays consistent

Schedule

Rule: Δ weeks = Δ hours with reserve ÷ team capacity. Capacity is entered or “hours ÷ weeks” of the approved scope

Calculation rules v1.0 (2026-10-13)

Risk rules

Risks are hints with an explanation, not a verdict: the client and the contractor decide.

Rule	Level	When it fires
CR-RISK-DONE	high	Changing or removing a done module
CR-RISK-INPROG	medium	Changing or removing a module in progress
CR-RISK-BIG	high	The change exceeds 20% of the approved cost (or hours if there is no cost) → re-planning recommended
CR-RISK-CUM	medium	Together with earlier approved changes the scope has grown by more than 20%
CR-RISK-LATE	medium	More than 60% of the work is done (by module hours)
CR-RISK-DEP-REMOVE	high	A module that other modules depend on is removed
CR-RISK-RIPPLE	medium	The changed module has dependents (transitively) — review them
CR-RISK-NEW-DEP	medium	A new module depends on a module that is not in the current scope
CR-RISK-DEADLINE	high	Planned end + shifts of all approved CRs and this CR is after the deadline

CR-RISK-DONE

Level: high
When it fires: Changing or removing a done module

CR-RISK-INPROG

Level: medium
When it fires: Changing or removing a module in progress

CR-RISK-BIG

Level: high
When it fires: The change exceeds 20% of the approved cost (or hours if there is no cost) → re-planning recommended

CR-RISK-CUM

Level: medium
When it fires: Together with earlier approved changes the scope has grown by more than 20%

CR-RISK-LATE

Level: medium
When it fires: More than 60% of the work is done (by module hours)

CR-RISK-DEP-REMOVE

Level: high
When it fires: A module that other modules depend on is removed

CR-RISK-RIPPLE

Level: medium
When it fires: The changed module has dependents (transitively) — review them

CR-RISK-NEW-DEP

Level: medium
When it fires: A new module depends on a module that is not in the current scope

CR-RISK-DEADLINE

Level: high
When it fires: Planned end + shifts of all approved CRs and this CR is after the deadline

Risk rules

Limitations

The change estimate inherits the approved scope's assumptions: if the original estimate is off, so is this one.
A new module uses the scope's average rate by default; if the work needs a different role (for example design only), enter the rate manually.
The schedule shift uses total team capacity and ignores that a change may land on one overloaded role.
Approval is a note as stated by the user — not an electronic signature and not a contract amendment.

Privacy

Everything is calculated in your browser: the calculator itself does not send the scope, requests or text to a server, and they never appear in the page address.
The document and versions are stored only in this browser (localStorage); “Clear all” deletes them. Share via JSON and Markdown/PDF files.
Analytics receives only the fact of a submission, decision or export and categories (risk level, number of changes, format) — no amounts or text.
The result reaches us only if you send a request yourself and keep the “Attach the result” box ticked — the form shows exactly what will be sent.

Related tools

All tools · 40

MVP validation toolkitHypotheses with thresholds, a landing page and lead form, UTM links, a funnel, interviews and an experiment report → continue, pivot or stop.

Proposal builderProposal templates for IT projects: scope, phases, estimate, timeline, assumptions and exclusions, versions with number control, approval and PDF.

Idea → Product blueprintAn interview about your idea → roles, features, three MVP scope options, priorities and risks. You get a Product Blueprint to start development from.

MVP complexity estimateProduct type, platforms, modules and integrations → a complexity band, workstreams and the questions you need answered before any honest price.

Scope and cost calculatorModules, effort, your rates, complexity factors, dependencies and a risk reserve → a cost and timeline range with every number explained, plus estimate comparison.

Technical brief generatorBuild a brief step by step: goal, roles, scenarios, integrations, data, acceptance criteria. You get Markdown to copy or download.

Tell us about your task — we'll review your request and get back to you

Is the project scope changing mid-flight?

An InterLAB technical consultation helps review the changes, rebuild the plan and agree on new boundaries. The first short conversation is free; the cost is set after a brief.

The first short conversation is free — we choose the format
NDA — yours or ours
Pricing after a brief and an agreed scope

Message on WhatsApp