{"id":4290,"date":"2026-10-07T06:59:05","date_gmt":"2026-10-07T06:59:05","guid":{"rendered":"https:\/\/rentaldesk.co.ke\/blog\/?p=4290"},"modified":"2026-10-07T07:26:27","modified_gmt":"2026-10-07T07:26:27","slug":"property-unit-naming","status":"publish","type":"post","link":"https:\/\/rentaldesk.co.ke\/blog\/property-unit-naming\/","title":{"rendered":"Property Unit Naming: 7 Powerful Checks for Clear Records"},"content":{"rendered":"<p>Property unit naming helps Kenyan rental teams connect the correct tenant, invoice and maintenance request. Give every unit a consistent identifier and use it across your operational records. Informal labels such as the upstairs room can become confusing when several buildings contain similar layouts or repeated door numbers. Confirm that caretakers and office staff use the same identifiers during routine handovers.<\/p>\n<p>Before importing information, compare your unit list with the <a href=\"https:\/\/rentaldesk.co.ke\/blog\/rental-management-software-setup-guide-kenya\/\">RentalDesk setup guide<\/a>. Check for duplicate labels, missing property references and outdated occupancy details. Assign someone to resolve uncertain entries rather than filling gaps with guesses during the import.<img decoding=\"async\" src=\"https:\/\/rentaldesk.co.ke\/img\/screenshorts\/units.webp\" alt=\"property unit naming \u2014 RentalDesk\" loading=\"lazy\"><\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_83 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/rentaldesk.co.ke\/blog\/property-unit-naming\/#1_Give_every_unit_a_stable_identity\" >1. Give every unit a stable identity<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/rentaldesk.co.ke\/blog\/property-unit-naming\/#2_Write_a_convention_that_ordinary_staff_can_apply\" >2. Write a convention that ordinary staff can apply<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/rentaldesk.co.ke\/blog\/property-unit-naming\/#3_Compare_existing_records_before_importing_anything\" >3. Compare existing records before importing anything<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/rentaldesk.co.ke\/blog\/property-unit-naming\/#4_Separate_unit_identity_from_occupancy_and_balances\" >4. Separate unit identity from occupancy and balances<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/rentaldesk.co.ke\/blog\/property-unit-naming\/#5_Check_the_convention_on_site_and_during_handover\" >5. Check the convention on site and during handover<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/rentaldesk.co.ke\/blog\/property-unit-naming\/#6_Control_changes_and_document_exceptions\" >6. Control changes and document exceptions<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/rentaldesk.co.ke\/blog\/property-unit-naming\/#7_Test_the_software_workflow_with_fictional_examples\" >7. Test the software workflow with fictional examples<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/rentaldesk.co.ke\/blog\/property-unit-naming\/#Worked_example_two_buildings_with_an_A1\" >Worked example: two buildings with an A1<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/rentaldesk.co.ke\/blog\/property-unit-naming\/#A_practical_property_unit_naming_review_sheet\" >A practical property unit naming review sheet<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/rentaldesk.co.ke\/blog\/property-unit-naming\/#Frequently_asked_questions\" >Frequently asked questions<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/rentaldesk.co.ke\/blog\/property-unit-naming\/#Before_approving_your_property_unit_naming_list\" >Before approving your property unit naming list<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/rentaldesk.co.ke\/blog\/property-unit-naming\/#Discuss_your_records_with_RentalDesk\" >Discuss your records with RentalDesk<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"1_Give_every_unit_a_stable_identity\"><\/span>1. Give every unit a stable identity<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Property unit naming should begin with a simple question: can a colleague identify the same physical space from the record without asking who currently occupies it? A unit identifier should remain understandable when a tenant moves, a caretaker changes or an office assistant takes over. Names based only on the current occupant do not provide that stable reference.<\/p>\n<p>Separate the property from the unit. Two buildings can both have a unit called A1, so a unit label alone may be insufficient in a portfolio. Decide how the property reference and unit reference appear together in everyday work. Write examples that include more than one building, rather than testing the convention only against the first property on the list.<\/p>\n<p>Avoid inventing a new convention before reviewing the identifiers already in use. Existing agreements, invoices, maintenance records and signs may contain useful references. Property unit naming should account for these records so staff can relate an old description to the current identifier. A consistent convention is helpful only when the transition does not leave people guessing which unit an older record describes.<\/p>\n<p>Identify who owns the authoritative list. That person or role should coordinate corrections and communicate approved changes. The responsibility need not mean doing every data entry task. It means ensuring that two departments do not quietly maintain different versions of the same unit\u2019s identity. Agree where colleagues check the current answer when conflicting labels appear.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"2_Write_a_convention_that_ordinary_staff_can_apply\"><\/span>2. Write a convention that ordinary staff can apply<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A property unit naming convention should explain the parts of the identifier in plain language. For example, it might combine a property reference with a unit code already used on site. The example is illustrative; choose a convention that fits the actual portfolio and records. Do not add floors, wings or building phases merely because another organisation uses them.<\/p>\n<p>For property unit naming, define how spaces, punctuation and letter case are handled. Small differences can confuse manual searches and make spreadsheets appear to contain different units. Show an accepted example beside an incorrect variation so staff understand the rule. Confirm how the software treats the format before relying on an assumption about automatic matching or duplicate detection.<\/p>\n<p>Think about units with similar descriptions. A shop, store and office might all be on the ground floor but serve different purposes. The identifier should distinguish the spaces without becoming a long narrative. Keep descriptive attributes in the appropriate fields where available. Staff should not need to decode an entire property description every time they select a unit.<\/p>\n<p>Test the convention with someone who did not design it. Give that colleague a few fictional examples and ask them to identify the property and unit. Property unit naming becomes easier to maintain when the rule works without an explanation from its author. If several people interpret an example differently, revise the instructions before applying them widely.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"3_Compare_existing_records_before_importing_anything\"><\/span>3. Compare existing records before importing anything<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>For property unit naming, collect the approved source lists that need reconciliation. These may include the current software export, an office register and the caretaker\u2019s operational list. Keep their origins clear instead of merging them immediately. If two sources disagree, the disagreement is useful evidence that needs review; choosing the more recent file without checking may preserve an error.<\/p>\n<p>Create a working comparison that shows each source label beside the proposed current identifier. Property unit naming reviews should highlight duplicate references, missing property names and unexplained gaps. Do not fill a missing identifier by assuming that a number sequence is complete. Check the actual space and relevant records through the organisation\u2019s approved process.<\/p>\n<p>Distinguish a duplicate record from two legitimate spaces with similar labels. Two entries might describe the same unit, but they might also refer to separate rooms or different buildings. Ask an authorised person with knowledge of the property to confirm the relationship. A software import is not the right moment to make an unsupported decision about the physical portfolio.<\/p>\n<p>Keep unresolved entries in a review list with an owner and next action. Property unit naming work can continue on confirmed records while uncertain cases are investigated. Do not import a guess simply to make a spreadsheet look complete. The review list should explain what evidence or confirmation is still needed and when the issue will be checked again.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"4_Separate_unit_identity_from_occupancy_and_balances\"><\/span>4. Separate unit identity from occupancy and balances<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A unit reference, an occupant\u2019s identity and an account balance describe different things. Changing one should not be treated as automatic evidence that the others should change. Keep the unit identifier stable where appropriate, while updating occupancy through the correct process. Confirm how the chosen software represents these relationships before planning a migration or correction.<\/p>\n<p>Property unit naming should not depend on an occupant\u2019s personal details. A label that includes a tenant\u2019s telephone number or full name can expose unnecessary information when copied into operational lists. Use the approved unit reference for routine coordination and store tenant details where authorised colleagues are expected to access them. This also makes the reference more useful after occupancy changes.<\/p>\n<p>Before making a correction, identify the records that rely on the existing label. These may include maintenance requests, statements, inspections or administrative reports. Do not assume that changing a display name updates every related record in the same way. Ask the software provider to explain the supported process and test with fictional or approved sample information where possible.<\/p>\n<p>If historical documents retain an older description, record the relationship between the old and current labels through the approved process. Property unit naming should help staff interpret history without rewriting it carelessly. A clearly documented reference change is more useful than several silent edits that leave colleagues unable to explain why two documents use different names.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"5_Check_the_convention_on_site_and_during_handover\"><\/span>5. Check the convention on site and during handover<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Compare the approved list with the way authorised staff identify spaces during ordinary work. A desk-based naming rule may look clear but conflict with signs, access arrangements or a caretaker\u2019s established references. Record those differences and decide how to communicate the current convention. Avoid changing physical labels casually without checking who is responsible for that work.<\/p>\n<p>Use property unit naming examples in the handover between office staff and caretakers. Ask each person to identify a unit from the same reference and explain where they would record an issue. If one person uses a wing name while another uses a block number, the list should explain the relationship. Shared understanding matters as much as consistent spelling.<\/p>\n<p>Consider visitors who receive only a limited work instruction. A contractor may need the building and approved unit reference without access to tenant records. Make the instruction sufficient for the task while keeping private information in the authorised channel. Do not turn the naming list into a directory containing every person\u2019s contact details.<\/p>\n<p>Review the convention after a staff change. Property unit naming rules that depend on informal local knowledge can fail when an experienced colleague leaves. Give new staff a short guide, representative examples and a clear contact for uncertain cases. Encourage them to raise a mismatch rather than creating another label that seems convenient in the moment.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"6_Control_changes_and_document_exceptions\"><\/span>6. Control changes and document exceptions<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>For property unit naming, agree what requires approval before an identifier changes. A spelling correction, a property reference change and a physical reconfiguration are different situations. The person coordinating the list should understand which process applies. Do not treat an instruction to tidy a spreadsheet as authority to change the meaning of unit records or rearrange their relationships.<\/p>\n<p>For property unit naming, keep a short change record containing the old identifier, current identifier, reason, date and responsible reviewer. Store it where authorised colleagues can find it. A change record helps staff answer later questions without relying on memory. It also makes it easier to identify whether an unexpected label came from an approved correction.<\/p>\n<p>Document exceptions instead of forcing every unusual space into an unsuitable pattern. A mixed-use property or an older building may have identifiers that cannot be changed conveniently. Explain the accepted exception and how it is distinguished from ordinary entries. A small number of clear exceptions can be safer than an apparently uniform list that conceals important differences.<\/p>\n<p>When new units are added, review the proposed identifiers before staff begin using them in multiple records. Property unit naming is easier to maintain when the first entry follows the convention. Check for collisions with existing or historical references and confirm the supporting property information. Communicate the approved entries to the people who use them operationally.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"7_Test_the_software_workflow_with_fictional_examples\"><\/span>7. Test the software workflow with fictional examples<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Ask for a demonstration using a small fictional portfolio that resembles the structure of your real records. Include two properties with similar unit labels, an occupied unit, a vacant unit and a record needing correction. The demonstration should show how staff find the right space and distinguish its identity from other information attached to it.<\/p>\n<p>Property unit naming tests should include an ordinary search and a handover task. Ask one colleague to find a unit from a maintenance note and another to identify the same unit in a report. Compare what each screen displays. If an abbreviated label appears in one place, confirm whether enough property context remains visible to avoid a mistake.<\/p>\n<p>Before any real import, confirm the supported file format, required fields and method for reviewing errors. Ask how duplicates are identified and what happens when an identifier already exists. Do not assume that a demonstration with one clean row establishes how a full portfolio will behave. Keep the provider\u2019s instructions with the preparation checklist.<\/p>\n<p>Record the outcome of the trial and any unresolved questions. Property unit naming preparation is complete only when the team understands the process it will actually use. A software feature does not replace a decision about which source record is correct. Keep data verification responsibilities clear even when the system provides helpful checks or import tools.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Worked_example_two_buildings_with_an_A1\"><\/span>Worked example: two buildings with an A1<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Imagine a fictional portfolio with two buildings whose on-site unit labels both include A1. Office staff sometimes send maintenance requests containing only that label. The problem is not necessarily that either building needs new door numbers. The operational record may simply need the property reference to accompany the unit label consistently wherever work is assigned.<\/p>\n<p>During property unit naming review, the team compares its current records and confirms that the two entries refer to different spaces. It documents an agreed combined reference and shows examples in the staff guide. Historical records remain interpretable through an approved mapping. The team checks how the reference appears in the software before adopting it in daily communication.<\/p>\n<p>A caretaker then receives a fictional request and identifies the correct building and unit without another phone call. The office tests the same reference in a report. If either task remains ambiguous, the team adjusts the convention or instructions. This example illustrates the review method; the appropriate identifier format depends on the actual portfolio and the system being used.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"A_practical_property_unit_naming_review_sheet\"><\/span>A practical property unit naming review sheet<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Use columns for source, existing label, property reference, proposed identifier, verification status, reviewer and next action. Add an explanation field for discrepancies. Keep private tenant information out of the sheet unless it is necessary and handled through the approved process. The sheet should support a naming review, not become an uncontrolled copy of the full property database.<\/p>\n<p>Mark confirmed and unresolved rows clearly. Property unit naming reviews often stall when an unanswered question looks identical to a completed check. Give each uncertain row an owner and a review date. If the answer depends on a site check or provider guidance, identify that dependency. This allows the team to continue with reliable records while retaining visibility of the remaining work.<\/p>\n<p>Before signing off, sample records from different buildings and types of space. Ask a colleague who did not prepare the sheet to interpret them. Review any disagreement and correct the instructions where needed. Keep the final approved list and the supporting change history in their designated locations so the next review starts from a reliable reference.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Frequently_asked_questions\"><\/span>Frequently asked questions<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Should the tenant\u2019s name be part of the unit identifier? A stable operational reference is generally easier to maintain when it describes the unit rather than its current occupant. Store occupancy information in the appropriate record. Property unit naming should remain useful when a tenancy changes and should avoid exposing personal details in ordinary task lists.<\/p>\n<p>Can every unit be renamed at once? A bulk change requires careful preparation. Identify affected records, confirm the software\u2019s supported process and resolve uncertain mappings first. Do not assume that a new label will automatically repair historical inconsistencies. Ask the provider how to review results and handle exceptions before making widespread changes.<\/p>\n<p>What if the caretaker\u2019s list disagrees with the office register? Record the discrepancy and verify it through the approved process. Neither source should automatically win solely because it is more convenient to access. Property unit naming depends on accurate identification of the real space and a clear decision about the current authoritative reference.<\/p>\n<p>How often should the naming guide be reviewed? Revisit it when properties are added, identifiers change, staff report confusion or a migration is planned. A short review of real examples is more useful than rewriting the whole guide on a fixed schedule without a reason. Keep the current rule easy to find and remove obsolete instructions from ordinary use.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Before_approving_your_property_unit_naming_list\"><\/span>Before approving your property unit naming list<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Check that every confirmed row identifies a real space, carries the correct property context and follows the agreed format. Ask the reviewer to explain one ordinary example and one exception. Property unit naming instructions should be understandable to the people who will use them during busy working hours, without a separate explanation from the original author.<\/p>\n<p>Keep unresolved questions visible after the initial review. A clean presentation should never hide uncertainty. Assign the remaining property unit naming checks to named colleagues and agree when the team will review their answers before importing or changing affected records.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Discuss_your_records_with_RentalDesk\"><\/span>Discuss your records with RentalDesk<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Commercial occupants may use <a href=\"https:\/\/prim.co.ke\/\" target=\"_blank\" rel=\"noopener\">Prim<\/a> for salon operations or <a href=\"https:\/\/vega.co.ke\/\" target=\"_blank\" rel=\"noopener\">Vega<\/a> for retail work. Keep their business tools separate from the landlord\u2019s unit identifiers. An occupant changing software or trading name should not automatically change the property\u2019s approved naming structure.<\/p>\n<p>Write a short written naming rule that new staff can follow. Review examples from each building and identify the authoritative list. If an identifier changes, document the reason and check affected records through the approved process. Explore <a href=\"https:\/\/rentaldesk.co.ke\/features\">RentalDesk features<\/a> and confirm the current setup options. Call <a href=\"tel:+254725345345\">0725345345<\/a> to discuss your portfolio, existing records and preparation for a demonstration using fictional sample information.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Property unit naming helps Kenyan rental teams connect the correct tenant, invoice and maintenance request. Give every unit a consistent identifier and use it&hellip;<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-4290","post","type-post","status-publish","format-standard","hentry","category-rental-desk"],"_links":{"self":[{"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/posts\/4290","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/comments?post=4290"}],"version-history":[{"count":4,"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/posts\/4290\/revisions"}],"predecessor-version":[{"id":4316,"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/posts\/4290\/revisions\/4316"}],"wp:attachment":[{"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/media?parent=4290"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/categories?post=4290"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/tags?post=4290"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}