30-Day Maintenance Software Rollout Plan for 10 Sites

Many maintenance software rollouts fail quietly. Nobody decides the system is bad. It just stops being used, because managers were busy, the vendors ignored it, and the person who set it up moved on.

This maintenance software implementation plan is built to avoid that. It assumes you operate around ten locations, such as restaurants, convenience stores or similar sites, and that you have no dedicated IT or facilities team. Adapt the timing to your situation.

Where numbers appear, they are our estimates or illustrative targets, not benchmarks.

The principles

1. Start small, then widen. Two or three pilot sites before ten.
2. Make the first use trivial. Reporting a problem should take under a minute.
3. Do not ask vendors to change. If contractors need an account, expect delay. Passwordless links avoid that.
4. One owner. Someone is accountable for the rollout, with a named backup.
5. Count real repairs, not logins. A site is live when it has logged a real repair.

Before day 1: preparation (2-3 hours)

Do these before you touch the software.

• Name the rollout owner. Usually an operations lead or the owner.
• List your sites. Names, addresses, site manager, regional manager. Mark which two or three will pilot.
• List your vendors by trade. Primary and backup for HVAC, refrigeration, plumbing, electrical, pest, fire, grease trap.
• Agree what each priority means. Concoct uses four fixed priorities: Low, Medium, High and Emergency. Write one line and one example for each. For example, Emergency means food safety, a safety hazard or a store that cannot operate.
• Pick your success measures. See "How you will know it works" below.
• Decide your tier. Recurring preventive maintenance schedules are on every tier. If you employ in-house technicians or want checklists and inventory, you need Growth or Professional. Prices are in USD per location per month on the pricing page.

Week 1: set up and pilot (days 1-7)

Day 1-2: configure the basics

• Create your organisation and add your pilot locations. Add the other locations as each one goes live, not before: every location is billed from the day it is added.
• Add user accounts for the rollout owner, regional managers and the pilot-site managers. Users are unlimited, so there is no reason to share logins.
• Add your vendor list. If it already lives in a spreadsheet, it can be imported.
• Decide who reviews requests from store staff and turns them into work orders, and who sends jobs to vendors.

Day 3: load the pilot equipment

Choose two or three pilot sites. Pick ones with a cooperative manager, a mix of equipment, and an ordinary level of complexity. Not your best store and not your worst.

At each, record the major equipment: make, model, serial number, install date. Aim for the top ten items by cost or by how much trouble they cause.

You do not have to be the one walking every store. Ask each pilot manager to photograph the data plates, and import any equipment list you already have from a spreadsheet (CSV) rather than typing it. On the Professional tier, the AI nameplate scan can read details from a data-plate photo.

Day 4: brief the pilot managers (30 minutes, in person or call)

Cover only this:

• How to report a problem (a few fields and a photo).
• What the four priorities mean at your sites.
• That their first work order is expected within the week.
• Who to call when stuck.

Do not cover every feature. Explain what you need today.

Day 5-7: first real work orders

Ask pilot managers to log every issue, even small ones. Make the first dispatch to a vendor yourself, with the manager watching, so you see it from the vendor's side.

By the end of the week, each pilot site should have at least one real work order. If one does not, call the manager. That call is more useful than any reminder email.

Week 2: fix friction and bring vendors in (days 8-14)

Review the pilot

Hold a 30-minute review with the pilot managers. Ask three questions:

1. What was annoying?
2. What did you not use?
3. What would you tell the next manager?

Fix what can be fixed this week: adjust your priority guide and what you ask managers to include in a report.

Bring your vendors on

Contact your primary vendors by phone before the first system-generated message arrives. Say:

• You are moving to a single process for work orders.
• They will get a link by email for each job. No account or password is needed. Concoct does not send texts, so tell text-first vendors to watch their inbox.
• What you need back: whether they accept, an arrival time, whether a part is needed, and completion with a short note on what was done.
• When you expect an acknowledgement. Mention that an assignment nobody answers within 24 hours is unassigned automatically.

Send a test job to each primary vendor and confirm they can open it on a phone. Then cancel the test job. A test job left unanswered is unassigned after 24 hours and sends an alert to your owners and operations managers, which is noise you do not need. This step catches a lot of vendor friction early.

Start the weekly review

Pick a 20-minute weekly slot and keep it short so it survives. Look at four things:

1. Open work orders older than seven days. Why are they waiting?
2. Emergency and High items from this week. Was the response fast enough?
3. Repeat issues. Same equipment, same store, same fault.
4. Spend outliers. Any store far above or below the others? In Concoct, spend views are on the Professional tier; on other tiers, check your invoices.

Twenty minutes weekly beats a three-hour quarterly cleanup.

Week 3: expand to all ten sites (days 15-21)

Roll out in two waves

Go live with the next four or five sites early in the week, and the final batch late in the week or the following Monday. Add each wave's locations when that wave goes live. Splitting waves keeps support manageable.

For each site:

• Run the 30-minute manager briefing.
• Add their key equipment (start with the top five items; fill in the rest over time).
• Confirm their vendor list matches reality.
• Set a first-work-order deadline of seven days.

Add routines

Recurring preventive maintenance schedules are on every tier; checklists need Growth or Professional. Add the daily and weekly lists at pilot sites first, and widen them as the sites settle. Start with a short list; five items done every day beats thirty done never. Our restaurant maintenance checklist is a template you can cut down.

Week 4: tighten, measure, decide (days 22-30)

Chase the stragglers

Look at which sites have logged no work orders. For each, find out why. Common causes:

• The manager is new or overloaded.
• The manager has a workaround, such as texting you.
• They think nothing has broken.

Handle each differently. A workaround needs a conversation; an overloaded manager needs a delegate. If a pilot manager leaves, brief their replacement in their first week. The record they inherit is the point.

Review the data

Pull the month's numbers. Do not expect trend lines yet. Check that the data is complete enough to be useful:

• Is every site represented?
• Are equipment records present for key items?
• Are work orders closed, not left open?

How you will know it works

Pick a small set of measures before you start, and track them weekly. Illustrative targets by day 30 for a 10-site rollout:

• Sites that have logged at least one real repair. Target: 10 of 10.
• Share of repairs logged rather than handled by text. Target: most, and rising.
• Vendors acknowledging within the window you agreed. Target: rising week over week.
• Open work orders older than 14 days. Target: shrinking.

Also ask your managers directly whether they would go back to the old way. Their answer tells you more than any number.

Your own baselines matter more than these targets. If you can, count last month's repairs from texts and invoices before you start, so you have something to compare against.

Run this plan with your own sites

If you want to price it first, the per-location rates are on the pricing page. If you would like to run this plan with Concoct for your ten sites, book a demo. Bring your site list and vendor list, and we will walk through what week one would look like.

FAQ

Can we really roll out to ten sites in 30 days?

It is realistic if you start with two or three pilot sites, keep early training short, and have one named owner. Ten sites is manageable; the bigger risk is lack of ownership, not volume.

How much time does the rollout owner need?

Our estimate: roughly 4 to 6 hours in week one, then an hour or two a week after that. It depends on how much equipment you record and how much you delegate.

Should we add all ten locations on day one?

No. Each location is billed from the day you add it, so add your pilot sites first and the rest as they go live.

Do we need to load all our equipment first?

No. Start with the top five to ten items per site and add the rest over time.

Do managers need to use their personal phones?

No. Concoct runs in a web browser, so managers can report from a phone, a store tablet or the back-office computer. If you prefer staff not to use personal phones, a shared store device works.

What if a vendor refuses to use the system?

They do not need an account; they get a link by email for each job. If they do not respond within 24 hours, Concoct unassigns them and alerts your owners and operations managers, so someone can send the job to your backup.

How do we handle site managers who resist?

Find out why. It is usually workload or an existing workaround. Show them the time saved on the first work order, and use a peer to help.