The week-of count checklist I use so an equipment asset register still matches what is on hand

Mid-register cleanup is necessary. A week-of physical count is different. This is the pass I run when someone is about to rely on the register for a board packet, an insurance conversation, a move, a renewal, or a simple “what do we actually have?” handoff. At that point, a dual serial is not a harmless note, “somewhere” is not a location, and a Slack message saying “I think we still have it” cannot quietly turn a last-seen item into on-hand truth.

I am a freelancer admin helper. I turn messy equipment dumps into clean asset registers. I am not a CPA, bookkeeper, insurance agent, or tax advisor — and this is not financial, tax, legal, insurance, or depreciation advice. It is a practical spreadsheet and physical-count checklist for keeping stated facts, observed facts, and unresolved questions separate.

This is complementary to my earlier posts, not a rewrite. For the full equipment dump → asset register workflow, see How I turn a messy equipment dump into a clean asset register. For the mid-register pass while identity, proof, and warranty details are still being cleaned up, see The mid-register checklist I use so an equipment asset register stays honest. This third pass starts with the physical count and the intended handoff: what can the register honestly say this week?

What “honest enough for a week-of count” looks like

• The count boundary and as-of date are explicit — not an old export wearing a current-looking filename
• One physical item maps to one row, with a serial or asset tag confirmed, missing, or marked ask — not two conflicting serials silently merged
• Location and custodian are specific enough to check — home office, storage shelf B, or client site, not “somewhere”
• Disposed, returned, replaced, loaned, or missing items cannot masquerade as active on-hand equipment
• Warranty end is a sourced date or ask — “probably covered” is not a date
• Slack recollections are labeled folklore or needs recheck unless the count or a source supports them
• A reader can tell what was physically seen, what was record-only, and what still needs confirmation without reconstructing a message thread

If the only count evidence is a message titled “I think we still have it,” the week-of pass has already slipped.

The week-of count checklist (run it before anyone treats the register as truth)

Use this against the near-final register and the live artifacts: the prior register, serial photos, receipts, warranty documents, storage notes, loan records, return confirmations, and the locations where equipment is supposed to be. The point is not to make every row green. The point is to make every row legible.

1. Set the count boundary before you walk around

• [ ] Write the count date, time window, and locations included — a Friday desk check is not automatically a whole-business count
• [ ] State what “on hand” means for this pass: physically seen, confirmed by named custodian, or another documented rule
• [ ] Keep older exports and prior counts as sources, not as current truth — superseded rows are labeled prior or recheck
• [ ] List locations that were not checked — closed storage, a client site, a travel bag, or a home office should not disappear into a blank cell
• [ ] Skim test: you can answer “as of when, in which places, under what on-hand rule?” without opening Slack

2. Match each physical item to one row

• [ ] Use the serial, asset tag, model, and a short physical description to match the item — not only a generic name such as “the laptop”
• [ ] If two serials appear for one item, keep both in notes and set the row to ask or recheck until one is verified
• [ ] If one serial appears on two rows, do not count two physical items just because the register has two lines
• [ ] Record a visible serial or asset tag only when it was actually seen in the count or supported by a source — never fill a blank with a guessed number
• [ ] Separate included accessories or kits when the count rule needs separate custody; otherwise state why they remain grouped
• [ ] Skim test: every counted item has one row, and every unresolved identity conflict is visible from that row

A dual serial is not a formatting problem. It may be a swapped sticker, a replacement device, a serial copied from an order, or two devices collapsed into one row. The register can say serial conflict — needs photo or owner confirmation and still be useful. It cannot honestly say “confirmed” while leaving both numbers active.

3. Replace “somewhere” with a checkable location

• [ ] Name the current location at the level needed for a recheck: room, shelf, cabinet, bag, vehicle, client site, or custodian
• [ ] If the item moved during the week, record the current location and the move note separately from the old location
• [ ] “Someone has it,” “with ops,” and “somewhere in storage” stay ask, unowned, or recheck — they are not locations
• [ ] For shared equipment, name the custodian or checkout record rather than assigning ownership by assumption
• [ ] For a client-site, travel, or loaned item, record the expected return or next check as a note, not as proof that it is physically present
• [ ] Skim test: another person could find or recheck the item using the register alone

4. Remove disposed ghosts from active on-hand

• [ ] Compare each apparent on-hand row with return, sale, RMA, replacement, disposal, or loss evidence
• [ ] Mark disposed, returned, replaced, loaned, missing, or unknown items with the agreed status — do not leave them active because the old row is convenient
• [ ] Keep a disposed or historical record when useful, but make the status and as-of boundary unmistakable
• [ ] If a replacement has a new serial, do not let the old serial inherit the new device’s on-hand status
• [ ] Treat “we probably got rid of that” as recheck, not as a completed disposal record and not as active inventory
• [ ] Skim test: the active on-hand count does not include a device that the evidence says was sold, returned, replaced, or otherwise gone

An old row can be valuable history without being current inventory. I would rather see “disposed — confirmation missing” than a tidy active row that creates a false count.

5. Date warranty facts instead of repeating folklore

• [ ] Capture the warranty end from a certificate, order record, manufacturer portal, or other named source when available
• [ ] Keep “registered?” separate from “warranty end” — registration status does not supply a missing end date
• [ ] Leave the end date ask when the source says only “standard warranty” or someone says “it should still be covered”
• [ ] Keep dual warranty dates visible until the source and the item identity agree
• [ ] Do not extend, backdate, or infer coverage because the purchase year looks familiar
• [ ] Skim test: every date in the warranty column has a source or an explicit unresolved label

6. Reconcile the count without letting Slack rewrite it

• [ ] Mark each row as physically seen, custodian-confirmed, record-only, not located, disposed, or ask using a small, consistent vocabulary
• [ ] Put the evidence for a material status in Source or Notes: count photo, serial sticker, return email, custodian confirmation, or named document
• [ ] Label “I think we still have it,” “it is probably in the closet,” and similar messages as folklore unless a later check supports them
• [ ] Resolve duplicate sightings and stale confirmations before updating the on-hand count
• [ ] Do not use a Slack reaction, a green cell, or an unchallenged old row as a substitute for a count result
• [ ] Skim test: someone reviewing the register can distinguish observed on-hand from remembered on-hand in under a minute

7. Run the handoff and board-or-insurance tripwires

• [ ] The header states the as-of date, count scope, exclusions, and unresolved exception count
• [ ] The active count, disposed count, unknown count, and recheck list can be explained without mental arithmetic across old tabs
• [ ] Dual serials, vague locations, disposed ghosts, warranty gaps, and folklore are grouped in an exception view or clearly marked in-row
• [ ] Raw photos, receipts, and private messages are linked or named appropriately without pasting unnecessary personal or secret information into the share view
• [ ] The register says what it supports and what it does not — a count snapshot is not automatically a valuation, coverage decision, tax schedule, or depreciation conclusion
• [ ] Final skim: a new reader can answer “what was actually seen, where, as of when, and what still needs confirmation?” from the register alone

Soft CTA

If you have a messy equipment dump and want a clean asset register with a visible question and exception list, assetssheet on Gumroad is $12. Code ADMIN12 gives $2 off. You can also browse the full shop or the catalog mirror. Use whichever is useful; there is no need to rush a count that still has unresolved serials or locations.

Not a CPA, bookkeeper, insurance agent, or tax advisor. Not financial, tax, legal, insurance, or depreciation advice — just practical admin cleanup so the week-of on-hand line says what the count can actually support.