A practical guide to designing procurement systems that scale

Most property organizations don't actually have a procurement strategy, in fact, they have procurement habits. 

A property manager buys HVAC services the way they always have and a facilities team sources cleaning supplies from whoever answered the phone. No brilliant rocket science applied here. But then portfolio heads wonder why spend varies wildly across properties that should be identical. Well this is where procurement strategy comes in as it's the difference between reactive buying and intentional sourcing. Read on as we have simplified it all for you.

What a Real Procurement Strategy Actually Does

So a procurement strategy answers a few specific questions like 'What does this organization buy? Who decides how we buy it? How do we measure whether we're buying it well?' These may sound like abstract questions at first but they are not. Believe it or not but they directly hit your operating costs, your vendor relationships and how quickly you can scale across new properties.

You may have worked with a portfolio of 40 office properties where procurement was fragmented and each property negotiated its own janitorial contracts. You may have wondered that despite same service, same volume across the entire portfolio, there are forty different agreements with forty different rates. You see, when they built a portfolio-level strategy, they consolidated to three vendors and cut costs by 18 percent. That's not about being ruthless. It's about knowing what you're buying before you buy it.

Moving on, a good strategy also keeps risk visible. Meaning, if you don't know how many suppliers you depend on for critical services then you can't manage supply chain risk. If approval thresholds aren't documented then you get either bottlenecks or overspending. If success metrics don't exist then nobody knows whether last year's contracts actually worked.

Start with What You Actually Have

Before designing anything you need to map your portfolio as it exists today and ask certain questions like what property types do you own? High-rise office, retail, industrial? Understand that each type has different procurement needs and an industrial building needs different suppliers than a mixed-use complex.

Where are these properties located? The basic thing to comprehend is that a vendor who serves your Chicago portfolio might not operate in Phoenix. A strategy that ignores geography is a strategy that fails in practice.

So who runs the operations? If each property has its own management company then your procurement will look different than if you operate everything in-house. It's a common and simple fact. If you're a REIT with regional managers then procurement needs centralization in some areas and flexibility in others. Simple!

Ask yourself, what systems do you currently use? If properties are already in different buildings management systems then a centralized procurement process has to account for that. You can't just simply declare that everyone should use one software system and expect it to work in week one because honestly, it just does not happen that way.

Understand existing agreements first. 

How many active supplier contracts do you have? 

What's the annual spend? Which contracts are about to expire? 

Because believe us, f you don't know this, you're designing a strategy in the dark.

One property portfolio that you may have reviewed would have had over 200 active contracts across 15 properties. Now imagine nobody having a central list! What a chaos that would be. You won't be able to see overlaps, expiring agreements or renewal opportunities. 

So the strategy starts with a simple spreadsheet that includes every contract, every vendor, every expiration date and finally from there, consolidation became possible.

Segment What You Buy

The most common mistake most organizations make is treating all purchases the same way. A $15,000 annual cleaning contract should not go through the same procurement process as a $800,000 HVAC replacement because if you do that then you'll unintentionally slow down the small stuff and miss details on the big stuff.

To keep thing smart and procurement technology seamless, segmentation should reflect majorly four things: 

how often you buy it, 

how much it costs, 

how important it is to operations, 

and how many vendors can actually provide it.

Once you have all these questions sorted, you have half the work done!

Recurring services like cleaning, landscaping, waste management need standardized agreements that you can apply across properties whereas one time capital projects like roof replacement, parking lot reseal need a different approach. Lastly, emergency services like 24 hour mechanical response have different risk profiles than planned maintenance.

Consider market availability too because in a market with 50 landscape companies, you can be selective about pricing but in a small market with three qualified vendors, your leverage is different and your strategy should acknowledge this.

Decide What Gets Decided Where

This is where most strategies get complicated, so here's the practical version.

Portfolio level procurement decisions usually include contracts that affect multiple properties, establish vendor relationships, or set pricing benchmarks. If you're contracting for landscaping services across 20 properties, that's a portfolio decision.

Regional procurement process makes sense when properties are scattered geographically and local market dynamics matter. A Portland property's vendor landscape is different from a Los Angeles property's, even though you own both.

Property-level decisions apply to unique situations. A specific property might need a specialized contractor because of its building system or tenant requirements. That should stay local.

The table below illustrates how a real estate portfolio could distribute procurement responsibilities across portfolio, regional and property teams.

Clear responsibilities can help teams act quickly while maintaining spending controls. A property manager could arrange an emergency repair within an approved limit. A long-term landscaping contract would require regional or portfolio approval, depending on its value and the company’s delegated authority rules.

Set the Governing Rules

Governance sounds bureaucratic but it prevents expensive mistakes. You need to document a few things clearly.

Who approves what? Define spending thresholds. Below $5,000 maybe the property manager decides. Between $5,000 and $50,000 requires regional approval. Above $50,000 requires portfolio approval. Write this down. Don't keep it in someone's head.

What information is required before approval? For a $100,000 vendor contract, do you need three bids? A reference check? Insurance verification? Specify it.

How do you handle exceptions? There will be emergencies. A pipe bursts at 2 a.m. You can't wait for procurement process when there's water damage. Document what 'emergency' means and who can approve outside normal process.

How often do you review agreements? Annual contract reviews catch problems. Set a schedule. Communicate it to vendors.

One regional portfolio I studied had no documented approval authority. Everyone assumed someone else was checking bids. A property manager spent $400,000 on a generator replacement without getting competitive quotes because nobody stopped her. The governance rules didn't exist.

Establish Measures That Matter

You can't improve what you don't measure. But measuring activity instead of outcomes kills momentum.

Three metrics matter: time, money, and risk.

On time: How long does a procurement cycle take? Measure from requirement identification to signed contract. If it's taking nine months to buy cleaning services for a building, something is broken. Most recurring services should take 4-6 weeks.

On money: Are you getting competitive pricing? Track spend by category. Are you negotiating renewing contracts or just paying last year's rates? One portfolio saved $180,000 annually by renegotiating three routine service contracts during renewal cycles, just because they measured and tracked expiration dates.

On risk: How visible is your supply chain? How many critical vendors do you depend on? How many contracts don't have documented service levels? If something matters to operations, you should know if a vendor can actually deliver it.

Measure adoption of your strategy too. If the procurement process is designed but properties aren't using it, the strategy failed. Track how many purchases are going through the centralized process versus avoiding it.

Build Your Implementation Timeline

Strategy on paper doesn't move spend. Implementation does.

Start with immediate fixes. If contracts are expiring next month and nobody noticed, fix that first. If your three facilities managers are all buying cleaning services separately, consolidate that before you design new processes.

Add standardization next. Take your three largest categories by spend and create standard contracts. Template them. Make them available. Get them signed at portfolio level.

After that, address your technology. Do you need a procurement platform? Can you manage it with spreadsheets and email? Be honest about your team's capacity. A beautiful software platform that nobody uses is expensive and useless.

Run a pilot. Pick one region or property type and implement the full strategy. Work out the problems. Adjust. Then roll out to the rest of the portfolio.

Expand gradually. Don't try to change everything simultaneously. Organizations that attempt major change too fast usually revert. Incremental wins build support.

One portfolio spent six months planning and three months trying to implement everything at once. It failed. They reset, started with one category, got it right, moved to the next. By month 14 from reset, they had the full strategy working.

Let's Understand Some Common Mistakes

Starting with technology first instead of understanding what you're buying is probably the most common error one can make. Software doesn't fix broken procurement technology and process. Clarity about what you buy, how you buy it and who decides that fixes broken procurement. Then the software can finally help.

Assuming all properties should work the same way is a big no-no. A downtown high rise and a suburban industrial park have different vendor markets, different operational needs and obviously different scales. Understand that standardization should mean clear processes but not identical execution.

Setting objectives without baselines is something one regrets when it is too late. You can't measure improvement if you don't know the starting point. Before declaring you'll reduce cycle time by 50 percent, know your current cycle time. Before pledging cost savings, know current spend.

Ignoring the people who actually execute can sound like a small detail but is actually quite a big deal. Operations teams know why current processes exist and they know what works and what doesn't. Ask them if procurement strategy ignores operational reality and if staff will work around it.

Lastly, it all comes down to failing to assign clear ownership. 'Procurement strategy is everyone's responsibility' means it's nobody's responsibility. To make things easier, pick a point person and give them authority to enforce the process. Another thing to add to this is measuring what's easy instead of what matters. Number of bids obtained is easy to measure but quality of vendor relationships is harder so measure what actually impacts operations and cost.

FAQ

Q: Should our procurement be centralized or decentralized?

A: Neither is absolutely right because remember that you need to centralize the decisions that create leverage like vendor selection for recurring services, contract standardization and decentralize those decisions that should be fast like routine maintenance, emergency response. Your portfolio characteristics determine the balance.

Q: How often should we review and update the strategy?

A: Ideally, you can do it annually at minimum but if your portfolio is growing, markets are changing or new vendors are emerging in your space then review more often. Remember that a three-year strategy without review becomes outdated and you do not want that.

Q: What metrics should we prioritize?

A: Start with cycle time like how long procurement takes and vendor spend concentration for example are you over dependent on one vendor and finally contract compliance as in do vendors actually deliver what they even promised. Add stakeholder satisfaction later once the process is working for a smooth experience.

Q: Who owns the procurement strategy?

A: It needs to be someone with authority to enforce process and access to spend data and regular contact with both operations as well as finance so usually opt for a procurement manager and sometimes a director of operations may also be a good choice.

Q: How do we handle vendors who want special arrangements?

A: Your strategy exists partly to prevent this as a vendor requests a higher rate for one property or longer payment terms for another and reference your documented process plus apply it consistently.

Key Takeaways

A procurement strategy is the difference between reactive buying and intentional sourcing and it all begins with understanding what you actually have like property types, locations, existing agreements and operational structure. Segment your purchasing by frequency, cost, operational importance and market availability and then distribute decision making across portfolio, regional and property levels based on where each decision creates the most value. 

Document approval authority clearly to avoid any last minute error and confusion and measure cycle time, cost competitiveness and supply chain risk frequently. Implement gradually, starting with immediate fixes, then standardization, then technology.

Sources

• CIPS: How to Develop a Procurement Strategy
• CIPS: Category Management Cycle
• CIPS: Procurement and Supply Cycle
• CIPS: Procurement KPIs and Performance Measures

Also Read:

Real Estate Procurement Process: How to Score Bids and Select Suppliers

How AI Is Transforming Real Estate Procurement