External organization / analytics enablement
Ministry analytics enablement
Turned manually maintained ministry data into corrected reporting inputs, a leadership presentation, and practical guidance for recurring metrics.
Analysis and guidance delivered; future capture process recommended- Business question
- What could leadership learn from the existing records, and what would make reliable monthly reporting possible?
- My role & scope
- Analytics and stakeholder-facing delivery
- Consequential contribution
- I repaired the datasets, checked findings against source records, and connected the analysis to recommendations for metric ownership and data capture.
- Outcome
- Delivered corrected reporting inputs, a leadership presentation, a validation memo, and guidance for data capture and recurring metrics review.
01 / Judgment
The problem and the choice
Leadership wanted to understand attendance, baptism, and event patterns. The manually maintained workbook mixed row types, text dates, and inconsistent year labels. Direct analysis risked excluding valid records or assigning them to the wrong period.
Repair and validate the data before presenting trends, preserve unresolved discrepancies, and recommend simpler capture practices before adding technical complexity.
02 / Delivery responsibility
What I owned
I rebuilt attendance, baptism, and event datasets, cross-checked them against the workbook, and prepared a leadership presentation. I kept validation detail in a companion memo and recommended a lightweight Google Forms and Sheets approach for future monthly reporting.
- Assessed the workbook and identified which records and questions could support reliable analysis.
- Built corrected attendance, baptism, and event datasets and documented unresolved source discrepancies.
- Created a leadership presentation with a companion validation memo, keeping technical checks available without crowding the findings.
- Prepared meeting guidance and recommendations for data capture, metric ownership, and recurring review.
03 / Working with others
How the work moved forward
I prepared the analysis, leadership presentation, validation memo, and meeting guidance for stakeholder alignment. Recommendations gave the organization a practical basis for metric ownership and recurring review.
04 / Technical detail
The implementation decisions
- Dates and exclusions
- A tab labeled 2024 contained later records; text-labeled special services also required explicit review to avoid silently dropping valid events.
- Source traceability
- Cleaned attendance rows were cross-referenced with the original workbook, formulas were checked, and event-level discrepancies were investigated.
- Capture design
- Recommendations separated dates from notes, made exclusions explicit, and kept Sunday baptisms distinct from event aggregates.
05 / Validation
Validation evidence
I cross-referenced cleaned data with the source workbook row by row, checked attendance formulas, restored special-service records omitted because their dates were stored as text, and investigated event-level discrepancies. Unresolved source totals remained flagged rather than being forced to reconcile.
06 / Outcome & status
What changed
Delivered corrected reporting inputs, a leadership presentation, a validation memo, and guidance for data capture and recurring metrics review.
The engagement delivered analysis and recommendations. Adoption of the proposed capture process and recurring review is not measured in the available record.