Launch Policy Upload Modernization

Project Context

Amerisure is replacing a legacy document intake flow in the Amerisure Agency Portal with a new policy submission and loss-run upload experience used by independent agents. The goal is to reduce submission errors, speed up underwriting intake, and retire a brittle service before peak renewal season. You are the Engineering Manager leading delivery for a 10-person cross-functional team, and the business has committed to launching before the next quarterly agency enablement release in 14 weeks.

Key Stakeholders

The VP of Underwriting wants the full workflow shipped on time because intake delays are affecting quote turnaround. The Director of Agency Distribution wants no disruption for top agencies during renewal season. The Security and Compliance lead will not approve launch without audit logging and retention controls. The Product Manager is pushing for all planned features, while the Platform team has warned that one shared API dependency may slip by up to 2 weeks.

Constraints

• Timeline: 14 weeks to production launch
• Team: 6 engineers, 1 QA engineer, 1 designer, 1 product manager, 1 engineering manager
• Budget: $180,000 remaining; no additional headcount approved
• Dependency: Shared document metadata API from Platform due by end of Week 6
• Quality bar: Must keep upload failure rate below 1.5% and avoid Sev1 incidents in the first 30 days
• Scope includes agent upload UI, validation rules, underwriting queue integration, audit logs, and migration for 25 pilot agencies

Complications

1. Two senior engineers are each allocated 20% to production support for legacy intake services.
2. A top-10 agency has already been promised early access in Week 11, three weeks before general availability.
3. Security review uncovered a new requirement for document access logging that was not in the original plan.

Deliverables

1. Create a 14-week execution plan with phases, milestones, and dependency management.
2. Explain how you would protect delivery dates without lowering quality standards.
3. Propose scope trade-offs for the Week 11 pilot and Week 14 GA launch.
4. Define launch readiness criteria, rollback triggers, and post-launch monitoring.
5. Identify the top risks, stakeholder conflicts, and how you would manage escalations.