General Manager's Checklist for Approving a Capital Expenditure Request

A solid capital expenditure (capex) approval process starts with five core questions: Does this align with our strategic goals? What's the ROI timeline? Do we have cash flow to support it? Will it improve CSI, gross profit, or operational efficiency? And critically—have we stress-tested this against a worst-case scenario? Before you sign off on anything above your approval threshold, you need a repeatable checklist that forces the right conversation between you, your finance team, and the department head requesting the spend.

Why a capital expenditure checklist matters at your dealership

You know that moment when a technician walks into your office asking for a $45,000 alignment machine, or your service manager comes in with a proposal for a new estimating system, or your fixed ops director wants to rebid the entire lot resurfacing project? If you don't have a structured decision framework in place, one of two things happens: either you rubber-stamp it because you're busy and trust the person asking, or you spend three hours asking questions that could've been answered on a one-page summary.

The best-run dealerships we see across the Northeast—the ones that aren't cash-strapped by year three because they bought five things they didn't need,they all use a capital expenditure checklist. It's not about being cheap or slow. It's about being intentional. A checklist removes emotion from the decision, forces the person requesting the spend to articulate their business case clearly, and gives you a paper trail when the board or your lender asks why you spent $120,000 on a new DMS upgrade.

Here's the brutal truth: most dealerships approve capex requests on vibes and politics. The service manager who's been there 12 years gets what he asks for. The BDC director who's new gets told "maybe next year." That's not strategy; that's chaos.

The five foundational questions every capex request must answer

Before you even look at the price tag, the request needs to answer these questions clearly. If it doesn't, send it back to the requester and ask them to fill in the blanks.

• Strategic alignment: Does this investment move us toward one of our stated business goals? (Examples: increase used vehicle gross, reduce service write-up time, improve delivery CSI, expand our market share in commercial fleet.) If the request doesn't ladder up to something you've actually committed to as a dealership, it's a nice-to-have, not a must-have.
• Problem definition: What specific operational problem or constraint does this solve? Don't accept vague answers like "it'll make things easier." You need to hear: "We're turning away service customers on Saturdays because we can only run eight alignment jobs per day, and we're losing an estimated $8,400 a month in gross profit because of it." That's a problem statement.
• ROI and payback period: What's the quantified financial return, and over what timeframe? For a $45,000 alignment machine that generates an extra $8,400 in monthly gross, the payback is roughly 5.4 months. That's compelling. For a $35,000 software system that "saves 2 hours per week in admin time," you need to calculate that into actual dollars and months.
• Cash flow impact: Can we absorb this without disrupting payroll, parts inventory, or franchise fund payments? This is non-negotiable. A great investment that bankrupts you is not a great investment.
• Risk and contingency: What if the ROI takes twice as long to materialize? What if the vendor goes out of business? What's our exit strategy if it doesn't work?

The complete general manager approval checklist

Here's a practical checklist you can adapt to your dealership's size and approval thresholds. Adjust the dollar triggers and require signatures from your controller and operations manager as appropriate.

Pre-submission requirements (requester completes before it lands on your desk)

• ☐ Clear project title and one-sentence description of what's being purchased
• ☐ Requester name, department, and date of request
• ☐ Total project cost (including installation, training, setup, freight, taxes)
• ☐ Vendor name and contact information; confirm vendor is solvent and has been in business for 3+ years
• ☐ Explicit business problem statement (not a wish list, an actual operational constraint)
• ☐ Quantified monthly or annual impact: gross profit increase, cost savings, time savings converted to dollars, or CSI improvement with baseline and projected metrics
• ☐ Payback period calculation in months
• ☐ Comparison to at least one alternative solution or vendor (price, features, support)
• ☐ Implementation timeline: start date, completion date, downtime requirements, training plan
• ☐ Approval from the department head's direct manager (service director signs off before it goes to fixed ops director; fixed ops director signs off before it goes to you)

GM evaluation (you complete before final sign-off)

• ☐ Strategic fit: Does this align with our 3-year plan? Rate: Critical / Important / Nice-to-have
• ☐ Urgency: Must we do this in the next 90 days, or can it wait until Q3? Is there a seasonal window we'll miss?
• ☐ Cash position: What's our operating cash as of last month? Can we write this check without impacting working capital? (Review with your controller.)
• ☐ Staffing readiness: Do we have trained staff to operate/maintain this? Will we need to hire or contract for training?
• ☐ Vendor due diligence: Have you spoken to at least one reference customer? (Don't skip this for purchases over $15,000.) Ask the reference: Did it deliver the promised ROI on timeline? What surprised you? Would you buy again?
• ☐ Worst-case scenario test: If this vendor goes away or the ROI is 50% lower than projected, can we still justify the spend? Is there a resale/liquidation value if we need to cut losses?
• ☐ Financing option review: Should we lease, loan, or buy outright? (Work with your accountant on tax implications.)
• ☐ Competitive impact: Will our competitors have a material advantage if we don't do this? Or are we overspending to keep up?
• ☐ Approval threshold check: Is this within your authority to approve, or does it require board/principal approval?

Post-approval (before vendor gets a deposit)

• ☐ Signed approval form filed in capex folder with date and your signature
• ☐ CFO/controller has written confirmation of funding source and P&L impact
• ☐ Requester and department head are clear on approval conditions (if any) and next steps
• ☐ Project manager assigned; kickoff meeting scheduled with requester, vendor, and operations
• ☐ Implementation success metrics defined: what does "this worked" look like? (E.g., "Alignment jobs per day increase to 11 by month 2.")
• ☐ 30-day, 90-day, and 6-month check-in dates added to your calendar

Common capex mistakes general managers make (and how to avoid them)

We see patterns. The best GMs learn from other people's mistakes instead of their own.

Mistake #1: Approving based on emotion or politics, not metrics

Your long-time service manager is a good guy who's been loyal for 12 years. He asks for a $50,000 vehicle lift because "ours is getting tired." Without a clear problem statement and ROI, you're making an emotional decision. What's the actual constraint? Is it downtime? Are you losing jobs because of it? Or is he just tired of looking at an older lift? There's a difference. A hard-nosed checklist forces the conversation to be about the business, not the relationship.

Mistake #2: Ignoring cash flow reality

You approve a $200,000 lot resurfacing project in July. You didn't check whether Q3 traditionally has slower used-vehicle sales and tighter cash flow. By October, you're scrambling to make payroll because your receivables are thin and you're out $200,000 in liquid cash. A five-minute conversation with your controller before you sign prevents this.

Mistake #3: Not vetting the vendor

A slick software demo and a good sales pitch are not due diligence. Call three reference customers. Ask them specifically: "Did you hit the ROI targets?" and "What would you do differently?" A vendor that can't produce three willing references is a red flag.

Mistake #4: Underestimating implementation cost and disruption

A new DMS isn't just the software license. It's installation, data migration, staff training, temporary productivity loss while people learn the new system, customization to fit your workflows. The $35,000 software becomes $60,000 when you add it all up. Build in a 20-30% contingency for anything over $25,000.

Mistake #5: No success metrics or follow-up

You approve the alignment machine. Twelve months later, you haven't checked whether it's actually generating the promised $8,400 in extra gross per month. Maybe it is, and you should be celebrating and thinking about a second one. Or maybe it isn't, and you need to understand why so you can make better decisions next time. Either way, you need to measure.

How to structure approval thresholds for your dealership

Not every capex needs the same level of scrutiny. A $2,000 software subscription is different from a $250,000 lot renovation. Here's a common approval structure:

• Under $5,000: Department manager approval only. No formal checklist required, but document the spend.
• $5,000 to $25,000: Requester completes the pre-submission checklist. Department manager and you (GM) approve. CFO confirms cash availability.
• $25,000 to $75,000: Full checklist. GM and CFO approval. You conduct vendor due diligence (at least one reference call).
• $75,000 to $150,000: Full checklist plus board review if applicable. GM, CFO, and owner/principal approval. Vendor due diligence required (three references minimum).
• Over $150,000: Board presentation. Full due diligence. Consider getting competitive quotes from multiple vendors.

Adjust these thresholds based on your dealership's size and complexity. A 30-unit store has different risk tolerance than a 200-unit megadealer.

Red flags that should trigger deeper investigation

Some requests warrant extra scrutiny, even if they fall within normal approval authority.

• Vendor has been in business for fewer than three years
• Requested payback period is under six months (sounds too good to be true; it usually is)
• Vendor can't produce references, or references are vague or evasive
• The requester can't articulate the specific problem in measurable terms
• Implementation timeline is aggressive (less than 30 days) and the vendor is pushing urgency
• Cost of ownership is unclear (is support included? What about training? Upgrades?)
• Your cash position is already tight (month-to-month operating margin under 5%)
• This is the third similar request in 18 months (pattern of underperformance)

If three or more of these are true, have a conversation before you approve. You're not being paranoid; you're being prudent.

Real-world scenario: Walking through the checklist

Let's work through an example. Your service director proposes a $28,000 estimating and menu-building software system. Here's how the checklist works:

The request arrives: "We need new estimating software. Our current system is slow and our service advisors are spending too much time on estimates instead of selling menus and upsells."

You ask the service director to complete the checklist: What's the actual problem? He clarifies: "Advisors spend 12 minutes per estimate on average. With 35 estimates per day, that's 7 hours of labor daily on quote-writing. If we cut that to 8 minutes per estimate, we save 2.3 hours per day. At $22/hour loaded cost, that's $50.60 per day or roughly $12,400 per year in labor savings."

ROI calculation: $28,000 cost ÷ $12,400 annual savings = 2.26-year payback. Not as tight as he first pitched it, but reasonable for an operational efficiency play.

You dig deeper: Have you compared this to the three other estimating platforms out there? He has, and this one won the comparison on speed and menu customization. You ask for one reference customer call. The reference says they hit the time-savings target and their advisors like the interface. You check cash flow with your CFO: we can absorb a $28,000 spend without impacting payroll or working capital.

You approve it with conditions: Implementation happens in Q1 when service traffic is seasonal. Service director owns the training plan. You schedule a 90-day check-in to confirm advisors are actually hitting the 8-minute estimate time.

This whole conversation takes maybe 45 minutes across multiple days. Without the checklist, you either say "yes" in 30 seconds or spend two hours grilling the guy on details. The checklist gives you the middle path: structured, defensible, thorough.

Frequently asked questions

Should I use a formal capex request form or just email communication?

Use a form. Email gets lost, forwarded without proper context, and doesn't create accountability. A form (digital or paper) with signature lines ensures the request has been reviewed at each level and you have a documented audit trail. This becomes critical when your accountant or lender asks why you spent $90,000 on a lift system.

What if a capex request is truly urgent and I don't have time for full due diligence?

You always have time for a problem-statement conversation and a cash-flow check. Those take 15 minutes. If you don't have 15 minutes, you don't have time to make a good capital decision. Urgent requests are exactly when you need the checklist most,they're when emotion and time pressure lead to bad choices. At minimum: confirm the problem is real, confirm you have the cash, get one reference, and get it in writing.

How do I handle a capex request from someone who gets defensive about the checklist?

Frame it as dealership policy, not personal doubt. "This is the process we use for every capex request over $10,000. It's not because I don't trust you; it's because I need to document my decisions and make sure we're being disciplined." People respect structure. If someone gets angry that you won't approve a $40,000 spend without a clear ROI calculation, that's actually useful information about their thinking.

Can I approve capex requests that score low on ROI if they're strategic or necessary?

Yes, but document why. Example: a new compliance software system might have a three-year payback, but you're buying it because franchise regulations require it. Write that reasoning on the approval form. The checklist isn't meant to block necessary spending; it's meant to make sure you know what you're approving and why. This kind of workflow,where you're making strategic trade-offs with full information,is exactly what a robust checklist enables.

How often should I revisit my capex approval thresholds?

At least annually. If your dealership has grown 30% in the last two years, your $75,000 threshold might now need to be $100,000. If you've had two bad years, you might lower thresholds to be more conservative. Revisit thresholds when ownership or strategy changes, or when your cash position shifts materially.

What's the difference between a capex request and an operating expense?

Generally: if the asset has a useful life of more than one year and costs above your materiality threshold (usually $2,500–$5,000), it's capex and goes on the balance sheet. Software licenses under one year, consumables, and routine maintenance are operating expenses. Your accountant will clarify the line, but this is why you need your CFO involved in the approval process,they need to code it correctly.

The checklist doesn't slow you down,it speeds up good decisions and kills bad ones before they cost you money. Use it every time, no exceptions, and you'll look back in three years and realize how much stronger your balance sheet is.