Selected founder experienceWorkstream 4 of 4
Three-campus enrollment operations
Building an attendance-to-evidence workflow across three campuses
A custom application connected HubSpot roster and cohort data to role-based attendance, progress benchmarks, standardized reports, and a staff-mediated finance handoff.
Case facts
Context before conclusions.
The evidence type, scope, role, and review date are separated before any conclusion is drawn.
- Evidence basis
- Dated planning, rollout, training, production-support, and operating-procedure records.
- Operating context
- Attendance and evidence workstream within the three-campus flagship case
- Case period
- February 2025 through continuing adoption and refinement in late 2025
- Scope
- Three campuses, multiple vocational programs, instructors, cohorts, attendance, progress benchmarks, reports, and finance support
- Brian's role
- Project manager and operational liaison for requirements, priorities, reporting, stakeholder coordination, and data-quality follow-through
- Technical delivery
- A lead engineer built technical components with support, training, campus, instructional, finance, and leadership contributors
- Last reviewed
- July 19, 2026
Evidence summary
The claim stays attached to its boundary.
Dated implementation record. Each statement below includes the source class and the limit that controls how it can be read.
3: campuses in the operating scope
The workflow supported a multi-campus implementation context.
- Source
- Dated implementation and operating records.
- Status
- Documented operating scope.
- Limit
- Scope, not an adoption or performance result.
Feb - Nov 2025: documented implementation progression
The retained sequence runs from planning through production refinement.
- Source
- Dated planning, rollout, training, and support records.
- Status
- Documented implementation progression.
- Limit
- It does not establish continuous use by every eligible user.
Mar 25, 2025: reported end-to-end core milestone
The internal update reported core workflows implemented and phased rollout underway.
- Source
- Dated internal implementation update.
- Status
- Reported internal milestone; phased rollout underway.
- Limit
- It does not prove universal deployment or adoption.
Operating problem
Instructional activity needed to become consistent operating evidence.
Instructors needed a role-bound way to record attendance and progress. Administrators needed to manage campuses, programs, instructors, transfers, successive cohorts, and historical records.
Finance staff needed structured evidence at defined funding milestones before preparing or supporting invoices. The defensible baseline is that the existing process did not provide the unified access, roster, cohort, benchmark, and report workflow required for the new model.
Operating model
A visible sequence of control.
Each stage creates the context or evidence required by the next. Specialist systems retain authority where they should.
Reuse the roster source
Supply active enrollment and cohort context from HubSpot instead of recreating parallel student lists.
Assign role-bound access
Give instructors and administrators the classes, cohorts, and records relevant to their work.
Capture source evidence
Record daily attendance and structured progress benchmarks close to the instructional event.
Generate the evidence package
Produce standardized reports with program, campus, cohort, and milestone context.
Hand off to finance
Use the reports in a staff-mediated Xero-centered invoice-preparation process.
Refine production exceptions
Resolve cohort dates, roster display, transfers, successive classes, new instructors, and other edge conditions found in use.
Responsibility boundary
Systems leadership with explicit technical credit
Brian's role
Brian served as project manager and operational liaison. His documented work included requirements, priorities, leadership reporting, stakeholder coordination, data-quality attention, and issue follow-through.
Institutional responsibility
The organization retained responsibility for day-to-day operations, policy, approvals, adoption, and outcomes.
Contributors and specialist-system owners
A lead engineer owned the core technical build. Support and training contributors, organizational leaders, finance staff, campus administrators, instructors, and users shaped requirements and adoption. Contributor names remain private unless each person approves public naming.
Outside scope
This record does not attribute every implementation step or outcome to Brian and does not present the historical work as a Koro engagement.
Documented findings
What changed in the operating record.
Implementation, management visibility, and business outcomes are different claims. This list preserves those distinctions.
Planning and development were active by February 14, 2025.
Evidence class: Dated implementation record
A class was in early use in March 2025. This is pilot evidence, not a quantified outcome.
Evidence class: Dated implementation record
A March 25 internal update reported core workflows implemented from start to finish and a phased rollout to programs and instructors.
Evidence class: Dated implementation record
An all-instructor training session was scheduled for April 9. The record does not establish attendance, competency, or universal adoption.
Evidence class: Dated implementation record
September through November support records document live roster, access, transfer, cohort, and expansion issues, providing evidence of production use and iteration.
Evidence class: Dated implementation record
Platform-generated reports supported a staff-mediated finance handoff. No direct Xero API is claimed.
Evidence class: Dated implementation record
Implementation chronology
The record shows progression.
A dated milestone establishes what was reported at that point. It does not automatically establish adoption or outcome.
February 14, 2025
Planned
Planning and development were active.
An implementation start, not an outcome.
March 2025
Early use
One class was in early use.
Pilot evidence only.
March 25, 2025
Reported milestone; phased rollout
An update reported end-to-end core workflows and phased rollout.
Reported milestone, not universal deployment.
April 9, 2025
Training activity
All-instructor training was scheduled.
A scheduled event is not proof of attendance or competency.
September - November 2025
Production refinement
Support records documented live exceptions and continued refinement.
Evidence of use and iteration, not measured adoption quality.
Evidence boundary
What the evidence supports
These limits are part of the case. They are not hidden in a general disclaimer.
- The March milestone was an internal report, not a universal-adoption measure.
- The April training event was scheduled, not confirmed as completed by every user.
- No matched workload, quality, billing, payment, or adoption baseline exists.
- Synchronization direction, latency, and all exception rules are not fully documented.
- The platform created evidence for a finance process. It was not the accounting system.
- Technical security, hosting, authentication, backup, and compliance claims are excluded without primary evidence.
Koro application
What Koro carries forward
We begin with the evidence required by the downstream decision. Then we define who creates it, which system supplies identity and context, how exceptions are handled, and how the final handoff is reviewed.
Training and production edge cases are part of implementation, not a postscript.
Source classes and declaration
How to read this record.
- Relationship
- Selected founder experience completed before Koro Solutions.
- Evidence class
- Dated implementation record
- Evidence basis
- Dated planning, rollout, training, production-support, and operating-procedure records.
- Why names are withheld
- Organization names remain withheld because written authorization for named publication is not part of the approved public record.
- Measurement boundary
- No quantitative business outcome is promoted beyond the bounded delivery evidence shown on this page.
- Last reviewed
- July 19, 2026
- Commercial interest
- Brian Koro participated in the work and Koro Solutions may benefit commercially from publication.
This retrospective case is based on the source types identified on the page. It is not a controlled experiment, independent audit, accounting assurance report, compliance certification, or peer-reviewed study. No student-level data, private screenshot, internal link, organization logo, or organization-owned graphic is reproduced.