Notion Agent can now first propose Suggest Edits, letting you decide one by one whether to accept them.
This is already much safer than:
“Fix the entire document directly for me.”
But if you’re editing an important document, I recommend taking one more step:
Before starting, clearly list what "facts that must not be changed" are in the text.
Today we focus on four categories:
Numbers.
Dates.
Proper nouns.
Commitments and conditions.
Why is this step necessary even with Suggest Edits?
Because Suggest Edits solves the problem of:
AI not secretly overwriting the original text directly.
But it doesn’t guarantee that every edit AI suggests keeps the original meaning intact.
For example, the original text says:
“The project budget cap is 300,000.”
You just tell AI:
“Make the tone more professional.”
If AI thinks the sentence could be more concise, it might offer a new version.
Of course, you can reject it in the end.
But if a document has 20 or 30 edits, you can't always immediately spot which number, date, or commitment has been altered.
The better way is:
Before AI starts, tell it which content is not a matter of style but factual elements that cannot be changed on its own.
Category 1: Don’t let AI change numbers on its own
Examples include:
Prices.
Quantities.
Discounts.
Percentages.
Budgets.
Delivery amounts.
KPIs.
Any confirmed numbers should be protected in advance.
If the original text is:
“The budget cap for phase one is 300,000.”
You can explicitly write:
“300,000 is a confirmed number and must not be modified, rounded, or recalculated.”
Then AI’s task becomes:
Improve the sentence.
Not re-evaluate the numbers.
Category 2: Don’t alter dates just for smoother wording
Dates easily hide inside ordinary sentences.
For example:
“The first version is expected to be delivered on September 15.”
If AI changes it to:
“The first version will be delivered in mid-September.”
It may read more naturally.
But the meaning isn’t exactly the same.
September 15 is a specific date.
Mid-September is a date range.
That difference matters greatly in formal work.
So items like:
Launch date.
Payment date.
Delivery date.
Event date.
Contract period.
Should all be clearly stated as:
Dates must remain exactly as is and should not be changed to approximate terms.
Category 3: Don’t "correct" proper nouns yourself
AI loves to standardize text.
But some unusual names may actually be the correct official terms.
For example:
Company names.
Product names.
Client project names.
Feature names.
Legal terms.
Internal department names.
If AI is unfamiliar, it might assume:
That it’s a typo.
That capitalization is wrong.
That the name should be changed to a more common version.
So for official documents, you can first tell it:
“Please keep all company names, product names, project names, and proper nouns as is; if you have doubts about errors, raise a question but do not correct on your own.”
This sentence is very practical.
Because:
Not knowing is not the same as guessing.
The most important category 4: Commitments and conditions
This is the area most likely to make documents “look better but become riskier.”
For example, the original says:
“We expect to complete within two weeks.”
AI might suggest:
“We will complete within two weeks.”
The wording sounds more confident.
But:
“Expect”
and
“Will”
are not the same commitment.
Another example:
“Payment arranged after acceptance.”
If changed to:
“Payment arranged after completion.”
The words “acceptance” are dropped, changing the condition.
So for items like:
Payment terms.
Refund conditions.
Delivery conditions.
Scope of services.
Liability limits.
Expected timeframe.
Possibility.
Depending on circumstances.
Subject to confirmation.
Anything that changes either party’s rights or commitments must not be strengthened, weakened, or removed by AI on its own.
Tell Notion Agent this directly
Before starting Suggest Edits, enter:
“Please proofread this document and only use Suggest Edits; do not directly modify the original text.
The following four categories are confirmed facts and must not be modified on your own:
- All numbers and amounts.
- All dates and deadlines.
- All company names, product names, project names, and proper nouns.
- All commitments, conditions, limitations, and liability descriptions.
You may improve grammar, redundancy, and sentence clarity.
If you think any of the above facts have issues, only raise questions and do not edit on my behalf.
I will decide whether to accept each.
”
This is not an official Notion prompt.
It’s a practical workflow SasaDaily developed based on how Suggest Edits handles manual review.
The key isn’t to copy it literally.
What matters is:
Define upfront what cannot be changed.
Why is saying “don’t change meaning” not enough?
Because “meaning” is vague.
You and AI might have different judgments about what “no change in meaning” means.
For example:
“Maximum discount 10%.”
and
“Discount around 10%.”
AI might consider them just different wording.
But anyone doing business knows:
They are completely different statements.
So don’t simply say:
“Keep the original meaning.”
Be clearer by specifically identifying:
Which fields are factual and not to be touched.
Leave the rest for AI to optimize text.
How to review Suggest Edits next?
Notion’s August 28 Agent Suggest Edits lets the agent first propose edits, then users review each item from top to bottom.
After setting the protections above, review each suggestion:
Grammar improved.
Accept.
Removed repeated sentence.
Accept.
Amount changed.
Reject.
Date changed to an approximate time.
Reject.
Changed “expect” to “guarantee.”
Reject.
At this point you aren’t rereading the entire AI-generated article.
You’re checking:
Whether this specific edit can stand.
This method isn’t just for Notion
Anytime AI helps you edit important documents, you can use the same approach.
For example:
ChatGPT.
Claude.
Gemini.
AI within Word.
AI within Google Docs.
Or your company’s own document agent.
The tools differ.
The principle remains:
Divide the document into two layers.
The first layer:
Text that can be optimized.
The second layer:
Facts that cannot be changed on their own.
Let AI handle the first.
If the second is touched, have it ask a human.
Remember today’s method in one minute
Next time you have AI proofread, don’t just say:
“Make it sound more professional.”
Add first:
The following must be kept as is and not modified on your own: numbers, dates, proper nouns, commitments, and conditions.
Then tell AI:
Only suggest edits.
Finally, you approve each one.
AI is best at helping you improve:
How you say things.
But some things must be decided by a person:
What was actually said.
Today, progress a little with AI.
Learn one AI tip each day.
Save a bit of time every day.
Improve a little bit every day.
SasaDaily, growing with you.
