A useful rollup has a defined audience, consistent source metadata, and a clearly bounded query.
Define the reader’s task
Choose a specific question for the rollup to answer, such as “Where are the current project updates?” Avoid an all-content feed that makes readers do the filtering themselves.
Keep authoritative content in its source location. A rollup should help people discover the original item rather than create another copy to maintain.
Choose sources and filters
The Highlighted content web part can display content from selected sources and narrow results with filters. Configure source scope, content type, and sorting around the reader’s task.
For a policy overview, agree on the metadata that identifies a current policy before configuring a query. If source libraries use inconsistent values, resolve those differences first.
Validate the results
Check the web part with representative reader accounts and compare the returned items with your expected set. Include newly published content and items that should be excluded.
Search-driven experiences can reflect indexing delays. Do not promise that every content change appears instantly, and distinguish indexing issues from incorrect metadata or permissions.
Maintain relevance and access
Audience targeting helps surface relevant content; it should not be treated as a security boundary. Protect the underlying content with appropriate permissions.
Assign an owner to review the query and source scope when sites move or terms change. Use an intentional sort order and enough context for readers to recognize the right result.
Further reading
Validate configuration choices against Microsoft’s current documentation and your tenant’s available licenses.
Microsoft: Use the Highlighted content web part ↗Microsoft: Target content to a specific audience ↗