Skip to main content
Bulk student import is efficient, but it is also one of the easiest places to introduce bad identity data.

Capabilities

This import workflow supports:
  • bulk student onboarding
  • operator review before commit
  • duplicate-signal review
  • class and section placement verification

Import principles

  • treat the import file as proposed data, not guaranteed truth
  • review class and section assignments carefully
  • use duplicate signals as support for the operator, not as an automatic final answer

Why duplicate detection is hard

  • the same student may appear under multiple valid name arrangements
  • two different students may share the same or very similar names
  • schools may have inconsistent historical naming quality
  1. prepare a clean file
  2. run the import
  3. review likely duplicates or related students surfaced by the client
  4. decide whether each row should create a new student or map to an existing one
  5. verify the resulting class and section placement

Follow-up checks

After a major import, verify:
  • student counts
  • class counts
  • section placement
  • access credential expectations if the school uses Access PINs