What belongs in the vault
Save accomplishments with enough detail to reuse: project context, your role, actions, metrics, stakeholders, decisions, feedback, and final outcome. The vault should include both polished statements and source notes, because final writing is stronger when it can trace back to real evidence.
- Add labels for skill themes like leadership, process, customer, analysis, training, and military transition.
- Keep source notes with the polished version so you do not lose context.
How search changes the workflow
When your accomplishments are searchable, you do not have to remember every project from scratch. You can search for "leadership," "metrics," "customer," "federal," or a target role and quickly find proof that matches the document or question in front of you.
- Tag stories by both skill and output: resume, review, interview, promotion, award, cover letter.
- Add job-posting keywords only when they honestly match the work you did.
Why grading belongs before reuse
A weak story gets weaker when reused in five places. Scoring before reuse helps you improve the source material once, then deploy the stronger version everywhere. The 0-10 rubric looks for missing specificity, unclear ownership, weak outcomes, and vague language.
- Improve the vault statement first; then adapt it to each output.
- Review low-scoring stories before using them in high-stakes documents.