# Events and meeting preparation

Start with what the user wants: to find relevant industry days, evaluate a conference, prepare for a meeting or organize follow-up. Use their company, target agencies, topic, location and dates where you know them. Discover the connected event tools before making calls; an event search on the G2X website does not prove that the MCP exposes it.

Search with the date, location, virtual and free/paid filters the current schema supports. Read the selected event's stored details: agenda, speakers, sponsors, organizer, registration link and whatever business context is available. Preserve unknown dates, times, time zones and prices as unknown. Keep listed attendees separate from likely attendees; a sponsorship or a speaker listing does not prove that a specific person will be in the room.

Use your model to prepare a short plan: why the event fits, the relevant sessions, people or organizations to research, questions to ask and useful follow-up. Link the event and the evidence. Use [Companies and people](companies.md) to resolve potential partners, and do not turn a matching name into a confirmed company or contact. Save a requested brief through [Save work in G2X](work-products.md).

When asked to save an event, check whether the destination is the user's own calendar or a shared team calendar. Use an explicit desired-state action when one is available, then read back the result. Do not blindly retry a toggle after an uncertain response. Team calendar changes can create or archive a shared event-planning workspace, so inspect the action's stated effects before changing it. A removal must match the shared scope the user intended.

Saving, exporting or subscribing to an event calendar does not register the user with the organizer. For registration, use the official returned registration link and the user's authorized browser workflow. Keep private calendar subscription links out of public documents and shared briefs.

After the event, turn the user's notes into proposed relationship updates and next steps. Use [GovCon CRM](crm.md) for requested saves. An event plan does not authorize sending outreach, inventing a completed meeting, purchasing a ticket or scheduling future monitoring.