Project handover fills the asset register
When a project is handed over, its assets join maintenance automatically, with warranties and maintenance contracts attached.
LiveWhat does Construction-to-maintenance continuum do? Developers and facility managers skip re-typing everything between construction and operations.
How it works
At handover, every asset goes into the maintenance register under the right company, already linked to its maintenance contract and manufacturer warranties. Repeating a handover never creates duplicates, and a failure is tried again rather than lost. Assets are then grouped by location and function, so costs and downtime add up.
A repeated handover never creates duplicate assets, because each project and asset tag is recorded only once.
Step by step
- The project team lists the assets in the handover packet. Each asset has a tag, a name, the make and model, and the manufacturer warranty period.
- The packet is issued and signed. The customer signs the packet. Unfinished items are counted when the packet is issued, and handover is refused if the packet is unsigned, unless the owner deliberately allows that.
- Sign-back is recorded. The project manager records that the customer accepted the handover. This starts the defects period and hands the assets over to maintenance.
- Maintenance registers each asset. Every asset in the packet enters the maintenance register under the right company, marked under maintenance contract, with the manufacturer warranty recorded from the packet.
- A repeat does nothing harmful. Each project and asset tag is recorded once. If the same handover arrives twice, no duplicates appear. If it fails, it is tried again and then parked for follow-up, not dropped.
- The facilities team takes over. Assets are grouped by location and function, so work orders, costs and downtime add up where you expect them.
See a handover packet turn into an asset register on sample data.
What you see on screen
Two places: the project handover screen, and the maintenance asset register.
| Screen or button | What it shows or does |
|---|---|
| Handover and retention (project) | The defects period and its end date, the two separate retention amounts (performance and defect liability), open snags as at the date the packet was issued, the signing envelope, and a Record sign-back button. |
| Release early | Lets you release defect-liability money before the period ends. It has to be ticked deliberately and says what you are accepting. |
| Asset register (maintenance) | Each handed-over asset with its tag, location, lifecycle stage, linked maintenance contracts and warranty. |
Who uses it
| Who | When |
|---|---|
| Project manager or site head | Prepares the packet and records the customer's sign-back. |
| Facilities or maintenance head | Receives the register, sets up routine maintenance and tracks warranties. |
| Finance head | Watches the retention release dates tied to the defects period. |
Related
- Maintain: the asset register, maintenance contracts and warranties.
- Projects and contracting: handover packets, snags and retention.
- Follow every tonne from estimate to installed: what must be reconciled before the project closes.
Questions
What is Construction-to-maintenance continuum in Kinnow?
When a project is handed over, its assets join maintenance automatically, with warranties and maintenance contracts attached.
What changes for the business?
Developers and facility managers skip re-typing everything between construction and operations.
Is it available today?
Yes, it is live.
Do I have to type every asset again after handover?
No. The assets listed in the signed handover packet become asset records in maintenance, with the warranty period from the packet. You then assign maintenance routines to them.
What if the handover is sent twice by mistake?
Each project and asset tag is recorded only once, so the second one adds nothing. If the first attempt fails, it is retried rather than lost.
More in the Your records and documents
Change approvals safely, see the impact first Live in part
Change approval rules in plain words, see which pending items are affected, trial it quietly, then go live.
Your records and documents · Record trace & document chainWhere is this stuck, and with whom?
Key documents show their journey: the steps done, who holds the record now and how long it has waited, with who did each step where that was recorded.
Your records and documents · ProcessesYour processes, mapped honestly
See each end-to-end process as a diagram showing which steps the system enforces and which are just notes.
Your records and documents · Your Statements, Your LayoutFinancial statements in your old system's format
Switched systems? See your P&L and balance sheet in the same layout your team already checks against.
Your records and documents · Statement Bridge (As Seen On · Entered Since)Match receivables to a customer's statement, fast
Tie your receivables to a customer's statement date: what they saw, what changed since, what's owed now.
Your records and documents · Work-to-Money SettlementFinished field work becomes invoices and paperwork
Every completed duty, delivery or visit is priced with the calculation shown, and goes to billing when someone presses Settle.
Tell Kinnow what slows you down.
Answer three questions. Get the applications, the agents and a two-week plan for your business.