HR Foundation Package for Healthcare software providers
What this looks like in your business
Plenty of healthcare software companies reach their first dozen staff with HR held together by a shared drive and the founder's memory. Developers, implementation engineers and support executives have all joined on slightly different terms, and nobody has written down how a go-live roster is set or who can see live patient data. The Foundation Package is for the owner who wants the basics in place before the next hospital contract lands. GullyHR writes, tests and hands over a handbook, five core processes, standard letters, first records and a simple report, on a schedule and fee agreed in writing first.
Basics missing while the product keeps shipping
In a young software company the product always comes first, and HR follows by accident. A developer joins on a verbal understanding, an implementation engineer is told that travel will be reimbursed and a support executive agrees to cover nights until a hire is made. Months later the arrangements differ person to person, and nobody can say which is the rule. This matters sooner here than in a quiet office, because the work is unusual. Staff touch real patient data in test and live systems. Engineers are away from home for weeks at a go-live. Support calls come at all hours and the clinical knowledge sits with one adviser. Each of these needs a written rule that a new manager can apply without asking the founder, because the founder is in a hospital meeting or on a call with a client. A foundation package suits the business that has grown past informal habit but has no HR function to write the rules. The aim is not a thick binder that nobody opens. It is a small set of documents that match how this company actually staffs a go-live, answers a call and protects patient information.
Which five processes to write first
GullyHR starts from your own working week rather than a standard list. Joining comes first, because a developer who will see patient data needs a confidentiality undertaking and access approval before the first login, and an implementation engineer needs a clear brief on travel and stay. Leave and attendance follows, since support rosters and go-live weeks make the usual rules awkward, and an engineer away for three weeks needs a clear rule on leave before leaving, not after returning. Third is the travel and expense claim process, written so a claim has a deadline and an approver. Fourth is the night and out-of-hours support rule, setting who is on, what is given back and how the call is logged. Fifth is exit, covering the return of laptops, removal of access to client systems and a handover of any open go-live tasks. Each process is a one-page document, tested on a real recent case before it is handed over. The handbook is written in plain words for developers and support staff, and the standard letters cover offer, confirmation and the common notices your managers will otherwise improvise.
Suppose a founder with twelve people and a deadline
Suppose the founder of a laboratory information system company has a dozen staff, a diagnostic lab chain waiting for go-live next quarter and no written HR at all. The delivery manager, Rohan, is hiring two implementation engineers and asks what leave and travel terms to offer. The founder has given three different answers in the last year. GullyHR sits with Rohan and the founder, agrees the terms the business can honour, and writes them into the joining process and the offer letter template. The test is a real case: a tester joining on Monday. The process is run against her file, and the team finds that no one had decided who approves her access to the test database holding anonymised lab results. That gap is settled and written in. By the end of the week Rohan has a one-page joining process, a letter he can send himself and a first employee record. The founder decides the terms and the approvers, and GullyHR records them without second-guessing the choice, then leaves Rohan with a process he can run himself.
Owners, records and what you keep
A foundation is only handed over once each document has an owner, and the founder has read it. Settle who keeps the employee records, whether the founder, an office manager or the delivery manager, and where they live. Agree who approves travel claims and who signs the joining letter. Name the person who rosters night support and the person who confirms access to client systems has been removed at exit. The simple report, on a schedule agreed in writing, can show joiners, leavers, open claims and support hours worked, and someone must be named to read it. Standard letters are checked by your own legal adviser before they are issued, because wording and local rules differ by country. GullyHR writes, tests and hands over, and the package ends there. Running these processes each month, chasing claims and keeping records current is a separate ongoing service if you want it. What stays with you is every choice about terms, people and pay, and the habit of using the documents once they exist, which only the managers can build by applying them on the next joiner, claim and night call.