SaferSheetsSaferSheetsBeta

EXCEL HARDCODE DETECTOR

An Excel hardcode detector that surfaces every buried number.

Hardcoded values inside formulas — a 5000 jammed into a SUM, a 0.23 multiplied through a revenue line — are one of the most common sources of "the model is wrong but nobody knows why." SaferSheets' Excel hardcode detector finds every one of them and tells you which cell to interrogate.

Find hardcodes freeSee pricing →

Free tier — 30 audits/month — no card required.

Hardcoded values are invisible until they're not

Picture a quarterly forecast model. The Revenue line uses a formula referencing pipeline data. Halfway through the quarter, leadership decides to "adjust" the forecast by $50K and someone types =Pipeline!B5 + 50000 over the original formula. Three weeks later that adjustment is forgotten — but the formula is still adding 50K to whatever Pipeline reports.

Multiply this pattern across every cell where someone has manually "fixed" a number, and you get models where the numbers don't match anyone's source of truth. The hardcode detector finds every override so you can audit them deliberately.

How hardcode detection works

  1. 1

    1. Upload the workbook

    SaferSheets parses every formula and walks the syntax tree looking for literal numeric values that aren't naturally part of the formula's intent.

  2. 2

    2. Triage by severity

    A literal 0 or 1 inside a logical test is probably fine. A literal 47,832 inside a SUM is almost certainly an override. Severity reflects suspicion.

  3. 3

    3. Cell-by-cell review

    Every flagged formula shows the full syntax with the hardcoded value highlighted. You decide which are intentional and which are mistakes.

  4. 4

    4. Download annotated copy

    Cell comments document every hardcode so a reviewer sees them in Excel. Useful for hand-off, audit sign-off, or board-pack review.

Patterns the hardcode detector flags

Not every literal number is a problem — some formulas legitimately use constants. The detector ranks findings by how likely they are to be unintentional overrides.

  • SUMs with appended numbers

    =SUM(A1:A10) + 5000 — almost always an override. The 5000 isn't part of any cell range; it's a hand-typed adjustment.

  • AVERAGEs with hidden fudge factors

    =AVERAGE(C1:C20) * 1.1 — multiplying an average by an arbitrary constant. Sometimes intentional, often a forgotten adjustment.

  • Tax / rate constants

    =Revenue * 0.23 (VAT), =NetIncome * 0.20 (income tax). Should live in a named range or a constants sheet so when the rate changes you update one cell, not fifty.

  • Magic threshold values

    =IF(A2 > 100000, "approved", "review") — fine if the threshold never moves, brittle when it does. Better as a named cell.

  • Off-by-one corrections

    =COUNTA(A:A) - 1 — typically subtracting a header row. Usually correct but worth confirming the count actually has a header.

  • Hardcoded values overriding formulas

    Cells where the surrounding column is all formulas, but this specific cell is a literal number. Someone typed over the formula. Flagged separately.

Frequently asked questions

Why is finding hardcoded numbers important?

+

Because spreadsheets get re-used. A model built for Q1 gets copied for Q2, then Q3. Every hardcoded number from Q1 — a one-off adjustment, a manual override, a now-stale assumption — silently rides along. By the time someone notices, the model has accumulated months of forgotten overrides. The hardcode detector lets you find them deliberately instead of accidentally.

What if the hardcoded value is intentional?

+

That's the right question. The detector doesn't remove anything — it surfaces every hardcode so you can decide. Intentional ones stay; the forgotten ones get cleaned up. Bigger constants (like tax rates) often belong in a named range so future-you can update them in one place.

Does it flag every number in every formula?

+

No. The detector ranks by suspicion. =IF(A2 > 0, ...) using 0 as a test value is unlikely to be a problem. =SUM(A1:A10) + 5000 with a five-figure literal at the end almost certainly is. Soft hits sink to the bottom of the list so you can skim past them.

Can I exclude certain formulas from the check?

+

Per-cell exclusions are on the roadmap. Today, the workflow is: review the list, mark intentional hardcodes in your team's review notes, and the audit will surface them again next quarter so you can re-confirm. Most teams prefer this — explicit re-confirmation beats silently ignored.

Does this work on Google Sheets too?

+

Yes. Use the Drive Picker on the Hardcode Detector page to pick a Sheet. SaferSheets reads it via the Google Sheets API and runs the same hardcode analysis.

Further reading

Deep-dives from the SaferSheets blog

Audit your next spreadsheet before you send it.

Free tier covers 30 audits a month. No card. Sign in with Google and you're running in under a minute.

Find hardcodes free

Audit. Validate. Trust your data.

Related tools