Joseph Rehall / Work in detail
Audi Nuvobook: warranty audit automation
I built Audi Nuvobook around the warranty audits I perform. It connects claims and supporting records with review logic and reporting, automates repetitive work, and helps auditors focus on higher-risk claims. I designed the application from firsthand experience of what it takes to investigate a claim and explain a finding.
- My role
- Application design, automation, and risk-profiling logic
- Domain
- Automotive warranty auditing and operational systems
- Connected application
- Audi Team Dashboard
I knew the work before I built the application
At Audi, I review warranty claims alongside repair orders, technician notes, and labor records. I check whether the repair and claim meet policy and whether the documentation supports what was submitted. That means working through technical details and explaining the findings to dealership management and Audi stakeholders.
I brought that experience into Nuvobook’s design. I know how much context sits behind a claim, and how easily that context can get lost when the review and the reporting are treated as separate tasks. I built the application to keep that work connected.
Keep the finding connected to the evidence
Nuvobook brings claims, supporting records, audit logic, and reporting into one workflow. The connection matters because a finding has to be explainable. Another reviewer needs to understand what was checked and how the evidence supports the result.
That is also how I work as an auditor. When I identify an adjustment or a documentation gap, I need to substantiate it. I carried that requirement into the software so the application supports the reasoning behind the review as well as the final report.
Reduce the repeated work around the review
I developed automation to reduce repetitive manual steps in the audit workflow. The point is to give auditors more time for the parts that need their attention: checking the records, investigating discrepancies, and deciding what the evidence supports.
I think about audit efficiency in terms of the whole task. A report is only one part of it. The information still needs to make sense to the person reviewing the claim and to the person reading the result. That is why I designed the automation and reporting around the audit itself.
Use risk profiling to decide where to look
I built risk-profiling logic into Nuvobook to help prioritize claims for review. Risk scores and flagged claims help auditors focus attention on higher-risk work and make the selection process more informed.
A risk flag gives the auditor a reason to look more closely. The review still needs to establish what happened. I keep that distinction in mind when connecting automated checks with audit decisions, because a suspected issue and a supported finding have different meanings.
Let completed audits inform the next ones
Nuvobook provides published audit data to Audi Team Dashboard, which brings results together for management and executive reporting. Findings from that wider view feed back into Nuvobook’s risk-profiling logic, connecting what we learn from completed audits with the planning of future reviews.
I designed and developed both applications. My ownership covers the application workflow, automation, and risk-profiling logic, along with the connection to management reporting. It is the same kind of work I enjoy across process improvement and software development: understand the problem in detail, then build the system that helps the team work through it.