Asset Request Management

Every transfer requires a barcode or QR code scan at the new location. The custodian receiving the asset scans the code using a mobile device, then confirms the new building and room. The register updates in real time. The previous custodian's responsibility ends when the new custodian accepts the transfer. A complete transfer history is maintained for each asset, showing every location change with timestamps, so auditors can trace an asset's movement throughout its lifecycle. If an asset is scanned in a location that does not match the register, the system generates a discrepancy alert for the operations team to investigate.

Each asset category is configured with a depreciation method (straight-line, declining balance, sum-of-years-digits, or units-of-production), useful life, and salvage value. The system calculates depreciation automatically and posts journal entries to the general ledger on the accounting calendar you define, monthly or quarterly. Because the asset register and accounting module share the same database, there is no reconciliation step. When an asset is disposed, the system removes the remaining book value from the fixed asset account and records the disposal entry in a single transaction. Your controller sees depreciation expense by department, category, and funding source in standard financial reports without exporting data between systems.

Yes. Approval chains are fully configurable by asset category, dollar threshold, department, funding source, and campus location. For example, you might route IT equipment under $1,000 to the IT director only, lab equipment between $1,000 and $5,000 to both the department head and the operations director in sequence, and any request above $5,000 to the CFO as a final approver. Grant-funded requests can add a parallel approval from the grants compliance officer. Delegation rules automatically redirect approvals when an approver is unavailable, and escalation timers push stalled requests to a backup reviewer after a configurable number of business days.

Maintenance schedules are defined at the asset category level with configurable intervals. HVAC equipment might have quarterly filter changes and lab instruments might require semi-annual calibration, while vehicles need annual safety inspections. When a due date arrives, the system generates a work order with the asset location, custodian contact, required parts, and maintenance checklist. Completed work orders log the date, technician, cost, parts consumed, downtime hours, and any condition notes. If a work order is not completed by the due date, the system escalates to the operations director. Maintenance cost per asset accumulates over time, giving the CFO a total cost of ownership figure that informs repair-versus-replace decisions at budget time.

A typical deployment for an institution with 5,000 to 10,000 tracked assets takes six to ten weeks. Weeks one and two cover configuration: asset categories, depreciation methods, approval workflows, barcode label format, location hierarchy, maintenance schedules, and user roles. Weeks three through five handle data migration, importing existing asset records from spreadsheets, assigning barcodes, validating serial numbers, uploading warranty documents, and linking custodians to employee records. Weeks six and seven focus on user training for requestors, approvers, receiving staff, facilities coordinators, and maintenance technicians. Institutions with complex multi-campus location hierarchies or large fleets of specialized lab equipment may extend to ten weeks. A phased rollout is common: start with IT equipment in phase one, add lab and facilities assets in phase two.