The short answer
Start with a recently completed reporting cycle. Follow its source files, adjustments, spreadsheets, and review sign-offs to understand how the report was produced. Record who performed or approved each step and which questions remain unanswered. Review the map with the process owner before removing or redesigning a step, since it may support a control or accounting decision.
Understand the process you are taking over
A new reporting lead inherits a Workiva workspace, a shared folder, and a deadline. Nobody can say with confidence which file is authoritative, which steps are still manual, or who resolves exceptions. The temptation is to redesign from file names and an old procedure document.
Before changing the structure, check how a completed cycle worked. A step that looks redundant may support a control, and moving a file can affect links used elsewhere in the package.
Map one completed cycle
Choose a recently completed period and follow its artifacts from source to reviewed output. At each handoff, ask the person who did the work what happened. Do not infer a step from a timestamp or a file name.
| Cycle step | Input or artifact | Who performed or approved it | Evidence seen | Open question |
|---|---|---|---|---|
| Source received | The file, export, or Wdata table actually used | Source owner or preparer | File, import record, or receipt | Is this the authoritative source for the period? |
| Change applied | The adjustment or transformation, and where it happened | Preparer; approver if judgment was involved | Change record, formula, approval | Was it required, and who authorized it? |
| Report prepared | The spreadsheet, document, or presentation and when it entered review | Reporting operator | Output and review handoff | Which totals and narratives were checked? |
| Cycle closed | Reviewer sign-off and anything left open | Reviewer or process owner | Sign-off or open-item list | What carries into the next cycle? |
Tag every statement observed, owner-confirmed, or unknown. The unknowns are the most valuable part of the map.
Five questions before you propose a change
- Can you identify the source used for the cycle, including its period and owner?
- Can you tell each mechanical transformation apart from an accounting or policy judgment?
- Do you know who is authorized to approve each judgment or exception?
- Can you name the reviewer and the evidence that the cycle was complete?
- Are unresolved questions still visible on the map, rather than drawn as if they were automated?
If any answer is no, the next task is to answer it.
What to look for inside Workiva
A few places tend to hold undocumented behavior in inherited workspaces:
- Links. Which spreadsheet ranges feed which document tables, and are any destinations orphaned or pointing at the wrong period?
- Hardcoded values. Numbers typed into presentation sheets where a formula or link should be. These are often last year’s fixes that were never undone.
- Roll-forward settings. Dates and period labels that roll correctly versus text that someone edits by hand each period. The roll-forward checklist is a useful companion here.
- Data connections. Wdata tables, queries, or chains that refresh inputs, and who maintains them when a run fails.
- Permissions. Whether the people who actually do the work have the access they need, or whether the process quietly depends on an administrator account.
Review the map with your reporting team
Share the map with the Controller before proposing changes. Point to the steps that affect reported numbers and the places where ownership or approval needs a decision. Agreement on those points is what makes it safe to simplify the rest.
- Overview
- What you inherit
- Source received
- Change applied
- Report prepared
- Cycle closed
- Decide with the Controller
What you get from the map
The first useful deliverable is a one-cycle map with evidence and open questions. It lets the Controller decide what must stay, and it shows exactly which handoff is ready to improve. Often the answer is a handful of targeted repairs. If you are weighing the two, see whether to improve or rebuild a Workiva report.
Common questions
Where do I start with a Workiva package I did not build?
Start with the most recent completed cycle, not the original design documents. Follow the actual source files, adjustments, spreadsheets, and review sign-offs that produced the last report.
Can I trust the old procedure document?
Use it as a lead. Confirm each step with the person who performed it or with evidence in the files, because procedures often drift from what the team actually does.
When is it safe to remove a manual step?
When you know why it exists and the accountable owner agrees it is no longer needed. Some manual steps that look inefficient are controls or accounting judgments.
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.