Run a Rental Spend Review Across University Campuses

A university system with a dozen campuses rarely buys equipment the same way twice. One campus routes every rental through a central facilities office. Another lets each department call a supplier directly when a project needs a lift or a generator. When a procurement director asks you to consolidate all of that spend under one contract, the request sounds simple. Getting there safely takes real discovery work, and the account manager who skips that work usually ends up making a promise the data cannot support.

Why This Conversation Goes Wrong

Procurement directors managing rental spend across several campuses often open with a number. They want to know how much money one consolidated contract will save before anyone has looked at actual usage. That instinct makes sense. They have a budget cycle to justify and administrators asking for results. But an account manager who answers with a savings figure before examining purchase authority, usage patterns, and department level buying is guessing, and most procurement directors have heard that guess before.

The pressure gets worse because rental spend inside a university system is genuinely scattered. Athletics rents on a different schedule than facilities. A research lab renting specialized equipment for a grant funded project answers to different rules than a maintenance crew renting a scissor lift for routine building work. Some campuses attach safety or access rules to specific equipment types, similar to the constraints covered in Clarify Warehouse Access Before Discussing a Lift, and those rules do not disappear just because someone wants one master agreement. Promise savings before you understand those variables and you set a number the institution will hold you to later. When the real analysis contradicts that number, you lose the standing you need to get the actual program approved.

How to Prepare

Before you sit down with a procurement director, gather the pieces that let you speak from data rather than hope.

1. Identify who holds purchase authority at each campus and each department, because a single contract conversation only works if you know whose approval actually matters.
2. Pull whatever usage and spend records already exist, even if they sit in three different spreadsheets across three offices, and note the gaps so you can ask for the missing pieces directly.
3. Find out which departments buy outside the central process today, and why. A department that rents independently usually has a reason, like a faster turnaround or a longstanding supplier relationship, and a program review has to account for that reason instead of overriding it.
4. Map the campus rules that affect access or equipment needs. A campus with strict site access or a specialized safety requirement needs separate handling in any plan, the same way access constraints shape how you would approach a lift rental request in a restricted facility.
5. Decide who else needs to be in the room. A useful data review usually needs someone from finance and someone from facilities, not only the procurement director who first raised the idea.

Walking in with this groundwork changes the entire tone of the meeting. You stop reacting to a request for a number and start running a conversation the institution can actually trust.

What to Say

Lena, a facilities procurement director, said, "Can you guarantee real savings if we move every campus onto one contract."

Marcus said, "I cannot answer that yet, and I would rather not guess at a number I cannot back up. First I want to understand which departments rent outside your central process today and where campus rules affect what they can request. Which campuses should join a data review, and who can walk me through the access requirements on your research campus."

Lena said, "A few departments buy directly. Athletics has its own supplier relationships, and the research campus has security rules about who can be on site for equipment drop off."

Marcus said, "That is exactly the kind of detail I need. I will build a usage and supplier view together with your finance and facilities contacts, then we can decide what a full program review should cover and what a realistic timeline looks like once the data is actually in front of us."

Marcus never creates a financial claim before the institution has examined its own data. He names the reality that some campuses carry separate rules and some departments hold separate authority, and that protects the credibility of whatever recommendation follows. The same discipline applies when you plan a large account that spans many locations with different conditions, the way you would plan a national account for wildfire season, where local demand and local rules shape what a single national number can honestly promise.

Mistakes to Avoid

1. Giving a savings percentage or dollar figure before anyone has looked at real usage data.
2. Treating every campus as if it buys the same way, when local rules and department habits differ from site to site.
3. Skipping the question of who can validate the numbers, which leaves you defending a claim nobody else in the room will confirm.
4. Scheduling a program meeting with the wrong attendees, so the people who can actually approve a change are not there to hear the proposal.
5. Moving straight to a full proposal without naming the specific campuses or departments involved, which makes the plan feel generic and easy to set aside.

Each of these mistakes shares the same root cause. The account manager answers the question that was asked instead of the question that matters, and that shortcut costs more time later than it saves now.

How to Practice and Score It

Pick one real account in your territory with decentralized buying across multiple sites. Write down where the spend, utilization, and purchasing authority data actually lives, even if that means three separate spreadsheets held by three separate offices. Then run the roleplay. Have your counterpart open by demanding a savings number, the way Lena did, and practice returning to the data question instead of answering it on the spot.

Score yourself, or have a manager score you, on three points. Did you ask about purchase authority and decentralized buying before you discussed any numbers. Did you name at least one campus specific rule or constraint instead of treating the account as uniform. Did you end the conversation by proposing a next meeting with the people who actually make the decision, not just the person who asked the question.

DealSpeak scores this kind of conversation the same way, checking whether you gathered the right facts before making a claim and whether your proposed next step matches the decision actually on the table. If you want more scenarios built around situations like this one, the Equipment Rental practice conversations cover other moments where a customer pushes you toward a commitment you are not ready to make.

Close

A university spend review rewards patience more than confidence. Show up with real questions about authority and usage, name the constraints that make each campus different, and let the data drive whatever number comes next. That approach takes longer than promising savings on the spot, but it is the only version of this conversation that survives contact with procurement's own numbers.

You can rehearse this exact conversation in the Equipment Rental practice conversations library before it happens for real. When you have this one down, read Clarify Warehouse Access Before Discussing a Lift next.