The formatting died in a plain-text email. Which file is the delivery?
The delivery is the formatted file that still has the tables, the styles, the tracking, or the layout you actually prepared. The plain-text email is a message about that file. Once the body of the mail has flattened the columns, stripped the marks, and reflowed the lines, that body is a damaged copy. It is not what the client should review, print, or file. Reply with the attachment, named with version and date, and say in the first line that the words in the mail body are not the delivery.
Someone pasted a bilingual clause table into a mail because the attachment had bounced for a colleague. The mail client turned the table into a run of phrases separated by odd spaces. A decimal that had sat in its own cell slid next to the neighboring lot code. The reader answered “approved” on that mail. The approval could not be mapped back to cells, and one number was no longer the number in the file. The recovery was to ignore the approval as an approval of text, resend the workbook and the document as attachments, and ask for comments on those files. The pasted body was kept only as evidence of how the confusion started.
Say, in the mail, which file is the file
The first lines of the message name the attachment, the version, and the date, and they say that formatting in the body should be disregarded. If you need to quote a sentence for a question, quote it and give its location in the file. Do not rely on the quote as the only copy. Email review works by attaching the file and talking about the file. It does not work by promoting the mail body into a document. A shared drive drop, if one is required, gets the same formatted file, not a paste.
The project system holds the formatted version. People who forward mails will keep stripping formatting. The attachment can be saved and checked. The body cannot be unflattened with confidence, because two numbers that collide in plain text do not tell you which cell they came from.
How to answer a client who has already edited the plain text
Treat their edited mail as a set of intentions, and retype those intentions into the formatted file yourself only after you can place them. Where the flattened text makes a number or a name ambiguous, ask, quoting the formatted cell. Do not “reconstruct” a table from the paste and call it reviewed. Mark the version as a new one once their intentions are applied to the real file, and send that file back with tracking if they need to see the edit. Their “approved” on the broken mail is not a sign-off on the reconstructed file. Ask them to confirm the attachment.
This is slower than pretending the paste was fine. It is the pace at which a number pass still means something. A reviewer can handle about two to three thousand source words a day of real reading. An ambiguous paste can take longer than the clean file would have, which is the cost of the shortcut.
What belongs in the body instead of the document
A short question, a list of open points, a filename, a date. Those survive plain text. Full tables, signature blocks, stamped certificates, subtitles with times, and tracked contracts do not. Certificates billed by the page and checked for names should travel as page files. A plain-text recital of a name is how a character gets dropped. There is no public unit price that includes a second reconstruction because the first delivery was a paste. The quote assumes the file is the file.
If a client’s gateway strips attachments, agree a path before the deadline: a permitted drive with named access, or a portal, using the same formatted file. Inventing a paste on the day of delivery is how the format dies.
Can a PDF avoid the problem?
A PDF attachment keeps layout better than a paste, and it is the delivery if a PDF is what was ordered. It is still an attachment, not the body. A PDF of a spreadsheet may freeze the look and block the client’s edits. Send the format the job requires, as a file, and keep plain text for the cover note.
What if the only record of a decision is now the broken mail?
Recover what you can, mark every doubtful token, and confirm the doubtful ones against the source before the formatted file moves on. Write the confirmation into the new version’s change list. The broken mail stays in the thread as history. The next person to open the job follows the formatted version, not the paste.
The related service page is translation services.
Quick FAQ: AI Translation Accuracy
- How accurate are AI translators? Accuracy is often high for repetitive or general content, while domain-sensitive content still needs expert review.
- How to improve AI translation quality? Use glossary control, domain prompts, QA checks, and human post-editing in one workflow.
- Where does human translation still win? Legal, medical, and high-stakes brand content usually requires human nuance and accountability.