01The Model
Two loops, running at different speeds.
Most student societies organise events. Events end, everyone graduates, and next year somebody writes the proposal again. We run a rhythm instead — and a second, faster loop that turns the people it produces into engineers with something to show.
Slow loop
The Chapter
One school or university, with its own OCS branch run by students who already study there.
- Speed
- Monthly, forever
- Where
- Inside one school or university
- Who
- Every student on that campus who signs up
- What
- Study halls, workshops, contest nights, hackathons
- Output
- A warm, counted, surveyed community — and students good enough to be trusted with real work
Fast loop
The Build Squad
A small team pulled from a chapter to build one real system for one real business.
- Speed
- 8–12 week engagements
- Who
- 3–4 students picked from their chapter
- What
- A real working system for a real small business
- Output
- A shipped product, a documented case study, a paid student, and a story the chapter recruits on
feeds
A chapter without squads is a social club. Squads without a chapter is an unlicensed agency. The coupling is the point.
02Rhythm
The calendar is the product.
Not what we run. That we always run. The same four weeks, repeated — because predictability is what turns attendance into a habit, and habit is the only thing that compounds.
| Week | Phase | What happens |
|---|---|---|
| Week 1 | Prepare | Lock topic, room, facilitator. Publish the poster. Open sign-ups. |
| Week 2 | Run | The session happens. Attendance at the door. Survey sent within the hour. |
| Week 3 | Debrief | Read the survey. Write five honest lines. Post the photos and the numbers publicly. |
| Week 4 | Decide | Pick next month from the menu. Assign the roles. Rest. |
Week 3 is the one everyone skips and the one that matters. Reading the survey and publishing the result is what separates this from every other student club in the country.
The menu — and the ladder you climb
Chapters don't invent formats. They pick from a menu with a run-sheet for each, and they earn the right to the bigger ones. A chapter that hasn't run three consecutive months doesn't get to host a hackathon.
| Tier | Format | Effort | Why it's on the menu |
|---|---|---|---|
| T1 | Peer study hall | VERY LOW | Two hours, a room, snacks, seniors helping juniors before exams. The highest value-per-rial thing here. Every chapter starts here. |
| T2 | Hands-on workshop | LOW | One skill, ninety minutes, everyone leaves with something that runs. Git, Docker, prompting, Excel, Figma. |
| T3 | Contest night | LOW | LeetCode ladder, CTF, SQL golf. Runs itself once set up, and the leaderboard generates return visits. |
| T4 | Demo & critique | LOW | Students show what they built and get real feedback. This is where we spot the next build squad. |
| T5 | HackathonEarned | HIGH | One or two days. Genuinely energising, genuinely expensive. |
| T6 | Cross-universityEarned | HIGH | Two or more chapters, one problem. Unlocks after three chapters are each stable for a semester. |
| T7 | Cross-border | MEDIUM | Online only. Dubai, China, Tanzania. Cheap because it's online — which is exactly why it should be the ambitious one. |
Online by default
Planning, mentoring, code review, workshops, contest nights, surveys, onboarding, handovers, all build-squad work, all cross-border activity.
In person, and only these
Study halls, hackathons, demo nights, and the first meeting with a new client.
A chapter whose school or university goes quiet for a semester loses its study halls. It does not lose its existence. Campus approval is a bonus, never a dependency.
03Chapters
A chapter is one campus.
One school or university, one OCS chapter — run by students who already study there, not visited by people who don't. Every campus gets its own, and each one runs the same monthly rhythm under its own name.
In plain words
A chapter is OCS inside your own school or university. Not a national committee you apply to and not an event that visits once a year — a group of five students on your campus who make sure something happens there every month. Middle East College has one. Your campus can have one. They share the same playbook, the same survey and the same dashboard, and each one belongs to its own campus.
And a chapter is five students, three hours a week
Not a committee. Five jobs, each small enough to hold alongside a degree — and every one of them trains a replacement from the first week, so nothing dies at graduation.
- 3–4 hrs
Chapter Lead
Makes sure something happens this month, and decides when there's a tie.
- 3 hrs
Programme
Owns the session itself — topic, speaker or facilitator, materials, room.
- 2 hrs
Signal
Posters, posts, reminders, and the group chat that doesn't die.
- 1–2 hrs
Records
Attendance in, survey out, numbers into the dashboard. Unglamorous. Load-bearing.
- 1–2 hrs
Understudy
Shadows one of the above and takes it over next semester. Not optional.
Two-deep on everything
No job has exactly one person who knows how to do it. Every role has an understudy from day one. This is the anti-graduation vaccine.
Terms end automatically
Two semesters, then you rotate or leave. Nobody has to be voted out, so nobody has to campaign. That's how you delete politics — remove the thing worth fighting over.
Handover is a deliverable
You don't leave a role, you hand over a folder: contacts, what worked, what failed, the passwords, the next three ideas. No folder, no certificate.
Write it, wait 72 hours, go
Anyone can propose anything in one paragraph. Others comment for three days. The Chapter Lead decides. No committees, no quorum, no meeting to plan the meeting.
Which campuses, and when
One chapter per institution, opened in waves — deliberately slowly, because one chapter that survives a full semester teaches us more than six that fold by November.
| Wave | Timeframe | Campuses |
|---|---|---|
| Wave 1 | Sept 2026 → Mar 2027 | Middle East College, Muscat University, UTAS Muscat, GUtech |
| Wave 2 | Apr 2027 → early 2028 | Sultan Qaboos University, Sohar University, NUST, MCBS, University of Nizwa, A'Sharqiyah University, Dhofar University, UTAS branch network The UTAS branches — Nizwa, Ibri, Salalah, Shinas, Ibra, Musanah, Suhar — are the single biggest reach multiplier in the country. |
| Wave 3 | 2028 | Dubai, China, Tanzania Cross-border chapters, online only. |
Your campus
can have one.
Your school or university isn't on the list? Then start its chapter. You need five people and a room — we bring the playbook, the run-sheets, the survey, and someone who has already done it.
Start a Chapter04Build squads
Three students. One real client. Ten weeks.
A café that needs an ordering system. A clinic drowning in a spreadsheet. A workshop with no way to see its own stock. Small businesses with real problems, and a small team of students who ship a working system and hand it over properly.
| Week(s) | Phase | What happens |
|---|---|---|
| Week 0 | Scoping visit | In person. One page: what hurts, what "done" means, what is explicitly out of scope. The client signs the page. This page prevents most of the disasters. |
| Weeks 1–2 | Requirements | Written requirements, screen sketches, and a written "we will not build" list. The client signs again. |
| Weeks 3–7 | Build | A demo to the client every week, no exceptions. A mentor reviews the code weekly. |
| Weeks 8–9 | Handover | Training session, written manual, credentials transferred, hosting moved to the client's own account. |
| Week 10 | Case study | Public write-up, photos, before-and-after numbers. This is what recruits the next hundred students. |
The rule that makes this safe
No orphan systems.
The predictable failure mode is a graveyard of half-finished systems that small businesses came to depend on, running on a student's personal account, breaking in month four with nobody to call. So: everything is built on the client's own accounts, every project ships with a written manual and a support window with a hard end date, and anything a squad can't hand over completely is out of scope — no matter how impressive it would be. Boring and handed-over beats brilliant and abandoned, every single time.
For students
You're picked from the chapter, not from a CV pile — showing up and being useful is the whole application. You get paid for the engagement, you get a mentor who reviews your code every week, and you finish with a real client and a real system you can point at. That is worth more than a certificate from any course.
For businesses
Four engagement sizes, from a single system that does one thing through to connected pieces with staff logins and reporting. Our first three clients are pro bono — we're buying case studies, not revenue, and we say so out loud. After that, indicative pricing on request.
Talk to us
about a project.
Guest talks, co-hosted builds, and student pipelines — reach the team on WhatsApp.
Reach us on WhatsApp05Evidence
Six numbers, published every month.
Student organisations collect ten times more data than they ever look at. So we keep three surveys and six numbers, and we publish them whether they flatter us or not.
Live chapters
Campuses that ran something in the last 35 days. Not chapters that exist on paper — chapters that moved.
Return rate
North starHow many come to a second session within 60 days. The one number that matters. A full room with a low return rate means we threw a party.
Volunteer survival
Officers still active at semester end. An early warning for burnout, months before a chapter dies.
Systems shipped
Build-squad projects delivered and handed over. Handed over is the operative phrase.
Outcomes
Members who report an internship, job or paid project they attribute to OCS. Slow to accumulate, and the only number a serious partner cares about.
Money in / money out
Per chapter, published publicly, every month. This one is a trust instrument, not a finance metric.
Your data
Asked for properly, or not at all.
Oman's Personal Data Protection Law has been fully enforceable since 5 February 2026, and an organisation whose whole premise is collecting student data is squarely in scope. So every form carries a real consent checkbox with real words — never pre-ticked — a plain-language privacy notice before anything is collected, separate consent for anything marketing-flavoured with a working unsubscribe, and a named person responsible for the data we hold.
Money
Free to join. Always.
Membership is free by default and stays that way. Chapters will be partly funded by a voluntary Chapter Fund, ring-fenced to the student's own campus, with every rial published against what it bought. Contributing buys no extra access and no privilege, and cancelling takes one tap with no conversation. The moment paying buys advantage, we've built a class system inside a student society.