AI Humanizer Ruined My Paper? Restore Citations and Formatting
Do not repair the returned file until it merely looks right. Start again from the last clean DOCX, use the damaged version as a map of proposed wording, and move back only the changes you can defend.
HumanPen Team
· 23 min read
The short answer
If an AI humanizer changed your citations or Word formatting, stop editing the returned file. Use the last clean DOCX as the recovery base and the damaged version only as a source of proposed wording. Compare the two, restore linked citations and document structure from the clean copy, then reapply only the prose changes you can verify.
That order matters. A sentence can be rewritten again. A flattened citation field, missing bookmark, or altered section break may be much harder to rebuild after more edits pile on top. The fastest-looking approach, fixing brackets and spacing in the damaged file, also makes it easy to keep damage you have not seen yet.
Make the incident reversible before fixing anything
Save three separate files before you update a field, accept a tracked change, or type over an error:
- `clean-source.docx`: the document as it existed before the humanizer touched it.
- `damaged-return.docx`: the exact file the tool returned.
- `recovery-working.docx`: a new copy of the clean source. This is the only file you repair.
If you have already edited the returned file, save that state as a fourth incident copy. Do not overwrite it with the next attempt. The point is to keep every later decision reversible.
No clean source in the folder? Check email attachments, shared folders, collaborator copies, and backups. If the file was stored in OneDrive or SharePoint, Microsoft's Version History instructions let you open an earlier version in a separate window and restore it if needed. Microsoft limits that feature to files stored in OneDrive or SharePoint, so it is not a recovery promise for a file that lived only on a local drive.
A PDF can help you recover visible wording and page appearance, but it is not a clean DOCX. It cannot give you back a live citation, cross-reference, table of contents, or section structure. Keep looking for the editable source.
Compare the files, then choose the clean one as the base
Open Word's Review > Compare > Compare, put the clean file in the original slot and the returned file in the revised slot, and show changes in a new document. Microsoft's legal blackline guide says this creates a third comparison document without changing the two source files.
The comparison is a damage map, not the file you will submit. Scan it once and classify each change:
| What changed | Source of truth | Recovery action |
|---|---|---|
| A number, quotation, technical term, method step, or claim boundary | Clean file plus the cited source or research record | Restore the exact content first; keep a rewrite only after checking it against that record |
| An in-text citation or bibliography entry | Clean linked citation plus the reference manager library | Work from the clean linked field; do not rebuild it by matching the visible punctuation |
| A heading, caption, table, note, list, page break, or section break | Clean DOCX | Leave the clean object in place and move approved wording into it |
| A table of contents or cross-reference | Clean field and its target heading, caption, or bookmark | Restore the target before updating the field |
| Ordinary prose with no protected content | Author's intended meaning | Keep, repair, or discard the proposed wording paragraph by paragraph |
This is the main recovery decision: copy safe words into sound structure; do not copy sound-looking structure out of a damaged file.
For the failure modes behind this table, see what happens to citations, tables and equations in an AI humanizer. That page explains what can break. The rest of this guide is about putting it back in the right order.
Restore dependencies before prose
Repair the document from the parts that other parts depend on.
1. Restore fixed content and evidence
Start with numbers, units, quotations, proper names, defined terms, equations, and method steps. Put back the clean wording unless you can verify the revised wording from the underlying data or source.
Then inspect every changed paragraph that carries a citation. The bracket may still be present while the revised sentence makes a broader claim. If the claim-source connection changed, restore the clean paragraph before doing any style work. The full method for checking that relationship is in how to revise a literature review without breaking the evidence chain.
2. Restore linked citations and the bibliography
If the clean file contains active Zotero citations, keep those fields and reapply approved prose around them. Zotero's Word plugin documentation says Refresh updates linked citations and the bibliography from the library. Its citation troubleshooting page separately warns that flat-text citations are not detected as active citations and that manual edits can stop automatic updates.
So a citation that merely looks correct is not enough. If the returned version flattened it, restore the linked citation from the clean file or reinsert it through the reference manager. Do not type the author, year, comma, and parentheses until they resemble the original. That repairs appearance while leaving the link dead.
3. Restore document machinery
Keep the clean headings, styles, captions, bookmarks, footnotes, tables, section breaks, headers, and footers in the recovery copy. Reapply approved wording inside those objects rather than recreating the objects in the returned file.
After headings, captions, and bookmark targets are back in place, update the fields. Microsoft's field update guide documents updating a field from its context menu. In Word for Windows, it also gives Ctrl+A followed by F9 for document fields and notes that tables containing fields may need to be selected separately. An error after the update is a failed dependency, not text to type over.
For a longer explanation of why a table of contents or cross-reference can look fine while its link is gone, read Word fields, tables of contents and cross-references.
Reapply only the prose that survives review
Now return to the comparison and review the changed paragraphs one at a time. Each proposed edit gets one of three decisions:
- Move it into the recovery copy when the meaning is equivalent and no protected element was changed.
- Repair it in the recovery copy when the idea is useful but a qualifier, citation attachment, term, or number needs to be restored.
- Discard it when it introduced strange word order, broadened a claim, changed fixed language, or touched structure for no good reason.
Do not make the damaged output the new input for another whole-document pass. That hides the first incident under a second layer of edits. If a paragraph still needs work, revise that paragraph manually or send only that small scope through a workflow that shows you the boundary before it runs.
HumanPen is one file-level option for that narrow retry: its public page says you can add passages directly, see a partial selection expanded to the paragraph that will be processed, and leave everything outside the confirmed scope unchanged. The useful feature in a recovery is the boundary. You should still compare the returned paragraph with the recovery copy before accepting it.
Run a recovery gate, not a visual spot-check
The repaired document is ready only when its remaining differences from the clean source are intentional prose edits.
- Compare `clean-source.docx` with `recovery-working.docx` again. Every difference should be on your approved list. An unexplained heading, field, table, citation, or section change fails the recovery.
- Refresh linked citations and the bibliography through the reference manager. Resolve any citation that no longer updates before moving on.
- Update Word fields after their targets are final. Investigate every bookmark, reference, or table-of-contents error instead of replacing the error message with typed text.
- Reopen the changed citation-bearing sources and confirm that the final claims still match them.
- Save, close, reopen, and export a PDF. Check the pages containing repaired tables, figures, notes, section changes, and the start of the reference list.
If all five pass, create a separately named submission copy. Keep the clean source, damaged return, comparison, and recovery copy until the assessment or publication is finished.
This gate is deliberately limited to incident recovery. How to review a humanized Word document before submission has the broader pre-submission check for meaning, citations, fields, page layout, comments, and tracked changes.
What if there is no clean DOCX anywhere?
Then this is reconstruction, not a quick repair.
Gather the best surviving records: a PDF, an emailed attachment, collaborator copies, reference-manager library, source notes, data tables, and any accepted draft. Create a new working copy and mark every element whose source is uncertain. Reinsert citations from the library, not from memory. Rebuild references from the cited works, not from a humanizer's output. Recheck quotations against the original pages.
Do not silently guess at a missing citation or claim because a deadline is close. A visible placeholder and a conversation with a supervisor or editor are easier to correct than a polished paper containing a source you cannot verify.
Frequently asked questions
Can Word Compare restore the original formatting? No. Compare shows differences. Recovery comes from starting with the clean file, which already contains the sound structure, and moving approved prose edits into a copy of it.
The citations still look normal. How do I know whether they are broken? Test whether the reference manager recognizes and refreshes them. A flat-text citation can look identical to an active field. If it is no longer linked, restore or reinsert it from the clean document and library.
Should I copy the missing citations back into the damaged paragraph? Restore the clean citation-bearing paragraph first, then reapply any verified prose around its linked citation. Moving a bracket by itself does not prove the source still supports the sentence.
Should I rerun the entire paper after repairing it? No. That recreates the same risk across paragraphs you have already recovered. Work only on the remaining prose that needs revision and keep protected content outside that scope.
What is the best way to prevent this next time? Keep the input file immutable, run tools on copies, confirm the rewrite scope before processing, and preserve the exact returned file for comparison. A recovery is much shorter when the clean base was never overwritten.
KEEP READING