Articles · Self-Advocacy
Knowing When Work Is Ready to Submit
A small stopping system for people who cannot tell when review is sufficient.
Shared Language editorial team
Published · Updated · 2 min read
Completion needs a visible boundary
Some people keep checking because they cannot tell when review is sufficient. The issue may be unclear quality standards or uncertainty about the consequences of missing a detail.
Build a stopping system
Use a short checklist, a defined number of review passes, an example of acceptable quality, a time limit, or a second reviewer for high-risk work. Managers can clarify what matters most and what does not need further refinement.
Define the checks that matter
For a routine update, the stopping rule might be: answer the requested question, check the dates and figures, and confirm the recipient. A high-impact document may need a separate reviewer. Match the checks to the task instead of applying the most demanding review process to every message. Ask the person requesting the work to identify the essential standard.
Agree what happens after submission
Clarify whether the next version is a draft for feedback or a final deliverable. If revisions are expected, say so; a person may be trying to eliminate every possible issue before a stage intended for discussion. Use a review deadline as a planning aid, not a reason to ignore a known serious error. When uncertainty remains, name it explicitly and ask the responsible person to decide the next step.
Try this next
Create a “ready to submit” checklist with no more than five items for one recurring task.