Guides
What Locksmith Software Should Record and the KPIs to Watch
How locksmith software should fit the calls, dispatch, and invoices a shop already runs, plus what records and fields to keep and which KPIs to track.
What to take away
- Buy software that fits how your shop already takes a call, dispatches a van, and closes an invoice. A demo that ignores your rekey and emergency mix is a demo for someone else's shop.
- Put the keying schedule, the customer's authorization, and the work order in the same record. If the technician cannot see who authorized the job, the job should not start.
- Test the hard cases before you signa callback on a master key system, a partial rekey, a disputed invoice, a failed card payment, and a full data export.
- Give every technician a named account with the permissions their role needs. Shared logins destroy the audit trail you will want when a customer disputes a charge.
- Confirm licensing, insurance, and record retention with your state licensing board, your insurer, and a tax professional. They vary by state and city.
Start with the calls you already run
Software does not fix a dispatch process. It records one. Write down what happens now, in the order it happens, for the four calls that make up most locksmith revenue.
Four Locksmith Call Types
- Residential lockout: call, quote, dispatch, open, collect
- Rekey and master key: survey, schedule, order, install, test
- Commercial account: work order, confirm scope, dispatch, bill
- Automotive: verify ownership, confirm vehicle, dispatch with programmer
The caller reaches a dispatcher. The dispatcher quotes a range and assigns a van. The technician confirms the address and the customer's authority to authorize work. The technician opens the door, collects payment, and closes the ticket.
Someone surveys the doors and counts cylinders. They write a keying schedule, order blanks, and schedule the work. Then they install, test every key, and hand over the schedule with the new keys.
A commercial account call: a property manager emails a work order, you confirm the scope and the site contact, dispatch inside an agreed window, and bill against a purchase order.
An automotive call: you verify the caller owns the vehicle or is authorized to authorize work on it, confirm the year, make, and model, and dispatch a technician with the right credential programming equipment.
Each of those four has a different record. A system that only models the first will fail the other three, and the failure shows up as a callback or an unbilled hour.
What the software has to hold
Every job needs the same spine. It must record who called and what they authorized. It must record what was quoted and who was dispatched. It must record when they arrived and what parts left the van. It must record what was installed and what was paid. It must record what the customer signed.
Locksmith-Specific Record Fields
- Keying informationcylinder, keyway, master key level
- Authority to workname and reference number
- Credential and code datatransponder, key codes, safe combinations
- Restricted keyway flagged as not re-cuttable at hardware store
- Confirmation written into ticket, not a text thread
- Credential data access limited to fewer dispatchers
For locksmith work specifically, add three fields most generic field-service tools do not have.
Keying information. Which cylinder, which keyway, which master key level, and what the customer's existing system allows. A restricted keyway job cannot be re-cut at a hardware store, and the record has to say so.
Authority to work. Who authorized the job, and how you confirmed it. For a landlord, a property manager, or a fleet account, that is a name and a reference number. For a vehicle, it is proof of ownership. Write the confirmation into the ticket, not into a text thread.
Credential and code data. Transponder and proximity credentials, key codes, and safe combinations belong in a record with tighter access than the general job list. Not every dispatcher needs to see them.
If a system cannot hold those three, it is a scheduling tool with a locksmith label.
The numbers that change a decision
Pick the smallest set of measures that would make you do something differently. A report nobody acts on is a report you stop reading.
KPIs and What They Change
Measure
- Response time
- Arrival minus call time
- First-visit completion
- First-trip jobs divided by dispatched
- Callback rate
- Return visits divided by completed
- Revenue per van hour
- Invoiced revenue divided by paid hours
- Quote-to-close
- Jobs sold divided by quotes
- Receivables aging
- Outstanding invoices by age band
Formula
- Response time
- Next van placement
- First-visit completion
- Van stock and dispatch
- Callback rate
- Training, parts, install checks
- Revenue per van hour
- Pricing and routing
- Quote-to-close
- How the phone is answered
- Receivables aging
- Which accounts get credit terms
What it changes
- Response time
- First-visit completion
- Callback rate
- Revenue per van hour
- Quote-to-close
- Receivables aging
| Measure | Formula | What it changes |
|---|---|---|
| Response time | Arrival time minus call time | Where you place the next van |
| First-visit completion | Jobs finished on the first trip divided by jobs dispatched | Van stock and dispatch questions |
| Callback rate | Return visits divided by completed jobs | Training, parts, and install checks |
| Revenue per van hour | Invoiced revenue divided by paid van hours | Pricing and routing |
| Quote-to-close | Jobs sold divided by quotes given | How the phone is answered |
| Receivables aging | Outstanding invoices by age band | Which accounts get credit terms |
Let R be your response-time target, V the number of vans on the road, and C the calls per hour your dispatcher can actually handle. Your reachable service area is set by R and V together, not by how far you are willing to drive.
Callback rate is the one to watch hardest. A rekey that fails because the cylinder was worn, a master key system that will not accept the new key, or an electric strike installed without checking the frame all come back as a second trip you did not bill. Track the cause, not just the count.
Test it before you sign
Run these in a sandbox with your own data, not the vendor's demo script.
- A callback on a master key system.Check that the record shows the original keying schedule, the cylinder, and the keyway.
- A partial rekey.Check that the schedule updates only the doors you touched and leaves the rest of the master key levels intact.
- A disputed invoice.Check that the quote, the authorization, the technician, and the payment sit in one record.
- A failed card payment.Check that the ticket does not close until the money is collected or invoiced.
- A full data export.Check that every customer record leaves in a format you can open outside the vendor's system.
- An account authority check.Send a work order the way a property manager or fleet customer would, then confirm the ticket holds the name and the reference number.
- A restricted-record test.Sign in with a dispatcher account and confirm it cannot open key codes, transponder and proximity credentials, or safe combinations.
Sandbox Test Before You Sign
- Time a full call-to-payment cycle
- Enter three-level master key system, print schedule
- Process partial completionfour of six doors rekeyed
- Void invoice, refund, confirm accounting export
- Export every record in openable format
- Sign in as dispatcher, confirm no safe combinations
- Pull network, confirm mobile app records completed job
If step five fails, stop. Data you cannot export is data you do not own, and the cost of discovering that after cancellation is a rebuild of every customer record.
Access, records, and the rules around them
Give every person a named account. Shared logins mean the audit trail names nobody, which is exactly the trail you need when a customer disputes a charge or a key code goes missing.
The federal guidance is not locksmith-specific, which is why it holds up. The NIST small business quick-start guides walk through risk assessment and access control in plain steps. The CISA small business guidance covers the practical side of protecting customer data. Neither tells you which software to buy; both tell you what to require of it.
Record retention has a tax side and a licensing side. The IRS recordkeeping guidance explains how long to keep the documents behind your income and expenses. Your state licensing board may set a separate rule for work orders and keying records. Confirm both before you set a deletion schedule.
If your website advertises a response time, a coverage area, or a license number, the claim has to hold up. The FTC advertising guidance explains what substantiation means for a small business. A dispatcher quoting thirty minutes at 2 a.m. is making an advertising claim.
Comparing platforms against these requirements is the work behind locksmith software reviews. Bring the seven sandbox tests to every demo and score the results, not the sales pitch.
Common questions
Should the software hold safe combinations and key codes?
Only if you can restrict who sees them. If every dispatcher and technician can open the record, keep that data in a separate system with its own access list.
How do we handle a customer who cannot prove authority?
Do not start the work. Record the refusal, the reason, and the name of the person who could not authorize it. That record protects you if the property owner calls later.
What belongs on a keying schedule?
Door number and location are recorded. Cylinder type and keyway are recorded. Master key level and quantity of each key issued are recorded. A schedule a customer cannot read is a schedule they will lose.
When should we replace the system instead of fixing it?
When the export test fails, when the record cannot hold keying or authority data, or when the vendor will not commit to support hours in writing. Fixing a scheduling tool that cannot hold a locksmith record just delays the same decision.
