Skip to content
Fermium
All workflows

Multi-stepOperations

Let the notes lead somewhere useful.

Turn supplied meeting notes into a shared summary, an action table, and decisions worth remembering.

A complete worked example

Give the meeting a useful second life.

The project call produced decisions and follow-ups across several topics. The agent has the supplied notes and needs to make the next steps legible.

Fictional project and sample data. This preview does not submit, publish, or change access.

Team workspace
Acorn / Team / September 23 recap

Project team · illustrative result

Three next steps from the project call

The team agreed on the launch direction. These are the actions supported by the supplied notes.

Confirmed
Use the calm, direct headline direction
Open
Final owner for the review invitation
Three next steps from the project call · sample records
ActionOwnerDue
Supply photographyJamieOct 12
Revise the coverMayaOct 13
Send review invitationTo confirmTo confirm

Context worth keeping

The headline decision can be recorded in the project Agent with a reference to the meeting notes. Ownership and deadlines remain explicit, including where the notes do not supply them.

Select After follow-up to see what the next request changes.

What the recipient can access

The recap, supported actions, and confirmed project decisions.

Kept out of this handoff

Off-topic discussion and any private notes omitted from the recap.

How it runs

  1. Bring the notesSupply the meeting material and identify the intended audience.
  2. Extract the next stepsHave an agent draft actions, owners, and dates, leaving unknowns explicit.
  3. Keep the contextPublish the summary and save confirmed decisions in the project Agent.
  4. You getA published summary and structured next steps linked to the original notes.

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.

Use [meeting notes] to draft a summary and action table. Include only supported owners and dates, mark missing details, and link to the source. Publish for [team] and save confirmed decisions in [Agent].

What this workflow needs

Supply notes or a transcript. This does not record meetings or automatically transcribe audio. An owner field is ordinary tracking data, not an automatic assignment notification.

What if the notes do not give a due date?

Leave it unset or identify it as an open question rather than inventing a commitment.