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
Recommended workflow
- prepare a clean file
- run the import
- review likely duplicates or related students surfaced by the client
- decide whether each row should create a new student or map to an existing one
- verify the resulting class and section placement
Before upload
Validation and confirmation
Treat every validation message as a row-level instruction. Correct the source file when the same problem affects several rows; use the operator review when a potential duplicate needs human judgment. After submission, keep the success and failure summary until failed rows have been corrected. Reimport only the records that still need creation.Follow-up checks
After a major import, verify:- student counts
- class counts
- section placement
- access credential expectations if the school uses Access PINs
- failed-row count and error reasons
- inactive or duplicate-looking accounts