Use a Vendor Change Freeze to Protect Critical Dealer Weeks

Peak Weeks Leave Less Room for Guesswork

A dealership may have a major sales event, a holiday schedule, a service capacity push, a model launch, or an ownership transition that concentrates customer demand. During that window, several vendors may want to update pages, forms, feeds, tracking, creative, or integrations. Even a well-intended release can alter a phone route or break a destination while the BDC is already busy. A change freeze defines which work must wait, which urgent fixes can proceed, who approves exceptions, and how the team verifies that critical customer paths remain stable.

Choose the Window From Business Risk

Start with the dates and customer promises that matter, not a generic rule that freezes everything every weekend. Include the launch period, the days before it when final changes are being tested, and the period after it when delayed leads or appointments are reconciled. Sales, fixed ops, marketing, finance, BDC, and vendors should identify dependencies such as inventory refresh, offer updates, staffing, and scheduled messages. Write the start and end time with timezone so an outside partner cannot interpret “Friday” differently.

• List systems covered: website, forms, CRM, scheduler, feeds, call routes, ads, email, and reporting.
• Name a business owner and technical escalation owner for the freeze.
• Define allowed changes, prohibited changes, and the approval path for exceptions.
• Require a rollback or workaround plan for any approved release.
• Schedule a post-freeze reconciliation of leads, appointments, inventory, and campaign status.

Freeze Risky Work, Not Customer Safety

Routine redesigns, untested integrations, nonessential tracking changes, and large template migrations can wait. A broken form, incorrect hours, unsafe service instruction, expired offer, or routing failure cannot wait merely because a freeze is active. Define emergency criteria in customer terms and require a named approver. The vendor should make the smallest safe change, test the affected path, communicate the result, and record what remains. A freeze without an exception route encourages people to bypass it; a freeze with an uncontrolled exception route is only a label.

Use a Release Packet for Exceptions

An exception request should state the problem, customer impact, requested change, affected systems, exact owner, test method, rollback, and communication plan. The vendor should provide the final version rather than changing production from an informal chat. A dealer tester follows the path on mobile and desktop, confirms source capture and routing, and tells frontline teams what they may see. Keep the packet with the event record so a later incident review can distinguish a planned emergency fix from an unrelated change.

Exit Deliberately

When the freeze ends, do not open every queued request at once. Prioritize by customer value and dependency, test one change at a time, and watch the reports for delayed effects. Compare current inventory, offer, hours, lead routing, appointment availability, and tracking with the approved event state. Ask each vendor to confirm what was held, what changed during the window, and what remains scheduled. The review should improve the next freeze rather than become a post-event blame exercise.

A change freeze gives busy weeks a stable operating boundary. It helps vendors plan, gives store teams confidence in the customer path, and preserves a clear route for the fixes that genuinely cannot wait.