These asset management dashboard examples use three unique equipment IDs to show custody, readiness, and requests separately. The initial October 13, 2026 view has one checked-out projector, one available adapter, and one returned laptop awaiting review. Filters expose the records behind each count, while a conflict example shows when a custodian needs confirmation.
Read the three records
A01 is a projector checked out to U01 on October 10 and due October 12. No return is supplied, so it remains checked out. A02 is a display adapter with check-in R02 dated October 10 and readiness record V02 supplied. Under this example's rule, it is available. A03 is a laptop with return receipt R03 dated October 13 but no V03 readiness record. Its state is Returned awaiting review.
The records are fictional and date only. Their exclusive states reconcile as 1 + 1 + 1 = 3 assets. The record labels describe the supplied sample, not an inspection of actual devices. Keep the responsible role, actual event date, and source reference with each real checkout, return, and review.
Use filters that answer an operational question
Choose Awaiting review to isolate A03 and the missing V03 reference. Its filtered count is one; the whole register still has three unique assets. Choose Available to see only A02. Q02, a proposed October 14 request for A02, stays in a separate request note. It does not create a checkout or reserve the adapter.
Snipe-IT's getting-started documentation describes assignment, return, and a later return to circulation within an example workflow. Use that distinction to decide what your own readiness evidence must contain. The dashboard does not supply technical preparation instructions, actual assignment permission, or an assurance that an item works.
Count overdue as an overlapping flag
On October 13, A01's October 12 due date is in the past, and its actual return is absent. It therefore has one overdue flag. That flag belongs to the existing checked-out asset; adding it to the three exclusive states would invent a fourth asset.
The header gives the as-of date. In this example, a due date earlier than that date with no actual return produces the overdue flag. Use your team's actual date and time rules for a real register. Do not manufacture a grace period or a contact deadline from the example. No reminder is sent when the flag appears.
Inspect a contradictory custodian
Open the custody-conflict example. A second A01 source names U02, contradicting the supplied U01 checkout. The unique asset total remains three, but A01's current custodian becomes unresolved. The view retains both references and stops treating A01's assignment as confirmed. It does not pick the last row or count two projectors.
Return to the baseline to restore the consistent sample, then filter by asset ID to trace one item. An unmatched ID produces an empty result with an explicit zero matching count. Resolve the source conflict before assigning the item. A change in the display is only an inspection aid; actual custody events and decisions remain in the team's maintained register.
Copy this prompt to adapt the example
Design an equipment desk with custody totals above a searchable asset list, keeping unresolved custody separate from confirmed assignments. Return one self-contained HTML file with embedded styling and working interactions. Use readable type, strong contrast, clearly labeled keyboard controls, and a layout that flows on a narrow phone. Identify the supplied data as a fictional example.
Use three fictional assets as of October 13, 2026. A01 projector: checkout to U01 October 10, due October 12, return absent. A02 display adapter: check-in R02 October 10 and readiness V02 supplied, Available under the sample rule. A03 laptop: receipt R03 October 13, readiness V03 missing, Returned awaiting review. Show unique total 3 and baseline states 1/1/1. Overdue A01 is an overlapping flag, never a fourth asset.
Provide real filter buttons for All, Available, Awaiting review, and Checked out, plus an asset-ID search. Filtered count and visible records must agree; show an empty state for an unmatched query. Keep the whole-register total labeled separately. Include a button to inspect a conflicting A01/U02 source beside A01/U01. In that mode retain three unique IDs, show current custody unresolved, and exclude A01 from confirmed custody-state counts. Restore baseline with another button. Keep Q02, a proposed October 14 request for A02, separate from checkout. No assignments, real-device checks, or persistence.
A03 now gives the equipment owner a specific follow-up: find the missing review before counting the item as available. Render the sanitized HTML comparison in NOS when that person needs to see the custody history beside the totals. Their answer belongs in the asset register; the next issue count should follow that corrected history.