How to correct a returned or rejected contribution
Address the specific review comment and retain history instead of creating replacement copies.
WORKING DRAFT · awaiting editorial approval
Working documentation — awaiting owner approval. Legal and operational texts are not final terms for a public service.
Procedure
- Open your document and read the latest decision and affected revision. Distinguish factual corrections, missing evidence, rights concerns and technical media processing. Note the specific issues to resolve.
- For returned text, continue through permitted editing. For rejected or closed states, use the available reopen action before saving again. Do not change another person’s document or source rights; an accepted project editor can act only within current permissions.
- Add evidence and explanation, save a new revision and compare it with the review comment. Restoring an older version creates another revision and can require renewed access to older private resources. Do not bypass missing permission by renaming a file.
- For a version conflict, retain your unsaved text, load the current state and compare the changes. Then submit the genuinely corrected version for review. Repeating the same request does not overwrite an independent decision.
What to watch for
- An editorial return and moderation of a community post are separate workflows. Community appeals refer only to an actual decision affecting the member; they are not a general button for immediately publishing a rejected article.
- If permission or evidence is missing, acknowledge the limitation and postpone publication. The cloud preview does not save corrected manuscripts, and corrections must not silently erase earlier revisions.