Asset or stock?
The dividing line is whether you follow the individual one. Ten spare heaters in a store are a stock line; the heater installed in room 12 is an asset with a history. Towels are stock: nobody follows towel number 7.
For each asset, record what it is, a tag or code, where it is, its state — in store, installed, in repair, written off, missing — what it cost, and every move. Write-offs and missing items need a reason; a register where anything can quietly disappear answers nothing about a theft.
The register is also what preventive maintenance schedules against, and what a repair ticket points at.
Example
TV-014, bought for ₹22,000, installed in room 205. Moved to repair on 3 March, back in store on 10 March, installed in room 107 on 12 March. The log shows every move, when, and who made it.
How Nivasik handles it
- An asset register — in store, installed, in repair, back, written off — with a movement log that cannot be edited.
- The log is written by the database whenever an asset moves, not by the screen, so it cannot be skipped.
- Issuing a stock item into a room makes it a tracked asset; a repaired unit returning to store goes back on its own stock line.
- A reason is required for disposal, write-off and missing.