Run the Colony Semester¶
The colony semester demonstrates that the team can recruit, develop members, deliver programs, govern itself, and ask for help before problems become emergencies.
Before setting the calendar, review the advice gathered from earlier colonies. The recurring lesson is to begin with a manageable rhythm, communicate consistently, and expand only after the team can deliver reliably.
Initial pledge class size¶
Plan for fewer than 20 pledges during the colony's initial semester. The first class should remain small enough for the founding EBoard to provide consistent education, individual support, mentorship, safety oversight, and useful feedback while the chapter is still testing its systems.
Treat 20 as a ceiling, not a target. Set the final class size from the number of trained educators and mentors available, the EBoard's weekly capacity, campus requirements, and the quality of support the colony can sustain. If the applicant pool is larger, keep the published selection process consistent and do not lower standards simply to fill every available place.
Monthly National check-in¶
Use the same short agenda each month:
- Progress since the last meeting
- Wins worth repeating
- Challenges or risks
- Support needed from Nationals or a mentor chapter
- One to three goals before the next meeting
Record owners and due dates in a shared action summary. Keep private member or applicant information out of public documentation.
First check-in: after recruitment¶
Confirm that the initial pledge class remains below 20. Review whether promotion reached the intended campus audience, which event formats worked, whether the process was manageable for the EBoard, and how new members will remain engaged. Document reusable lessons, not applicant details.
Second check-in: member development¶
Review the member-development timeline, understanding of KTP's history and pillars, attendance patterns, officer workload, constitution questions, and any retention risks. Adjust the plan early rather than protecting the original calendar.
Third check-in: charter readiness¶
Confirm that governance is finalized, the founding class is prepared, required private forms are complete, the EBoard can explain its operating systems, and unfinished issues have owners.
Evidence of a sustainable colony¶
| Area | Evidence to review |
|---|---|
| Governance | Meetings occur, decisions are recorded, and the constitution is followed. |
| Membership | Recruitment and development processes are repeatable and school-compliant. |
| Programming | The colony has delivered activities across several KTP pillars. |
| Operations | Calendars, rooms, budgets, and responsibilities are maintained. |
| Culture | Members can describe the chapter's purpose and expected conduct. |
| Support | The colony communicates consistently with Nationals and its mentor chapter. |
Suggested operating rhythm¶
| Weekly | Monthly | End of semester |
|---|---|---|
| EBoard and general meetings; education safety review; calendar and task review; finance exceptions; public-detail check | National check-in; budget close; access review; recruitment or program metrics; officer-capacity review | Reconciliation; compliance package; constitution and policy review; access transfer; program retrospectives; charter-readiness record |
Use the detailed founding guides for recruitment, new-member education, marketing and outreach, finance, and technology.
Next: Charter and hand off.