A tenant handover can leave a landlord with three different versions of the same tenancy: the signed agreement, the caretaker’s notes and the payment ledger. When evaluating tenant management software in Kiambu, start by asking whether those records can be brought together into a clear, reviewable handover.
Decide what a completed handover means
A handover is more than issuing keys. Before a tenant moves in, the property team should know which unit is being occupied, the agreed start date, the documents received and the charges recorded. A tenancy record should distinguish the person signing the agreement from an emergency contact or someone paying on the tenant’s behalf.
For a landlord managing units across several Kiambu properties, use a stable property-and-unit reference. A description such as “the back bedsitter” may make sense to one caretaker but become ambiguous when office staff reconcile records. Keep the practical description alongside the reference, not in place of it.
Separate money received from money allocated
A payment confirmation does not, by itself, explain which charge the money settles. Record the payment reference, amount, date and payer, then show how it was allocated. An initial payment might cover several items agreed with the tenant; those items should remain distinguishable in the ledger.
Use a demonstration with a partial payment and a payment made by someone other than the tenant. Ask what happens when the payment reference is incomplete. The useful question is whether staff can investigate an unallocated receipt without quietly changing the tenant’s opening balance. Confirm any bank or mobile-money integration in writing rather than assuming it is included.
Keep inspection evidence tied to the tenancy
An inspection report should identify the unit, date and people involved. Photographs need enough context to show what they record. A folder of unnamed images makes a later discussion about condition much harder. Record keys and access items separately, including anything still to be provided.
Agree how both parties can acknowledge the record and how a correction is documented. The objective is a shared account of the handover, not a promise that software will settle every disagreement. Have tenancy documents and deposit procedures reviewed by an appropriate adviser where necessary.
Give each staff member a defined task
The caretaker may inspect the unit and record keys while the accounts team checks payments. The owner may need an exception summary rather than access to every personal document. Write down who creates, reviews and approves each part of the handover.
Test what each role can see and change using demonstration accounts. Include an attempted correction after approval. A useful history should explain what changed, when and by whom. Ask how access is removed when a member of staff leaves and how the property’s records remain available.
Rehearse one incomplete move-in
Consider an illustrative tenant whose payment is received but whose inspection is unfinished. The system should make that incomplete step visible to the team. Ask whether the handover can be marked complete prematurely, how an outstanding task is assigned and what the next member of staff sees.
This exercise is more revealing than entering a perfect tenancy with no exceptions. Use invented or anonymised details during the demonstration. Do not upload real identity documents just to test a sales presentation.
Start with a small, reconciled set of records
Before migration, compare the unit list, active tenancies and opening balances. Investigate differences instead of importing them as unexplained adjustments. Select one property for a pilot and name the person responsible for approving the starting data.
At the end of the pilot, check whether the team can retrieve a complete handover, explain an opening balance and identify unfinished tasks without searching several chat threads. Use those results to agree the next rollout step. Ask about export formats, support arrangements and data ownership before committing to a wider deployment.
Plan the next step
Ask RentalDesk to demonstrate a move-in using your handover checklist, a partial payment and an unfinished inspection. Confirm the available functions and any integration work in the written scope.
Visit RentalDesk to discuss your requirements.
Powered by Zama Systems.
