ChiefOSby ConversintStart free
Menu
← Back to the library
Meetings and learning

Attendee research

Prepare an evidence-backed brief on every named meeting participant, tying public professional facts to a user-supplied thesis, challenge, or agenda and suggesting honest conversation openers. Use when a user has an attendee roster and needs person-by-person research for an upcoming discussion. Use meeting-preparation for meeting history, decisions, commitments, or a general agenda; use Notion Meeting Intelligence when Notion-backed context, an agenda or pre-read, or related Notion work is primary; use research-synthesis for broad topic, company, or market research not organized around a roster.

Works with the context you provideVersion 1.0.0

Attendee research

Use this method to turn a named attendee roster and a user-supplied thesis, challenge, or agenda into a practical, evidence-backed preparation brief. It is roster-first public-professional research, not a method for reconstructing meeting history, researching a topic generally, or working from Notion context.

Use [references/evidence-and-identity-rules.md](references/evidence-and-identity-rules.md) before resolving people or turning research into openers. Use [references/attendee-brief-template.md](references/attendee-brief-template.md) when drafting the final brief.

Inputs and routing

Require a named attendee list and a thesis, challenge, or agenda. Preserve the thesis as **user context**, not as a sourced fact. Use supplied information before asking for a missing decision-critical detail.

Accept, when available: attendee organization or title, event page, event purpose, date or location, desired outcome, the user's role, excluded topics, priorities, depth or time budget, and requested categories.

Route away instead of stretching this method:

  • Use meeting-preparation when the primary need is meeting purpose, prior context, decisions, commitments, or questions for the meeting as a whole.
  • Use Notion Meeting Intelligence when the primary need is Notion-backed meeting context, agenda or pre-read creation, or related Notion work.
  • Use research-synthesis when the outcome is broad current research rather than a roster brief.
  • Handle ambiguous identity and source conflict with the rules reference; preserve the ambiguity rather than selecting a profile without support.

Workflow

  1. Normalize the roster in the supplied order. Keep every named attendee in one main sequence, including marketing, distribution, technology, operations, or other specialists. Do not create an "adjacent" appendix merely because perspectives differ; use categories only when the user explicitly requests them.
  2. Resolve identity carefully using the rules reference. Record supplied, publicly resolved, conflicting, or unknown role and organization status, plus a source date for public-role claims. Call a role current only when a timely source verifies it; otherwise retain the source date and label it dated or uncertain. Do not merge people on a name-only match.
  3. Research only public professional facts that could help connect the person to the user context. Capture each URL and its relevant date while researching. Do not sign in, contact anyone, or use personal details.
  4. For each attendee, use separate labeled fields for Public fact, User context, Relevance inference, Suggested question or opener, and Uncertainty. The opener is a concise, answerable question by default. Use a clearly labeled observation only when a question would be less appropriate. Neither form may assert that the attendee holds a view or agrees with the thesis.
  5. Recheck every non-trivial public claim against its cited URL. Put a Markdown inline citation immediately after every non-trivial public fact, including dated role facts and each side of a conflict: `[short source descriptor](https://example.com/source)`. Do not put a bare URL only in a separate Evidence or Sources line; a Sources-only URL is not an inline citation. Then add a `## Sources` section that lists each cited URL exactly once with a short descriptor. Inline citations may repeat a URL when multiple claims depend on it; Sources must not.
  6. Check that every supplied attendee appears exactly once, supplied order is retained where practical, every attendee has an opener, uncertainty is visible, roles are not called current from stale evidence, and no unsupported belief or private-source claim slipped in.

Capability fallback

Full researched briefs require public-web research. If that capability is unavailable, use only user-supplied links and excerpts. When relying on supplied links or excerpts, cite each factual statement inline using the supplied URL and include the same URL once in Sources; label the source as supplied and state that it was not independently opened or verified. Return a clearly labeled **provisional attendee framework** or brief, identify coverage gaps for each person, and state that live public research did not occur. Do not fill gaps from memory or imply that web research, sign-in, or a private source was reviewed.

Boundaries

This method is read-only. Do not mutate CRM, calendar, records, or notes; publish a brief; send messages; contact attendees; sign in; or treat a suggested question or observation as a statement of fact. Follow-up writing belongs to the appropriate writing method, not this one.