Equipment Check-In & Check-Out

Equipment check-in and check-out is how NexusRMS tracks every item as it leaves and returns to your warehouse. By scanning equipment at both ends of a project, you create a complete chain of custody — recording who handled each item, when it moved, and what condition it was in. This process is essential for accurate availability data, damage accountability, and insurance documentation.

The three tracking methods

How equipment is scanned during check-out and check-in depends on the tracking method configured on the equipment item. NexusRMS supports three methods, each with different scanning behaviour:

• Bulk — Tracks by quantity only. No individual serial numbers are scanned. The operator enters the number of units being dispatched or returned. The fields quantity_check_out_scanned and quantity_check_in_scanned record how many units have been processed.
• Serialized — Tracks individual units by serial number. During check-out, the operator scans any serial number belonging to the equipment type — NexusRMS does not mandate which specific serial is used. This is ideal when units are interchangeable.
• Serialized Specific — Tracks individual units with exact assignment. The operator must scan the exact serial number that was assigned to this project line item (stored in equipment_serial_id). Scanning a different serial of the same type will be rejected. Use this when specific units have been promised to the client or when regulatory compliance requires tracing exact assets.

Check-out from warehouse

Check-out is the process of recording equipment as it leaves the warehouse for a project. To begin, open the project and navigate to the equipment or warehouse interface, then start the check-out session. The screen displays all equipment allocated to the project with the expected quantity for each line item.

As each item is scanned or entered, the following fields are updated on the ProjectEquipment record:

• check_out_scanned — Boolean flag set to true when the item has been scanned out
• check_out_scanned_at — Timestamp of when the scan occurred
• check_out_scanned_by — The user who performed the scan
• checked_out_at and checked_out_by — Timestamp and user confirming the check-out
• check_out_scan_log — A JSON array recording each individual scan event, including the serial number (if applicable), timestamp, and user

For bulk items, quantity_check_out_scanned increments with each unit processed until it matches the allocated quantity.

Condition recording at check-out

Each item scanned during check-out is assigned a condition rating in the condition_out field. This establishes a baseline that will be compared against the condition recorded at check-in. The operator can accept the default (the item’s last recorded condition) or override it if the item’s state has changed. Any observations can be noted in the condition_notes field.

Prep tracking

Before check-out, warehouse staff may prep equipment — picking, testing, and packing items ready for dispatch. NexusRMS tracks this preparation with dedicated fields:

• quantity_prepped — How many units of this line item have been prepped
• prepped_at — Timestamp of when prep was completed
• prepped_by — The user who performed the prep

Prep tracking is separate from check-out. An item can be prepped (packed and ready) but not yet checked out (not yet dispatched). This distinction allows warehouse teams to prepare equipment in advance whilst keeping dispatch as a separate, auditable step.

Kit and container operations

Equipment can be organised into kits and containers for efficient handling. NexusRMS tracks these groupings with detailed audit fields:

• Kits — Line items with is_kit set to true act as parent containers. Individual items reference their kit via parent_kit_id. When a kit is fully packed, it can be sealed, recording kit_sealed_at and kit_sealed_by. Items are assigned to kits with timestamps: assigned_to_kit_at and assigned_to_kit_by.
• Containers — Physical transport containers (flight cases, road cases) are tracked via container_id. Packing an item into a container records packed_into_container_at and packed_into_container_by. Sealing the container records container_sealed_at and container_sealed_by.

Sealed kits and containers can be scanned as a single unit during check-out rather than scanning every individual item inside, saving significant time on large projects.

Check-in to warehouse

Check-in is the reverse process — recording equipment as it arrives back at the warehouse. The check-in screen displays all items that were checked out, along with their check-out condition for reference. As items are scanned, the following fields are updated:

• check_in_scanned — Boolean flag set to true when the item has been scanned in
• check_in_scanned_at — Timestamp of the scan
• check_in_scanned_by — The user who performed the scan
• checked_in_at and checked_in_by — Timestamp and user confirming the check-in
• check_in_scan_log — A JSON array recording each scan event
• condition_in — The condition of the item upon return

For bulk items, quantity_check_in_scanned increments with each unit processed.

Condition comparison and damage reporting

When an item is scanned during check-in, NexusRMS automatically compares condition_in against condition_out. If the condition has deteriorated (e.g., from Excellent at check-out to Fair at check-in), the item is flagged and the operator is prompted to add notes in the condition_notes field, describing the damage. Photographs can be attached as evidence. The operator can also create a repair ticket directly from the check-in screen, routing the item to the Repairs & Maintenance module.

Equipment status transitions

Each ProjectEquipment line item has its own status that tracks its lifecycle within the project:

1. Available — The item exists in inventory and can be allocated
2. Reserved — The item is allocated to the project (soft or hard depending on project status)
3. Checked Out — The item has been scanned out of the warehouse
4. Checked In — The item has been scanned back into the warehouse
5. Cancelled — The allocation has been cancelled (item released back to stock)

Warehouse status integration

Check-out and check-in operations drive the parallel warehouse status on the project. When items begin to be checked out, the warehouse status progresses through Prepped and Dispatched. When all items are checked back in, the warehouse status moves to Returned. The project cannot move to the Completed status until all equipment has been checked in.

Bulk scanning operations

For large projects with dozens or hundreds of items, NexusRMS supports rapid bulk scanning. Enable Continuous Scan Mode on the check-out or check-in screen — each successful scan automatically advances to the next item without requiring a tap between scans. An audible confirmation tone plays for each successful scan, and an error tone sounds if an item is not recognised or not allocated to the project.

Tips

• Always record condition at both ends — A documented condition at check-out and check-in protects you in damage disputes with clients
• Use Continuous Scan Mode for large projects — It dramatically speeds up the scanning process
• Seal kits before check-out — Sealed kits scan as one unit, saving time on repetitive item-by-item scanning
• Resolve missing items before completing the project — The project cannot reach Completed status until every checked-out item has been accounted for

Next steps

Continue to the troubleshooting article for solutions to common project issues, including equipment conflicts, financial calculation errors, and status transition problems.