A Meeting Attendance Report Swapped Host and Attendee Roles After CRM Handoff

A meeting attendance report with host and attendee roles reversed should be corrected from source records, not from the exported report alone. Start with the meeting ID and participant IDs, then compare the calendar event and platform attendance artifact against the CRM record.

Do not assume the CRM owner is the host. In HubSpot, `hubspot_owner_id` determines the user shown as the meeting creator on the record timeline. That is useful ownership context, but it does not prove who hosted or attended the call. HubSpot's meeting API documentation distinguishes meeting properties from record associations.

• Freeze the affected report export and note its export time.
• Use immutable meeting and participant IDs wherever the source provides them.
• Keep the original roster as an audit record while publishing a corrected roster.

Which meeting events establish who hosted and who attended?

Use the calendar event to establish scheduling context. Google Calendar event resources include `creator` and `organizer` information, plus an `attendees` collection. An attendee record can identify whether that attendee is the organizer and can include an invitation response status. Google Calendar Events

Use the online-meeting artifact to establish attendance. Microsoft Graph describes a meeting attendance report as an artifact for an online meeting or virtual event, with meeting start and end times, a total participant count, and attendance records. Microsoft Graph meeting attendance reports should be kept separate from a calendar invite because invitation and attendance are different facts.

Use a host-event record, when the meeting provider supplies one, to establish the host role. If that record is absent, mark the host role as unresolved rather than inferring it from CRM ownership or invitation data, including a participant's acceptance status.

How do you build an attendance-role correction ledger?

Create one ledger row for each participant, not one row for each email address shown in the export. Record the meeting ID, participant ID, exported role, actual role, join evidence, host-event evidence, affected CRM fields and consent impact. Also record reporting impact and corrected roster value, then name the reviewer.

Use the same participant ID through every comparison. Names and email text can vary, including through aliases. A stable source ID lets a reviewer prove that the correction changed a role, not a person.

Write the evidence value exactly as returned by its source. Add a short decision note only after the evidence fields are complete. This makes a later recheck possible without replaying the whole handoff.

• Exported role: the role in the broken attendance report.
• Actual role: the role supported by the strongest available source record.
• Affected field: every downstream CRM field, including fields used for reporting or consent that consumed the exported role.
• Reviewer: the person who confirms the corrected roster.

Which CRM fields can consume reversed roles?

Check fields that label the meeting owner, organizer, host, attendee, contact, no-show, meeting outcome, or booking source. Also inspect downstream transformations that group booked calls by rep, assign follow-up, calculate attendance, or attach a meeting to a contact.

HubSpot meeting records can be associated with existing records such as contacts and companies. Its API also supports updating meeting properties and associations. HubSpot's meetings guide makes the distinction important: changing an association is different from changing a property.

Correct the narrowest field that is wrong. If the attendance report reversed a role but the meeting association is right, leave the association intact. If the meeting owner is only a creator field, do not rewrite it to imitate a host field.

How should consent attribution be reviewed after a role swap?

Treat consent attribution as a separate review. A reversed attendee role can send a consent flag, lawful-basis note, contact preference, or communication history to the wrong participant record.

For every corrected participant, identify the consent record ID, source, timestamp, and CRM field that consumed the reversed role. Change attribution only when the participant identity and source record support the change. If the evidence does not settle it, flag the record for privacy or operations review.

• Do not copy consent from the exported host to the exported attendee.
• Do not infer consent from meeting presence.
• Do not delete the original consent audit trail.

How do you correct reports without merging distinct identities?

Keep the host and attendee as distinct participant records even when their names, domains, or CRM associations look similar. A role reversal is a classification error. It is not evidence that two identities represent one person.

Create a corrected roster keyed by participant ID, then rerun the affected report from that roster or from corrected source fields. Preserve the original export, ledger, correction timestamp, and reviewer so the changed totals remain explainable.

Microsoft Graph event resources include an event `id`, an `organizer`, an attendee collection, and an `isOrganizer` property for the calendar owner. Microsoft Graph event resources support keeping organizer context separate from attendee identity.

What should the reviewer verify before the corrected report ships?

Verify source records for every corrected role and ledger entries for every changed CRM field. Verify a documented decision for every affected consent record. Confirm that participant IDs are unchanged during the correction.

Publish the corrected roster with a correction note that identifies the affected report period and the review date. Keep the original report restricted to audit use so teams do not continue using the reversed version.

• Meeting ID and participant IDs match across the ledger and corrected roster.
• Host, organizer, creator, attendee, and CRM owner fields are not treated as interchangeable.
• Consent attribution has been reviewed where the reversed role reached a consent-related field.
• A named reviewer approved the final roster.