The risky part is not the import button
Acadence connects several instructor workflows that normally live apart: class context, attendance, student records, gradebook activity data, absenteeism follow-up, schedules, and notes. Once those workflows share data, a wrong destination becomes more serious than a small UI mistake.
The current faculty-pilot work therefore treats class identity and roster membership as protected boundaries instead of assuming that every imported row is safe to write.
The roster stays authoritative
The PSCS class roster determines who belongs to the selected class. eLMS gradebook data can contribute matched activity or submission information, but it is reconciled against that roster. It cannot silently create an unmatched student or redefine the class.
Subject, academic year, semester, and roster state are validated before sensitive writes. When the destination cannot be established safely, Acadence blocks the operation for review instead of guessing.
Pilot hardening is also performance work
Safety is only useful if the app remains practical during a real teaching day. Student-directory work has moved away from repeated identity scans and unnecessary UI-thread work toward indexed grouping, cached visible results, background processing, debounced search, and asynchronous list updates.
The pilot is meant to test whether those decisions hold together on phones and tablets while an instructor moves repeatedly between attendance, records, students, notes, and follow-up—not whether one screen looks polished in isolation.