<h2>Prerequisites</h2><ul class="accent-bullets"><li>Access to the Wunder Backoffice.</li><li>Appropriate user role to create and manage damages and tasks.</li><li>Service workers set up in the Service App.</li></ul><h2>How It Works</h2>Damages and tasks are tightly connected but serve different purposes.<ul class="accent-bullets"><li>Damages describe the state of a vehicle or vehicle part. They capture what is wrong, where it happened, and its lifecycle over time.</li><li>Tasks describe work that needs to be done. They are the operational backbone and the main entry point for daily fleet operations.</li></ul>Operators should primarily manage their fleet by working through open tasks. Damages provide context, history, and analytics, but tasks drive execution.Typical task categories include cleaning, relocation, inspection, repair, and billing. Damages move through defined states to prevent false reports and unnecessary vehicle downtime.<img src="https://uploads.productlane.com/a15be44ae476de8dc2b545de2409e796.jpeg" data-processed-src="https://uploads.productlane.com/a15be44ae476de8dc2b545de2409e796.jpeg" data-original-src="https://uploads.productlane.com/bdd125c28668a219c31fdb2dfcd4b5b7.png"><h2>How Damages Are Structured</h2>Damages in Wunder are always created based on a vehicle part.Each vehicle category should be configured with a clear and consistent set of parts. These parts represent what exactly can be damaged on that vehicle.Typical examples of parts:<ul class="accent-bullets"><li>Puncture</li><li>Brake</li><li>Door</li><li>Windshield</li><li>Accident</li><li>Light</li><li>Handlebar</li></ul>When damage is created, the operator or service worker selects the relevant part. The damage record then describes the state of that part over time.This approach ensures:<ul class="accent-bullets"><li>Consistent damage reporting across the fleet</li><li>Clean historical data per vehicle part</li><li>Meaningful analytics on where and how damages occur</li></ul>Damages are never generic. They always belong to a specific part.<h1>Step-by-Step Guide</h1><h2>Core Flow Example: Accident in a Car Sharing Fleet</h2><ol class="steps-list"><li>Accident occurs<ol class="steps-list"><li>A customer or authority reports an accident.</li><li>The operator has a vehicle part named Accident configured.</li></ol></li><li>Create a damage record<ol class="steps-list"><li>Create a new damage on the vehicle part Accident.</li><li>Set the damage state directly to Approved if the incident is confirmed (e.g. customer call or police report).</li></ol></li><li>Create an inspection task<ol class="steps-list"><li>From the damage, create a task for a service worker (e.g. Inspect accident damage).</li><li>Assign it to the appropriate team or individual.</li></ol></li><li>Service worker completes the task<ol class="steps-list"><li>The worker inspects the vehicle on site.</li><li>The task is marked as completed in the Service App.</li></ol></li><li>Create follow-up tasks<ol class="steps-list"><li>Based on the inspection, create follow-up tasks such as:<ol class="steps-list"><li>Tow vehicle</li><li>Repair damage</li><li>Charge customer</li></ol></li></ol></li><li>Resolve or close the damage Once work is finished, mark the damage as Repaired or Ignored, depending on the outcome.</li></ol><img src="https://uploads.productlane.com/6a50060cd1645d3880f543051f8879f2.jpeg" data-processed-src="https://uploads.productlane.com/6a50060cd1645d3880f543051f8879f2.jpeg" data-original-src="https://uploads.productlane.com/d3adc369c071f276557455aa0f4744bb.png"><h3>Alternative Flow: User-Reported Damage</h3><ol class="steps-list"><li>A user reports a damage via the Consumer App.</li><li>The damage is created in New state.</li><li>An operator or service worker verifies the damage.</li><li>The damage is Approved if it exists, or ignored if not valid.</li><li>Tasks are created to inspect, repair, or handle billing.</li></ol>This approval step prevents spam reports and avoids taking vehicles out of service unnecessarily.<h2>Damage States Explained</h2><ul class="accent-bullets"><li>New – Reported by a user. Not yet verified.</li><li>Approved – Verified damage. Can trigger tasks and operational actions.</li><li>Under repair – Actively being worked on.</li><li>Repaired – Fixed and resolved.</li><li>Ignored – Verified but intentionally not repaired (e.g. cosmetic scratches).</li></ul>Only approved damages should influence operational decisions.<h2>Damages, Tags, and Fast Fleet Filtering</h2>Every active damage automatically creates a vehicle tag.As long as a damage is in an active state (for example New, Approved, or Under repair), the vehicle receives a tag with the following structure:<code class="inline-code-shadow bg-gray-100 border border-gray-200/60 dark:border-gray-800 font-medium dark:bg-gray-700/60 text-gray-700 dark:text-gray-200 font-mono text-md px-1 py-0.5 rounded-[0.2rem] [&amp;::before]:content-none [&amp;::after]:content-none">damage:&lt;part-name&gt;</code>Examples:<ul class="accent-bullets"><li><code class="inline-code-shadow bg-gray-100 border border-gray-200/60 dark:border-gray-800 font-medium dark:bg-gray-700/60 text-gray-700 dark:text-gray-200 font-mono text-md px-1 py-0.5 rounded-[0.2rem] [&amp;::before]:content-none [&amp;::after]:content-none">damage:puncture</code></li><li><code class="inline-code-shadow bg-gray-100 border border-gray-200/60 dark:border-gray-800 font-medium dark:bg-gray-700/60 text-gray-700 dark:text-gray-200 font-mono text-md px-1 py-0.5 rounded-[0.2rem] [&amp;::before]:content-none [&amp;::after]:content-none">damage:windshield</code></li><li><code class="inline-code-shadow bg-gray-100 border border-gray-200/60 dark:border-gray-800 font-medium dark:bg-gray-700/60 text-gray-700 dark:text-gray-200 font-mono text-md px-1 py-0.5 rounded-[0.2rem] [&amp;::before]:content-none [&amp;::after]:content-none">damage:accident</code></li></ul>Once the damage is Repaired or Ignored, the tag is removed automatically.<h3>Why this matters operationally</h3>These tags allow operators to instantly answer questions like:<ul class="accent-bullets"><li>How many vehicles currently have a puncture?</li><li>Which cars are affected by accidents right now?</li><li>Where on the map are vehicles with unresolved windshield damages?</li></ul>You can filter by these tags:<ul class="accent-bullets"><li>In the vehicle list</li><li>On the map view</li><li>In operational workflows when creating or assigning tasks</li></ul>This makes damage-based fleet visibility fast, reliable, and scalable — without manual tracking.<h2>Working with Tasks Day-to-Day</h2><ul class="accent-bullets"><li>Treat the Tasks page as your operational control center.</li><li>Focus on:<ul class="accent-bullets"><li>Open tasks</li><li>Correct assignment</li><li>Timely completion</li><li>Use task categories to structure work and responsibilities.</li><li>Create follow-up tasks whenever new actions are required.</li></ul></li></ul>Keeping tasks up to date ensures clear ownership and predictable execution.<h2>Tips and Best Practices</h2><h3>Linking Damages and Tasks for Full Traceability</h3>Damages provide context. Tasks drive execution.When damage is created on a specific part, operators should create one or more tasks linked directly to that damage.Typical examples:<ul class="accent-bullets"><li>A damage on part Accident → task Inspect accident</li><li>A damage on part Puncture → task Fix puncture</li><li>A damage on part Door → task Inspect and repair door</li></ul>All tasks linked to a damage remain visible in the damage view. This creates a complete operational history:<ul class="accent-bullets"><li>What happened</li><li>What actions were taken</li><li>Who executed them</li><li>What follow-up was required</li></ul>If additional work is needed, operators or service workers create follow-up tasks linked to the same damage, such as:<ul class="accent-bullets"><li>Towing</li><li>Repair</li><li>Billing or customer charge</li></ul>Tasks may be completed independently, but the damage acts as the long-term anchor for documentation, accountability, and analysis.<h2>Troubleshooting</h2>Damage reported but vehicle should not be blocked<ul class="accent-bullets"><li>Ensure the damage is still in New state.</li><li>Do not approve until verified.</li></ul>Tasks are getting missed or delayed<ul class="accent-bullets"><li>Check task assignment and priorities.</li><li>Ensure service workers actively use the Service App.</li></ul>Too many low-value damages clutter the system<ul class="accent-bullets"><li>Train operators to use the Ignored state consistently.</li><li>Align internally on what requires action and what does not.</li></ul>

Fleet & Operations

Damages and Task management

Platform overview

Getting Started

Locations and branches

Service App (Beta)

Optimizing Vehicle On-Field Maintenance Flows

Card Management (RFID)

Managing On-Demand Rentals

Radar

On-Demand vs. Pre-Booking

Additions and Insurance

Subscriptions & Multi-Benefit Packages

Pricing, Memberships & Promotions

Login Options & Sign up Fee for End Users

User Management & Profiles

Roles and Permissions 

Business accounts and corporate billing

Users & Accounts

Payment Gateways and Methods

Invoicing

Invoice PDF Structure & Customization

Revenue Protection and Payment Assurance

Payments & Invoicing

Mobile App Translation Keys: Sign Up, Rental & Booking

App Configuration & Customization

MaaS API

FreeNow Integration Overview

Credit Rating (CRIF)

Veriff Driving License Verification

Onfido Identity & Driver's License Verification

Braze Messaging integration 

AppsFlyer Integration

Zendesk Chat

Integrations & APIs

INVERS IoT Integration

Vehicle & IoT Support

Introducing Wunder Analytics (Beta)

Issues Analytics (Beta)

Data Insights

Two-Factor Authentication (2FA)

Security

Choosing the Right Sign-In Method in Wunder  (Email OTP vs Phone Login vs Password)