Implementing Multi-School Management

Hello Gibbon Community,

Our organization oversees multiple schools under a single foundation, and we’re keen on using Gibbon’s flexible features to streamline operations. I understand that a multi-school installation feature is in Gibbon’s future roadmap, but I’d like to get started now by customizing or working within the existing framework.

Here are a few questions I hope the community can help with:

  1. Implementation Approach
  • How would you recommend setting up multiple schools using Gibbon’s current version?
  • Is it better to maintain separate installations for each school, or can a centralized setup be configured?
  1. Business Processes to Cover
  • What key processes should be included to manage multiple schools effectively? For example:
    • Centralized vs. localized admissions and enrollment.
    • Cross-school reporting and analytics.
    • Resource sharing (e.g., staff, facilities).
    • Consolidated communication and announcements.
  1. Technical Customization
  • Are there recommended plugins, modules, or tweaks to make Gibbon more suitable for multi-school operations?
  • What challenges should I anticipate in areas like data segregation, user permissions, or scalability?
  1. Future Proofing
  • Since Gibbon is planning a dedicated multi-school feature, how can I design my setup to ensure an easy transition to this functionality when it becomes available?

I’d appreciate insights, suggestions, or success stories from anyone who has tackled similar projects.

Thank you!
Looking forward to your thoughts!

1 Like

Hey, good question, and Ihope this feature would be added soon, meanwhile, I have worked a way around, We are managing 5 different locations under one school. Look at the document on the link below, it may give you an idea how I did it; I am open for feedback and suggestions. Thanks!

Also, please note thats this is a few weeks old file and ever since I did lots of changes, especially renaming year groups and form groups, so they can allign more to the rules of naming the fields of a database.

@hwaeen how did you take care of "Sequence Number " in year groups as it is important for automating rollover at the end of the academic year. @triastanto very good question and waiting for that roadmap as this is a challenge when it comes to multi-school setup.

Hi, Kelvin. There are 55 Year groups in toal and sequenced them from 1 to 55. Any suggestions? I will appreciate. Thanks!
I was having some issues with Roll Over but there are were so many other things to work on and to learn that I started with year 2025 so I would have a whol year to set it up before worrying about Roll Over.

@hwaeen Since after you setup, the system will be used for longer time, I’d suggest you do a multiple installation (tedious but safe) for future switch of multi-school as per the roadmap Gibbon Road Map | Gibbon Documentation.

It’s great to see that Multi-School Installation is being considered for the future.

Sometimes it becomes necessary to maintain separate Gibbon installations for each school within a school district. This is often the case when schools have differing:

  • Administrative teams
  • Start and end dates for school years/terms
  • Daily schedules, including start and end times

I’ve been working on a method to generate reports tailored for school districts.

Example 1: District-wide student enrollment counts presented as both a pie chart and a bar chart.

Example 2: Summary data for an individual school.

I’ll be sharing more examples in the coming days and weeks.

Don’t hesitate to reach out with any questions.

1 Like

A very usefule module to show data from multiple Gibbon databases [assuming cumpases will be database].

Thank You so much for the suggestion.

Hi, which module is that you mentioned?