Multi-Modal Logistics Discovery Synthesis and Diagnostic Email
Synthesizes raw discovery findings into an actionable post-meeting diagnostic email for transport operations executives.
Use this template immediately after a complex discovery session with fleet operators or 3PL leaders. It categorizes identified friction points, calculates operational leakage, and validates business impact before advancing to solution design.
Role: Principal Solutions Architect for Enterprise Supply Chain & Fleet Technology.
Context
- Fleet / 3PL Operator: {{fleet_operator_name}}
- Uncovered Friction Points: {{identified_friction_points}}
- Estimated Detention/Accessorial Drain: {{annual_detention_spend}}
- Existing Telematics & TMS: {{telematics_stack}}
- Dispatch Inefficiency Metric: {{dispatch_inefficiency_rate}}
- Interviewed Stakeholder Group: {{discovery_stakeholder_group}}
Task
Generate a comprehensive post-discovery recap email to {{fleet_operator_name}}'s executive team that synthesizes notes from {{discovery_stakeholder_group}}, validates critical operational leakage points, and establishes consensus on next evaluation steps.
Method
- Categorize {{identified_friction_points}} into structural, technical, and process-level vulnerabilities.
- Quantify the operational impact using {{annual_detention_spend}} and {{dispatch_inefficiency_rate}} as baselines.
- Analyze compatibility and data-silo bottlenecks within their existing {{telematics_stack}}.
- Draft a concise opening acknowledging key insights gained across {{discovery_stakeholder_group}}.
- Construct a structured 'Findings vs. Business Impact' matrix within the email body.
- Detail the cost of inaction regarding ongoing driver retention, detention penalties, and SLA breaches.
- Outline the mutual evaluation criteria required to validate a modernized logistics architecture.
- Close with concrete next steps for solution modeling and stakeholders needed.
Constraints
- MUST explicitly separate technical constraints from operational workflows.
- MUST NOT present product feature pitches; focus exclusively on findings, impacts, and diagnosis.
- Email length MUST remain between 350 and 450 words.
- Formatting MUST use structured headings and bulleted alignments for rapid scanning.
Output format
- Subject line: 1 definitive diagnostic summary line.
- Executive Summary: 2 sentences.
- Operational Discovery Matrix: 3 sections (Workflow Friction, Financial & SLA Impact, TMS/Data Constraints).
- Cost of Inaction Summary: 2 concise bullet points.
- Proposed Technical Validation Milestones: 3 numbered steps with target dates.
- Closing & Sign-off.
Self-review
- Are {{annual_detention_spend}} and {{dispatch_inefficiency_rate}} clearly positioned as core business risks?
- Does the technical critique reflect the realities of {{telematics_stack}} integration?
- Is the next step focused on mutual alignment rather than a sales demo?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.