WIN A&P — ED clarifications (Michelle Vest)¶
Source: Email reply from Michelle Vest (ED, Warriors In Need) to Ryan Curry on Candidate Progress Bridge questions.
Screenshot: ed-email-progress-bridge-clarifications.png
Also see: Scrubbed status enum + columns in WIN_Candidate_Progress_Bridge_structure.csv (no candidate rows); blank consent in Candidate Consent Fillable.md; AvTech checklist in AvTech Certification Pathway Checklist.md. Builder import: pipeline-template-win14.csv.
Answers below are operational truth for the builder. B0 captures structure (phases + named outputs). Email / upload / Adobe e-sign / third-party attestors land in B1–B3.
1. FAA documents (what the veteran actually gets)¶
| Step | What happens | Artifact |
|---|---|---|
| After Intro Zoom | WIN emails asking for documents, including a completed but unsigned 8610-2 | Upload request (unsigned pack) |
| After FAA appointment | Veteran receives 8610-2 signed by FAA + veteran (ID verification) | Upload: signed 8610-2 |
| AvTech enrollment gate | Signed 8610-2 required; WIN sponsorship generally if ≤ 6 months EAS | Org gate, not veteran upload |
| After O&P / DME | Final DME sign-off → FAA Certification physical document | Upload: FAA cert |
2. Who confirms AvTech / testing¶
- WIN decides who attends AvTech under WIN sponsorship (generally based on EAS).
- AvTech runs on-site testing and coordinates DME scheduling.
- Platform does not need AvTech as a login attestor in B0; WIN org attestation + veteran uploads are enough for the skeleton.
3. Outreach / triggers (RecruitCRM today → platform later)¶
| Trigger | Action | Platform note (later gates) |
|---|---|---|
| Intro Zoom follow-up | Email: request FAA docs + resume | Outgoing email → triggers upload |
| FAA docs & resume review | Email: schedule FAA + resume tips; Candidate Agreement via Adobe e-sign | Outgoing email + e-sign |
| Follow-up | Remind FAA schedule + agreement status | Follow-up email |
| AvTech scheduling & COOL/VA funding | Email with instructions / link | Outgoing email + link |
| Manual Q&A | Back-and-forth (often funding/invoices) | Possible AvTech invoice upload |
| After DME | FAA Certification certificate | Upload |
4. Employer visibility¶
- Opt-in is the Candidate Agreement (e-sign). Sample =
Candidate Consent Fillable.md(blank). - Today: employers only see candidates when WIN forwards resumes to a POC.
- Target: hiring partners log in and see opted-in candidates (B4+), not B0.
Builder map (Excel 14 + ED answers)¶
Phases = Excel Current Status enum. Outputs = milestones / docs / check-ins. Keep seeded Job placement verified as the sole outcome on Hired.
| # | Phase | Outputs to add in B0 (name only) | Evidence first | Later (B1–B3) |
|---|---|---|---|---|
| 01 | Intake / Zoom | Intro Zoom complete | org | — |
| 02 | Documents | FAA docs pack uploaded (incl. unsigned 8610-2); Resume uploaded; Candidate Agreement signed | veteran / veteran / veteran | email trigger; Adobe e-sign |
| 03 | 8610-2 Review | Docs & resume reviewed; FAA schedule instructions sent | org | follow-up email |
| 04 | FAA Sign-Off | Signed 8610-2 uploaded | veteran | upload |
| 05 | Funding | AvTech / COOL / VA funding instructions sent; AvTech invoice uploaded (optional) | org / veteran | email + link; invoice upload |
| 06 | AvTech / Prep | AvTech prep complete (WIN-sponsored path) | org | — |
| 07 | Testing | Written exams complete; O&P / DME complete | veteran | — |
| 08 | A&P Certified | FAA Certification uploaded | veteran | upload |
| 09 | Resume | Resume ready (post-cert polish) | veteran | — |
| 10 | Employer Ready | Employer-ready (opt-in already via agreement) | org | — |
| 11 | Employer Introductions | Employer intro made; Tools issued (if used) | org | hiring-partner visibility later |
| 12 | Hired | (do not add output) keep Job placement verified outcome | — | three-party close already modeled |
| 13 | Alternative / OJT | OJT / alternate path noted | org | — |
| 14 | On Hold | leave empty or single “On hold” marker | org | — |
Rename seed phase¶
Employment adopt seeds a phase named Placement. Rename it to Hired (or delete after moving the outcome… outcome is tied to Placement slug from template; safest: rename Placement → Hired and put employer-facing work in phases 09–11).
Do not reintroduce live rosters¶
Do not commit WIN’s live Progress Bridge workbook (candidate names, MOS, dates, employer notes). Keep ops data local. Structure-only export: WIN_Candidate_Progress_Bridge_structure.csv.