Board-ready.
Monday morning.

Standard SIS dashboards show academic data in isolation — enrollment counts, attendance rates, grade distributions. PCR Intelligence draws on the full platform data model, so a single report can cross enrollment data (SIS), tuition revenue and financial aid (ERP), admissions funnel and yield (CRM), and campaign giving (advancement) without exporting from multiple systems. A head of school can see enrollment trend, budget variance, admissions pipeline, and major gift campaign status on one screen. That cross-domain view is not possible when SIS, ERP, and CRM run on separate data models.

Yes. PCR Intelligence includes a report builder designed for administrative staff, not SQL developers. Administrators select data fields from a visual interface, apply filters, define groupings, and schedule delivery. Common reports — enrollment by grade and demographic, tuition receivables by cohort, admissions funnel by source, giving by campaign — ship as pre-built templates that staff can customize. Reports that require more complex logic can be built by the PCR implementation team and added to a school's report library during or after implementation.

A head of school dashboard in PCR typically shows: current enrollment vs. prior year with grade-level breakdown, open applications and admissions pipeline status, tuition receivables and outstanding balances, recent major giving activity, and a staff and student communication summary. The dashboard is configurable — heads of school choose which metrics appear and at what cadence. Data is live; there is no manual refresh or export step before a board meeting.

Yes. PCR ships with a set of board reporting templates covering the metrics most independent school boards request: enrollment trend (3-year and 5-year), financial summary (revenue, expenses, budget variance), tuition dependency ratio, admissions pipeline and yield, and advancement giving by year. These templates are formatted for presentation and can be exported to PDF. Schools can add custom metrics and adjust formatting without requiring PCR support involvement.

When SIS, ERP, and CRM run on separate systems, every cross-domain report requires a manual reconciliation step — usually a spreadsheet that someone builds the night before a board meeting, combining exports from each platform. That process introduces error and delay. In PCR, all three data domains write to the same underlying record, so a report pulling enrollment (SIS), tuition revenue (ERP), and admissions yield (CRM) is always internally consistent. There is no reconciliation step because the data was never separated in the first place.