Skip to main content
GullySystem
Home services

Estimate/Quotation Management for Locksmiths

Keep itemised estimates and their approved revisions together.

Finance & Accounting

Does this function belong in your operation?

Use when scope and prices are agreed before an order.

A buyer asks for pricing before confirming work.

Prices a lock upgrade, a door repair after a burglary or a full building rekey from the lock count and hardware grade. The quote can be revised on site. An accepted version becomes the job card.

Bring the records the workflow depends on.

  • Items and units
  • Rates and tax settings
  • Approval terms

Outputs to check

  • Versioned estimate document
  • Approval and acceptance history
  • Accepted billing or order input

Follow the estimate/quotation management workflow.

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

  1. 1. Record the requirement

    Capture scope, quantities and the customer's requested terms.

  2. 2. Prepare the estimate

    Use approved units, rates and tax settings.

  3. 3. Review exceptions

    Approve discounts, exclusions and nonstandard terms.

  4. 4. Issue and revise

    Retain the version sent and each subsequent change.

  5. 5. Record acceptance

    Link the agreed version to order creation or final billing.

Who uses the module, and who approves?

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

Sales executive

Sees quotes waiting to be sent, quotes waiting on the client, and today’s follow-up list.

Estimator

Builds the costing behind the quote from measurements, material and labour, and keeps it beside the drawing.

Owner

Sees what went out this week, at what margin, and which discounts were given without being asked for.

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.

Customer changes quantity

Save a revision and recalculate affected lines before acceptance.

Expired validity

Require the price and terms to be reviewed before using the estimate.

Discount beyond authority

Hold the revision for approval and retain the original proposed amount.

Can this work independently?

An estimate can be prepared independently from entered items and rates. Item catalogues, pricing and tax settings improve consistency when connected. Order creation and invoicing are downstream processes; acceptance should preserve the agreed version rather than overwrite the estimate with later rates.

Systems and records it connects with

  • Lead management: Enquiry sources, owners and qualification decisions.
  • Proforma invoice: Provisional supply amounts and related advance requests.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Price lists and schemes: Effective-dated rates and customer eligibility rules.

Configure, test and introduce the workflow.

  • We read quotations you sent recently. You pass over the rate list and a few finished quotes, and we sketch the screen layout.
  • Items, units, discount limits and standard terms go in. Proofreading the list is yours. The printed quotation is matched to your letterhead. A draft PDF is sent for your comments.
  • Executives raise real quotes in parallel with the old method. Mismatches are logged and discussed. New enquiries start in the system. Estimators and executives get a short session each.

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.

  • Earlier revisions remain available.
  • Totals use approved settings.
  • The accepted version is identifiable.
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 estimate/quotation management?

Use when scope and prices are agreed before an order. A buyer asks for pricing before confirming work.

What should we bring to the requirements discussion?

Bring anonymised examples of Items and units; Rates and tax settings; Approval terms. 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 itemised estimates and their approved revisions together. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An estimate is not a tax invoice or proof of acceptance.

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. Earlier revisions remain available. Use this check when reviewing the first working version.

Talk to us

Discuss estimate/quotation management 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