LOADING THE ACADEMY ▮
// FOR THE VETS · lesson 3

The System Prompt That Turns a Chatbot Into a Rater

The Veteran's AI Playbook: Run Your Own VA ClaimFree preview
Text lesson. No video on this one — the words carry it.

You built the workspace last lesson. The instructions field is still empty, so what you've got is a general-purpose chatbot that happens to have read your file. Ask it about your back pain and it shrugs, tells you to see a doctor, wishes you luck. That's not what you came for.

The fix is one block of text. You paste it once into the instructions field, fill in the brackets that are yours, and from that second on every conversation inside the workspace inherits a role, a priority stack, and a set of standing orders. Same machine. New job. What separates a bot that knows some VA regulation from a strategist that never loses the plan is the prompt below, and installing it costs you about fifteen minutes.

This is education, not legal advice. Verify every regulation the AI cites against the actual text before you act on it. Now we give the intern a job description.

What a system prompt actually does

A system prompt is the set of instructions the AI carries into every conversation in the workspace. It fixes four things: the role it plays, the priorities it holds, the rules it follows, and how it talks to you. You write it once. It rides along on every question you ever ask in there, automatically.

Without one, you wrestle corporate hedging on every question. You ask something sharp and back comes something soft, padded with disclaimers and "consult a professional" on a loop. The prompt strangles that up front. It tells the machine to be direct, to show its math, to flag the stakes before a high-consequence answer, and to quit caveating every single response.

It also nails down the plan. The chatbot's memory of what you're after evaporates every conversation. The system prompt doesn't. It's the one document that says, every time, here is who you are and here is what we're driving toward.

The role and the veteran context block

The first line establishes who the AI is. Paste this exactly:

"You are a VA disability claims strategist and research assistant helping a veteran navigate toward 100% combined rating and maximize all available benefits. You are not a VSO, attorney, or accredited claims agent."

That second sentence carries as much weight as the first. It sets the role and the limit in the same breath, which keeps the machine honest about where its job ends and a professional's begins.

Then comes the part that makes the thing yours: the Veteran Context block. This is a bracketed section you fill with the facts of your situation. Current combined rating and the conditions that make it up. Marital status and dependents. State of residence. Employment status and annual income. Service branch, dates, MOS. Deployment locations and dates. Known exposures. Pending claims. And your Intent to File status, expiration date included if one is ticking.

Load all of it. Every field you fill is a thing you never explain twice. The thinner this block, the more your analyst makes you repeat yourself. The fatter it gets, the faster every conversation reaches the actual work.

The priority stack

Right under the role, you tell the AI what it's driving toward, in order. The order is the strategy.

  1. 100% schedular rating, via VA combined rating math.
  2. TDIU as the parallel path if schedular 100% is not mathematically reachable.
  3. Permanent and Total designation.
  4. SMC screening at every stage.
  5. Full federal, state, and local benefits optimization.

That stack earns its keep. It tells the machine to chase the combined-rating math first while keeping TDIU running as a second track the whole time, never as a consolation prize. It tells the machine to screen for Special Monthly Compensation at every rating change, because SMC is money most vets never get told about. And it puts state and local benefits on the board so the AI knows your file doesn't close at the federal letter.

The operating rules

This is the long section, the one that drags a polite chatbot down into the trenches with you. It's a list of standing orders. A few are load-bearing enough to call out.

Communication: be direct and specific, no cheerleading, no filler, no motivational padding. When a question crosses into territory that needs an accredited attorney, VSO, or medical professional, say so once and move on. Flag the stakes before answering anything where a wrong answer costs you, like filing strategy, effective dates, or appeal deadlines.

VA math: always calculate using the combined rating formula under 38 CFR 4.25, never straight addition. Keep a running tracker. Apply the bilateral factor, the 10% bonus before combining, on paired-extremity conditions. And show the work, not just the result, so you can check it.

Condition strategy: build a Condition Strategy Map, sorted into Currently Rated, Increase Targets, New Claims, Secondary Claims, and Presumptive Claims. That map is the next lesson, and it's the central planning document for your whole claim. For each condition, cite the specific diagnostic code and the 38 CFR rating criteria. Flag reduction risks before recommending any filing. Note protection status for conditions rated 5+ years (partial) or 20+ years (essentially protected).

Effective dates: ask about Intent to File status early in any major filing discussion, and calculate estimated retroactive back pay when it matters. This is what protects the front edge of your effective date, and it's a thread we pull hard later.

The rules also cover TDIU evaluation, SMC screening, C&P exam prep, decision-letter analysis, and evidence strategy. Each gets its own block of standing orders so the AI knows what to do the moment one of those situations shows up, without you having to teach it from scratch every time.

Then the rule that outranks all the others: verification. When the AI cites 38 CFR or M21-1, it quotes the specific regulation text and hands you the section reference. When it's unsure about a current regulation, it says so out loud and tells you to check against ecfr.gov or the live M21-1. And it does not invent citations. This is your hedge against the one thing this tool reliably gets wrong. It's a brilliant intern with a reading addiction, and left unsupervised it will pass you a confident, wrong regulation number with a straight face. The verification rule is the leash.

Last piece is the disclaimer block, and the instruction on it is specific: internalize this, do not repeat it. This is education, not legal advice. When a question crosses into territory requiring an accredited attorney, VSO, or medical professional, say so once and move on. The veteran understands the limitations and accepts responsibility for all filing decisions. That last sentence is you, on the record, owning every choice about your own file.

Customizing it to you

Most of the prompt is identical for every veteran. Role, priority stack, operating rules: paste those verbatim. They work the same for everyone holding a claim.

The bracketed Veteran Context block is the only part that's yours, and it's where this stops being a generic template and becomes your analyst. State of residence drives the entire state-benefit analysis down the road. Employment status and annual income drive TDIU. Service dates and exposures decide which presumptive doors are even open to you. None of that lives anywhere but in the block you fill.

So fill it heavy. Every fact you load is a fact the machine already holds the next time you open a conversation, which means you spend your questions on strategy instead of retyping your service history into the box for the ninth time.

Same question, different tool

The whole argument fits in one before-and-after.

Ask a generic chatbot "can I get a higher rating for my back pain" and you get mush. See a doctor. File a claim. Good luck. Nothing you can act on.

Ask the same machine, now carrying this system prompt and your documents, that exact question, and the answer changes shape entirely. It pulls your current rating under 38 CFR 4.71a, diagnostic code 5237 or 5243. It lays out the thresholds for 10, 20, 40, 50, and 100 percent. It tells you which threshold your symptoms map to based on what's actually sitting in your records. It tells you what evidence you'd need to push the increase through. It flags whether filing for an increase might drag your other conditions back under review, a reduction risk you want in front of you before you file, not after. And if your ITF is active, it runs you a retroactive back-pay estimate.

Same question. Different tool. The prompt and the documents are the whole difference. And every threshold it just handed you is a thing you go verify against the live regulation before it becomes a thing you file.

Mark this one complete. The prompt is installed and the analyst is awake. Next we put it on the math, and you find out what your combined rating actually is versus what you thought it was.

COURSE CHAT · THE VETERAN'S AI PLAYBOOK: RUN YOUR OWN VA CLAIMlive
Loading the room…
Open full search ↵esc closes · ↑↓ move · ↵ opens