HR Foundation Package for Software training institutes
What this looks like in your business
Most software training institutes begin with a founder who teaches, a counsellor who sells and a friend who looks after the lab. Years later there are trainers on three kinds of arrangement, a placement desk, batch coordinators and perhaps a second centre, and the HR basics still live in chat messages and memory. The HR Foundation Package is what an owner reaches for at that point. GullyHR writes the handbook, the core processes, the letters and the first records in the institute's own terms, so a branch head can onboard a trainer or handle a leave request without phoning the founder.
Why institutes outgrow informal HR quickly
An institute changes shape faster than its paperwork. In the first year, the founder agrees timings and pay with a trainer over a call. Then a second trainer joins with a day job elsewhere, a counsellor is hired on an incentive for admissions, and a batch coordinator starts handling student complaints. Each person was promised something slightly different, nothing is written in one place, and the founder is the only person who remembers what was agreed with whom. The strain shows at predictable moments: a trainer asks whether leave during a live batch is allowed, a new counsellor asks what the incentive covers, a lab administrator is unsure who approves an equipment purchase. The founder answers each from memory, and answers drift. A foundation set of documents stops the drift. It gives the institute one handbook for how trainers, counsellors and support staff work, one written process for the actions that repeat, and one set of records showing who joined, on what terms and with which responsibilities. Without it, every new hire widens the gap between what the owner intended and what each employee understood. The package is meant for institutes at exactly this point, with real people and no real system.
What the package sets down in your terms
GullyHR begins by listing what already exists: appointment letters, the trainer allocation sheet, the counsellor incentive note, any messages that act as policy. From that, the handbook is written around how an institute works, covering batch timings and substitution, rules on teaching alongside outside employment, ownership of course material, counsellor conduct when speaking about placement, lab and licence care, and how student complaints reach a named person. Five core processes are then written as one-page documents, for instance joining a trainer, requesting leave during a running batch, handing over a batch, recording a student complaint and exiting a trainer who holds course files. Each is tested with the people who will use it before it is handed over, and standard letters and a first set of employee records follow, with a simple report on a schedule agreed in writing. Scope and fee are agreed in writing before the work starts. The package is built from your own materials, not copied from another institute. The wording of any clause that touches employment law is reviewed by your own legal adviser before issue.
Take a branch head covering a trainer's exit
Take a cloud and DevOps institute whose senior trainer announces he is leaving at the end of the month, in the middle of a batch. Before the package, the founder would have telephoned him, the branch head would have guessed at a notice arrangement, and the course material would have walked out with his laptop. With the package in place, the branch head opens the exit process, a single page. It asks for the notice date, names the person who will take over each live batch, lists the master files to be copied into the institute's own storage and says who signs that the copy is complete. The handbook already states who owns course material, so no argument is needed on the last day. The standard letter records the handover. The branch head tests the process on this exit and notes one step that was unclear, which GullyHR revises. The founder decides on the replacement trainer and any pay offer, as those decisions stay with the owner, while the branch head runs the steps without reference to memory.
Who holds each document after handover
A foundation is only useful if someone looks after it. GullyHR hands over the documents with a short note on who owns each. The branch head keeps the joining and exit processes and the employee records. The curriculum lead keeps the rule on course material and its revision dates. The placement coordinator keeps the approved wording for what counsellors may say about placement, so the handbook and the sales desk agree. The lab administrator keeps the equipment and licence routine. The founder keeps every decision about pay, structure and policy, along with the choice to change any document. The simple report, on a schedule agreed in writing, shows joiners, exits and open items so the founder sees the picture without asking. GullyHR does not give legal advice, so the letters and the handbook go to your own adviser before they are issued, and the package does not cover payroll or filings. Once the basics are in place, the institute can grow into the ongoing management or policy packages if it wants to.