Rewrite a set of interface errors with accurate causes, actionable recovery and a consistent review checklist.
A fictional upload form accepts PDF files up to 5 MB. The draft errors are Invalid, Something went wrong and Access denied. The system can distinguish unsupported file type, excessive size and insufficient permission, but it cannot always determine the cause of a network failure.
| Condition | Known fact | Recovery available |
|---|---|---|
| Wrong type | file is not PDF | choose a PDF |
| Too large | file exceeds 5 MB | choose a smaller PDF |
| No permission | account cannot upload | ask an administrator for access |
| Network failure | upload did not complete | check connection and retry |
An error message should explain the problem at the level the audience can use and offer a feasible next step. It should not expose internal details merely to sound precise. Start from what the system actually knows. The writing course focuses on messages rather than implementation, and this project follows that boundary.
Map the four conditions to known facts and available actions.
Error context table
Record your result and evidence here or in a separate file.
No message asserts a cause beyond the known condition.
Separate observed failure from a guessed explanation.
Name the relevant object and the correction without unnecessary blame. A file-type error can specify PDF; a size error can state the actual limit. Avoid vague pronouns when several fields or files are present. Keep the primary message concise and use supporting detail only when it helps recovery.
Rewrite the type and size errors in one or two sentences each.
Two validation messages
Record your result and evidence here or in a separate file.
Both messages state the rule and a feasible correction.
Replace invalid with the specific condition that failed.
Some failures cannot be fixed by changing the current input. A permission message should explain the available route without promising access will be granted. A network failure should not be described as a bad password or server outage without evidence. Preserve uncertainty while still offering a useful retry path.
Write permission and incomplete-upload messages.
Two recovery messages
Record your result and evidence here or in a separate file.
The network message says the upload did not complete and does not invent a cause.
Use a known effect plus a practical next step.
Review terminology, tone, length and placement across the set. Do not rely on a red border or icon alone. An implementation would need to associate messages with fields and announce relevant updates; the writing package specifies these requirements without claiming they were implemented.
Create a review checklist and annotate where each message belongs.
Message specification
Record your result and evidence here or in a separate file.
Every message has a trigger, location and recovery action.
Connect copy to the exact state that displays it.
A scenario review asks whether a reader can identify the problem and next action from the message. It is not a substitute for actual usability research. Use the supplied conditions to test accuracy and create a plan for future user review. Do not invent participant feedback or support-ticket reductions.
Review all four messages and record one revision with its reason.
Error-copy handoff
Record your result and evidence here or in a separate file.
Claims of effectiveness are limited to the review actually performed.
Replace performance promises with a testable question.
Deliver the condition table, four final messages, trigger and placement notes, checklist and scenario review. Add a fifth condition where retrying is unsafe and explain a different recovery instruction.
Every stated cause is supported by the known condition and every recovery step is feasible in that state.
| Criterion | Points | Evidence |
|---|---|---|
| Evidence and correctness | 30 | Calculations, source use and results match the supplied case; limitations are honest. |
| Required artifacts | 30 | All five stage outputs and the capstone handoff are present and inspectable. |
| Reasoning and decisions | 20 | Choices, assumptions, alternatives and the case-specific critical condition are explained. |
| Reproducibility | 10 | A reviewer can follow the stated steps and distinguish expected from observed results. |
| Clear communication | 10 | Labels, units, structure and evidence references make the work easy to review. |
Score at least 80/100, supply every required artifact, and satisfy the path-specific critical condition. Rework missing evidence before marking complete.
For an oversized file: This PDF is larger than 5 MB. Choose a smaller PDF and try again. For an unknown network cause: The upload did not complete. Check your connection and try again. The second message avoids claiming that the server or the user caused the failure.
This is a content-design specification, not implemented interface behavior or measured reduction in user errors.