Asset Transfer & Location Move Log

The problem this kills

An asset moves. A laptop goes from Sales to Support. A forklift gets shuffled from the north warehouse to the south. A test rig is "borrowed" by another team and never comes back on paper. And your asset register - the spreadsheet or system that's supposed to say who owns what, where it lives, and which cost center pays for it - quietly goes stale.

The damage is slow but real. Finance keeps charging depreciation to a cost center that no longer has the equipment. An audit turns up a machine that's "in Building A" but physically sits in Building C. A department manager gets billed for gear they handed off months ago. And when something walks out the door for good, nobody can say who last owned it. The root cause is almost always the same: someone moved the thing, but the move never got recorded - or it got recorded on one person's say-so, with no agreement from the team receiving it.

This tool replaces the "I'll update the spreadsheet later" honor system with a clean, two-signature process. Nothing in the register changes until both sides agree the asset really moved.

What you'll build

A small internal web app, just for your team, that:

• Imports your asset register from a CSV (asset ID, name, current owner, department, cost center, location, status) and your org / department list.
• Lets a facilities coordinator or manager raise a transfer request: this asset, from here, to there, with a target effective date.
• Requires dual approval - the sending owner approves the asset is leaving, and the receiving owner accepts they're taking it on. Nothing moves on a single signature.
• Blocks transfers of Retired or disposed assets - you can't move something that's officially gone.
• Dedupes on (asset + open transfer) so the same asset can't be caught in two pending moves at once.
• Only after both sign-offs, updates the register - department, cost center, location, and owner - stamped with the agreed effective date.
• Keeps a complete transfer log and exports a journal CSV for finance so cost-center moves can be tracked and posted.

What's inside the Implementation Plan

The plan is a single markdown file you paste into Claude Code (a free AI coding agent). It walks the agent through building the whole tool, step by step, each step ending with a ready-to-paste prompt.

The most important part: the plan opens by interviewing you about your business. Before it writes a single line, the agent asks how assets get moved today, what your register actually looks like (the real field names, your asset-ID and cost-center conventions), who the sending and receiving "owners" are, how effective dates drive your cost-center accounting, and your messiest edge cases (an asset mid-move that gets disposed, a transfer to a brand-new cost center, a swap between two sites). It reads a short tailored spec back to you, you confirm it, and only then does it build - so you get a tool shaped to your asset register, not a generic template you have to bend to fit.

Inside you'll find:

• The discovery interview and how the agent turns your answers into the data model.
• The full build: database, login, register + org-list import, the transfer-request form, the dual-approval flow, the register update with effective date, and the finance export.
• The hard human approval gate and the dual sign-off logic, enforced in code.
• Verification steps so you can prove it works, and the CSV-export fallback so it's fully usable even before you connect it to your asset system.

The governance it includes (this is the point)

This isn't a toy. The plan builds in the controls a facilities and finance team actually needs:

• Login so only your team can see or touch anything.
• Row-level security so people only see the assets and transfers that belong to your organization.
• A complete audit trail - every request, approval, acceptance, rejection, and register update is logged with who and when.
• A hard human-in-the-loop gate - the AI drafts and routes the transfer, but the register is updated only after both real owners sign off; nothing is ever auto-applied.
• Dual approval enforced in code - the register physically cannot change on one signature.
• Duplicate guards - a Retired/disposed asset can't be moved, and the same asset can't have two open transfers at once.

Who it's for

Facilities coordinators, department managers, and asset/finance owners who are tired of an asset register that drifts out of date the moment something gets moved - and who want a real, auditable transfer process without hiring a developer or buying a heavyweight asset-management platform. You don't need to write code. You need your register CSV, your department list, and an afternoon.

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