Asset Decommission & Transfer Log

The problem this kills

Assets do not live forever. A pump gets scrapped. A generator moves from one site to another. A leased machine goes back to the customer. And almost every time, the paperwork lags behind reality.

So your asset registry slowly fills with ghosts - equipment that is gone, sold, or sitting at a different address, but still showing as active. Those ghosts keep generating preventive maintenance (PM) tasks nobody can do. Technicians get dispatched to assets that are not there. Contract renewals quote equipment that left months ago. And when someone finally retires an asset, its service history - every repair, every inspection, every part - quietly vanishes or gets tangled up at the new location.

The worst part is there is usually no gate. Anyone can flip an asset to "retired" in a spreadsheet, even when it still has open work orders. There is no record of who decided, when, or why. History is lost. Schedules keep firing. The registry drifts further from the truth every quarter.

This tool ends that. Every removal, retirement, or move becomes a reviewed change request. Before anything is committed, the tool shows the real impact, blocks the unsafe ones, and waits for a manager to approve.

What you'll build

A small, secure web app your asset controllers, service managers, and dispatchers log into. With it they can:

• Submit a change request for any asset - decommission (retire/scrap) or transfer (move to another site or customer) - with the reason, the effective change date, and the destination.
• See the impact instantly: open work orders on that asset, its active PM (preventive maintenance) schedule, and any linked contract - all surfaced before anyone commits.
• Be blocked from decommissioning an asset that still has open work orders, so you never retire something with unfinished jobs.
• Send it to a manager who reviews the impact and approves or rejects - the human gate.
• On approval: the asset's status flips (retired or transferred), its full service history is preserved and carried with it on a transfer, and future PMs are stopped automatically.
• Export a clean change log as CSV in exactly the columns your system of record expects.

What's inside the Implementation Plan

• It starts by interviewing you about your business. Before building anything, the plan has the AI agent ask you about your asset registry, your status codes, your site and customer naming, your PM schedule, your approval rules, and your messiest edge cases. It reflects a short tailored spec back to you and waits for your thumbs-up. The tool that gets built matches your registry - not a generic template.
• A copy-paste runbook you feed to Claude Code one step at a time.
• The exact data model for assets, change requests, history, and the audit trail - shaped by your interview answers.
• The impact view: open jobs, PM schedule, and contract for the asset being changed.
• The decommission block when open work orders exist, and the history-carry logic for transfers.
• The manager approval gate, with email notifications via Resend.
• Duplicate guards so the same change (asset + change date) can't be processed twice.
• The CSV import (your registry) and CSV export (the change log) fallback, so it works today with zero integration.

The governance it includes (this is the point)

This is not a loose spreadsheet macro. The plan builds in real controls from the start:

• Login so only your team can open the tool.
• Row-level security so people only ever see their own organization's assets and changes.
• A complete audit trail - who submitted, who approved, what changed, and exactly when.
• A hard human-in-the-loop approval gate - the tool drafts the change and shows the impact, but a manager must approve before the registry or any schedule is touched.
• Duplicate guards keyed on (asset + change date) so the same decommission or transfer can't slip through twice.
• A safety block that refuses to decommission an asset with open work orders.

Who it's for

Asset controllers who own the registry's accuracy. Service managers who sign off on retirements and moves. Dispatchers who get burned when a "live" asset turns out to be gone. If you maintain a fleet of equipment across sites or customers and your registry keeps drifting from reality, this is for you.

You've got this - paste the first prompt and let the agent interview you.