Asset & IT Management

Asset and IT Management defines a small equipment register and a practical handover workflow. Its recommendation is to give each asset a serial number and named holder, record assignment on day one, and release it on exit. The proposed sequence is purchase, assignment to a person, location recording, return on exit, and write-off. The emphasis is on keeping handovers accurate rather than merely recording purchases.

A short recommendation is the default output. Advice receives a direct answer, a review checks the supplied process, and a build request produces the requested artifacts after essential questions are resolved. An existing spreadsheet or inbox-based process can be captured before conversion. The skill asks only one missing question at a time and stops when further answers would not change the design.

Intake considers asset count and categories, whether equipment is shared or personal, who assigns it, acknowledgement practices, serial-number tracking, warranties, insurance, the current list, and missing assets. It also distinguishes an inventory, returns view, or spend view as the requested outcome. Unknown facts remain unknown.

Use it for an asset tracker, IT asset management register, laptop inventory, or equipment register. It fits Growth stage in the Onboard layer. A request can be:

Laptops keep disappearing after people leave and we cannot find them.

It provides empty templates, not device imaging, wiping, or MDM enforcement. It does not calculate payroll, tax, leave balances, KPIs, or depreciation. No automation, reminders, or synchronization are included. Human legal, tax, and HR review remains necessary before using a design for real decisions.

The nineteen-field structure covers Asset Name and ID; Asset Type; Assigned Date and Assigned To; Linked Accounts; Brand/Model; Condition; Current Value; Department; Location; Notes; Purchase Date and Purchase Value; Currency; Return Date; Serial Number; Status; and Warranty Expiry. Purchase and current values retain currency types, lifecycle dates retain date types, and Linked Accounts is a relation rather than free text. Return Date may be absent before return or without a verified source; it must not be invented to satisfy a schema.

Starting asset types include Laptop, Monitor, Phone, Tablet, Accessory, Furniture, and Software License. Condition runs from New through Needs Repair to Retired; status includes In Use, In Stock, In Repair, Retired, and Lost. These sets can be adjusted to the business vocabulary.

Requested CSV, SQL DDL, JSON Schema, and Notion mapping derive from one field list. CSV and JSON preserve matching display names, with normalized SQL identifiers documented. Excel-compatible CSV uses a UTF-8 byte order mark; number, date, and currency formats need application after import. An Excel workbook requires a specific request. Templates remain empty unless clearly synthetic examples are requested.

Notion output is handled by notion-manual-import. Linked Accounts requires the target database to exist before its relation resolves. Manual mappings need no connection; live workspace changes require verified access, target, and authorization and must be confirmed by a successful operation.