Skip to content
DDelTech MUNDocs

Recruitment overview

The pipeline from an application form to a society member, in one picture.

Recruitment is how the society takes on new members. It runs at /recruitment, is organised into cycles, and has its own roles that are not the admin roles.

Intakeform importGDpanelPIone to oneDecisionselect or notSocietyseparate stepbypass, with a recorded reason

Selecting someone and adding them to the society are two deliberate actions.

A candidate moves left to right. Every transition is recorded, and none of them happen automatically.

The shape of it

An Administrative Council member creates a cycle and configures it: how long each stage runs, what candidates are scored on, and what the selection email says. Then the cycle opens.

Candidates arrive by importing a Google Sheet of form responses, or through a live form connection. Nobody is typed in by hand.

Junior Council members build group discussion panels and run them. Senior Council members run interviews. Both score against the cycle's rubric.

At the end, the Administrative Council finalises results and, as a separate action, adds selected candidates to the society.

Things that surprise people

Recruitment authority is not admin authority. A Junior Council member has real power inside /recruitment and none at all inside /admin. A global admin is automatically an Administrative Council member on every cycle, so a stuck cycle can always be repaired.

Adding someone to the society can only ever grant a non-privileged role. Recruitment structurally cannot hand out console access. That remains a separate, deliberate change in users.

Nothing is inferred. A candidate's result is stored because somebody set it, never computed from their scores. The system will not decide who passed.

Everything is recorded. See the audit trail.

The pages in this section