Agency operations workshop / 5 MIN READ
Give reviewers the page they need before the meeting
Prepare a decision-focused pre-read that makes questions and disagreement visible early.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A concise pre-read lets reviewers absorb context before live discussion. Its job is to expose the choice, evidence and uncertainties so the meeting can focus on what still needs judgment.
What you will leave with: A decision page with a review request, comment window and clear disposition of open questions.
Use this when
- Meetings spend most of their time rebuilding background.
- Reviewers arrive with different understandings of the proposed decision.
This is not permission to treat silence as approval or to replace mandatory live consultation where it is required.
State the decision at the top
Atlassian’s page-led meeting guidance uses written context to support a clear meeting outcome. Start the pre-read with the choice the authorized owner will make.
Name the decision scope, why it matters now and what input is requested from reviewers. Distinguish a proposal seeking feedback from a final recommendation seeking approval. Keep the background limited to what changes the choice, with links for deeper context. A reader should not have to reach the final paragraph to discover why they were asked to review the page.
Show the reasoning and its weak points
Present the options, relevant evidence and meaningful trade-offs. Label assumptions and unresolved questions explicitly. Explain why the preferred option is recommended without making competing options look artificially foolish. Reviewers need a fair account of the decision, including what might change your view.
Attach only material the audience may access and needs to inspect. Do not paste private research records into a broadly shared pre-read. If evidence is restricted, provide an appropriate summary and a route for authorized review. Keep source dates and applicable scope visible where they matter to the recommendation.
Ask for focused comments
Tell reviewers which questions they should address and when their input is useful. Ask them to distinguish factual corrections, missing constraints and preferences. Provide a way to raise sensitive concerns privately with the appropriate owner rather than forcing every issue into a public comment thread.
Allow enough time for the intended review depth and check availability before calling the deadline realistic. Invite reviewers to say they cannot complete the review. Silence may mean they were unavailable, confused or unable to access the page. It should not be silently converted into approval unless a valid agreed process explicitly supports that interpretation.
Use the meeting only for unresolved judgment
Before the discussion, consolidate factual answers and identify the remaining choices. Update the page so people do not repeat questions already resolved. If the input settles the matter through the authorized process, consider whether a meeting is still needed.
During the meeting, focus on the consequential disagreements and record the decision with its conditions. Afterward, update the page to reflect the actual outcome and notify affected people. Avoid leaving the proposal looking approved when the decision was different. The pre-read becomes a useful reference only when its final status is clear.
Make the reasoning concrete.
A fictional agency sends a long campaign deck before a review and asks for “thoughts.” Half the meeting is spent discovering that the client is being asked to choose between two event formats.
Keep the broad review request
Opening: Ask attendees to react to the whole deck.
Hypothesis: Reviewers can comment freely.
Risk: The specific decision remains hidden and feedback may scatter across irrelevant details.
Send a decision page
Opening: State the format choice, constraints, options and questions for reviewers.
Hypothesis: The live discussion can focus on unresolved trade-offs.
Risk: The team must still obtain the actual required approval.
The agency replaces the vague request with a concise page and gathers factual corrections in advance. The meeting addresses the remaining format decision, and the page is updated with the approved outcome.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Decision
What exact choice should reviewers help resolve?
Evidence
What information changes that choice?
Uncertainty
Which assumption or constraint needs challenge?
Request
What input is needed, from whom and by when?
Status
How will the final decision replace the draft recommendation?
Watch for the wrong conclusion.
- Asking for general thoughts when a specific decision is needed.
- Treating silence as agreement.
- Leaving a rejected proposal displayed as the current plan.
Your next action
Rewrite the first paragraph of your next pre-read so it names the decision, the requested input and the real review deadline.
Sources & scope
The workflow, worksheets and hypothetical examples are original editorial analysis. Sources support only the identified principles. No measured business results or named human reviewer are claimed.
- Atlassian Team Playbook: Page-Led Meetings →Primary framework-publisher guidance · Supports: A written page can establish a meeting’s context and intended outcome; the asynchronous review workflow is original analysis.