Multi-stepFiles and feedback
From collected feedback to a clearer revision.
Collect the assets, gather contextual comments, and ask your AI to prepare a revision brief.
A complete worked example
Turn three reviewers' notes into one useful revision brief.
Acorn's cover image and launch film have separate client responses. The designer needs a compiled brief that preserves both context and disagreements.
Fictional project and sample data. This preview does not submit, publish, or change access.
Private revision brief · illustrative result
Creative round 1 · next changes
Two concrete edits and one decision to resolve with the client.
- Cover · pin 1
- Leave more room for the headline
- Film · 00:12
- Hold the title card two seconds longer
- Open decision
- Two reviewers prefer different closing images
For the designer
Use launch-cover.png version 1 and launch-film-v2.mp4 as the sources. Preserve the warm palette, which reviewers supported. Do not choose the closing image until the client resolves the conflicting preferences.
What the recipient can access
A team-only compilation of submitted feedback with its source context.
Kept out of this handoff
Individual responses are not exposed as a shared guest discussion.
How it runs
- Collect the right versionsRequest the originals and identify the versions under review.
- Gather independent feedbackShare a review form and inspect each respondent’s comments.
- Prepare the next roundAsk an active agent to summarize the notes, then create a new review for the revised files.
- You getVersion-specific responses and a sourced list of changes for the next round.
A prompt to start with
Copy this into your AI tool after connecting it to Fermium. Replace the bracketed details and let it ask for the context it needs.
Set up a review round for [creative files]. Collect contextual comments from [audience]. When I ask, summarize requested changes with file, page, or timestamp references and separate disagreements for a person to resolve. Publish the revision brief for [team].
What this workflow needs
Guest responses are separate. The agent runs synthesis on request; it should not invent consensus or replace a human decision. Each revision round needs the intended source versions.
Will everyone see one shared discussion?
No. Current forms collect private responses. Team editors can inspect them and prepare a combined revision brief.