How to use the Proofreading Checklist Generator.
Match the checklist to the document's actual risks. A proposal needs checks for scope and prices; a newsletter needs checks for links and offer conditions.
Make the workflow fit your task.
Identify the document's purpose and the consequences of an error. Turn those risks into checks tied to specific sections, covering names, references, numerical consistency and the final action requested of readers.
- What you provide
- Document type and editorial requirements.
- What you get
- Document-specific review checklist.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Proofread a proposal with three deliverables and a fixed quote.
Completed example
Check deliverable names, exclusions, price arithmetic, dates, client name and approval instructions.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
How is a checklist different from proofreading the text?
The checklist defines repeatable checks; proofreading applies them to a particular draft. Keep both the rule and the finding available.
What if the checklist is too generic to use?
Replace broad instructions with observable checks, such as matching the quoted price to the scope table or opening every destination link.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑