Internal Redo (Bounce) Rate
Weekly fail rate vs. target
Target: 4.5%
Enter Production and Bounce counts
per week — fail rate is calculated automatically as bounce ÷ production, so
it can't drift out of sync. JSON: an array (or a "weeks"
object) of {"week":"WK33","production":2000,"bounce":100}.
CSV: header row Week, Production, Bounce.
Uploading a week that already exists updates it in place.
Weekly NPS & detractor mix
By symptom/category, with NPS overlay
JSON: either a plain array, or an object with a
"weeks" array, of entries shaped like
{"week":"26.W33","nps":70.2,"values":{"Repair Result":5,...}}.
CSV: header row Week, NPS, Repair Result, Contact
Center, Repair Speed, Other, Product Quality, Service Center/Process, Website
Experience, one row per week. Either way: uploading a week that already
exists on the chart updates it in place; a new week gets added. Nothing saves
until you click Save changes.
True RRR / Bounce Rate
IW pickup vs. OOW/Exchange, with True Bounce Rate overlay
Target: 0.70%
Total Incoming Bounce Rate and True Bounce APKUDO Calc are calculated automatically
from the counts you enter. True Bounce Rate (SEA) is entered directly, since it isn't
derivable from the other fields — that's the line plotted on the chart.
JSON: an array (or "weeks" object) of
entries shaped like {"week":"WK33","production":2200,"iwShipped":800,
"oow":1400,"bounceCount":55,"rrrCaseTotal":7,"factors":{"Product Quality":1,"Repair
Skill":3,"Process":1,"UBIF":0,"Other":2,"NTF":0},"trueBounceRateSEA":1.10}.
CSV: header row Week, Production, IW Shipped, OOW,
Bounce Count, RRR Case Total, Product Quality, Repair Skill, Process, UBIF, Other, NTF,
True Bounce Rate SEA.
Corrective Actions (Pending)
Corrective actions
Document library
Select a folder to browse its documents
Records
Completed audits, evaluations, and reviews
| Record | Site | Date | Outcome | Notes |
|---|
Forms
Placeholder slots for your existing forms — wiring these in is the next pass
Detailed Description of why an Action Request has been initiated.
Actions taken to immediately correct the reported condition and prevent potential increased severity / spread.
Determine the root cause of the reported condition, by asking "why" as many times as necessary.
Actions taken to correct the root cause of the reported condition and prevent future occurrences.
Approval
Activities performed to ensure the proposed action have been taken and effective.
Link an existing document, or add a new one to the CAR Folder in Documents.
This creates a linked entry in Documents (tagged CAR Folder) with the file name and
metadata. The file's actual contents aren't stored yet — that needs separate file
storage wired up on the backend (e.g. Cloudflare R2), which isn't part of this pass.
Attached
Action Request List
Click an ID to reopen and continue
Import format: a JSON array of objects with keys ID (or shortId), Status,
Date, AR Source (or source), Reported Condition, Resulting From (or resultingFrom), Issued
To (or issuedTo). Extra fields are ignored; missing ones are left blank. Re-importing
a row with an ID that already exists updates it in place rather than duplicating it.
| ID | Status | Date | AR Source | Reported Condition | Resulting From | Issued To |
|---|