Roll out Builder to your team

Last updated: October 23, 2026

Start small: pick one or two customers who send a lot of tenders in a predictable format and don't tender by EDI. Have a few reps build those loads in Drumkit for a week or two, send us every miss, then add customers. This page is for the manager or team lead running that rollout.

Why start small

Builder learns each customer's habits: which number is the PO, how they write appointment times, where the weight lives on their PDF. The misses you send us are how we tune Builder for each customer, so the first customers you pick improve fastest. A narrow start also means your reps learn the form on emails that look alike, instead of on a different layout every time.

1. Pick your first customers

A good first customer ticks all of these:

  • High volume. They tender to you every day or close to it, so reps get plenty of practice and we get plenty of examples.
  • Predictable. Their tenders look the same each time: same template, same PDF, same lanes.
  • Not EDI. If a customer's loads already arrive in your TMS by EDI, building them from email would create a second copy. Leave those customers out.
  • Set up in your TMS. The customer and their regular pickup and delivery locations already exist, with hours and instructions filled in.

Fill in the customer's locations in your TMS before you start. Builder reads hours and instructions from those records, so a blank field there is a blank field on every load.

2. Pick your first reps

Choose two or three reps who handle those customers and are happy to try something new. Ask your Drumkit admin to make sure Load Building is turned on for them. It can be turned on for some users and not others, so check each rep. Each rep then follows How Builder works and the guide for your TMS.

3. Week one and two: build, check, send misses

Ask your reps to build every load from those customers in Drumkit, and to check each section before they click Build Load. Nothing reaches your TMS until they do.

When Kit gets a field wrong, the rep fixes it in the form, builds the load, and forwards the email to support@drumkit.ai with one line on what should have happened. Report a Builder miss shows the format.

One clear example per pattern is enough. A note like "For this customer the PO is the Release # on page 2" helps with every load from them, not just the one.

What to expect

  • Most fields fill in; some don't. Kit leaves a field blank when it isn't sure, or when the value is blank on your TMS record too. Reps type those in.
  • Appointment times stay blank unless the email clearly gives one. That's on purpose: a time in that field reads as booked to the next person who opens the load. See Times look shifted in my TMS.
  • The same miss twice means send it. Repeated misses for one customer are what we look at first.
  • The first few loads take longer. Reps are learning where each field lives in the form. Give it a few days before judging the time it saves.

4. Add customers

Once the first customers' loads come through with few or no corrections, add the next one or two, then the next. Keep the same rules: high volume, predictable, not EDI. Then widen to more reps.

Keep EDI customers off the list, even later. If an EDI load is also built from its email, you'll have two loads for one shipment.

FAQs

Can we turn Builder on for everyone on day one?

You can, but teams that start with a couple of customers get cleaner results sooner. Reps learn the form on familiar emails, and we can tune those customers first.

Who should send the misses, the rep or the manager?

Whoever spotted it. Reps see the misses first, so most teams ask reps to forward them as they go. A manager can batch them at the end of the day if that's easier.

Some reps don't see the Load Building tab.

Load Building is turned on per team, and sometimes only for some users. Ask your Drumkit admin to check those reps.

Does Builder create loads without a rep checking them?

No. Kit fills in the form; the rep checks it and clicks Build Load.

What if a customer sends several loads in one email?

Builder builds one load at a time. If your team has load cloning turned on, see Clone loads from an email.

Related