A fixed-asset audit that took three weeks now takes two days.
62 branchesFour states1,900 staff
The situation
What we found
The annual fixed-asset verification took a team of six almost three weeks, and still closed with a schedule of items marked “not sighted”.
Equipment moved between branches informally. The register recorded where an asset was bought, not where it currently sat.
Access to server rooms and vaults relied on a card that could be lent, and a visitor book nobody reconciled.
Branch queue times were discussed in every management meeting and measured in none of them.
Where three weeks of asset verification went
One annual verification cycle across 62 branches, before any change.
Travelling between branches8 days
Locating items by hand, room by room6 days
Reconciling against the register4 days
Investigating items not sighted2 days
And 214 items still closed the year unresolved.
Almost none of this is judgement work. It is looking for things, which is the one task a machine does better than a person.
Illustrative scenario
The service blueprint
Everything the customer sees, and everything they do not.
A service blueprint lays the whole service out at once: the touchpoints across the top, and underneath each one the evidence, the customer’s own actions, the staff they meet, the work happening out of sight, and the systems holding it up. The line of visibility is the one that matters — almost every delay lives below it.
Opening an account, blueprinted end to end
The customer experiences four minutes of form-filling. Below the line of visibility sits everything that decides whether they wait four minutes or four days.
Enquire
Arrive at branch
Identity capture
Approval
Card and activation
Physical evidence
EnquireThe website, a messaging reply, a reference number.
Arrive at branchThe branch door, a queue ticket, a seat with a visible wait time.
Identity captureThe camera, the fingerprint reader, a printed acknowledgement.
ApprovalAn SMS the same day, not a promise to call back.
Card and activationThe card, handed over in branch, and a wallet pass on the phone.
Customer actions
EnquireAsks one question: what do I need to bring?
Arrive at branchTakes a ticket and sits down.
Identity capturePresents identification once; photograph and fingerprint captured.
ApprovalWaits — and can see how long the wait should be.
Card and activationActivates the card and makes a first transaction.
Line of interaction — the customer touches the organisation here
Onstage — staff the customer meets
EnquireA contact-centre agent, or an automated reply with a document checklist.
Arrive at branchA floor host who directs, and a screen showing position in the queue.
Identity captureOne account officer, who does the whole capture rather than passing it on.
ApprovalNobody. The customer is not made to sit through the approval.
Card and activationThe teller who hands over the card and watches the first transaction succeed.
Line of visibility — everything below this line is invisible to the customer
Backstage — work they never see
EnquireNothing yet — but the enquiry is logged, so a follow-up is possible.
Arrive at branchTicketing data feeds the branch dashboard in real time.
Identity captureDocuments scanned and validated; the photograph checked against what was captured.
ApprovalCompliance review, with a turnaround target and a named owner.
Card and activationCard printed and encoded, and the asset register updated if hardware moved.
Line of internal interaction — where staff hand work to systems
Support systems
EnquireEnquiry log and contact-centre record
Arrive at branchQueue and branch performance dashboard
Identity capturePhoto validation and fingerprint capture
ApprovalApproval workflow with escalation after 24 hours
Card and activationInline card encoding, wallet passes, asset register
The bank had spent years improving the top three rows. Every real delay lived below the line of visibility — which is exactly why nobody had found it.
Illustrative scenario
The workflow
The same service as a workflow, exceptions and all.
The asset verification workflow
What used to be three weeks of searching, rewritten as a route with exceptions.
1
The branch schedule is issued
Each branch gets a date and an expected asset list drawn from the register.
Head office financeAsset registerAutomatic
2
A staff member walks the branch with a handheld reader
Several hundred tags are read in a room without opening a single cabinet.
Branch operations officerHandheld UHF reader
If an item does not respondIt is flagged on the spot, not written on a list to investigate weeks later.
3
Found, missing and unexpected are separated automatically
Three lists rather than one, so the exceptions can be worked while the team is still there.
No staff involvementAsset registerAutomatic
4
Unexpected items are traced to their real branch
Most “missing” assets turn out to be present somewhere else. The portal logs show when they moved and through which door.
Regional operationsDoorway reader portals
If there is no movement recordIt becomes a genuine loss investigation — a much shorter list than before.
5
Movements are approved retrospectively or corrected
The register is brought back into line with reality, once, rather than drifting all year.
Regional operationsAsset register
6
Finance signs off
Two days after it started, with an exception list short enough to actually read.
Head office financeAsset register
Illustrative scenario
The work
What we put in
What we put in, and in what order
Deployed branch by branch over one quarter, starting with the four largest.
1
Stage one
Every asset tagged, including the awkward ones
UHF tags across ATMs, servers, generators and branch IT. On-metal tags where the surface would otherwise kill the signal — which covers most of what a bank owns.
2
Stage two
Verification by walking, not by looking
A handheld UHF reader picks up several hundred tags in a room without anyone opening a cabinet.
8 days of travel to 2
3
Stage three
Doors that record what passes through them
Reader portals at branch back doors and the head-office loading bay. An asset leaving is logged automatically; one leaving without a movement note raises an alert.
4
Stage four
Access that cannot be lent
Facial recognition on server rooms and vault doors, with fingerprint at the till for supervisor overrides. A card can be handed to a colleague; a face cannot.
5
Stage five
Visitors on the record, not in a notebook
Photograph captured and validated at reception, badge printed and encoded on the spot, and the badge deactivates itself at the end of the day.
Paper visitor book retired
6
Stage six
Queue times that appear on a dashboard
Ticketing data feeding a branch performance view, so a regional manager sees which branch is struggling on a Monday morning rather than in next month’s report.
Illustrative scenario
The result
What changed
One audit cycle later
Same asset base, same audit scope, same finance team.
Duration of the fixed-asset verification3 weeks
Staff assigned to it6
Items closing the year unresolved214
Assets whose current branch was knownAbout half
Proof of who entered the server roomA signature
An audit finding waiting to happen, every single year.
Duration of the fixed-asset verification2 days
Staff assigned to it2
Items closing the year unresolved9
Assets whose current branch was knownEvery one
Proof of who entered the server roomA face, with a timestamp
The finance team stopped dreading the fourth quarter.
Illustrative scenario
The technology
What each piece is actually for
The technology, in plain words
Nothing exotic. The value is in reading things automatically instead of by hand.
UHF RFID tagsLong-range tags, readable several metres away and hundreds at a time. This is what turns a search into a walk.All fixed assets
On-metal tagsA tag built to work when stuck to metal, which ordinary tags cannot do. Banks are full of metal.ATMs, servers, safes, generators
Handheld readersA staff member walks through a room and the register updates itself.Branch verification
Doorway reader portalsFixed readers either side of a door that record every tagged item going out and coming back, without anyone doing anything.Back doors and the loading bay
Facial recognitionConfirms the person, not the card. Removes the borrowed-badge problem entirely.Server rooms and vaults
Fingerprint recognitionUsed where a deliberate, witnessed action matters more than speed.Supervisor overrides at the till
Photo validation and instant badgingVisitor photographed, checked, and issued an encoded badge that expires the same day.Reception
Illustrative scenario
About this case study.
Banking is a fictional organisation. The situation, the figures and the outcomes are
illustrative — they show how BTS Consulting approaches a problem of this shape and
what the technology involved actually does. They are not a record of a delivered project,
and nothing here should be read as a client result.
More case studies
The same approach, different sector
A state university
Higher Education
A university where every department held its own version of the student, and nobody could say where the laboratory equipment was.
Tell us where performance is being slowed, hidden or lost. We will help you define the problem, identify the priority actions and build a practical path forward.
