Clanker CloudA research brief can be carefully qualified while its presentation sounds certain. A source says a feature is planned, the summary says it is available, and the slide makes it the main reason to buy.
Use Clanker Cloud Workspace to keep the checked brief, sources, and presentation work in one Project. Ask an Agent to preserve the evidence behind consequential claims as it changes the format for a client audience.
Define the decision the presentation serves
Name the audience and what they must decide. A vendor shortlist, a market-entry discussion, and an internal research update need different structures.
Supply the checked brief and a source register with retrieval dates where relevant. Label claims that are confirmed, provisional, or unresolved. Keep material from older research separate from current facts.
Start with a claim-to-slide map
Before asking for polished slides, request an outline that connects each proposed claim to its evidence. Use a fictional comparison to test the method:
| Supplied evidence | Suitable presentation treatment |
|---|---|
| Vendor A documents the requested export | State the documented capability and source date. |
| Vendor B lists it on a roadmap | Mark it planned; do not present it as shipped. |
| Support terms were not supplied | Add a question for verification. |
This map makes it easier to catch a stronger claim before it spreads into a headline, recommendation, and closing slide.
Request an outline, notes, and source register
Use this fictional, checked research packet to prepare
a six-slide client decision presentation.
First save slide-outline.md with slide purpose, claim,
source reference, uncertainty, and decision requested.
Then prepare the presentation and speaker notes.
Keep planned capabilities labeled planned and missing
support terms unresolved. Include a source register.
Do not invent charts, customer results, or recommendations
that depend on unverified claims. Do not send the files.
If the selected tools produce a presentation file, inspect that file as well as the outline. A sound outline does not establish that the final slide labels and notes are correct.
Review the saved deliverables together
Open the presentation in Preview and check every slide. Follow the source behind the strongest recommendation. Confirm that an uncertain estimate did not become a precise number and that a footnote did not disappear during revision.
Ask for a correction to one claim and check all affected slides, notes, and the source register. Download the final file and open it in the intended presentation software when that is how the client will receive it.
Preserve the research trail
Keep the source packet and reviewed deliverables in the Project. Use separate Sessions for new research and presentation revisions when that keeps the work clearer. Refresh changeable claims before reusing the deck for a later meeting.
For recurring client reporting, the weekly report starter supplies another way to organize observations, missing facts, and next decisions.
Common questions
Does a source link make a slide accurate?
No. Check that the source supports the exact wording, applies to the right product or period, and is current enough for the decision.
Should unresolved findings appear in a client deck?
Include them when they affect the decision. Label the uncertainty clearly and give the reviewer a specific question to resolve.
Sources
Give your assistant one useful job
Verify claims and source dates before turning a research brief into a client-facing deliverable.