🪪 Identity Management: Name Structures in GCMS

This guidance explains how personal names must be structured and recorded in the Global Case Management System (GCMS), the official case processing system used by Immigration, Refugees and Citizenship Canada (IRCC). Accurate name recording is essential for identity integrity, document issuance, system interoperability and security screening.

🔎 Purpose of Name Structuring Standards

Name structure standards ensure consistency across immigration, citizenship and enforcement programs. Proper structuring:

  • Prevents duplicate client records
  • Ensures accurate document production (visas, permits, PR cards, certificates)
  • Supports identity verification and biometric matching
  • Maintains compatibility with international travel document standards

📂 Core Name Fields in GCMS

1️⃣ Primary Name

The Primary Name represents the family name, surname, last name, or — in cases where a person has only one name — the full legal name (mononym).

If an individual does not have a family name, the entire name is recorded in the primary name field.

2️⃣ Secondary Name

The Secondary Name includes given names (first and middle names) that remain after the primary name has been defined.

If no given name exists, this field may remain blank according to system rules.

3️⃣ Name Type

GCMS allows classification of name types, including:

  • Legal name
  • Alias
  • Preferred name
  • Other documented variations

4️⃣ Name Source

Each name entry must reference a supporting source document, typically:

  • Passport
  • National identity document
  • Birth certificate
  • Legal name change certificate

The system may also capture the document issue date and collection date for traceability.

🌍 Handling Complex Name Structures

✔ Mononyms (Single Names)

When a person has only one name (common in some cultures), the full name is entered in the primary name field. The secondary name field remains empty.

✔ Compound and Multi-Part Names

Hyphenated, compound, and multi-word surnames must be entered exactly as shown in the official document. Names must not be shortened or rearranged unless supported by documentary evidence.

✔ Non-Latin Scripts & Transliteration

Names written in non-Latin alphabets must be recorded according to the transliteration appearing in the official travel document. Diacritics and special characters must follow system capability rules.

⚙️ Data Integrity & Record Consistency

Officers must ensure that names recorded in GCMS:

  • Match the Machine Readable Zone (MRZ) of the passport where applicable
  • Remain consistent across all related applications
  • Reflect any documented legal name changes
  • Avoid unnecessary abbreviations or truncation

📌 Recording Alternate Names

If a client uses alternate spellings, aliases, maiden names, or previous legal names, these must be recorded in the alternate name fields. Each alternate name should reference its documentary source.

🛡 Why Proper Name Recording Matters

Accurate identity data in GCMS supports:

  • Security and admissibility screening
  • Information sharing with partner agencies
  • Fraud prevention and identity resolution
  • Reliable long-term client record management

📖 Best Practices Summary

  • Enter names exactly as they appear on official documents.
  • Do not modify name order unless supported by policy.
  • Record mononyms entirely in the primary field.
  • Capture all alternate names with documented sources.
  • Maintain consistency across all GCMS entries.