--- name: evidence-tracker description: Use when the user is building a case against a list of criteria (a work visa petition, a grant, an award, a promotion case, a professional designation) and asks what they have, what is missing, or what to do next. Maps documented evidence to each official criterion, rates it Strong, Building, or Not started, and lists the next actions with owners and dates. metadata: id: evidence-tracker version: "1.0.0" author: BotPlaza --- # Evidence Tracker > Not legal advice. These bots brainstorm and draft; a licensed lawyer must review anything before it is filed or sent. ## What it does Shows where a criteria-based case really stands. It pulls the official criteria, matches each one to evidence that actually exists (not plans or drafts), rates every criterion honestly, and turns the gaps into a short list of next actions with deadlines. It's useful for anyone assembling a petition, a nomination, or an application judged against a checklist. ## When to use - "How strong is my case right now?", "which criteria am I closest to?", "what should I focus on this month?", "update the tracker, I got the new reference letter". - Not for predicting whether the case will be approved. ## Requires Web access to the official criteria page (for example the government agency's page for that visa or program). A place where the evidence list lives: a spreadsheet, a notes app, a folder, or a list the user pastes in. ## Schedule Default: monthly on the 1st at 9:00 AM, plus on demand when new evidence arrives. ## Inputs | Setting | Default | Notes | |---|---|---| | `program` | required | For example a work visa category, a fellowship, or a grant. | | `criteria_source` | official page | Always the issuer's own page, checked live. | | `evidence_location` | ask | A sheet, folder, or pasted list. | | `target_date` | none | The planned filing or submission date. | | `owners` | the user | Optional names for who handles each action (a person or another bot). | ## Steps 1. **Criteria.** Open the official page and list the criteria exactly as written, with the date checked. 2. **Evidence.** For each criterion, list the evidence that exists, with document names or links: letters, publications, awards, contracts, press coverage, peer-review roles. 3. **Rate.** Mark each criterion: - *Strong*: documented evidence that clearly fits; - *Building*: some evidence, or work in progress (submitted, accepted, or scheduled); - *Not started*. Drafts, applications, and intentions are never Strong. 4. **Gaps.** For each Building or Not started criterion, list what would move it up, such as an independent article, a letter from a recognized expert, or a peer-review role. 5. **Actions.** Turn the gaps into dated actions with an owner. Put the ones due within 30 days first. 6. **Summary.** Lead with the three biggest gaps, the three next actions, and the count of criteria at each rating. ## Output format ```markdown # Evidence tracker · {program} · {date} *Criteria checked on {official source} on {date}. Not legal advice. These bots brainstorm and draft; a licensed lawyer must review anything before it is filed or sent.* ## At a glance Strong: {n} · Building: {n} · Not started: {n} · Target date: {date} ## Biggest gaps 1. {Gap} ## Next actions | Action | Criterion | Owner | Due | |---|---|---|---| ## By criterion ### {Criterion as officially worded} **Rating:** {Strong/Building/Not started} - Evidence: {document}, {date} - To strengthen: {what} ``` ## Edge cases - **The official criteria changed:** show what changed and re-rate the affected rows. - **Evidence that fits two criteria:** list it under both and note it. - **The user asks "will I get approved?":** say that only an adjudicator decides, then point to the weakest criteria and to their lawyer. - **Missing documents:** an item without a document stays Building until the document exists. ## Boundaries - Never predict approval or state a legal conclusion. Mark interpretations "for your lawyer to confirm". - Never invent or embellish evidence. Count only documents that exist. - Read-only on the user's files unless they ask you to update the tracker.