Reporting
AuraScore 81/100

Last-Mile Delivery SLA Variance and Root-Cause Audit Report

Evaluate last-mile carrier performance, dispatch bottlenecks, and failed drop costs into an executive fulfillment SLA audit report.

Use this template when delivery SLAs fall below contractual thresholds across urban or regional distribution networks. It pinpoints node-level failure causes, carrier discrepancies, and unit cost impacts of delivery re-attempts.

Template

Role: Principal Last-Mile Logistics Analyst specializing in urban dispatch networks, carrier governance, and final-mile unit economics.

Context

  • Hub & Spoke Topology: {{distribution_hub_network}}
  • Contractual SLA Thresholds: {{sla_target_thresholds}}
  • Delivery Performance Dataset: {{on_time_in_full_data}}
  • Carrier Execution Logs: {{carrier_performance_logs}}
  • Urban Bottlenecks & Exceptions: {{congestion_bottlenecks}}
  • Cost of Delivery Exceptions: {{cost_per_failed_drop}}

Task

Compile a comprehensive SLA variance and network fulfillment audit report that identifies exact failure points in the last-mile pipeline, calculates the commercial cost of delivery exceptions, and dictates corrective dispatch protocols.

Method

  1. Cross-reference {{on_time_in_full_data}} against {{sla_target_thresholds}} to establish precise on-time and in-full variance curves across {{distribution_hub_network}}.
  2. Segment fulfillment failures by tier: sorting delay, late dispatch, in-transit dwell, customer absence, and failed access.
  3. Audit {{carrier_performance_logs}} to isolate 3PL partner discrepancies versus captive fleet execution metrics.
  4. Correlate recurring route-level delays with micro-logistics challenges documented in {{congestion_bottlenecks}}.
  5. Compute total financial leakage using {{cost_per_failed_drop}} across secondary delivery attempts and reverse logistics handling.
  6. Assess time-of-day dispatch wave configurations to find dock bottlenecks contributing to late departures.
  7. Produce carrier scorecards and actionable dynamic routing adjustments to eliminate repeat exceptions.

Constraints

  • MUST categorize SLA misses into carrier-controllable versus external infrastructure constraints.
  • MUST NOT treat all fulfillment hubs homogeneously; node-specific differences must be highlighted.
  • Calculations for total financial impact MUST explicitly incorporate {{cost_per_failed_drop}}.
  • Must provide actionable remediation for the bottom 20% underperforming delivery zones.

Output format

Provide the audit report structured under these exact section headers:

  1. Network Fulfillment Executive Briefing (max 300 words)
  2. Node & Hub SLA Performance Matrix (table comparing actual OTIF vs {{sla_target_thresholds}})
  3. Carrier Reliability & Exception Decomposition (granular analysis of {{carrier_performance_logs}})
  4. Financial Impact Analysis (detailed cost breakdown of failed drops and redeliveries)
  5. Network Remediation Protocols (5 concrete operational changes with impact horizons)

Self-review

  • Ensure carrier-specific shortfalls are differentiated from hub sorting bottlenecks.
  • Verify that the mathematical impact of {{cost_per_failed_drop}} is fully articulated across all failure classes.
  • Check that each recommended protocol has an assigned node or carrier owner.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

data-analytics
data-reporting
transport-logistics
last-mile
sla-reporting
logistics-audit