Reconcile conflicting attendee names in meeting notes with Gemini

An attendee name reconciliation register is useful when you need to resolve conflicting name spellings without merging distinct people. The result should make the underlying records easier to inspect and the next decision easier to explain. This guide develops a specific attendee name reconciliation register with a source schema, operating rules, a fictional example, and observable review checks. It is intended for someone who already has the underlying material and needs a dependable way to organize it.

Product references checked: 7 October 2026. The examples and implementation specifications below are original editorial guidance. They illustrate expected behavior and have not been presented as a benchmark or as a completed tool tested inside another product.

Define the deliverable and its scope

Reconcile only the supplied meeting record and authorized roster. This is separate from assessing attendance or searching for personal information.

Write the acceptance standard before asking Gemini for a draft. A reviewer should be able to identify the mention id, inspect the original name, and understand the correction proposal without guessing what a blank field means. Decide which records belong in the deliverable, which are out of scope, and who can confirm the final interpretation. Keep those choices visible in the working specification rather than leaving the assistant to supply convenient defaults.

Prepare the source package

Gather meeting notes, an authorized attendee roster and explicit identity corrections. Assign source IDs and preserve original wording wherever a small difference could change the outcome. Record the collection date and the version of each source. If two files disagree, keep both references and mark the conflict. Do not replace a disputed value with whichever one produces the cleanest display.

Use a small representative subset for the first draft. Include one ordinary record, one incomplete record, and one record that challenges an important rule. For this task, use the following as the incomplete-record check: Two plausible roster matches leave the mention ambiguous. Preserve the original package separately from the assistant's transformed output. A polished result is easier to audit when its IDs still lead back to the original supplied material.

Define the record schema

Treat mention id as a deliberate part of the data model. Source note location for each name mention. Keep its representation consistent when you sort, filter, or revise the output. The original name field has a different job: Exact spelling retained from the notes. Combining these fields into one sentence can hide the distinction the reviewer needs to inspect.

Pay particular attention to roster candidate and evidence. The former means: Proposed match to an authorized attendee entry. The latter means: Explicit source for the match or distinction. Store them separately and label both in the detail view or report. This makes disagreements visible at the exact point where they affect the result instead of burying them in a general note at the bottom.

Apply the task rules

Rule 1. Similar spelling alone never confirms that two people are identical.

Rule 2. Retain original mentions and the reason for every proposed correction.

Rule 3. Keep names and action ownership separate until identity is confirmed.

Rule 4. Do not add people from private directories or unrelated meetings to fill gaps.

Make these rules inspectable alongside the attendee name reconciliation register. Ask Gemini to describe how each rule affects a record and what should happen when the supplied data does not establish an answer. A rule written in prose still needs a defined output state. Use an explicit missing, disputed, or not-applicable label where appropriate, and reserve a valid zero or an empty result for cases where it has a defined meaning.

Work through a fictional example

A fictional meeting note mentions A. Khan and Ali Khan. The supplied roster contains Ali Khan and Ayesha Khan, so the abbreviated mention remains ambiguous. A later authorized correction explicitly identifies A. Khan as Ayesha. The register records that evidence and proposes the full name at its original location. An action assigned only to A. Khan remains unresolved until the correction is reviewed. A misspelled Aly Khan can be a candidate for Ali but is not silently merged. The corrected notes preserve a review trail showing which evidence established each identity.

Use the example as a review fixture rather than as real operational data. Before generating the output, write down which fields should be populated and which should remain unresolved. Then compare the generated result with that expectation. If Gemini supplies an unsupported value, correct the underlying instruction or calculation rule instead of merely editing the one visible record. Otherwise, the same error may return when the next record is processed.

Build the first version

Ask Gemini for an extraction table before asking for a polished attendee name reconciliation register. Review a few source references against the original material and correct the table first. Then request the reader-facing output using the approved fields. Keep changes to the source document separate from this drafting pass so a mistaken extraction does not automatically overwrite the authoritative record.

The final review should explicitly cover resolution state: Confirmed, ambiguous or no roster match. Also check correction proposal: Reviewed replacement spelling with preserved mention ID. These two fields often establish whether a reader can act on the result. Make missing information visible beside the affected record and ask the owner for the exact evidence needed to resolve it.

A reusable prompt

Create a attendee name reconciliation register from the supplied source package. Goal: resolve conflicting name spellings without merging distinct people. Use these fields: Mention ID: Source note location for each name mention.; Original name: Exact spelling retained from the notes.; Roster candidate: Proposed match to an authorized attendee entry.; Evidence: Explicit source for the match or distinction.; Resolution state: Confirmed, ambiguous or no roster match.; Correction proposal: Reviewed replacement spelling with preserved mention ID.. Preserve source IDs. Rules: Similar spelling alone never confirms that two people are identical. Retain original mentions and the reason for every proposed correction. Keep names and action ownership separate until identity is confirmed. Do not add people from private directories or unrelated meetings to fill gaps.. First explain the proposed data model and unresolved inputs. Then build the smallest usable version. Use only supplied facts; label the demonstration fictional. Do not invent approvals, thresholds, owners, or external integrations. Include an empty state and explain the expected result for these checks: Two plausible roster matches leave the mention ambiguous. An explicit correction resolves only the mentions it identifies. An unresolved identity does not receive an invented action owner.

Review behavior and edge cases

Check 1. Two plausible roster matches leave the mention ambiguous. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.

Check 2. An explicit correction resolves only the mentions it identifies. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.

Check 3. An unresolved identity does not receive an invented action owner. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.

Repeat the checks after adding another source record or changing the presentation. A working first example does not prove every record is handled correctly. Pay attention to retained selections, stale derived values, and unexplained changes in the number of displayed records. For attendee name reconciliation register work, the reviewer must be able to tell whether a difference comes from new evidence, an edited rule, or merely a changed view.

Maintain the reviewed version

Keep a version label, source cutoff, and short change record with the finished attendee name reconciliation register. Record who approved the rules and which demonstration cases were reviewed. When the source package changes, preserve record IDs and revisit the checks affected by the change. Do not treat yesterday's verified result as evidence that today's replacement input is complete.

Before handing the output to another person, review its audience and the material it contains. Use a sanitized demonstration for general feedback when the real source package is confidential. Explain whether changes are saved, whether the output is a preview, and which source remains authoritative. If persistence or sharing is required, verify that behavior in the actual account and intended environment instead of assuming it from a successful preview.

Frequently asked questions

Sources and related reading

Consult the current primary references for account-specific availability and controls: Gemini in Google Docs documentation, Google source-management documentation. The schema, examples, prompts, and review checks here are editorial recommendations rather than documented built-in features.

For broader context, read the related Gemini workflow guide.