The record of record, for every department.

A Student Information System is the operational core of a school's academic records. It manages enrollment, student demographics, class rosters, grades, transcripts, attendance, scheduling, and family contact information. Every other administrative function — billing, admissions, reporting — should be able to draw on the SIS record without re-entering data. In PCR, the SIS is the canonical student record shared by every other module: ERP, CRM, Intelligence, and AI all read and write from the same file.

Most standalone SIS products stop at the academic record and require integrations to reach billing, admissions, or advancement. PCR's SIS is connected to ERP (tuition billing, payroll, financial aid), CRM (admissions funnel, alumni records), and Intelligence (enrollment dashboards, board reports) without a sync job or middleware. A student's financial status is visible to the registrar. An applicant's record converts directly to a student record on acceptance. No duplicate data entry, no reconciliation step between systems.

Yes. PCR's SIS supports roster sync and grade passback with major LMS platforms. Class roster changes made in PCR propagate to the LMS automatically. Grade data entered in the LMS can be reflected in the PCR gradebook. The specific integration depends on your LMS vendor — integration scope is documented in the implementation proposal. PCR has active integrations with Canvas, Google Classroom, and several independent school LMS platforms.

PCR is designed for schools operating across multiple campuses, time zones, and countries. The data model supports separate academic calendars, grading scales, and transcript formats per campus while maintaining a single consolidated view at the group level. Finance teams see a consolidated ledger; heads of school see enrollment and demographics by campus or system-wide. International schools with students from multiple countries can configure custom fields, currency handling, and report formatting per campus.

PCR migrates the full student record: demographics, enrollment history, transcripts, grades, course history, attendance records, family contact data, and custom fields. Financial history (billing records, payment history, financial aid awards) migrates as part of the ERP migration. The migration scope is documented field by field in the implementation proposal before you sign. No data is assumed — every field that matters to your school is mapped explicitly, and schools receive a validation report before go-live.