Finding a hardcoded override

This is some text inside of a div block.

You finished the rent roll paste at 11:40. The occupancy column looked fine on a glance. The print pack was already half built. Then you noticed F86 did not change when you bumped the unit count on the source sheet. The formula bar said 0.92. Not a formula. A typed figure sitting where a live link used to live.

That is a hardcoded override. It is not an Excel error banner. It is a cell that refuses to recompute while every neighbor still moves. Partners find those at midnight. So do associate reviews. The search term people type is not "model issue." It is "hardcoded override" plus the row, because the row is what they will ask you to defend.

Row 86 occupancy is typed over the formula. Restore the link before this file goes upstairs.

How to find the cell that will not move

You do not catch this by scanning for red triangles. You catch it by asking which cells still show a bare number in the formula bar after the inputs moved. Work the occupancy column first, then NOI drivers, then anything that feeds the print pack. If the face of the cell looks current and the bar does not show a formula, treat it as suspect until you prove otherwise.

Select the suspect column and arrow down while watching the formula bar on every row that feeds the print pack.
When the bar shows a literal (0.92, 14200, 1.05) instead of a formula, stop. That is the override.
Note the sheet, column, and row before you touch anything else. Write it down. Memory fails at midnight.
Check whether the typed figure matches last period, a peer paste, or a one-off "make the print look done" edit.
Scan two columns to the left and right. Overrides rarely travel alone after a bulk paste.

Why this shows up right before send

Hardcodes cluster at the end of a long night because the print pack wants a finished face. Someone pastes a peer, freezes a rate, or types last quarter's occupancy "just for the deck." The model still opens. The IRR still prints. The only tell is a formula bar that stopped telling the truth.

Put the formula back without losing the history

Restore the link to the rent roll. Keep the typed figure in a comment or a side column if you need the audit trail. Do not leave the literal in the live path. Market data still comes from your firm's own subscription. Moraton does not invent comps, and it does not approve the send.

Re-link F86 to the rent-roll occupancy source, not to a parked value on another sheet.
Recompute the column once and confirm neighboring rows still move when the unit count changes.
Re-run the read-back and confirm the row clears instead of renaming itself.
Sign off the flag yourself. The add-in names the row. It does not approve the send.

A typed figure that survives a recompute is not a rounding choice. It is a decision someone already made for you.

What Moraton actually reports

A flag with a row number and a plain description of what it saw. Not a certificate that the model is correct. Not investment advice. Not a green light to email the partner. A person still signs off every output before the file is sent upstairs. That posture is written into the terms on purpose, because the product is a read-back, not a substitute reviewer.

Before you hit send

If you are searching this at midnight, you already know the shape of the problem. Find the cell that will not move. Name the sheet and the row. Put the formula back. Recompute once. Then send only after a person has signed the flag, not after the print pack looks finished.

Hardcoded overrides survive because they look calm. Your job is to make them loud again: formula bar first, row second, restore third, sign-off last.