Agreeing the job · Guide · For homeowners
What does accepting a building project actually mean?
You have reviewed the scope, the price and the stages. The screen now asks you to accept the project.
What are you actually agreeing to?
That question should be answered before the button, not after a disagreement.
Acceptance should apply to one exact version
A building project changes while it is being prepared. Prices are corrected. Milestones move. A drawing is revised. An exclusion is clarified.
Your acceptance should identify the exact version containing:
- the customer and contractor;
- the property and project;
- scope, inclusions and exclusions;
- total and price basis;
- assumptions and allowances;
- milestones and amounts;
- completion criteria and evidence;
- responsibilities and customer decisions;
- referenced documents and versions;
- terms and consumer information.
It should not apply vaguely to “the project as amended later”.
Acceptance is a real commitment
An electronic acceptance can have legal effect. A click is not harmless simply because there is no handwritten signature.
The screen should tell you:
- which party you are acting for;
- which version you are accepting;
- what legal and commercial package applies;
- whether the action creates payment obligations;
- which separate steps remain.
If the effect is unclear, ask before accepting.
What it normally confirms
Subject to the governing terms, project acceptance should confirm that you intend to adopt the displayed project basis.
That may include:
- the work the contractor has agreed to provide;
- the price or way the final price will be calculated;
- how the work and payment are divided into stages;
- what each party must provide or decide;
- how changes will be recorded;
- the legal terms identified in the package.
What it should not silently mean
Accepting the project does not automatically mean that you:
- accept future extra charges;
- approve work not yet carried out;
- certify the design or workmanship;
- agree every allowance will equal its estimate;
- fund the project;
- authorise every product order;
- instruct work to start immediately;
- accept later variations;
- waive rights concerning defects or delay;
- give up statutory consumer or cancellation rights.
Those effects need their own valid basis and, where appropriate, separate decisions.
Acceptance, funding and starting work are different
After the project is accepted, the first milestone may still need funding. A bespoke product may still need order authority. Work may need access, an inspection, final design or an express early-start request.
Your project should therefore show three different questions:
- 1Have the required parties accepted the project basis?
- 2Has the required money been put in place?
- 3Are the practical and legal start conditions satisfied?
One does not prove the others.
What if something is wrong?
Do not accept with a condition hidden in a comment.
For example:
Accepted, provided the windows are included.
That creates a record saying you accepted the version while your comment says the version needs to change.
Instead:
- ask a question if you need an explanation;
- request changes if the package itself is wrong;
- review the revised version;
- accept only when the record says what both sides mean.
What happens when you request changes?
In Assurr's current plan model, the proposed version is preserved. A request for changes cancels it as the live proposal and opens a fresh draft. The contractor can revise the project and send a new version.
The history remains visible, so neither side needs to argue later about which proposal was rejected or what changed.
Does acceptance remove cooling-off rights?
Do not assume so.
Depending on how and where the consumer contract was entered, a cancellation period may apply. Starting services during that period may need a separate express request and specific information about the possible payment consequence.
Project acceptance should not hide that request or claim that a general click waives statutory rights.
Who needs to accept?
Every required project party should decide on the same version. That may include more than one customer and the contractor business.
The person clicking must also have authority to act for the named party. Project access alone does not create that authority.
How Assurr fits
Assurr's plan model records required-party decisions against the exact frozen content hash. It rejects a decision on a stale version and preserves the proposal history.
The current platform does not yet pin the accepted plan to the complete enabled contract-product and consumer-notice package required for live-money operation. It must not be presented as though the present plan click alone completes every legal, cancellation, funding and payment-provider step.
The safest question before accepting is:
If somebody read only the acceptance summary and the package it identifies, would they understand exactly what I agreed and what still had to happen?
In the same moment
- Do not rely on one ambiguous clickFor builders
- The project said accepted, but the customer thought it was only a reviewBoth sides
- Quote or estimate: what is the difference?For homeowners
- What is actually included in the building quote?For homeowners
- The builder has the drawings. Is everything shown included?For homeowners