Municipal Portal Stress Test Remediation Advisory
Brief municipal IT leaders on load testing bottlenecks and required infrastructure fixes.
Use this template when performance and load testing identify critical failure points in public civic infrastructure. It turns load runner metrics into an urgent engineering and leadership email advisory.
Role: Senior Public Sector Performance and Reliability Test Architect.
Context
- Municipality / Local Government: {{municipality_name}}
- Civic Portal Service: {{portal_service}}
- Target Concurrency Threshold: {{peak_concurrency_target}}
- Measured Failure Points: {{observed_bottlenecks}}
- Security / Vulnerability Findings: {{security_findings}}
- Scheduled Launch Window: {{deployment_window}}
Task
Author a comprehensive technical advisory email to the municipal Chief Information Officer and lead infrastructure engineers detailing stress testing failures on {{portal_service}}, demonstrating capacity risks under civic surge loads, and mandating technical fixes before {{deployment_window}}.
Method
- Contrast actual throughput and latency figures against the mandated {{peak_concurrency_target}}.
- Dissect {{observed_bottlenecks}} across database connection pools, caching layers, and external civic API dependencies.
- Analyze how {{security_findings}} interact with performance under heavy load conditions (e.g., resource starvation).
- Calculate citizen service degradation risks (e.g., payment failure rates, dropped public assistance applications).
- Specify concrete infrastructure, architectural, and query optimization steps for the engineering team.
- Propose a structured re-testing schedule that concludes safely before {{deployment_window}}.
- Define quantitative performance exit criteria required for final deployment authorization.
Constraints
- MUST quantify latency (e.g., p95, p99) and error rates relative to civic peak traffic.
- MUST NOT recommend infrastructure scaling without first addressing underlying query/code bottlenecks.
- MUST define clear ownership for infrastructure versus application development teams.
- Tone MUST be urgent, technically rigorous, and risk-managed.
Output format
- Email Subject line with severity tag
- Context & Executive Brief (max 75 words)
- Load Testing Results vs {{peak_concurrency_target}} (Key Metrics Table)
- Root Cause Breakdown: {{observed_bottlenecks}} & {{security_findings}}
- Mandatory Pre-Launch Action Matrix (Owner, Action, SLA)
Self-review
- Does the advisory directly compare actual performance against {{peak_concurrency_target}}?
- Are architectural recommendations distinct from temporary horizontal scaling?
- Is the timeline achievable prior to {{deployment_window}}?
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.