Joseph Rehall / Work in detail
Audi Team Dashboard: audit reporting and business intelligence
I built Audi Team Dashboard to bring audit results together and help management and executives understand what is happening across the business. It connects individual audits with team, auditor, and dealer analysis. The findings also feed back into Audi Nuvobook, linking management insight with the risk profiling that guides future audits.
- My role
- Data pipeline, application design, and development
- Focus
- Audit business intelligence and management reporting
- Connected application
- Audi Nuvobook
Bring the audit results into one application
An individual audit tells you about the work that was reviewed. Management also needs to understand how those results relate to the rest of the audit activity. I built the dashboard’s data pipeline to integrate all audit results and make that wider view available in one application.
Audi Nuvobook supplies the published audit data. The dashboard brings that information into reporting that connects team activity with dealer findings and individual audit records. I designed the two applications to work together so the reporting stays connected to the audit work that produced it.
Help management investigate the results
I developed the application for management and executive use, with views of the team, individual auditors, and dealers. Filters by period, region, and auditor let people examine the part of the work they need to understand.
Dealer history by quarter adds context, while the audit register provides a view of individual audits. I want someone looking at an overall pattern to be able to explore the records behind it. That connection between the summary and the underlying work is central to how I approach business intelligence and management reporting.
Keep the meaning of the numbers intact
Audit reporting includes different stages of work. A claim that has been flagged is different from one selected for review, imported into an audit, or reviewed. The dashboard distinguishes those measures so someone interpreting the activity can understand what each count represents.
The same care applies to risk information. Risk scores and high-risk claim counts describe where attention may be needed. Audit findings describe what the review established. My experience doing the audits helps me keep those meanings in view when I build the reporting.
Make room to check the data
I included data-quality review in the application because the report depends on the information behind it. The dashboard has a dedicated Data Quality view alongside its team, auditor, dealer, and audit-register views.
I treat that review as part of understanding the report. Before acting on a pattern, I want to know which records are represented and whether the information supports the interpretation. The filters and individual audit records give the reader context for that work. It reflects the same attention to evidence that I bring to warranty auditing.
Use what we learn to guide the next audit
The connection with Nuvobook works in both directions. Nuvobook supplies the audit results, and findings from Audi Team Dashboard feed back into Nuvobook’s risk-profiling logic. That feedback loop helps shape future audit planning using what has already been learned from the work.
I owned the data pipeline, application design, and development. Building the dashboard gave me a way to connect my audit experience with the questions management needs to answer. I care about that connection because the value of reporting comes from what people can understand and do with it.