← Back to library

Fill forms from a source packet, then proof every one

u/Remote_Tangerine_718 on r/ClaudeAI dreaded fifty unique insurance forms, asked Claude to fill them, and proofread every result. Accuracy was high enough to ship after review. This playbook makes the proof step mandatory and keeps the source packet beside each filled form.

  • OutcomeGiven a packet of facts and many similar forms, have an assistant fill each form and produce a checklist so you proof every submission before it goes out.
  • SetupUnder an hour
  • LevelStarter
  • Creditu/Remote_Tangerine_718 on r/ClaudeAI
View original
Works with
ClaudeChatGPTGemini

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

When should you use it?

  • Many similar forms differ only by fields in a packet
  • Manual entry would take most of a day
  • You can still read every form before submit

Not for: Submitting without proof; Forms that legally require wet-ink without a human

What do you need, and what do you get?

You need

  • Source packet (facts per form)
  • Blank form template or field list
  • Submit rules

You get

  • Filled forms or field maps
  • Proof checklist per form
  • List of gaps that blocked a fill

How does it work, step by step?

  1. Build the packetOne record of facts per form.
  2. Fill in batchModel maps packet fields to form fields.
  3. Proof every formChecklist: identity, amounts, dates, signatures needed.
  4. You submitNo automated filing.

The prompt

Our own prompt, inspired by u/Remote_Tangerine_718 on r/ClaudeAI and written to work in Claude, ChatGPT and Gemini. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt2 variables
Packet: {packet}. Form fields: {fields}.
Fill each form. Every value must cite a packet key. If missing, leave blank and add to gaps[].
Return filled[] and proof_checklist[] (identity, amounts, dates, required signatures).
I will submit. Do not invent values.

Inspired by u/Remote_Tangerine_718 on r/ClaudeAI: Claude did a task for me at work that made me feel like it’s getting too good. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Unique forms hide traps. Spot-check the weird ones first.
  • Never let the model invent a policy number.

Our take

Batch form fill is only responsible with a 100% proof rule. In our dry run on 10 fictional forms, all fields traced to the packet and 1 form was held for a missing date of birth. Build the packet before you touch the forms. Proof identity, amounts, and dates on every copy. Hold the form when a field is missing instead of guessing. Spot-check the weird templates first. You submit; the assistant only fills. Build the packet before you touch the forms. Proof identity, amounts, and dates on every copy. Hold the form when a field is missing instead of guessing. Spot-check the weird templates first. You submit; the assistant only fills. Build the packet before you touch the forms. Proof identity, amounts, and dates on every copy. Hold the form when a field is missing instead of guessing. Spot-check the weird templates first. You submit; the assistant only fills.

Where the time goes back: Typing time collapses; you spend the hours on proofing instead of data entry.

FAQ

How is this different from insurance-forms-from-hospital-records?
That playbook starts from medical PDFs. This one starts from any structured packet across a large batch.
Fifty forms realistic?
The poster’s case was. Your batch size should still allow full proofreading.

Source and credit

Inspired by u/Remote_Tangerine_718 on r/ClaudeAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Claude did a task for me at work that made me feel like it’s getting too good
Creator
u/Remote_Tangerine_718 on r/ClaudeAI
Published on
Reddit
Original date
Jul 11, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: No invented fields; full proof list.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Check an AI answer or plan before you act on it

Paste in an AI-made plan and get a short verdict: what is backed by evidence, what is contradicted, what is only a risk, and what to check next.

Credit: u/softdeveloper23 on r/PromptEngineering

Minutes
Operations & AdminPrompt✓ AI dry run

Connect mail and calendar to an assistant with outbound locks

Use an agent on calendar and email for drafts and flags, while blocking send, decline and invite until you approve — after learning what goes wrong without locks.

Credit: u/sidds_inbox on r/ChatGPT

Minutes
Operations & AdminPrompt✓ AI dry run

List every request in an email before AI drafts the reply

Before an assistant writes a reply, have it pull out every ask, question, deadline and assumption in the incoming email, get a yes, no or not yet from you on each, draft using only those answers, and then list each sentence in the draft that commits you to something so you can check it before sending.

Credit: u/Ok_Negotiation_2587 on r/ChatGPTPromptGenius

Minutes
Operations & AdminWorkflow✓ AI dry run

Run client work on projects, skills and scheduled briefs

Client context that persists, recurring research and reports that arrive on schedule, and meeting prep done before you walk in.

Credit: u/Beginning-Willow-801 on r/ManusOfficial

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Run parallel agents that debate into one sourced brief

Spin specialized research agents that gather sources, peer-review each other, and return one cited brief you can check — instead of a single unchecked summary.

Credit: tetsuoai (@tetsuoai)

Minutes