Evidence
Capture concrete artifacts that prove your contributions.
Every piece of evidence must answer: "What changed because of this?" This prevents weak artifacts like "I attended meetings" or "I reviewed PRs". Instead, focus on impact: "Reduced latency by 40%" or "Mentored 3 engineers who got promoted".
Design Doc
Technical design documents, architecture proposals, RFCs
PR/Code
Significant pull requests, code contributions, technical implementations
Metrics
Dashboards, data showing impact, before/after comparisons
Feedback
Manager feedback, peer reviews, performance reviews
Meeting Notes
Decision documents, meeting outcomes where you led discussions
Other
Presentations, external talks, blog posts, documentation
Be honest about your role
You drove it
You were the primary owner, made key decisions, accountable for outcomes
Shared ownership
You were one of multiple leads, shared decision-making
Significant contribution
You made meaningful contributions but weren't the owner
Consulted/informed
You provided input or were kept in the loop
You can import work documents (design docs, feedback, etc.) to extract evidence. The system uses your chosen processing mode:
1. Paste or Upload
Paste document content or upload a file (.txt, .md, .pdf)
2. AI Extraction
AI extracts impact summary, metrics, scope, and suggested criteria. Sensitive details are sanitized.
3. Review & Edit
Review the extraction, edit as needed, then save as evidence
When you add evidence, AI can suggest which rubric criteria it supports. You'll see confidence scores for each suggestion. Always review and confirm - the AI is a helper, not the final word.
When adding evidence, you can include a link to the source document (Google Doc, Notion page, Confluence, etc.). These links are included in your exported promo packet for easy reference.
How It Works
Use the "Document Link or Notes" field to paste a URL to your source document. URLs starting with http:// or https:// are automatically formatted as clickable links in the export.
Note: We don't access these documents - they're just included as references. Make sure reviewers have access to the linked documents when you share your packet.