Product R&D · Acquisition workflow
Keep task-order packages moving in one place.
Torpedo is an in-development foundation for assembling, routing, tracking, and administering Task Order Request Packages across a configured IDIQ workflow.
Torpedo is an in-development web application for replacing manual Word/Excel template assembly, email-based routing, status spreadsheets, and disconnected legacy workflows across the TORP lifecycle, from requirements gathering through document generation, review, approval routing, and post-award management.
What needs fixing
Contracting Officer's Representatives (CORs), technical counterparts, and acquisition support personnel often work across disconnected Word documents, Excel sheets, email chains, and legacy systems. That creates duplicate entry, delay, and limited status visibility. Torpedo records package cycle time and post-award workflow performance so each engagement can define and assess realistic targets.
What Torpedo Is Being Built to Do
Package Assembly
Data entered once, populated across all related documents. Web forms replace manual template filling. Output generation is configured for the agency's approved .docx, .xlsx, and PDF templates, with document fidelity verified during acceptance.
Routing & Approval
Electronic routing replaces email chains and provides configured review, comment, and approval workflows. The system records every approval in a complete audit trail.
Status Dashboard
A single dashboard shows all TORPs and their current stage, eliminating separate email searches and spreadsheet updates. The design target is 100+ concurrent packages; an engagement would verify that target with load testing in the customer environment.
Post-Award Management
Teams can configure ad hoc deliverables or use standardized templates for monthly status, financials, manpower, travel, overtime or excess hours, ODC approvals, resumes, training, and GFE requests. Awardees submit directly into the system, with due dates established from the start. Authorized users can review and authorize invoices, then track obligations, expenditures, and remaining balances in one place.
- Word templates filled manually
- Data re-entered across spreadsheets
- Routing via email chains
- Status tracked in yet another spreadsheet
- Some packages take months; measure the actual baseline
- Approved fields populate configured templates
- Electronic routing with audit trail
- Real-time status dashboard
- Awardees submit deliverables directly
- Cycle-time target measured in the engagement
Current design
The current design target is PostgreSQL-first, with a Go service, SolidJS frontend, and Connect RPC API. Deployment topology, approved dependencies, backup and recovery, and disconnected-operation needs would be configured for the customer environment. Section 508 conformance would be verified at acceptance.
Role-based access for Technical POCs, Acquisition Support, CORs/COTRs, and Contracting Officers. OAuth for initial deployment, PIV/CAC authentication planned for production government network deployment.
A practical first increment
Start with an agreed package type, template set, roles, approval path, security and identity boundary, deployment environment, and export format. Acceptance can test document fidelity, routing and audit history, permissions, cycle time, and Section 508 and accessibility behavior. Agency data, generated packages, configuration, training material, and operating documentation form the handoff package.