DBB3 Quality Control Center v6.3.1Shared coaching workspace
DBB3 ACTIVE
DBB3 CONTROL

Current Performance Week

Import reports to start.

Today

Who needs attention, who deserves a positive update, and how fresh the reports are.

Needs attention

Open a driver, read the reason, copy the message, done.
PRIORITIZED

Good work

Drivers with no current coachable issue can receive a short positive update.
WTD

Message status

Data health

Warnings and expected report lag.

Quick note

Source freshness

Separate cutoffs for Daily, DNR detail, Concessions, DWC and IADC.
NO FUTURE ZEROES

Week Coverage

Shows what is actually available for each day of the active Sunday→Saturday performance week. Missing days stay PENDING, never zero.
COVERAGE

Morning Control

A practical start-of-shift workflow: who to speak with, what changed, and what is still pending.

Start here

Drivers ordered by transparent internal priority points.
TODAY

Repeat issues

Same coaching signal appearing on multiple imported Daily dates.
REPEAT

Weekly coaching summary

Communication coverage

Data-quality watch

DBB3 import: upload reports produced for the station selected at the top.

Import Reports

Supported: Daily Report HTML, DWC/IADC HTML, and Delivery Associates / Concessions CSV or XLSX. You can upload Daily reports every day and refresh weekly data whenever you want.
LOCAL PARSER
Privacy: Raw Tracking ID, Place ID, postal code, customer notes/hints and item value are not stored. A short anonymous event key may be stored only to protect counting. Delivery Associates / Concessions keeps driver name + Transporter ID for internal profiles.
Import diagnostics: No import has been run in this session yet.
Import safety
No reversible import is stored for this session.

Imported source reports

Delete one source, or reset the workspace when you want to test from zero.
SourceTypeStationPeriodData Through

Concessions

Weekly snapshot by driver.

Concession Detail Signals

Daily DNR detail is used to explain each concession where available. The official WTD concession count still comes from the Concessions CSV.
GEO • CONTACT • SIMULTANEOUS • PHR
Important: DSC is treated as a score-inclusion flag: Y = included, N = not included. Coaching remains evidence-based: Contact, Geo, Mailbox, Simultaneous and reviewable scan mismatches.
DriverTransporter IDDeliveredDNR WTDDNR DPMORTSRTS %DNR Detail

Action Queue

A deterministic internal triage view — not an Amazon scorecard.

Driver Messages

Automatic operational coaching. Concessions first, then every Daily Report not yet communicated. CC is the main priority; RTS is coached only when the report shows a realistic delivery option or an excessive scan distance.

Concession Detail Signals

Daily DNR detail is used to explain each concession where available. The official WTD concession count still comes from the Concessions CSV.
GEO • CONTACT • SIMULTANEOUS • PHR
Important: DSC is treated as a score-inclusion flag: Y = included, N = not included. Coaching remains evidence-based: Contact, Geo, Mailbox, Simultaneous and reviewable scan mismatches.
DriverStatusDNRPending DailyFocus

Communication History

Saved only inside this workspace.
TimeDriverWeekLanguageConcessionsDaily Covered Through

Coaching Rules

Transparent, deterministic rules. No AI. Every automatic coaching line must be traceable to a field in a report.
REPORT-BACKED

What can generate a driver message?

🔴 Contact Compliance — highest Daily priority

Daily CC failures are actionable. When a contact opportunity is triggered, the driver should complete the required call/text workflow before returning or leaving a package unattended.

ACTION

🔴 Geo >25m

If Delivered ≥25m = Y, coach the driver to complete the delivery confirmation at the correct delivery point.

ACTION

🔴 Mailbox eligible, delivered elsewhere

If the report explicitly says the package was mailbox eligible but delivered elsewhere, coach mailbox use when the app/package allows it.

ACTION

🟠 Attended scan + text-only contact

If a concession is recorded as Household Member/Customer and the only recorded interaction is a text, show LIKELY INCORRECT DELIVERY STATUS. Driver-facing wording: we believe the parcel was most likely delivered to the mailbox rather than handed directly to a person. Household Member should only be used for a real hand-to-hand delivery.

REVIEW

🟡 Simultaneous Deliveries

Y means the delivery was part of a group stop completed together. It is context/coaching: complete each delivery carefully at its own correct location. It is not proof of an error by itself.

CONTEXT

🔴 RTS with usable delivery option

Strong coaching only for coachable return reasons such as Customer Unavailable / No Attempt when Mailbox Eligible or a Safe Place exists. OTP, damaged, rescheduled, object missing and similar cases are not automatically blamed on the driver.

ACTION

🔴 RTS scanned ≥100m away

If the report flags a return scan ≥100m away, coach the driver to make the attempt/scan at the delivery location whenever safe and possible.

ACTION

🔴 POD failure

Use the audit reason. Example: “No package detected” → make sure the package is clearly visible in the photo.

ACTION

DSC handling

Operational rule: DSC = Y is shown as Included in DSC score. DSC = N is shown as Not included in DSC score. The official weekly concession total is still taken from the Concessions CSV and is never recalculated from DSC detail rows.

DWC / IADC driver guidance

DWC — Contact Miss

When the app has no unattended recommendation, contact the customer before leaving the package unattended. If a call is not possible because of language, use SMS.

DWC — Photo Defect / Manual Bypass

Take a clear POD with the parcel visible and do not bypass a required photo step.

DWC — Geo >25m

Complete the delivery scan at the expected delivery location.

DWC — OTP

Follow the OTP workflow exactly and do not complete the delivery outside the required OTP process.

IADC

Follow the delivery location recommended by the app. Mailbox and customer safe-place recommendations are particularly important when shown.

Message philosophy

The driver-facing message contains only useful corrections. Raw identifiers, customer notes and unnecessary “No/No/No” fields stay out of the message.

Rules Simulator

Test a DNR scenario before changing a coaching rule. The simulator separates report evidence from system interpretation.
SANDBOX

Internal coaching priority — transparent points

This is not an Amazon score. It only sorts your workload. Points come from official concessions, pending CC, coachable RTS, RTS ≥100m, POD, DSC-included detail and repeat signals. The Driver Profile shows the exact point breakdown.

Repeat Issue detector

A signal becomes REPEAT when it appears on at least two imported Daily dates in the active performance week.

Improvement detector

Recent Daily issue load is compared with earlier imported Daily reports. It is shown as Improving / Stable / Worsening only when enough data exists.

Communication coverage

The system remembers the latest Daily date covered by a communication. New reports after that date remain Pending automatically.

DNR band

Secondary internal band retained for DNR only: 0–5 OK, 6–10 Attention, 11+ Action Plan. It does not replace the official scorecard.

Week Close & Comparison

Archive an operational snapshot without deleting source reports. Newer imported weeks automatically become the active week.

Settings

Local HTML
Another person's edits do not automatically appear on your PC.
Snapshot sharing
Export JSON including reports, communications and coaching follow-up states; another user can import it manually.
Shared mode later
The data model is prepared for a database + login when you want real collaboration.

Workspace snapshots

Continue in GPT

Portable development handoff for a new chat. Base Data is privacy-safe; use Workspace Export when you need the complete operational state.
HANDOFF READY
GPT Handoff Prompt
Copies the non-negotiable app rules, architecture, release expectations and testing instructions.
Base Data
Copies build metadata, active week, report inventory, reconciliation summary and week history without raw tracking/customer data.
Full Handoff
Copies the prompt and Base Data together, ready to paste into a new ChatGPT conversation.
Generated live from the current build and workspace.

Settings Security

Settings are protected by a session lock. Closing the browser session locks this page again.
UNLOCKED

Release Guardian

Read-only integrity checks for the current workspace: reconciliation, duplicates, privacy, messages, dates, storage and report consistency.
SYSTEM HEALTH
Not run yet.
Run the check after imports or before exporting a handoff.

Local activity log

TimeAction