Spreadsheets Are Not the Problem
Some of the most sophisticated corporate real estate organizations in the world rely on Excel every day. It remains one of the most flexible tools available for analysis, modeling, budgeting, and reporting. Spreadsheets are not going away, and they should not.
The problem begins when spreadsheets become the operational system. Not because teams lack technology. Most CRE organizations have invested millions in lease administration platforms, IWMS solutions, project management tools, and financial applications.
Teams use spreadsheets because they do not trust the data in those systems. And that distinction changes everything about how you solve the problem.
The Trust Problem
Ask a CRE leader why their team maintains critical reporting in spreadsheets instead of relying on their IWMS or lease management platform. The answer is rarely "we don't have a system." The answer is almost always some version of "we don't trust what's in the system."
The reasons vary. Lease records that were loaded during implementation and never properly validated. Space data that has not been updated since the last occupancy audit. Facilities data that depends on service providers entering information they were never trained to enter. Financial data that was configured for a chart of accounts that changed two years ago.
Over time, the people closest to the work learned which data they could rely on and which they could not. They built spreadsheets to compensate. Not because they enjoy the manual work, but because the spreadsheet is the one place where they control the inputs, verify the calculations, and know exactly where every number came from.
The spreadsheet is not a workaround for a missing system. It is a workaround for a broken trust relationship between the team and the technology they were given.
How Shadow Systems Grow From Trust Gaps
Once the trust breaks, the shadow systems grow fast. A lease administrator builds a tracking spreadsheet because the lease management system does not reflect the amendments processed last quarter. A project manager maintains a separate budget tracker because the numbers in the project tool do not match what finance approved. A regional director keeps an occupancy workbook because the IWMS data has not been reliable since the last reorganization.
Each spreadsheet is rational. Each one solves a real problem. But collectively, the organization ends up with multiple versions of the truth, reporting processes that depend on specific individuals, significant labor spent maintaining parallel systems, and no single source that leadership can point to with confidence.
When someone leaves the organization and takes with them the only working knowledge of how a critical reporting spreadsheet was built, the organization discovers how fragile its operational foundation actually is.
The Real Cost Is Decision Latency
The visible cost is labor. Consider a CRE team of five where each person spends 20% of their time on data gathering, reconciliation, and validation. At fully loaded cost, that is the equivalent of one full-time employee doing nothing but assembling information. For a mid-size organization, that represents $150,000 to $250,000 annually in effort spent preparing answers rather than acting on them. For larger portfolios with multiple regions and more complex reporting, that number is significantly higher.
Then there is the cost of key-person dependency. When one person maintains the critical spreadsheets that leadership relies on, and that person leaves, the organization loses months of institutional knowledge. Rebuilding those workbooks, understanding the formulas, and re-establishing trust in the numbers takes time and money that never appears on a budget line.
But the largest cost is decision latency. When leadership asks a straightforward question like "What projects are active at locations with leases expiring in the next 18 months?" the answer should take minutes. In most organizations, it takes days. Someone must pull data from multiple sources, reconcile it against their spreadsheets, verify that the system data matches reality, and assemble a response they are willing to put their name on.
While that answer is being assembled, decisions continue without it. A lease renewal gets negotiated without visibility into the capital projects planned for that building. A project gets approved without knowing the lease at that location may not be renewed. Budget is allocated to a site that facilities data would have flagged as underperforming if anyone had looked across systems.
One missed lease option, one poorly timed capital investment, or one renewal at an above-market rate can cost more than the entire annual spend on spreadsheet labor. The cost of the spreadsheet is not the time it takes to build it. It is the decisions that were made without the information it was still being built to provide.
More Systems Will Not Fix a Trust Problem
Many organizations respond to this problem by implementing additional technology. Another dashboard. Another reporting layer. Another analytics tool. The assumption is that better technology will produce better visibility.
But if the underlying data is not trusted, adding a new system on top of it simply gives people one more source they do not believe. The spreadsheet does not go away. It grows. Now the team is reconciling data from four systems instead of three.
This is why platform consolidation often underdelivers on its promise of unified reporting. Moving data from one system to another does not make it trustworthy. It transfers the trust problem to a new platform.
What Actually Fixes This
Solving the spreadsheet dependency requires addressing the root cause, not the symptom. The root cause is not that systems are disconnected. The root cause is that the data in those systems is not reliable enough for people to trust it for decision-making.
That means the fix has layers.
First, understand what you actually have. A CRE technology assessment that maps not just the systems but the data quality within them. Which records are current? Which fields are reliably populated? Where are the gaps? Where have people built workarounds? You cannot fix what you have not honestly evaluated.
Second, remediate the data that matters most. Not all data needs to be perfect. Focus on the data domains that drive the most important decisions: active leases and their obligations, capital project status and budget, occupancy and cost data at the portfolio level. Fix the 20% of data that drives 80% of the decisions.
Third, build a layer that reconciles rather than hides the problem. The right CRE analytics software does not just connect systems and present data as if it were clean. It compares data across sources, flags discrepancies, and shows the user where system data and reality diverge. It does what the spreadsheet does, but faster, at scale, and without depending on one person who knows where all the hidden formulas are.
When a team can ask "what projects are active at locations with leases expiring in the next 18 months" and get a traceable, auditable answer in minutes, including flags where the data is uncertain, the spreadsheet stops being necessary. Not because someone took it away. Because something better replaced the need for it.
The Path From Spreadsheet to Confidence
The organizations that successfully move past spreadsheet dependency do not do it by banning spreadsheets or mandating system usage. They do it by making the systems trustworthy enough that people choose to rely on them.
That means investing in data quality. It means deploying analytics that are transparent about where the data came from and where it might be unreliable. It means giving teams tools that are as flexible and honest as the spreadsheets they built for themselves.
The goal is not to eliminate spreadsheets. The goal is to eliminate the conditions that made them necessary.
Closing Thought
Most CRE organizations do not have a spreadsheet problem. They have a trust problem. The spreadsheet is just how the trust problem manifests.
The organizations that address the root cause, by honestly assessing their data, remediating what matters, and deploying analytics that reconcile rather than hide, will make faster decisions, reduce operational risk, and give leadership the confidence that comes from knowing the numbers are real.
The ones that keep layering new technology on top of data nobody trusts will keep building spreadsheets.
If your team spends more time validating data than using it, see how Osprey reconciles data across systems or book a 20-minute call to talk through your situation.