At the shop
A bumper job is booked into the only paint booth at 1 p.m. A second car is already prepped, but its trim clip is on backorder until tomorrow. Both customers expect Friday pickup.
Set up the demo
Use the sample records below when entering this fictional repair.
Records to enter in the demo
| Reference | Owner or event | Record entry |
|---|---|---|
| RO 0612-A | Production lead · 12:15 | Ready bumper, 1 p.m. booth slot, Friday pickup target. |
| RO 0612-B | Parts lead · 12:20 | Trim clip missing. Initial ETA Thursday morning. |
| ETA-612 | Vendor · 12:40 | Clip ETA now Friday morning. Advisor to call after production review. |
Which job goes into the booth, and what should the advisor promise?
Advance 0612-A at 1 p.m. Keep the clip hold on 0612-B, assign the parts lead to confirm arrival, and give the customer a callback time. A vendor ETA alone cannot establish pickup time.
Run the handoff
- Have the production lead move the ready job into paint. Ask an advisor looking at the other job to identify the missing part and its owner.
- Move the clip ETA back a day. Require the advisor to explain the revised promise before sending the customer a message.
Where AutoHound fits
AutoHound’s production board brings parts status, stage, assignment and promise risk together. Use this case to see whether the board and the advisor’s view tell the same story. Read the AutoHound field guide.
What to record
A visible production board does not itself prove finite-capacity scheduling. Ask to see any automatic booth-conflict rule you intend to rely on. Write down the role, screen and document that prove the result.
AutoHound feature reference