HR Foundation Package for Management colleges
What this looks like in your business
Some management colleges grow faster than their HR paperwork. An autonomous school attached to an engineering college may still use the parent's staff rules, a trust-run institute may hold faculty terms in old letters, and the executive MBA runs on goodwill with weekend teachers. The Foundation Package is the fixed-scope piece an owner or director reaches for when there is no real HR system yet and the next intake is close. GullyHR writes, tests and hands over a handbook, five core processes, standard letters and a first set of records, shaped around faculty, visiting teachers, placement staff and administration.
A college that outgrew its borrowed rules
The usual gap in a young or fast-growing management college is that the people rules belong to someone else. A business school attached to an engineering college follows a handbook written for lecturers in engineering, which says nothing about case writing, industry projects or placement season. A trust-run PGDM institute holds appointment letters in a cupboard, each worded a little differently. Visiting faculty arrive for a term with a phone call and a rate agreed in a corridor. The programme chair for the weekend MBA keeps her own notes on who teaches which session. Nothing is wrong yet, but each new hire widens the difference between what was promised and what is written. Student feedback begins to decide careers without a stated rule. Placement staff work late for weeks, and nobody has written how that time is recognised. A foundation package puts the minimum in place before those differences turn into disputes, and it does so in a sequence the college can absorb alongside classes, admissions and the placement calendar.
What the first foundation set looks like here
GullyHR begins with a baseline of who works at the college and under what paper. It lists core faculty, visiting faculty, placement and corporate relations staff, admissions and marketing staff, executive education coordinators, research associates and student services staff, and checks each group against the letters held. The handbook is then written for this college, with separate sections where the groups truly differ: teaching and research expectations for core faculty, session rules for visiting teachers, season rules for placement staff. The five core processes are chosen with the director. In a college they are likely to be core faculty joining, visiting faculty engagement, leave around exam and placement weeks, the appraisal cycle including how student feedback is read, and exit with handover of course material. Each is a one-page document, tested on a real case before it is handed over. Standard letters follow, and then a first set of records: a core faculty file, a visiting register and a placement hours sheet. Nothing is invented from a template; the gaps found in the baseline decide what is written first, and what can wait for a later stage.
A worked example at an engineering college's business school
Suppose a business school attached to an engineering college has been running on the parent's staff handbook for eight years, and the new director wants its own. GullyHR's baseline finds seventeen letter formats, a visiting register kept in two spreadsheets and no written rule on who may approve a leave request during placement week. The director and GullyHR agree five processes and a handbook with a faculty chapter, a visiting chapter and an operations chapter. Before handover, the visiting engagement process is tried on a real case: a banker invited to teach a derivatives elective. The programme chair raises the request, the director approves the rate, the coordinator issues a letter and the register is updated. One step breaks, because accounts want a signed session log before paying, and nobody had said who collects it. The process is rewritten, retried and then accepted. The director decides the rate bands and what the parent institution must approve. GullyHR writes the document and does not set the pay. GullyHR also keeps a short note of what was tried, so the next process is written faster.
Owners, records and what stays with you
A foundation set only lasts if someone holds it. GullyHR agrees a named keeper for each record before handover: the registrar or an administrator for the core faculty file, the programme office for the visiting register, the placement head for the hours sheet, and a student services lead for feedback summaries. Each process names who starts it, who approves it and who closes it, and the standard letters carry a short note on who may sign them. The simple report is agreed in writing, for example faculty joined and left, visiting sessions logged against engaged, and placement season hours, and it is sent on a set date to the director. What stays with the owner is every decision the documents record: pay bands, incentives for research or placements, the terms offered to visiting faculty, and the rules for outside consulting. The handbook and letters go to your own legal adviser before issue, because whether they fit local rules is not a point GullyHR confirms. The next intake then starts with the same documents in every programme office.