The Spreadsheet Quietly Running Your 2027 Multi-Site Program

There is someone on your 2027 program team who was never interviewed.

They know which sites need attention, which contractor quoted the work and which budget numbers changed after the last planning meeting. They work weekends. Everyone relies on them, although nobody can quite explain their job description.

Their name is something like 2027_Program_Master_v12_FINAL.xlsx.

The spreadsheet did not start out running the program. It started as a useful list. Then someone added costs, contractor assignments, inspection dates and a few formulas. Eventually, checking the spreadsheet became the first step in answering almost any operational question.

Nobody formally hired it to run the program. The responsibilities simply accumulated.

For teams preparing next year’s environmental, remediation, reclamation or field maintenance work, that quiet promotion deserves attention.

It Holds the Institutional Knowledge

The workbook knows that one site needs landowner coordination before access. It knows a contractor’s estimate excludes disposal. It knows why a project disappeared from the approved budget but remains on the monitoring list.

Or rather, that knowledge exists somewhere inside it.

Some details are in comments. Others are represented by colours, abbreviations or tabs named after former employees. The person who built the file understands the distinctions. A new project manager sees a yellow cell and has to ask what it means.

The risk is not storing information in rows and columns. It is storing operational meaning in conventions that only a few people understand.

For a multi-site program, a status needs more than a colour. It needs a definition, a responsible person and supporting context.

It Works Every Weekend

Imagine the Friday update.

Field notes have arrived. A contractor has revised a quote. Finance has supplied another cost export. Someone stays late to reconcile everything before Monday’s program meeting.

The spreadsheet appears tireless because the people maintaining it are doing the extra work.

By Sunday evening, the totals agree. But the file does not show how many emails, phone calls and manual checks were required to make that happen.

That effort belongs in the 2027 planning conversation. A reporting process that depends on someone repeatedly rebuilding the current picture has a staffing requirement, even if it never appears in the program budget.

The useful question is not whether the workbook still works. It is how much work everyone else must do to keep it working.

Everyone Uses It. Nobody Owns It.

Operations updates the schedule. Finance supplies actual costs. Consultants add findings. Management changes priorities.

Who owns the definitions?

Who decides when a site is complete? Who confirms that a revised estimate has replaced the old one? Who checks whether a contractor assignment is tentative or approved?

Shared access does not answer those questions.

A workbook can have many contributors while having no defined owner for its structure, quality or continuity. The person who fixes it most often gradually becomes responsible for it without being given the time or authority that responsibility requires.

Before the 2027 program begins, those responsibilities need names, not assumptions.

It Cannot Explain Its Formulas

A total can be correct without being easy to defend.

Perhaps the forecast includes approved work but excludes optional scope. Perhaps one formula treats a blank cell as zero. Perhaps a contingency allowance was entered directly into a subtotal during last year’s budget review.

The formula shows the calculation. It does not necessarily explain the business decision behind it.

That distinction matters when management asks why a region needs more funding or why two similar sites have different allowances.

A defensible program record connects the number to the location, scope, estimate source and approval behind it. Reviewers should not need the original workbook author beside them to understand what the forecast includes.

Its Absence Becomes a Crisis

Now imagine Monday morning without the file.

Not necessarily because it was deleted. The person who maintains it might be unavailable. A linked source might have moved. Two copies might contain different approved changes.

Could another team member explain which sites are ready, which costs are committed and what needs a decision?

Backups and version history help protect the file. They do not, by themselves, preserve the reasoning behind every entry.

That is the continuity test: can the program keep moving when the workbook or its unofficial caretaker is unavailable?

If the answer is no, the spreadsheet has become more than a tool. It has become a dependency.

Keep the Tool. Reassign the Job.

Spreadsheets remain useful for analysis, modelling and exploring alternatives. There is no reason to remove them from work they do well.

The change is to stop asking one workbook to be the site register, contractor directory, evidence library, approval process and institutional memory at the same time.

For 2027, the underlying program record should connect each location to its planned work, responsible people, supporting evidence, scope assumptions and costs. A spreadsheet can then analyse that information without being the only place the program makes sense.

Keep the Spreadsheet. Give the Program a Home.

Your spreadsheet can still handle the analysis without carrying the entire program.

Explore how Matidor could bring your 2027 sites, planned work, responsibilities and budget context into a shared, map-based workspace.

Start a free 14-day trial. Prefer to discuss your program first? Book a demo.