DocuWare Vehicle Damage & Insurance Workflow – Consolidated Meeting Notes
Overview
Purpose of the Workflow and Documentation
The workflow is specifically being designed and refined within the
DocuWaresystem for handling vehicles upon their arrival.These vehicles arrive for one of two primary reasons: either for routine, regular service, or as a result of an accident, referred to as "damage."
The overarching goal of this documentation and the associated meeting was to systematically incorporate feedback received from user-testing sessions.
Additionally, a key objective was to identify and eliminate any redundant or unnecessary steps within the existing or proposed processes.
Finally, the aim was to thoroughly finalize the comprehensive set of data points that the
DocuWaresystem must collect to ensure efficient and accurate processing of each case.
Tools, Systems, or Software Used
The primary software system utilized for the design and implementation of this workflow is
DocuWare.
Step-by-Step Process
Macro-Flow (Top Level Process) Initiation and Routing
Vehicle Arrival and Initial Data Capture via Inspection Sheet Web-Form
Action Trigger: The process commences when a vehicle physically arrives at the facility.
System Interface: Upon vehicle arrival, an authorized user is required to access and complete an
Inspection Sheet Web-Form.Visual Identifier: In the
DocuWaredesigner interface, this specificWeb-Formmodule is visually represented by the colorpurple, indicating its role as the initial data entry point (Inspection Sheet Web-Formvisualized aspurplein designer).
Automated Workflow Routing Based on Initial Input
System Logic: Once the
Inspection Sheet Web-Formis completed and submitted, theDocuWaresystem automatically processes the submitted data.Decision Point: Based on the information provided within the form (specifically, the
Purposeselection detailed below), the system intelligently routes the case into one of two distinct, primary workflows:The
Service Workflow: Dedicated to vehicles undergoing routine maintenance or non-damage-related services.The
Damage / Insurance Workflow: Specifically designed for vehicles involved in accidents or requiring damage-related repairs that may involve insurance claims.
Refined Damage / Insurance Workflow: Essential Task Series
The
"Damage / Insurance Workflow"has been thoroughly reviewed and streamlined. It now comprises only the absolutely essential tasks required for efficient and compliant processing of accident-related cases. These essential tasks include:Identify Fault & Collect Excess if Required: This initial task involves determining liability for the damage and, if applicable based on the determined fault, initiating the collection of any required insurance excess payment from the client.
Wait for Insurance Survey Report: The workflow must pause and await the official survey report from the relevant insurance provider, which contains critical assessment details.
Optional Parts-Ordering Checkpoint: A specific decision point is included where it is determined if new parts are necessary for the repair, and if so, their ordering is initiated. This step is explicitly noted as optional within the streamlined flow.
Issue Repair Instructions: Once all preliminary steps (fault, excess, survey, and parts consideration) are complete, the necessary instructions for commencing the vehicle repair are formally issued.
Track Vehicle Return & Hand-Over to Client: The final phase involves monitoring the vehicle's repair completion, managing its return to the facility, and facilitating the official hand-over back to the client.
Inspection Sheet – Critical Mandatory Data & UI Changes
Mandatory Data Collection Fields
The
Inspection Sheet Web-Formis designed to mandate the collection of the following crucial pieces of information at the initial stage:Vehicle Registration Number: A unique identifier for the vehicle.
Client Name / Company: Identification of the individual or entity responsible for the vehicle.
NEW Requirement: Driver’s Licence Number: This is a newly introduced mandatory field. Additionally, the system provides functionality where a picture of the driver’s licence can be attached to the case, enhancing record-keeping and verification.
Automated Timestamp: The form no longer solely records the date but now automatically stamps both the date and time of submission. This provides a more precise temporal record of when the inspection sheet was completed.
Consolidated Radio-Button Logic for Early Decision-Making (UI Enhancement)
Purpose of Consolidation: The user interface (UI) for early decisions has been redesigned to incorporate all initial critical choices into a single, comprehensive radio-button logic structure.
Downstream Task Management: The primary benefit of this consolidation is that it dynamically controls the visibility and necessity of subsequent downstream tasks; these tasks will only appear or be activated if they are genuinely required based on the user’s initial combined selections.
Combined Decision Points: The consolidated logic encompasses the following decision-making pathways:
Purpose of Visit: The user must select one of two primary categories:
Service: Indicating routine maintenance or non-accident related issues.Damage: Indicating the vehicle is at the facility due to an accident or damage.
If
"Damage"is selected, further cascading decisions are presented: These decisions guide the workflow through potential insurance claims and cost considerations:Will a claim be opened?: This is a direct Yes/No question.
If
"No"(a claim will not be opened): The system then prompts with a follow-up question:“Waive cost?”again, requiring a Yes / No response. This determines if the repair cost will be absorbed by the company or charged to the client outside the workflow.If
"Yes"(a claim will be opened): The system immediately asks for an initial estimate of the damage cost, categorized as: below | above . (Alternatively, a simpler direct question“Claim needed? Yes / No”could be used for initial filtering).
Fault Guess: This critical early assessment impacts subsequent financial steps (especially excess collection). The user must indicate the presumed party at fault:
Client: The vehicle owner/driver is believed to be at fault.Third-party: Another party is believed to be at fault.Unknown: The fault has not yet been determined.
> (Note: This“Fault guess”directly affects whether the"excess"collection step is triggered).
Detailed Damage / Insurance Workflow (Revised from User Feedback)
1. Fault & Excess Collection Automation
Task Identifier: The initial task in this revised workflow segment is explicitly labeled:
“Who is at fault?”Conditional Logic for Excess Collection: Based on the determination of fault:
If
clientis indicated as being at fault: The system will automatically display and activate the associated Collect Insurance Excess task. This ensures the prompt collection of the required deductible from the client.If
third partyis indicated as being at fault: The system will automatically skip the excess collection task, as the client is not liable for the deductible in this scenario.
Immediate Excess Payment & Manual Refund Handling: The workflow mandates that the excess amount is paid immediately upon determination of client fault. This prompt payment is crucial for the efficient opening of the insurance claim. It is explicitly noted that any refunds of this collected excess (for instance, if a later insurance survey overturns the initial liability assessment) will need to be handled manually outside of the automated DocuWare workflow.
2. Waiting for Survey Report and Parts Ordering Decision
Task Identifier: The current task is designated as:
“Upload Survey Report.”Mandatory Document Requirement: This task necessitates the upload of a mandatory document originating directly from the insurer. This document is critical and must contain:
The final assessed damage to the vehicle.
A comprehensive list of all parts required for the repair.
An official confirmation of liability (which may override the initial fault guess).
The total estimated cost of the repair.
Inline Question for Parts Ordering: While awaiting/uploading the survey report, an inline question is presented to the user:
“Order parts? Yes / No.”This decision point directly influences the subsequent workflow path.Conditional Workflow Branching Based on Parts Order Decision:
If
"No"(parts are not to be ordered at this stage): The workflow will automatically jump directly to the Issue Repair Instructions task, bypassing any parts-related steps.If
"Yes"(parts are to be ordered): A new, dependent task will immediately appear on the user’s interface.Required Input for Parts Order: The user is then required to Enter Work-order / WIP number (
Work-In-Process number). This field is designated as required to uniquely identify and track the parts order.
3. Issue Repair Instructions and ETA Management
User Action: At this stage, the user is required to directly input the Estimated Time of Arrival (ETA) for the completed repair. This ETA represents the anticipated date when the vehicle’s repair work will be finalized.
System Automation (DocuWare Functionality):
DocuWareperforms two key automated functions:The system securely stores the inputted ETA value within the case’s metadata.
DocuWarethen enters a"sleep"state, effectively pausing the workflow for this specific case until that specified ETA date is reached.
4. Automated Vehicle Return Reminder Loop
Automated Task Trigger (on ETA Date): On the precise ETA date that was previously entered and stored,
DocuWareautomatically reactivates the case and surfaces a new task to the user. This task is labeled:“Vehicle due back today – ready?”This serves as a prompt for the user to confirm the vehicle’s repair status.Conditional Workflow Progression Based on Readiness Confirmation:
If
"Yes"(Vehicle is ready): If the user confirms that the vehicle is indeed ready for return:The current workflow branch decisively ends.
The successful hand-over of the vehicle to the client is officially recorded within the system.
If
"No"(Vehicle is not ready): If the user indicates that the vehicle is not yet ready for return:The user is prompted to enter a new ETA, indicating a revised anticipated completion date for the repair.
Upon receiving the new ETA,
DocuWareautomatically re-schedules the reminder. The system will then again enter its"sleep"state and re-surface the“Vehicle due back today – ready?”task on this newly set ETA date, continuing the loop until the vehicle is confirmed ready.
Workflow Streamlining: Removed or Renamed Steps
Renaming of
"Get Quotation": The step previously known as“Get Quotation”has been officially renamed to“Waiting for Survey Report.”This change reflects the actual process, as insurers typically supply a comprehensive damage survey report rather than a simple repair quote.Deletion of Redundant Insurance Approval Gate: The previously existing and now redundant
Insurance Approval > /Relocation of Initial Estimate Decision: The critical decision point concerning whether an estimate is has been strategically moved earlier in the process. This decision is now captured directly on the initial
Inspection Sheet. This upstream capture eliminates the need for an additional, separateDocuWaretask dedicated to this decision, further streamlining the workflow.
Data Attachments & Media Handling Capacities
Photo Upload Capability: The
Inspection Sheet Web-formis designed to accommodate the upload of a significant number of visual evidentiary documents. It specifically allows for the attachment of up to photos per case.Photo Content Examples: These photos are intended to capture various critical aspects of the vehicle’s condition and documentation, including (but not limited to) images of the vehicle’s exterior, interior, odometer readings, close-ups of specific damage points, and a picture of the driver’s licence.
Example of Estimate Volatility: A practical example provided to illustrate the potential for initial estimates to change after a more thorough inspection is a tail-light replacement, which was initially quoted at . This scenario highlights precisely why the initial estimate provided on the inspection sheet can deviate significantly from the final cost determined after a detailed insurance survey.
Practical Examples & Scenarios (Workflow Application)
Scenario 1: Minor Scratch (Approx. )
Initial Input: The user would mark the
Inspection Sheetwith"Damage, No Claim, Waive Cost."Workflow Outcome: The system’s consolidated logic would immediately determine that no claim is needed and the cost is waived. Therefore, the workflow would leap straight to the Issue Repair Instructions task, minimizing unnecessary steps.
Scenario 2: Client Reverse into Pillar (Approx. )
Initial Input: The user would mark the
Inspection Sheetwith“Damage, No Claim, Charge Client.”Workflow Outcome: The system would proceed to Issue Instructions for the repair. However, the collection of payment for this repair would occur
outside the automated workflow, as it’s not an insurance claim.
Scenario 3: Front-to-Rear Collision, Client at Fault (>)
Initial Input: The user would select
"claim yes"and specify"client at fault"on theInspection Sheet.Workflow Outcome: This complex scenario would trigger the full, comprehensive damage workflow:
Excess Collected: The system would ensure the insurance
excessis collected from the client.Wait for Survey: The workflow would then enter the waiting for survey report phase.
Order Parts: Based on the survey, parts would be ordered.
Repairs: Repair instructions would be issued, and repairs would commence.
Vehicle Return: The vehicle return process would be tracked to completion.
Scenario 4: Stop-Sign Accident, Third Party at Fault
Initial Input: The user would specify
"claim yes"and crucially,"third-party fault"on theInspection Sheet.Workflow Outcome: Similar to Scenario 3 regarding a claim, but with a key difference:
Skip Excess: Due to third-party fault, the system would skip the collection of
excessfrom the client.Wait Survey & Order Parts: The workflow would proceed to wait for the survey and order parts as needed.
No Refund Task: Crucially, no separate refund task would be required within the workflow, as no
excesswas collected from the client.
Additional Metadata / Audit Requirements & System Integration
Manual Override Capabilities: The
DocuWareworkflow is designed with built-in flexibility, allowing for manual override at each individual task stage within the process.1. The initial
“fault”determination can be manually changed by a user if a subsequent insurance survey definitively proves otherwise.2. The recording of an
excessrefund, if one becomes necessary, can be handled and documented outside the automated workflow, without disrupting the primary process flow.
Replacement-Vehicle Assignment: The process of assigning a replacement vehicle to a client is handled by a separate, existing field or system module. This specific functionality remains unchanged and is not directly integrated into the revised damage workflow, but operates in parallel.
Version Control and Documentation Updates: A robust version control process is maintained for all documentation. The next iteration of the
PDFdocumentation will be updated to accurately reflect all the edits and revisions discussed and finalized, ensuring that the documentation remains current and synchronized with the implemented workflow changes.
Open Items / To-Do List (Actionable Tasks)
Kelin’s Priority Task: Kelin is specifically tasked with updating two email templates as a first and high-priority action item. These templates are essential for communications within the workflow.
Workflow Designer Modification: The workflow itself needs to be physically modified in the DocuWare designer instance. These modifications must align precisely with the diagram and summarized decisions established and agreed upon during the current discussions.
Inspection Sheet Form Editing: The
Inspection Sheetform withinDocuWarerequires specific edits:Addition of the
driver licence fieldas a new mandatory data point.Modification of the existing
Datecontrol to a more preciseDate-Timecontrol, ensuring that the exact time of entry is captured.
Team Testing Phase: A dedicated team, comprising Audrey, Mark, and Mick, is assigned to conduct thorough testing. This testing is to be performed on a substantial dataset, specifically imported contracts plus the existing vehicle fleet, following the successful deployment of the workflow updates.
Ongoing Manual Data Load: The ongoing, one-time manual data load for the remaining vehicle fleet (those not yet digitized) is to continue. It is explicitly stated that
post-cut-off, meaning after a certain point in time, all subsequent edits and data modifications for this fleet will exclusively happen insideDocuWare, enforcing the new digital workflow.
Ethical & Practical Implications of the Workflow Revision
Reduction in User Task-Load & Claim Cycle Time: By ensuring accurate upstream decisions (i.e., making correct choices early in the process on the inspection sheet), the revised workflow significantly reduces the subsequent burden and number of tasks for the end-user. This streamlining directly contributes to a substantial cut in the overall claim cycle time, leading to faster resolution of damage cases.
Company Protection through Immediate Excess Collection: The policy of immediate
excesscollection upon determination of client fault serves as a critical protective measure for the company. This ensures that the financial deductible is secured, mitigating the risk of monetary loss if a driver (who is liable) were to leave employment or otherwise become unreachable before liability is fully settled with the insurer.Enhanced Workflow Flexibility for Corrections: The design incorporates inherent workflow flexibility, allowing for manual corrections and adjustments to case details even after initial decisions are made. This critical feature means that if new information emerges