How to Write a Form Error That Names the Missing Field

Anyone shipping a form can write form error copy in 10 minutes that names the missing field, says what is wrong, and gives one fix. Run it in ChatGPT, Claude, or Gemini before "Invalid input" trains people to guess which box failed.

Form error copy is a label for a fail, not a joke. If the banner says oops, you wrote a 404. If it sells the product, you wrote a hero.

Do not write this error like empty-state copy when the table is empty. An empty table is zero rows and one create action. This screen already has a form. Do not write it like 404 copy that sends people onward. A 404 is the wrong URL. This is the right URL with a blank required field. It is not cookie banner copy that names the cookies. A banner names categories. An error names one field. Save the three-line shape as a skill prompt you can rerun.

Write form error copy that names the missing field

1. Paste the real field labels. Do not draft oops

Instruct ChatGPT, Claude, or Gemini: "Do not draft a joke. Do not draft a hero. Name the field labels I paste. If I did not paste labels, write UNKNOWN and stop. No oops. No something went wrong. No please check your details."

Paste the labels as they appear on the form. "Email" is a label. "Work email" is a different label. "Invalid" is not a label.

Banned: oops, uh-oh, something went wrong, invalid input, please check your details, there was a problem, try again, we could not process, hmm, whoops, looks like, please fill out this field with no field name.

If a field is not on the form, write UNKNOWN. Do not invent "Company Slack." Invented labels are how people hunt.

2. The error names the field, then the fault

Send the label back. Instruct: "Line one is the field label verbatim, plus the fault in five words or fewer: is missing, is too short, needs an @ and a domain, does not match. Do not pun. Do not open on sorry."

Good: "Work email is missing." Bad: "Invalid input." Invalid is a stack trace.

Good: "Work email needs an @ and a domain." Bad: "Please enter a valid email address." Valid is a lecture. The label already said email. Name the fault.

Good: "Start date is missing." Bad: "Looks like something is missing." Something is a treasure hunt.

If two fields failed, write two errors, each next to its field. A single banner that lists four nouns is a lecture at the top of the page. People fix the first noun and miss the rest.

Use the same words as the label. If the form says "Work email," do not switch to "corporate inbox" to sound human. Human is the label they already read.

3. One next action. One. Not a help center

Instruct: "Line two is one next action the user can do in that field: add your work email, pick a start date, use 8 or more characters. If I named no fix, write UNKNOWN. Do not invent a chat widget. Do not say contact support as the first fix."

Good: "Add your work email." Bad: "Please try again later." Later is a shrug.

Good: "Use 8 or more characters." Bad: "Your password is weak. Consider a passphrase for better security." A lecture is not a fix.

If the fail is a server timeout, say the server did not save, then one retry. Do not reuse the missing-field line for a 500. A timeout is not a blank box.

Do not add Learn more. Learn more is a landing page. The field is the work.

4. Force three lines per fail, then stop the model

Hard cap: three lines per failed field, labeled Field, Fault, Fix. Or two spoken lines if Field and Fault share a sentence: "Work email is missing." / "Add your work email."

Tell the model: "Name the field. Name the fault. Give one fix. Sit the error next to the field, not only in a banner. If a banned phrase appears, rewrite. Do not add oops. Do not add a slogan. Do not apologize for the product."

ChatGPT will write "Oops! Please check your details." Claude will hedge "you may wish to review." Gemini will invent a friendlier label so the line sounds warm. Cut all three.

A red banner that says "Please fix the errors below" with no field names is still a treasure hunt. The inline line has to name the field even if a banner exists.

5. One human pass on a cold submit

Open a private window. Load the real form. Leave the required field blank. Submit. Read the error out loud before you click anything else.

Check three traps:

• A line that could sit on a 404 or a toast: oops, something went wrong, try again
• A field name that does not match the label, or a banner with no inline name
• A fix that is contact support, learn more, or a second essay about password strength

Fix the words yourself. Then tell the model: "Replace only the lines I changed. Do not add a joke."

One pass. Paste into the form strings. Ship. If Invalid input is still the only red text, you never named a field. Stop.

Reusable skill card

Trigger: You are drafting a form fail and the first string still says invalid input, oops, or please check your details.

Input: The real field labels from the form, one true fault per fail, one fix the user can do in that field, plus the banned-phrase list.

Output: Form error copy that names the field, names the fault, and gives one fix, sitting next to the field. UNKNOWN where a label was not pasted.

Stop: After one read-aloud on a cold submit. No banner-only lecture. No invented label. No oops. No help-center as the first fix.

Takeaways

• Name the field. Name the fault. Give one fix. Then ship.
• Invalid input is a stack trace. Form error copy is a noun plus a fault.
• Use the label on the form. A friendlier noun is a treasure hunt.
• Two fails is two inline errors. A pile at the top is a lecture.
• Test a blank required field. If you still have to guess, rewrite.