Reasoning & math
AuraScore 81/100

Port Drayage Demurrage and Gate Delay Impact Analysis

Quantify terminal dwell costs, demurrage risks, and chassis delays to calculate true container detention liabilities.

Apply this template when reconciling container terminal delays against maritime billing rates and carrier detention penalty clauses. It helps intermodal operators pinpoint billing discrepancies and reduce avoidable accessorial charges.

Template

Role: Intermodal Logistics Financial Analyst & Freight Audit Specialist

Context

  • Cargo Scope: Auditing billing and turnaround performance for {{container_volume}}.
  • Terminal Grace Period: Standard operating baseline set at {{free_time_allowance}}.
  • Penalty Structure: Accruing accessorial costs under {{per_diem_rate_schedule}}.
  • Yard Congestion: Driver turn times impacted by {{average_gate_dwell_hours}}.
  • Equipment Dislocation: Secondary transit legs dictated by {{chassis_split_frequency}}.
  • Driver Billing Terms: Labor delay thresholds established in {{carrier_contract_terms}}.

Task

Produce an intermodal drayage dwell cost reconciliation report that quantifies terminal demurrage liabilities, models driver gate delay expenses, and isolates root-cause turnaround inefficiencies.

Method

  1. Establish the baseline dwell timeline from container discharge to final gate exit across {{container_volume}}.
  2. Subtract {{free_time_allowance}} from measured dwell days to isolate total chargeable penalty days.
  3. Apply tiered pricing from {{per_diem_rate_schedule}} to calculate gross terminal demurrage exposure.
  4. Calculate driver waiting cost by comparing {{average_gate_dwell_hours}} against driver detention thresholds in {{carrier_contract_terms}}.
  5. Compute additional transit hours and equipment rental penalties caused by {{chassis_split_frequency}}.
  6. Aggregate carrier detention charges, terminal demurrage, and chassis repositioning surcharges into total accessorial cost.
  7. Calculate cost per container and identify the top operational bottlenecks driving billable overrun.
  8. Formulate tactical mitigation actions to minimize gate turn delays and reclaim disputed penalty fees.

Constraints

  • Calculations MUST separate terminal demurrage from equipment detention into distinct line items.
  • The model MUST NOT include driver detention costs for gate dwell under the contractual threshold in {{carrier_contract_terms}}.
  • Financial figures must be presented with exact currency unit formatting.
  • Disputed dwell days caused by documented terminal closures must be noted separately.

Output format

Produce a 4-part financial reconciliation report:

  1. Audit Summary: Exactly 1 paragraph summarizing total exposure, container count, and average cost per container.
  2. Cost Attribution Matrix: A markdown table containing Cost Category, Calculated Chargeable Units, Contract Rate, and Total Financial Exposure.
  3. Turnaround Friction Breakdown: A numbered list of 3 root causes explaining operational delays (e.g., chassis availability, gate queuing, free-time expiration).
  4. Mitigation & Dispute Strategy: 4 actionable recommendations for disputing erroneous invoices and improving container retrieval speed.

Self-review

  • Verify that demurrage fees strictly accrue only on days exceeding {{free_time_allowance}}.
  • Confirm that driver waiting charges only apply to hours exceeding the contract threshold.
  • Validate that all math in the cost matrix sums accurately to the stated total exposure.
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.

research-analysis
research-reasoning-math
transport-logistics
drayage
intermodal
demurrage-cost