The work beneath the work
Reading the pattern behind repeated document follow-up
I did not simply report that documents were missing. I investigated the operational pattern behind the follow-up activity and used the evidence to identify where process improvement could potentially reduce repeated work.
- My role
- Analysed independently, in fiduciary and estate administration operations at a large South African financial institution
- What I analysed
- 228 cases, of which 73 required follow-up, generating 278 follow-up entries
- How common
- 73 of the 228 analysed cases, about 32%
- Tools
- Excel, including pivot tables
- Presented to
- Relevant stakeholders
- Skills shown
- Business analysis, process analysis, operational data analysis, pattern analysis, process-improvement thinking
The business problem
When a case arrives with missing or incomplete documentation, follow-up activity may be required before processing can continue. That follow-up is real operational effort, and it sits between a case being received and that case moving on.
The question I set myself was not how many documents were missing. It was whether the follow-up activity showed a pattern that a team could act on.
The investigation
73 of the 228 analysed cases required follow-up, generating 278 follow-up entries. I worked through those entries to understand:
- which documentation categories generated the most follow-up entries
- how follow-up entries were distributed across touch levels
- whether the follow-up activity showed recurring patterns
- where potential process-improvement opportunities might exist
Where this sits in the process
The analysis relates to the early documentation and completeness stage of a broader fiduciary administration workflow. The diagram shows only that stage and what surrounds it.
- Case received
- Document completeness check
- Missing or incomplete documentation?
Yes
- Follow-up
No
- Case preparation
- Verification
- Document generation and downstream processing
The stages the analysis relates to.
This is a high-level illustration for portfolio purposes. It is not a complete or authoritative representation of the institution's internal process.
What the data showed
Follow-up entries by documentation category
Follow-up entries occurred across a range of documentation categories. Letter of Instruction generated the highest number of follow-up entries in this dataset.
Categories are presented using generic labels for confidentiality. Some entries represent groups of required documents rather than individual document types, so the categories should be interpreted as descriptive follow-up classifications rather than mutually exclusive document categories.
Follow-up entries by touch level
Touch level indicates where an entry occurred in the sequence of follow-up activity. The entries span touch levels from one to seven, with most activity occurring at lower touch levels and a smaller tail extending to repeated follow-up.
Each count is a number of follow-up entries, not a number of cases.
Evidence and interpretation
Evidence
- 73 of the 228 analysed cases (about 32%) required follow-up.
- Those cases generated 278 follow-up entries. The 278 counts entries, not cases.
- Follow-up entries occurred across multiple documentation categories.
- Entries occurred across touch levels from one through seven.
Interpretation
- Follow-up activity represents recurring operational effort.
- Repeated follow-up represents additional activity that may need to be completed before a case can progress through downstream processing.
- These patterns point to potential areas for further investigation.
Opportunities to explore
These are hypotheses the pattern suggests, not conclusions, and none is an implemented solution. The data shows what was followed up and how often. It does not show why documents were missing or whether the follow-up could have been avoided, so each idea would need testing.
- Validate commonly followed-up documentation earlier in the process
- Handle follow-up in a more structured way
- Identify the recurring points of rework
- Improve visibility of outstanding requirements
What this case study demonstrates
- Business analysisFraming an operational question and presenting findings to stakeholders
- Process analysisLocating the analysed activity within a wider workflow
- Operational data analysisWorking from 228 analysed cases and 278 follow-up entries
- Pattern analysisIdentifying recurring patterns and being explicit about what they cannot establish
- Process-improvement thinkingTurning patterns into evidence-based opportunities
Limitations
- The underlying operational data is proprietary and is not reproduced here.
- This page uses aggregated, non-identifying findings only.
- The workflow is a sanitised, high-level representation.
- The analysis identifies patterns, not definitive causal relationships.
- Document-category counts are descriptive. Without knowing how many cases required each document category, the analysis cannot estimate the probability that a particular document was missing.
- No implementation or measured business outcome is claimed.
- The original operational process contained more detail than this representation shows.