Prepare a useful lab meeting presentation by turning approved notes into a clear update: what you tried, what you observed, what remains unresolved, and the question you want help answering. An AI teammate can help you organize the preparation so you can focus on explaining the work and getting useful feedback.
The example below is fictional. Use this routine for permitted meeting preparation; you and your research team remain responsible for the work and its interpretation.
Give the meeting one useful question
Start with what would make the discussion worthwhile. “Update on my project” is broad. “I need feedback on which missing check to prioritize before the next experiment” gives the group a specific job.
Keep three things separate:
- Work performed: What you actually did.
- Observation: What the approved record shows.
- Interpretation: What you think it may mean, with uncertainty intact.
A well-organized meeting does not require a confident conclusion when the evidence is still incomplete. An unresolved question can be the most useful thing to bring.
Copy this lab meeting preparation brief
Project and meeting date:
The question I want help with:
Work completed since the last meeting:
Observed result, with source location:
My current interpretation:
What the evidence does not establish:
Open checks or conflicting observations:
Options for the next step:
Feedback or decision requested:
Materials approved for this audience:
Use source locations that you and your group can actually access. Do not include confidential participant information, unpublished collaborator materials, or restricted data in an AI workspace unless your institution and research team permit that use.
A fictional example: make an unresolved check discussable
Suppose a graduate student is comparing two processing approaches. Their notes show that one run completed and another run encountered a setup issue. No valid comparison is available yet.
Weak update: “Approach A performed better.”
Clearer update: “The run for A completed. The run for B is not comparable because of a setup issue. I want feedback on the check we should complete before repeating B.”
The second update preserves the actual state. It lets the group discuss the next step without turning an incomplete comparison into a result.
| Brief section | Fictional entry |
|---|---|
| Work completed | One completed run; one incomplete run |
| Evidence | Approved run notes and setup log |
| Unknown | Whether the approaches differ under comparable conditions |
| Discussion question | Which setup check should be completed before repeating the run? |
| Useful return | An agreed next check and responsible person |
That is a useful presentation even without a finished comparison: the audience can see the evidence, the gap and the question.
Assign Aurora a preparation job
Organize these approved project notes into a lab meeting brief. Separate completed work, observations, my interpretations, and unanswered questions. Link each factual statement to the provided note. Do not invent results, select a research method, validate conclusions, or remove uncertainty. Suggest a concise agenda and questions for my supervisor. Return the draft and a list of points I must verify.
Aurora can help with context you provide and supported connected sources. Keep the instructions specific: preparing a brief is different from performing the research or deciding which conclusion is correct.
If a file is unavailable, provide an approved summary or use the available materials. Laboratory systems and campus storage are not automatically connected to Finta.
Review the brief before the meeting
Check every statement against the original notes. Confirm units, dates, figure references, and the distinction between a completed result and an unfinished check. Remove any material that the audience should not receive.
Choose a short agenda:
- The question and relevant context.
- The work completed.
- The evidence and uncertainty.
- The feedback requested.
- The next action and owner.
The brief should make the conversation easier, not add unnecessary slides or bury the important question in a long summary.
Keep the next action with the discussion
Afterward, record the agreed action, who owns it, and when to revisit it. Separate an advisor's suggestion from a decision the team has confirmed. Have the appropriate person review any meeting summary before treating it as an official research record.
For organizing course and document context more generally, use our student second-brain guide. For a recurring preparation routine, see student agent reviews.
Start with one meeting, not a new system
Try the preparation brief for your next permitted meeting and see whether it helps you explain the open question. Keep the useful structure and adjust the rest.
Finta for Students gives verified students an individual AI workspace for $10/month. The current plan includes 500 monthly Aurora credits; current usage limits apply. Start with your own approved notes and meeting preparation. The individual offer is not a shared lab subscription, and scientific judgment stays with you and your research team.