Home › Learn

How do you run a wall-to-wall asset inventory that's still accurate next quarter?

By Thaddeus Stepanovich — Founder, Harbinge.rs · 14 years in EMS and healthcare IT

When is a wall-to-wall inventory worth it?

A wall-to-wall inventory is a big, disruptive undertaking — it pulls staff off other work, requires access to occupied clinical spaces, and takes days to weeks depending on facility size. It's worth that cost in a handful of specific situations, and worth questioning in most others.

Audit prep. A Joint Commission survey, a DNV assessment, or an internal compliance review is coming, and leadership needs confidence that the asset register matches reality before an outside party starts asking. A wall-to-wall walk ahead of a known survey window is one of the more defensible reasons to run one — it gives you a documented reconciliation with a clear trigger and a clear audience.

CMDB or asset-register baseline resets. If the current database has drifted so far from reality that nobody trusts it — duplicate entries, phantom assets that were disposed of years ago, real assets that were never entered — patching it field by field usually costs more than starting over. A full walk gives you a clean baseline to build ongoing confirmation on top of, which matters because a good process built on a bad baseline just keeps the bad data current.

Mergers, acquisitions, and facility moves. When two organizations combine asset registers, or a department relocates to a new floor or building, the old records usually don't map cleanly onto the new physical reality. A walk at the moment of transition is often the only way to get an accurate starting point, because there's no existing record worth reconciling against — you're establishing one.

Financial reconciliation and PO sweeps. Finance or procurement periodically needs to verify that capitalized equipment still exists and is where the books say it is, particularly around depreciation schedules, insurance renewals, or a lease-versus-owned reconciliation. This is narrower in scope than a full CMDB reset — usually a defined asset class or a defined dollar threshold — but it's still a physical walk against a list, not a paperwork exercise.

What doesn't justify a wall-to-wall inventory, on its own, is "our data seems a little off." That feeling is almost always evidence of drift, not evidence that a full walk is the fix — see why CMDB location data goes stale for what's actually driving that feeling and what fixes it that a one-time walk won't.

How do you scope and sequence the walk?

Scoping decisions made before day one determine how smoothly the whole exercise runs. Two structural choices matter most.

By floor and department, or by asset class? Sequencing by physical location — one floor, one wing, one department at a time — keeps the walk room-complete: once a team clears 4-West, nobody has to come back to it later for a different asset type. Sequencing by asset class instead — all infusion pumps first, then all workstations on wheels, then all monitors — can make sense when a single specialized team (biomed, for instance) needs to handle one category and a different team handles another, but it means walking the same physical space multiple times. For most hospital inventories, room-complete sequencing by floor/department wins on total labor, because walking a room once and capturing everything in it is more efficient than four teams each walking it once for their own category.

How fast will the walk actually go? Pace estimates vary enormously by facility density, asset mix, and how much of the walk is spent locating assets versus recording them, so treat any finds-per-hour number as a planning heuristic to calibrate against your own pilot floor — not a measured fact you can import from somewhere else. A reasonable way to build your own number: run the process on one representative unit first, time it honestly including interruptions, and extrapolate from that rather than from an industry average that was measured in a different building with a different asset density. Dense clinical floors with high equipment turnover (ICU, ED) typically move slower per square foot than administrative space with sparse, static furniture and workstations — plan more walker-hours for the former and don't be surprised when the schedule you built off the latter runs long.

Locked and occupied clinical spaces. Operating rooms, isolation rooms, and occupied patient rooms can't be walked on the inventory team's schedule — they have to be walked on the unit's schedule, which usually means early morning before procedures start, during scheduled turnover windows, or with a charge nurse escort who can judge in real time whether entry is appropriate. Build these into the sequence as their own pass, planned with unit leadership in advance, rather than assuming the inventory team can access every room on a fixed calendar. Losing this coordination is one of the most common reasons a wall-to-wall inventory runs long — not because the counting is slow, but because the team spends half a day waiting outside a room that won't be clear until 2pm.

Why do outside contractors struggle with room names?

Hospitals frequently bring in outside contractors — biomed vendors, inventory specialists, or general labor — to do some or all of a wall-to-wall walk, especially when internal staff can't be pulled off patient-facing duties for days at a time. This is where room-name-based asset lists break down hardest.

Every hospital accumulates informal room names that exist nowhere in any official floor plan: "the old peds supply room," "the closet by 3-East nurses' station," "where radiology used to be before the remodel." Staff who have worked the unit for years navigate by this shared vocabulary without thinking about it. A contractor walking into the building for the first time has none of that context, and neither does a spreadsheet that lists an asset's location as one of those informal names. The contractor either has to find and interrupt a staff member to translate every ambiguous entry, or guess — and a guess that's wrong doesn't fail loudly, it just quietly places an asset in the wrong location on a record nobody checks again for months.

A floor plan with pinned rooms sidesteps this entirely. Instead of asking a contractor to decode tribal knowledge, you hand them a map and a marked location, and "walk to the pin" works identically whether the person doing the walking has been in the building for ten years or ten minutes. This is also why floor-plan-based records travel well across staff turnover generally, not just for contracted work — see what makes an asset inventory audit-ready for how location precision feeds into that broader evidentiary standard.

What should you capture at each asset?

The single biggest determinant of whether a wall-to-wall inventory produces lasting value, versus a spreadsheet that's already stale by the time it's delivered, is what gets recorded at each stop — not how fast the team moves.

• Tag or serial number. The baseline identifier, matched against the existing register or entered fresh if the asset has none.
• Location confirmation, not just presence. Recording "asset exists" tells you less than recording "asset exists, and here specifically is where it was found" — pinned to a room or a spot on a floor plan, not a hallway-level approximation. A record that only confirms existence still leaves the next person guessing where to look; a record that confirms location closes that gap.
• Condition and a photo. A timestamped photo does two jobs: it gives whoever reviews the walk later a way to spot-check without re-visiting every room, and it creates a defensible record of condition at a known point in time — useful for warranty disputes, insurance claims, and disposal decisions down the line.
• Timestamp and walker identity. Who confirmed this, and when. Without both, a record can't be trusted or challenged — you can't tell a confirmation from six months ago apart from one from yesterday, and you can't ask a follow-up question if something looks wrong.

Those last two fields — timestamp and identity — are what turn a spreadsheet into evidence. A list of tag numbers with room names is a count. A list of tag numbers with confirmed locations, photos, timestamps, and named confirmers is audit-evidence, and it's the difference a surveyor or an internal auditor will actually notice. See what makes an asset inventory audit-ready for the fuller list of fields that satisfy specific accreditation and compliance frameworks.

How do you keep the baseline from rotting?

Every wall-to-wall inventory has an expiration date, and it's shorter than most organizations expect. The moment the walk ends, assets start moving again — reassigned between units, relocated for repair, rolled to wherever the next shift needs them — and none of those moves are captured by the walk you just finished. This is the drift problem in its purest form: see why CMDB location data goes stale for the underlying mechanics of why this happens so fast in a mobile-asset-heavy environment like a hospital.

The instinct is to schedule the next big walk — annually, semi-annually, whatever cadence budget allows — and treat that as the maintenance plan. That's a losing strategy on its own, because it means the database is only accurate for a short window after each walk and drifts the rest of the time. A once-a-year reconciliation doesn't create ongoing accuracy; it creates a repeating cycle of accurate-then-stale-then-accurate-again, with the stale period lasting far longer than the accurate one.

The more durable approach is to stop treating location confirmation as a standalone project and start building it into work that's already happening daily — a technician servicing a device, a biomed tech responding to a ticket, a unit clerk doing rounds. If confirming an asset's location takes seconds and piggybacks on a task someone was already doing, it doesn't compete for dedicated time the way a scheduled walk does, and the baseline the wall-to-wall inventory established stays current instead of slowly reverting to guesswork.

Where Forager fits

Forager's Inventory Placement Mode is built for exactly the walk described above: as a team moves room to room, they scan each asset and place it directly on the building's floor plan — no informal room names to decode, no separate spreadsheet to reconcile afterward. Location, tag, condition, photo, timestamp, and walker identity are captured in the same pass, on the same floor plan a contractor or a permanent staff member can navigate identically.

The part that matters more than the walk itself is what happens after it. The floor plan and asset placements from the wall-to-wall inventory become the live baseline, and the same lightweight scan-and-confirm action that ran the walk is what technicians use afterward during normal ticket work — so the baseline the inventory established keeps getting re-confirmed as a side effect of daily activity instead of waiting for the next scheduled walk to catch up on everything that moved in between.

Forager doesn't replace the judgment call of when a wall-to-wall inventory is warranted — audit prep, a baseline reset, a merger, a PO sweep still call for one. What it changes is what that walk leaves behind: a floor-plan-anchored record built to stay current, rather than a spreadsheet built to go stale. See how Forager works.