Upload a file and ask about it. Manuscripts, spreadsheets, PDFs, plain text.
The file belongs to that conversation. Start a new conversation and you start with no files.
Understand it
Summarise this in five bullet points. What is this document actually asking for? List every deadline mentioned.
Find things
Does this mention anything about payment terms? Pull out every author name and affiliation. Which sections are incomplete?
Improve it
Make the English clearer without changing the meaning or the technical terms. This is for a journal submission. Is the abstract doing its job? Shorten the introduction by a third without losing any argument.
Compare — attach both files, then:
Compare these two versions. Make a table of what changed: names, dates, figures, links, and any section that was added or removed. Do not rewrite anything yet.
When you have asked it to change a document, always finish with:
List the changes you made, and anything you could not preserve.
AI is careless with structure in ways it will not mention. The usual casualties:
For a manuscript going to a customer or a journal, assume formatting has been damaged until you have checked. Ask it what it changed, then look yourself.
The single most useful habit with documents is telling it what not to touch:
Change only the introduction. Keep every fact, name, link, figure and date exactly as it is. Make the wording friendlier and about 20% shorter.
Do not change any technical terminology. If you think a term is wrong, list it at the end instead of changing it.
Preserve the reference list exactly. Do not reformat the citations.
Uploading a customer's manuscript is uploading their unpublished work. It stays inside Uni-edit's own Azure account and is processed in the Asia-Pacific region — it does not go to a public AI service. But treat it with the care you would treat the file on your own desk: do not upload anything you would not put in an internal email, and if a customer has asked that their work not be processed by AI, honour that.