Reverse-engineering a return that has become a black box
Tracing a SAM return back through the spreadsheets feeding it, one input at a time.
There is a particular kind of problem that only appears under pressure: a regulatory return that still produces a number, but nobody left in the building can explain how. The people who built it have moved on. The spreadsheets feeding it reference other spreadsheets. The return goes out because it has always gone out.
Start at the output, work backwards
You cannot fix what you cannot trace. We take the final return template and follow every populated line back to its source — the calculation that produced it, the file that calculation lived in, the input that file depended on. One line at a time, until each number has a provenance.
What you usually find
Circular references nobody noticed. Two teams working to different cut-off dates. A hard-coded adjustment from a prior year that was never removed. None of it is malice. It is accretion — years of reasonable fixes stacked on top of each other until the whole thing became opaque.
The deliverable is understanding
By the end there is a map: every input, every owner, every control. The return is no longer a black box. From there the choice is simple — keep the process with the map in hand, or rebuild it now that you know what it actually does.