SCALE Education and Research Foundation
Shared systems. Clear school-level responsibility.
A four-brand systems roadmap, live feedback workflows, and one-click affiliate payment reporting brought planning and daily operations together across SCALE’s education network.
Professional work by Brian Koro during a paid cross-organization engagement before Koro Solutions. This work included affiliated schools such as Mission Career College.
Explore the work
- Systems roadmap
- 4 brandsEducation brands covered by the leadership roadmap.
- Affiliate payout reporting
- 94 transactionsReconciled in seconds with one-click reporting for Spirit Preparatory Academy.
- Evaluation follow-up
- 2 remindersAutomated reminders supported by alerts, report access, and staff routing.
The challenge
Common systems had to serve different programs.
SCALE’s affiliated education organizations had distinct audiences and programs, alongside shared needs for websites, intake, payments, learning platforms, and reporting. Coordination had to reach beyond the technology: academic, administrative, and technical teams needed a common direction while each school retained responsibility for its own work.
Brian’s contribution
Connect the roadmap to everyday responsibility.
Bring shared needs into one roadmap.
Brian prepared and presented a systems-improvement roadmap spanning four education brands. It grouped website modernization, CRM and intake, online payments, platform coordination, systems support, and reporting into a common view for leadership.
The roadmap brought shared infrastructure and local program needs into the same discussion, providing a structure for prioritizing systems work.
Launch feedback workflows with a route for action.
Brian launched instructor-evaluation and student-concern workflows in HubSpot after coordinating review and approval. The implementation included lifecycle-triggered evaluation sends, two automated reminders, real-time alerts, report access, admissions/HR routing, and a Student Concerns page.
The workflow covered both participation and responsibility. Requests and reminders supported feedback collection; alerts, access, and routing connected incoming submissions with the teams responsible for acting on them.
Turn a payout export into a usable report.
For affiliate Spirit Preparatory Academy, Brian built a one-click Google Apps Script report that reconciled 94 payout transactions and produced program-level gross and net totals in seconds.
The automation combined transaction reconciliation with program-level views in a repeatable output. Staff could generate the report directly from the spreadsheet, making the payout data easier to review by program.
Program-level reporting turns transaction detail into a repeatable review process. Illustrative image. Connect system changes with the people using them.
Brian coordinated requirements, onboarding, integration, and staff training across HubSpot, Acuity, Acellus, and attendance systems. He translated academic and administrative needs into workflows, reporting requirements, and guidance for technical contributors and staff.
He also designed and delivered all-schools records-readiness training on records ownership, evidence preparation, current documentation, and retrieval. This connected the systems work to the daily responsibilities of the people using it.
A feedback process needs more than a form.
The configured evaluation and concern processes addressed four different parts of the operating work.
| Part of the process | What Brian configured | Purpose |
|---|---|---|
| Request | Lifecycle-triggered evaluation sends | Connect the request with the relevant stage |
| Follow-up | Two reminders | Provide a defined follow-up cadence |
| Visibility | Alerts and reporting access | Make incoming information available to staff |
| Responsibility | Admissions/HR routing and a Student Concerns page | Connect submissions with a route for action |
What the work produced
A shared direction, supported by working-level detail.
The engagement produced a four-brand systems roadmap and leadership presentation, launched evaluation and student-concern workflows, one-click affiliate payout reporting, platform onboarding and workflow guidance, and delivered records training. These examples span foundation-level coordination and work within affiliated schools, including the Mission Career College engagement described separately.
The takeaway
Standardize the process and name the local owner.
Shared infrastructure is most useful when each team knows its responsibilities within it. Start with one process that crosses schools or departments and check the trigger, follow-up, access, and responsible team together.
Ask this in your organization
- Which steps should be shared, and which belong to an individual school?
- After a submission arrives, who can see it and who must respond?
- Do staff have guidance for the work they actually perform in the system?
Bring the problem to Koro
Which process needs coordination across your teams?
Tell us which schools or departments are involved and where ownership or system use becomes unclear. We’ll review the context and help identify the next practical step.
Discuss your systems priorities