You finish a report and then discover that the reviewer needed a one-page decision brief. The work may be careful, but the definition of completion was never shared. Clarifying that standard early can prevent a painful final rewrite.
Ask for observable requirements
Identify the decision or action the work should support. Then confirm the required format, audience and essential information. “Professional” is a useful aspiration but a weak acceptance criterion on its own.
For an invented task, completion might mean a two-option comparison with costs sourced and one recommendation explained. Decorative slides may be optional rather than part of the requirement.
Separate required and useful
Make two short lists. Confirm the required list with the person responsible for accepting the work. Keep optional improvements visible so they can be weighed against available time.
If the task changes, update the shared understanding. Do not treat the initial list as permission to ignore a later agreed requirement.
Check before polishing
At a sensible midpoint, show the structure or a small sample. A reviewer can often spot a mismatch before you refine every sentence.
Finish by checking the actual requirements, not just whether the document looks complete. Pair this with clarifying a task before starting. A clear finish line gives both the work and the review a more useful shape.