HR Foundation Package for Banks
What this looks like in your business
For a bank, the Foundation Package means writing down the basics that branch life keeps in people's heads. A newly licensed bank, a small cooperative or a business correspondent network runs on one manager's memory of how transfers, cover and targets are handled. An owner or chief executive reaches for the package when branches multiply, a first transfer causes an argument, or head office cannot say who approved what. GullyHR writes a handbook, five short processes, letters and first records around the branch, the counter and the zone, tests each one with your staff, and hands them over.
Where a young bank has no written rules
A bank grows by adding branches, and each new branch arrives with a manager who has brought habits from somewhere else. One manager lets tellers swap counters freely. Another insists on written approval. One treats a sales target as a conversation and another as a threat. At head office there is no handbook to settle which is right, so every dispute becomes a personal ruling. Transfers are the sharpest case, since a posting can end a person's career and nothing says how much notice, explanation or appeal they should expect. Promotion has the same gap: the top seller gets the branch and no one tells them what a manager must now do. Without written basics, the first serious complaint becomes a precedent by accident. The Foundation Package is meant for exactly this stage, when the bank is real enough to need rules but too young to have an HR department that writes them. It turns the habits of the best managers into a shared standard that every branch can follow.
The first documents a bank should have
GullyHR starts by asking who does what across the branch roles: manager, teller, customer service officer, relationship officer, credit processor and back-office clerk. The handbook is then written for those roles, not borrowed from another sector, with plain wording on cover at the counter, behaviour with cash and customer records, targets and how they are explained, and how transfers are communicated. Five core processes follow as one-page documents. Joining, so a new teller has access, training and a named buddy before the first shift. Branch cover, so a short branch has a known route to borrow staff. Transfer, with the reason, notice and conversation recorded. Target setting, split by role. Exit, so keys, access and customer files are handed over on a checklist. Standard letters sit beside them: offer, appointment, transfer order, warning and exit. A first employee record and a simple monthly strength report complete the set. Your legal adviser reviews the wording before anything is issued. Where the bank already has a practice that works, such as one manager's careful cover routine, GullyHR keeps it and writes it down rather than replacing it.
Testing the transfer process with real branches
Suppose the bank has just opened its twelfth branch and a relationship officer in an older branch is asked to move there. Before the process is handed over, GullyHR tests it with the zonal manager and two branch managers. The one-page transfer process asks for the reason, the date the person is told, the date they move, who covers the vacated desk and what the person was promised about their grade. The test turns up two problems. The zonal manager has no place to record the conversation, and the draft letter does not say who the person speaks to if they object. GullyHR adds a short conversation note to the employee file and names the head of HR as the contact for objections. The letter is rewritten and tested again on a second, invented posting. The owner then decides one real question: whether a transfer order may be issued before the conversation or only after it. That ruling is written into the process. Each document is kept short enough that a branch manager reads it once and uses it.
Who keeps the basics alive after handover
A foundation set that nobody maintains decays within a year, so handover names owners. Head-office HR holds the handbook and the five processes and decides when a branch practice should change them. Branch managers use the letters and templates unaided and keep the employee record for their own branch current. Zonal managers send the monthly strength report on the agreed date. The bank's accountant or payroll provider continues to handle pay, and GullyHR does not run it. The owner keeps every decision on people, pay, grades and transfers, as well as any legal question about banking conduct or employment, which your own adviser confirms. Scope and fee are agreed in writing before the work starts, and you receive the documents in editable form so they stay yours. If the bank later wants help running these routines each month, that is a separate conversation about ongoing management and not part of the package. The process is then issued with the corrected letter, and the zonal managers are briefed on it in one short meeting. Every later transfer uses the same page.