Checking Out & Returning Assets

AccuArk's checkout system lets you track the temporary assignment of assets to employees. Unlike a transfer, which represents a permanent or long-term reassignment, a checkout is designed for short-term use — lending a laptop for a business trip, issuing tools for a project, or temporarily assigning equipment to a different team. The system tracks who has the asset, when it is due back, and what condition it was in at checkout and return.

Accessing the Checkout Form

To open the Asset Checkout form:

1. Navigate to Assets > Check Out Asset from AccuArk's main menu
2. This opens the the Check Out screen form

You can also initiate a checkout from within an asset's detail form by clicking the Check Out button on the toolbar, which opens the Check Out screen with the asset pre-selected.

Required Permission

You must have the Check Out Assets permission assigned to your role to check out assets and process returns. Without this permission, the Check Out Asset menu item is hidden and the Check Out button on the asset detail form is disabled. The Super Admin role has this permission by default.

Checking Out an Asset

To check out an asset to an employee:

1. Open the the Check Out screen form
2. Select the asset — Search by asset number, name, serial number, or barcode. Only assets with an 'Active' status that are not already checked out can be selected.
3. Select the employee — Choose the employee who will be receiving the asset. The dropdown lists all active employees.
4. Set the expected return date — Enter the date by which the asset should be returned. This is used for overdue tracking.
5. Record condition at checkout — Select the asset's current physical condition from the dropdown:
   • Good — The asset is in normal working condition with no visible damage
   • Fair — The asset is functional but shows some wear or minor cosmetic issues
   • Poor — The asset has significant wear, cosmetic damage, or functional limitations
6. Add notes (optional) — Enter any relevant notes about the checkout. For example, 'Issued for trade show in Dallas, March 1-5' or 'Battery replaced before checkout — new battery installed Feb 2026'.
7. Click Submit to complete the checkout

What Happens on Checkout

When you submit a checkout:

1. A checkout record is created in the asset_checkouts table with a status of 'checked_out'
2. The record stores the asset ID, employee ID, checkout date, expected return date, condition at checkout, and notes
3. An entry is written to the asset_activity_log with activity_type 'checked_out', including the employee name and expected return date
4. The asset's assigned employee is updated to the checkout employee (so it shows as assigned to them in the Asset Register)
5. A success message confirms the checkout

The asset remains in the 'Active' status but is now flagged as checked out. If another user tries to check out the same asset, they will see a message indicating it is already checked out to another employee.

Returning an Asset (Check In)

When an employee returns a checked-out asset, the return must be processed to update the checkout record and release the asset for future use.

To process a return:

1. Open the the Check Out screen form
2. Click the Returns tab or the Process Return button to switch to the return view
3. The form displays a list of all currently checked-out assets. You can search or filter to find the specific checkout record.
4. Select the checkout record for the asset being returned
5. Record the actual return date — This defaults to today's date but can be adjusted if the asset was returned on a different date
6. Record condition at return — Select the asset's physical condition at the time of return:
   • Good — The asset is in the same or similar condition as when it was checked out
   • Fair — The asset shows additional wear compared to checkout
   • Poor — The asset has noticeable new damage or degradation since checkout
7. Add return notes (optional) — Document any issues observed at return. For example, 'Screen has a small scratch on the upper left corner' or 'All accessories returned in original bag — no issues'.
8. Click Submit Return to complete the return

What Happens on Return

When you submit a return:

1. The checkout record's status is updated from 'checked_out' to 'returned'
2. The actual return date, condition at return, and return notes are saved to the checkout record
3. An entry is written to the asset_activity_log with activity_type 'returned', including the condition comparison
4. The asset is released and becomes available for future checkouts or transfers
5. A success message confirms the return

Checkout Status Values

Each checkout record has a status field with one of the following values:

Condition Tracking

One of the most valuable aspects of the checkout system is condition tracking. By recording the condition at both checkout and return, you create an accountability record that shows whether an asset's condition changed while it was in someone's possession.

Condition Comparison

The checkout record stores two condition values:

• condition_at_checkout — The condition recorded when the asset was issued to the employee
• condition_at_return — The condition recorded when the asset was brought back

Comparing these two values immediately reveals whether the asset deteriorated during the checkout period. For example:

This information is valuable for employee accountability, maintenance planning, and asset lifecycle decisions.

Overdue Tracking

AccuArk automatically tracks overdue checkouts by comparing the expected return date against the current date. When an asset has not been returned by its expected return date, it is flagged as overdue.

Where Overdue Checkouts Appear

Overdue checkouts are surfaced in several places to ensure they do not go unnoticed:

• Asset Dashboard alerts grid — The Asset Dashboard (Assets > Dashboard) includes an alerts section that lists all overdue checkouts. Each alert shows the asset name, asset number, employee name, expected return date, and the number of days overdue.
• Checkout list — In the the Check Out screen form, overdue checkouts are highlighted visually (typically in red or with a warning icon) so they stand out from checkouts that are still within their return window.

How Overdue Calculation Works

The overdue calculation is straightforward:

• If the current date is past the expected return date AND the checkout status is still 'checked_out' (not returned), the checkout is overdue
• Days overdue = Current Date - Expected Return Date
• Checkouts that have been returned (status = 'returned') are never flagged as overdue, even if the actual return date was after the expected return date

Managing Multiple Checkouts

An asset can only have one active checkout at a time. However, over the course of its lifecycle, an asset can be checked out and returned many times. The checkout history is maintained in the asset_checkouts table and is visible on the asset's Activity tab, providing a complete record of who had the asset and when.

To view checkout history for a specific asset:

1. Open the asset in the Asset Details screen
2. Navigate to the Activity tab
3. Filter or scroll to see 'checked_out' and 'returned' activity entries

Tips and Best Practices

• Set realistic return dates — Choose a return date that reflects when the asset is genuinely expected back. If you are unsure, estimate on the longer side — you can always process an early return. Setting artificially short return dates generates unnecessary overdue alerts.
• Review the overdue list weekly — Designate someone to review the overdue checkouts on the Asset Dashboard at least once a week. Follow up with employees who have overdue items to either process a return or extend the checkout.
• Document condition changes at return — When the return condition is worse than the checkout condition, always add detailed notes explaining the damage or wear. This documentation is essential if you need to file an insurance claim or discuss the issue with the employee.
• Photograph condition at checkout and return — For high-value assets, take photos before issuing and after receiving. Attach these photos to the asset record on the Images tab with descriptive captions that reference the checkout dates.
• Use checkouts for temporary assignments only — If an asset is being permanently reassigned to a new location or employee, use the Transfer Asset form instead. Checkouts are designed for temporary, time-bounded assignments.
• Communicate expectations to employees — When checking out an asset, make sure the employee understands the expected return date and their responsibility for the asset's condition. The notes field is a good place to document any verbal agreements.
• Process returns promptly — When an asset is physically returned, process the return in AccuArk immediately. Delayed processing leads to inaccurate overdue reports and makes condition documentation less reliable because memory of the return condition fades over time.

Related Articles

• Transferring Assets Between Locations
• Asset Dashboard & Analytics
• Editing Asset Details
• Asset Activity Log & Audit Trail