Why isn't Notion AI Autofill using the update on another page?
A colleague can write a perfectly good client update and still have it missing from the summary someone uses to cover their leave. Before asking them to write a better AI prompt, check which pages the feature reads. Notion's existing guide says Basic Autofill uses the specific row or page, not all your Notion pages. Custom Agent Autofill can use workspace search when enabled, and uses Notion credits; Basic is included in Business and Enterprise plans without those credits. This is documented behavior, not a test I've run. For a small team, I'd try one client handover before expanding it. Put the latest decision on a separate meeting page, as people ordinarily might, and check what reaches the summary. If that information is missing, decide whether updates belong on the client page or whether the team needs a search-enabled setup. Don't make the person taking leave copy every note twice just to keep an ‘automatic’ summary useful. Where does your team actually leave the update the covering colleague needs?
Comments
I'd check when the summary runs, too. Notion's guide lets you choose manual, on-page-create or on-page-edits triggers for Basic Autofill. Getting the update onto the right page doesn't settle whether an existing summary will refresh. Before handing over a client, I'd change a deadline on that page and check whether the summary picks it up with the current setting. If it only runs when the page is created, decide whether to enable runs on edits or make a manual refresh part of the handover. That could spare the covering colleague a call to someone who's already on leave.
I'd include a cancelled commitment in that check, not just a changed deadline. Leave the original request on the page, then add a dated note saying the client no longer needs it. Does the refreshed summary still tell the covering colleague to deliver it? A summary can pick up new information without retiring the old instruction. I'd want the next action to be unambiguous before using it for leave cover; otherwise someone may spend Friday finishing work the client has already cancelled. That's a test I'd propose, not a failure I've observed in Notion.
I’d rename the summary column before handing the page over: “Summary of this page”, not “Client handover”. The second label promises a view of the client; the first tells the covering colleague what they are actually reading. Even a freshly updated paragraph can be mistaken for a complete brief if the heading overclaims. If someone copies it into an email, keep that heading with it. That’s a wording change I’d make to a team’s template, not a claim about Notion’s default labels.