5 things to check in chimney sweep software

What to take away

This article covers business systems for chimney service companies. It is not advice in these areas:

What the software actually has to hold

A sweep's week is not a generic service call.

Those answers decide whether the job is a routine sweep or a Level 2 inspection, and whether you send one technician or two. Software that cannot store the answers forces the office to keep them in a notebook beside the screen.

From there the job runs through site protection, sweeping, a camera look at the flue, a written report, and often a repair estimate the customer takes to a mason or a WETT-certified technician. Each of those is a record the software either holds or loses.

Check one: dispatch and routing

Dispatch for a sweep is a route problem with a skills constraint. A technician certified for wood appliances may not be the one you send to a gas fireplace, and a two-storey masonry flue takes longer than a bungalow's.

Test whether the software can hold a certification field per technician and block an assignment that does not match. Test whether it can group jobs by postal area, because a sweep driving across a city between two sweeps loses the third.

Ask what happens when a job runs long. If the schedule cannot push the next arrival time to the customer automatically, someone in the office is making phone calls all afternoon.

Check two: flue and appliance records

This is where chimney software separates from general field-service tools. You need a record per flue, not per address. A house with a wood stove, a furnace flue and a fireplace has three, and they get swept on different cycles.

Test whether the software can flag a flue that is due, and whether it can hold a photo or video attachment from the inspection. If the report goes out as a PDF the customer can forward to their insurer, that is the document doing the work.

Check three: money handling

A sweep business takes deposits for larger repair work, runs callbacks that should be billed or written off, and often bundles a sweep with a inspection for one price. The software has to follow all three.

Run a test: a bundled sweep and inspection, a deposit on a liner job, a partial refund when the customer cancels the repair, and a failed card payment. Then check that the accounting export matches what the bank settled.

If the system shows revenue that has not settled, someone will eventually treat it as cash. Reconcile before you trust a dashboard.

Check four: data ownership and exit

Before you sign, ask for a complete export of jobs, customers, flue records, photos and invoices in a format you can open without the vendor. Ask what it costs, how long it takes, and whether attachments come with it.

Contracts should state who owns the data, how long it is retained after you leave, and what happens to it on deletion. Get the retention and deletion terms in writing.

Test the export during the trial, not at renewal. A vendor that cannot produce your flue history in a usable file is holding your business records.

Check five: total cost, not subscription price

The subscription is one line. Add data cleanup, migration of existing customer and flue records, configuration, training hours, and the owner's time on the project. Add the cost of running two systems while you transition.

Ask about support hours in your time zone, the escalation path when something breaks on a Saturday in cottage season, and how updates are scheduled. Ask whether the price is per user, per job or per technician, because that changes as you hire.

Budget for the year, not the month. A cheap subscription with a long migration is not cheap.

A worked example: one week, two jobs

A two-technician shop books a Monday sweep and a Wednesday WETT inspection. The sweep is a wood stove in a bungalow; the inspection is a masonry fireplace in a two-storey with a cracked crown the customer mentioned at booking.

In the software, the booking form captures fuel, appliance, last sweep and the crack note. Dispatch assigns the WETT-certified technician to Wednesday and blocks the uncertified helper. Site protection, sweep and camera notes attach to the flue record, not the customer record.

The report goes out Tuesday. The crown repair is quoted as an estimate and handed to a mason, with the inspection report attached. Payment for the sweep settles Thursday; the estimate stays open.

If any of those steps lives outside the system, the shop is running two records and will eventually bill from the wrong one.

Before you sign

If a vendor will not run these with you in a sandbox, that is the answer.

Where the checks come from

The security and recordkeeping questions are not invented for this trade. NIST's small business quick-start guides set out practical starting points for risk management, including access control and data handling.

CISA's guidance for small and midsize businesses covers the common digital risks a small operation faces, which is why individual accounts and multifactor authentication matter more than a feature list.

The IRS recordkeeping guidance explains what a business must be able to produce, which is the standard your export should meet.

The EPA's Burn Wise chimney sweep page carries public education material on annual inspection and wood burning, useful when you write the customer-facing reminder text.

For the wider comparison, see our review of chimney sweep software options and what each one handles well.

Common questions

Does a general field-service tool work for a sweep business?

Sometimes, if it can hold a record per flue and a certification field per technician. Most cannot do both, and you end up tracking flue history in a spreadsheet beside the software. Test those two things first.

How long should implementation take?

It depends on how many customer and flue records you are migrating and how much cleanup they need. Ask the vendor for a written plan with named milestones, then compare it against your own estimate of the owner time involved.

What is the biggest hidden cost?

Migration and training, not the subscription. Cleaning up years of inconsistent customer records takes longer than most owners expect. Budget the hours before you commit, and keep the old system readable until the new one is proven.

Should we switch mid-season?

Rarely. Chimney work peaks in fall and again before cottage season, and a mid-season migration puts two systems in front of the same technicians. Plan the change for the shoulder months when call volume drops.