Give the brief a specific purpose.
Identify the person, company and decision you want the meeting to support. Include recent notes and links you are allowed to use. Add a relevant goal, such as understanding why a customer paused onboarding.
Jarvis can retrieve context from its memory, but retrieval is selective. Supply the important source explicitly when you need the brief to account for it.
- Meeting identity and purpose.
- Notes, email excerpts or documents with source labels.
- Open commitments you want to revisit.
- Your company goal and questions you already have.
Ask for evidence and open questions.
A prompt to start with
Prepare a brief for my meeting with [name] at [company]. The purpose is [decision or goal]. Use only the sources I supply and relevant saved context. Separate facts, assumptions and open questions. Include a source label for each factual claim. Show commitments with owners and dates only when confirmed. If there is no prior history, say so. Do not contact anyone or change my calendar.
Make the brief useful in one glance.
A source label is a pointer you can inspect, not proof that the model interpreted it correctly. Open the source when the detail could change your decision.
Purpose: understand the onboarding blocker. Known: Maya paused setup at account connection. [Call notes, 18 September] Open commitment: share the revised setup guide. Owner: us. Date: unconfirmed. Question: which permission made the team hesitate? Missing: no notes from the most recent trial session.
Repeat the gathering, keep the judgement.
For recurring use, choose a supported calendar or schedule trigger, verify time zones and connect the required sources. A desktop-based source still requires that computer to be awake and connected.
Select the meeting
Match the correct person and company. Resolve ambiguous names before gathering context.
Collect relevant sources
Keep a source label and date with each input. Separate current information from older notes.
Generate the brief
Ask for the purpose, confirmed facts, commitments, questions and missing context.
Read it before the call
Check the claims that matter. Decide which questions you want to ask.
A missing history should stay missing.
Test these cases on your configured workflow. The website’s sample brief demonstrates a presentation pattern; it is not connected to your calendar or your Jarvis instance.
| Situation | Expected behaviour |
|---|---|
| First conversation with this person | Says no prior history was supplied or found |
| A source was removed | Does not repeat claims that rely only on that source |
| Conflicting dates in two notes | Shows the conflict with source dates |
| An uncertain commitment | Labels it as unconfirmed |
| A failed source connection | Identifies the unavailable source instead of implying the brief is complete |
By the Jarvis team · Reviewed