This is Cadenza's school workflow from student discovery through inquiry management, application packet review, faculty scoring, decisions, offer letters, export, analytics, and CRM handoff. The demo conservatory is fictional and labeled as demo data; it is not a customer, partner, or real institution.
Boston, MA, US
5 degree types, $54,000 undergrad tuition
Request Info leads with status, filters, notes, export, and webhook handoff
0 packet files, 0 offer letters
Cadenza now covers recruitment visibility plus a real admissions workflow: public profiles, Request Info, inquiry pipeline, application cycles, uploaded packets, recommendation requests, fee or waiver status, prescreening, jury scoring, decisions, offer letters, CSV export, analytics, and webhook handoff.
Students see the school profile, programs, faculty, tuition notes, deadlines, and application path, then submit a Request Info inquiry.
Schools filter by instrument, country, degree, start year, and status, then update notes, follow-ups, exports, and CRM webhooks.
Admissions cycles can collect resumes, statements, transcripts, repertoire, hosted audio/video, uploaded files, fee status, and waivers.
Applicants can request letters; recommenders submit through tokenized links, and schools see received or pending letters in review.
Prescreening and jury tools support faculty review, scoring, notes, shortlists, and application status movement.
Schools release decisions, send offer letters, receive applicant responses, export records, and route events to webhooks.
These are internal demo cycles if the demo seed is present. They are not published as proof of a real institution using Cadenza.
The School OS workflow is still available; seed or connect a demo school only in an intentional demo environment.