Skip to main content
GullySystem
Home services

Job Cards for Locksmiths

Keep the inspection, work, parts and status of a service job together.

Field Service

Does this function belong in your operation?

Use when service or repair work needs a record beyond an appointment.

A repair or field-service request is accepted.

A card follows each job from call to payment: address, lock type, what was opened or fitted and the proof of identity seen. Photos of the door before and after are attached. Customers sign on the phone.

Bring the records the workflow depends on.

  • Customer and asset details
  • Reported issue
  • Work and parts approval rules

Outputs to check

  • Service job and inspection record
  • Approved parts and labour statement
  • Completion and billing handoff

Follow the job cards workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Open the service job

    Capture the customer, asset and reported issue.

  2. 2. Inspect and estimate

    Record findings and proposed work before chargeable changes.

  3. 3. Obtain approval

    Retain the customer's or authorised manager's decision.

  4. 4. Perform the work

    Record labour, parts, tests and unresolved findings.

  5. 5. Close and hand over

    Issue completion evidence and send approved billing inputs to accounts.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Service advisor

Opens the card, builds the estimate, records approval and tells the customer where their machine stands.

Technician

Reads the complaints and inspection notes, and sees the parts issued to their job.

Storekeeper

Issues against a card number and not to a name shouted from the bay.

Accounts assistant

Bills from the card line for line, and records what was paid.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Extra repair discovered

Record the finding and obtain approval before adding chargeable work.

Part unavailable

Keep the job waiting with the required item identified.

Customer declines work

Record what was inspected, what was refused and the authorised closing outcome.

Can this work independently?

Job cards can run with entered customer and asset records. Scheduling assigns staff, stock controls parts, and invoicing creates the bill from approved work. Closing a technical job should be distinguishable from financial settlement or customer acceptance where those occur later.

Systems and records it connects with

  • Estimates and quotations: Approved estimate lines, revisions and acceptance references.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Spare-parts stock: Item-location quantities and authorised stock movements.
  • Technician scheduling: Assigned field jobs and technician availability.

Configure, test and introduce the workflow.

  • We trace a vehicle from gate to delivery. You show us today’s slips, and we return the card layout we propose.
  • Stages and who may change them are agreed. A chart on a page is yours to approve. The parts list and labour rates are loaded. Storekeepers test issuing against dummy cards.
  • Cards run alongside paper for a stretch. Differences are discussed with advisors and technicians. Cards become the only record. The workshop team gets a short practice on phones.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Parts usage links to the job.
  • Unapproved additional work remains flagged.
  • Completion retains the service record.
Locksmiths

How the business operates.

A locksmith firm sells speed and trust. A caller locked out at night wants someone soon, and a landlord or building manager wants proof of who was given which key. Both depend on private, accurate records. Neither can wait.

Call intake and dispatch

Log each call with address, lock type and urgency, then send the nearest available technician and keep the customer informed of arrival.

Job cards with identity checks

Record the work done, the person who authorised it and how their right to the property was checked, with photographs where needed.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Call intake and dispatch. Log every call with address, lock type and urgency, assign the nearest available technician and keep the customer informed.
  • Job cards and identity checks. Record the work, the person who authorised it and the check made on their right to the property, with photographs where needed.
  • Key and keycode register. Hold key systems, keycodes and issue lists for each site, visible only to chosen roles, with every view and change logged.
  • Master key systems. Record the levels of each master key system, which keys are cut, who holds them and which have been returned or lost.

Operational bottlenecks to check

Calls are dispatched from memory

Technicians are spread across an area, and the dispatcher keeps their positions in their head. The nearest available person is not always the one sent.

Key records are held on paper

Keycodes, master key charts and issue lists sit in a book or a spreadsheet. Anyone with access to the file can read them.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Call

    The phone rings. Address, lock type, urgency and caller details go on the record, and a price range is given before anyone is sent.

  2. 2. Dispatch

    The nearest available technician is assigned by area and skill. The customer receives an arrival window by message or phone.

  3. 3. Check and work

    The technician records how the caller’s right to the property was checked, then the work done and each part fitted.

  4. 4. Stock and keys

    Parts are deducted from the van. New keys, cylinders and systems are added to the site’s key record under restricted access.

  5. 5. Billing

    The job card produces the invoice. Payment by card or cash is posted on site, and account customers receive an invoice.

  6. 6. Follow-up

    Rekeying, key audits and contract visits are scheduled from the job. Reminders go out ahead of each date.

Industry reports to connect with

  • Calls received and response by technician and area
  • Jobs by type: lockout, rekey, fit and upgrade
  • Parts and blanks used against each job
  • Access log for key and keycode records

Questions before implementation.

When should locksmiths consider job cards?

Use when service or repair work needs a record beyond an appointment. A repair or field-service request is accepted.

What should we bring to the requirements discussion?

Bring anonymised examples of Customer and asset details; Reported issue; Work and parts approval rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Keep the inspection, work, parts and status of a service job together. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

A job card records work and does not itself certify repair quality or equipment safety.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Parts usage links to the job. Use this check when reviewing the first working version.

Talk to us

Discuss job cards for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements