The short answer
Repair your current Workiva report when you can isolate the problem and fix it while preserving the parts that work. Consider replacing a layer or rebuilding when the structure prevents reliable source tracing, review, or maintenance. Test either option against the same prior cycle and expected outputs. Confirm the source, responsible team, and review requirements before choosing.
Why “just rebuild it” is tempting
A recurring report is fragile or slow, and “let’s just rebuild it” sounds clean. Sometimes it is the right call. Often the package has one broken mapping or one unclear owner inside an otherwise usable structure, and a rebuild would trade a known problem for a large set of new ones.
Find where the problem starts
Before comparing options, name one concrete failure and the evidence for it: the reconciliation that does not tie, the table that shows last period, the step only one person can run. Then check where it originates, which outputs depend on it, who owns it, and what review it passes through.
The decision test
| Test | Improve the current structure | Replace a layer or rebuild | Defer |
|---|---|---|---|
| Where the failure is | Located and bounded; fixable without undermining adjacent controls | Spans dependencies or lineage that cannot be made reliable locally | Source or failure point not yet known |
| What already works | Core sources, calculations, ownership, and review can be kept | The structure itself blocks traceability or maintenance, based on observed evidence | Owner, access, or acceptance criteria missing |
| Change risk | Clear boundary, few known dependents | Explicit plan to preserve and transition every required output | Neither option can be tested responsibly yet |
| Acceptance | Rerun the same cycle; verify the repaired output and review | Test source-to-output lineage, review, and handoff | Name the missing evidence and who decides |
Signals that point to a repair
- The failure has one origin you can point to.
- Most outputs tie and review works; one area does not.
- The problem is a hardcoded value, a stale link, a missing mapping, or an undocumented step.
Signals that point to replacing a layer
- Calculations happen in presentation sheets, so every fix touches the report itself.
- There is no single place where a number enters; the same figure is keyed in several spreadsheets.
- Links cannot be listed or trusted, and roll forward breaks the same things every period.
- New requirements, such as a new entity or segment, cannot be added without copying and editing whole sections by hand.
Even then, a partial rebuild is often enough. Replacing the input and mapping layer while keeping the report documents can fix the root cause with far less disruption.
Run both options against the same cycle
Whichever way you lean, write down for each option what changes, what stays, what could break, and how the operator and reviewer will verify it. Then test against a real prior period with known results. A repair that passes the same acceptance checks as a rebuild is the better choice. A rebuild earns its cost only when the evidence shows the repair cannot pass them.
- Overview
- Where the problem starts
- Focused repair
- Replace one layer
- Defer
- Same prior cycle
Compare the options with your team
A one-page comparison is usually enough: what works today, where the failure starts, which outputs depend on it, what each option would change, and the checks that will be used to accept the result. That keeps the decision on evidence and gives the reviewer the same acceptance test either way.
If the package was inherited and you are not yet sure where the failure starts, map one cycle first.
Common questions
How do I know if my Workiva report needs to be rebuilt?
When the same class of failure keeps appearing across many dependencies and cannot be fixed locally without breaking something else, for example no traceable path from source to report or calculations spread across presentation sheets. A single broken mapping or unclear owner calls for a repair.
Is rebuilding in Workiva risky?
It can be. A rebuild changes every link, formula, and review point at once. Plan it with an explicit list of outputs to preserve, run it in parallel with the current version for at least one cycle, and compare results before switching.
What is a partial rebuild?
Replacing one layer, such as the input and mapping layer, while keeping the report documents and review structure that already work. It is often the best middle path.
Tell us what needs to work better
Describe the report, control process, or data flow that is not working the way it should. Every engagement starts with a fixed-fee Workiva diagnostic.