{"id":4299,"date":"2026-10-07T07:04:44","date_gmt":"2026-10-07T07:04:44","guid":{"rendered":"https:\/\/rentaldesk.co.ke\/blog\/?p=4299"},"modified":"2026-10-07T07:17:55","modified_gmt":"2026-10-07T07:17:55","slug":"property-task-lists","status":"publish","type":"post","link":"https:\/\/rentaldesk.co.ke\/blog\/property-task-lists\/","title":{"rendered":"Property Task Lists: 7 Powerful Steps for Clear Follow-Up"},"content":{"rendered":"<p>Property task lists help Kenyan managers turn scattered messages into clear follow-up. Record the property, unit where relevant, task owner, current status and next action. A note saying pending is incomplete unless another colleague can understand what must happen and who is responsible for moving it forward. Review the list together when responsibilities move between authorised staff members.<\/p>\n<p>Follow the <a href=\"https:\/\/rentaldesk.co.ke\/blog\/multi-property-management-daily-workflow\/\">multi-property workflow guide<\/a> when coordinating several buildings. Keep routine inspections, maintenance requests and tenant questions distinguishable. Use consistent status definitions so that completed means the same thing to caretakers, administrators and managers reviewing the portfolio.<img decoding=\"async\" src=\"https:\/\/rentaldesk.co.ke\/img\/screenshorts\/units.webp\" alt=\"property task lists \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-task-lists\/#1_Define_the_outcome_before_assigning_the_work\" >1. Define the outcome before assigning the work<\/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-task-lists\/#2_Assign_one_owner_and_a_realistic_review_date\" >2. Assign one owner and a realistic review date<\/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-task-lists\/#3_Use_statuses_that_describe_the_actual_situation\" >3. Use statuses that describe the actual situation<\/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-task-lists\/#4_Separate_approval_access_and_completion_checks\" >4. Separate approval, access and completion checks<\/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-task-lists\/#5_Review_the_list_through_a_short_daily_routine\" >5. Review the list through a short daily routine<\/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-task-lists\/#6_Make_handovers_understandable_without_a_phone_call\" >6. Make handovers understandable without a phone call<\/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-task-lists\/#7_Close_work_carefully_and_learn_from_repeat_issues\" >7. Close work carefully and learn from repeat issues<\/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-task-lists\/#Worked_example_a_repair_that_needs_approval\" >Worked example: a repair that needs approval<\/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-task-lists\/#A_practical_template_for_property_task_lists\" >A practical template for property task lists<\/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-task-lists\/#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-task-lists\/#Before_your_next_review\" >Before your next review<\/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-task-lists\/#Discuss_your_property_workflow\" >Discuss your property workflow<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"1_Define_the_outcome_before_assigning_the_work\"><\/span>1. Define the outcome before assigning the work<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Property task lists work best when each item describes a result that another person can check. \u201cContact the contractor\u201d describes an activity. \u201cConfirm a visit date for the leaking kitchen tap and record the contractor\u2019s reply\u201d explains what must exist when the action is finished. A colleague using property task lists tomorrow should understand the difference without searching through several conversations.<\/p>\n<p>For property task lists, start with one sentence explaining the issue, followed by the expected outcome. Include the building and unit where relevant, but avoid placing unnecessary tenant details in a widely shared list. Use an approved record for sensitive information and refer to that record through the normal internal process. The task should provide enough context to work safely without becoming a second tenant database.<\/p>\n<p>Decide whether the request belongs on your property task lists at all. An observation, an idea and an approved action are different things. If someone suggests repainting a corridor, record the suggestion for assessment rather than implying that expenditure has already been authorised. Distinguishing proposed work from agreed work prevents colleagues from treating an informal note as permission to proceed.<\/p>\n<p>Keep the original report available when details are clarified. If the problem changes from a faulty light to a damaged fitting, update the description and note what changed. Do not silently replace an earlier report in a way that hides why a visit was arranged. Useful context helps the next person understand the sequence and ask better questions.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"2_Assign_one_owner_and_a_realistic_review_date\"><\/span>2. Assign one owner and a realistic review date<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>An owner coordinates the next action; that person does not necessarily perform the repair or approve the cost. For example, an office assistant may organise access, a manager may approve a quotation, and a contractor may carry out the work. In property task lists, assign one person to keep the item moving while recording the separate decisions needed from other participants.<\/p>\n<p>Avoid assigning an item simply to \u201cmanagement\u201d or \u201cthe office.\u201d Those labels make it difficult to know who should respond when progress stops. If responsibility belongs to a team, identify the person covering the role during the current shift or working period. Make the handover explicit when that person changes, rather than assuming the next colleague has seen a message.<\/p>\n<p>Property task lists should distinguish a promised completion date from a review date. A contractor may not yet have confirmed availability, but your team can still agree to review the request tomorrow. Record what the date means so an unresolved appointment does not appear to be an overdue repair. Where timing depends on another party, say so clearly.<\/p>\n<p>Check workload in property task lists before setting dates. Giving every item the same urgent deadline makes the list less useful and can conceal genuinely time-sensitive work. Ask what blocks the action, who must provide information and when that information is expected. Agree a realistic next check, then update the record if circumstances change. A revised date should come with a brief explanation.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"3_Use_statuses_that_describe_the_actual_situation\"><\/span>3. Use statuses that describe the actual situation<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Keep status labels simple enough that two colleagues would classify the same situation in the same way. A practical starting set might include new, under review, awaiting approval, scheduled, in progress and completed. Adapt those labels to the process your team actually uses. Do not create a complicated list of options that nobody can distinguish during a busy working day.<\/p>\n<p>Write a short definition for each label used in property task lists. Scheduled should mean an appointment has been agreed, not merely requested. Awaiting approval should identify whose decision is needed. Completed should mean the agreed outcome has been checked, not just that a visit occurred. These definitions matter more than the particular words used in the menu or spreadsheet.<\/p>\n<p>For property task lists, record the blocker alongside the status. An item marked waiting is much clearer when the note says it needs the owner\u2019s approval of a quotation. The same status could otherwise refer to missing access arrangements, unavailable materials or an unanswered question. A brief explanation helps a colleague act instead of repeating work that has already been done.<\/p>\n<p>In property task lists, use a separate cancellation reason when work will not proceed. Cancellation is not the same as completion, and hiding cancelled requests can make repeated reports difficult to understand. Keep the history within your approved retention process. If the issue returns, staff can see the earlier decision and determine whether the new report requires a different response.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"4_Separate_approval_access_and_completion_checks\"><\/span>4. Separate approval, access and completion checks<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A request to arrange a visit does not automatically authorise a repair, a purchase or entry to an occupied unit. Record the relevant approvals through the organisation\u2019s normal process. Make the permitted scope understandable to the person coordinating the visit. If a contractor discovers additional work, the task should show how that change will be reviewed before anyone treats it as agreed.<\/p>\n<p>Access arrangements deserve their own check in property task lists. Confirm who will communicate with the occupant, who will meet the visitor and what happens if the appointment changes. Keep access codes, keys and private contact details in the approved location rather than in an open task description. The operational list can say that access is confirmed without exposing the information used to provide it.<\/p>\n<p>For completion, define evidence that fits the action. A meter-reading review may need the relevant reading and a checked reference. A repair may need a completion note and confirmation that the reported fault has been addressed. An administrative task may need the corrected record and a reviewer\u2019s acknowledgement. Avoid collecting extra personal information simply to make the item look more complete.<\/p>\n<p>Property task lists should also show who reviews a disputed outcome. If a visitor reports completion but the issue remains, keep the discrepancy visible and assign the next assessment. Do not close the request merely because one participant has finished their part. A clear record separates attendance, work performed and the result that the property team still needs to confirm.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"5_Review_the_list_through_a_short_daily_routine\"><\/span>5. Review the list through a short daily routine<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Review property task lists by starting with actions whose next check is due, then look at items that have changed since the previous review. This keeps attention on decisions that can move work forward. Reading every historical item aloud is rarely useful. Use the time to resolve ownership, clarify blockers and identify the next action, leaving detailed investigation to the responsible person.<\/p>\n<p>For each item, ask four questions: what changed, what is needed next, who owns that action and when will it be checked? Record the answers in the authoritative list. A conversation in a meeting or messaging group should not become the only place where a decision exists. Staff who were absent need the same current information as those who attended.<\/p>\n<p>Check property task lists for duplicates before opening another task. Two reports about one corridor light may refer to the same issue, while two similar descriptions in different buildings may be separate requests. Compare the location and context rather than relying on matching words alone. Link related work in the approved system when possible, without merging records in a way that loses important differences.<\/p>\n<p>Keep the review proportionate to the portfolio. A small team may need a brief check at the start of the day and another before handover. A larger operation may review by building or responsibility. Choose a rhythm that prevents forgotten actions without creating constant interruptions. The useful measure is whether colleagues know what to do next after the review.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"6_Make_handovers_understandable_without_a_phone_call\"><\/span>6. Make handovers understandable without a phone call<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Good property task lists let a receiving colleague continue work even when the previous owner is unavailable. Before handing over, update the latest action, current status, outstanding decision and next review date. Replace vague notes such as \u201cdiscussed already\u201d with a short statement of what was agreed. Refer to supporting records where the detail belongs instead of copying entire conversations.<\/p>\n<p>Ask the receiving colleague to identify their first action. This is a practical way to test whether the handover contains enough information. If they cannot tell whether to call a contractor, seek approval or wait for an appointment, clarify the record before the shift changes. A handover is complete when responsibility is understood, not merely when a message is sent.<\/p>\n<p>Avoid creating a separate private list that becomes more current than the shared record. Personal reminders can be useful, but decisions and completion updates should reach the authorised source. Otherwise one colleague may cancel a visit while another still expects it to happen. Establish which record wins if two copies disagree and who is responsible for correcting the difference.<\/p>\n<p>When someone is away, use property task lists to confirm who covers their open actions. Do not automatically transfer every task without checking the cover person\u2019s responsibilities and access. A temporary owner may coordinate updates while another manager retains approval authority. Make the arrangement visible and review it when the original owner returns, so actions do not remain stranded between two people.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"7_Close_work_carefully_and_learn_from_repeat_issues\"><\/span>7. Close work carefully and learn from repeat issues<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Before closing an item, compare the recorded outcome with the original request and any approved changes. Check whether related actions remain open. A repair may be finished while a follow-up inspection is still required; an appointment may be completed while a document remains outstanding. Record those remaining actions explicitly rather than leaving them inside a completed item\u2019s notes.<\/p>\n<p>Keep closure notes in property task lists short and factual. State what was checked, who confirmed it and whether another action was created. Avoid unsupported conclusions about causes or blame. If information is incomplete, say what remains uncertain and who will review it. Accurate closure notes make later reporting more useful and reduce the temptation to reconstruct events from memory.<\/p>\n<p>Review repeat issues in property task lists periodically. Repeated access failures may point to unclear appointment arrangements. Repeated missing approvals may show that responsibility is not understood. The purpose is to improve the process, not to assume that every delay reflects poor performance. Look at the pattern alongside the circumstances and ask the people doing the work what would make the next action clearer.<\/p>\n<p>Property task lists are most useful when the team maintains a small set of reliable habits. Clear outcomes, named owners, realistic review dates and checked closure are a stronger foundation than a long list of elaborate labels. Start with a manageable process, test it with ordinary requests and change the instructions when real examples reveal confusion.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Worked_example_a_repair_that_needs_approval\"><\/span>Worked example: a repair that needs approval<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Suppose a caretaker reports a kitchen tap that continues to drip in one unit. The first task is to clarify the report and organise an assessment through the approved process. Record the unit reference, the reported problem and the person coordinating the next action. Avoid declaring that a particular part must be replaced before the assessment has established what is needed.<\/p>\n<p>The contractor then provides a proposed scope and quotation. The item in your property task lists moves to awaiting approval, with the responsible decision-maker identified. The next review date concerns that approval, not the completion of the repair. Once approval is recorded, the coordinator confirms the appointment and access arrangements. If the appointment changes, the same record explains the new date and who has been informed.<\/p>\n<p>After the visit, the coordinator checks the agreed outcome and records any outstanding point. If a further assessment is needed, the request remains open or a clearly linked action is created. This example is illustrative; the exact approvals and records depend on your organisation. Its purpose is to show how a task moves through decisions without confusing a report, an appointment and a checked result.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"A_practical_template_for_property_task_lists\"><\/span>A practical template for property task lists<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Use the following fields as a starting point: task reference, property or unit, reported issue, expected outcome, owner, status, blocker, next action, review date and closure check. Include links to approved supporting records where appropriate. Keep the template short enough to maintain consistently. Add a field only when it helps someone make a decision or understand responsibility.<\/p>\n<p>Before introducing this template for property task lists across every building, test it with a few fictional examples. Include an ordinary completed action, a request awaiting approval and an appointment that was cancelled. Ask different colleagues to enter and interpret the same examples. Differences in their answers reveal where a label or instruction needs clarification before real requests depend on it.<\/p>\n<p>For property task lists, agree who can change important fields and how corrections are recorded. Staff should know whom to contact when the property reference is wrong or the owner is unavailable. Keep the instructions accessible during handovers. Review the template after a working cycle and remove unnecessary duplication instead of continually adding fields that make each update harder.<\/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>How many tasks should one person own? There is no single useful number for every team. Consider complexity, deadlines and the person\u2019s other responsibilities. A few complicated actions may require more coordination than many simple checks. Review workload when assigning work and raise capacity issues before missed dates become routine.<\/p>\n<p>Should every request be urgent? No. Describe the actual circumstances and follow your organisation\u2019s escalation process. A priority label should help staff decide what needs attention first. If everything carries the same label, the team still needs another way to distinguish work. Reassess priority when new information changes the situation.<\/p>\n<p>Can messaging replace the task list? Alongside property task lists, messages are useful for discussion and notification, but the approved record should hold the current decision, owner and next action. Otherwise updates can disappear into separate conversations. Establish a simple habit of recording an agreed change where authorised colleagues expect to find it.<\/p>\n<p>What should a software demonstration show? Ask the presenter to walk through a fictional request from entry to closure, including a changed appointment and an unresolved approval. Confirm which functions are available in the plan under discussion. Property task lists should support the way your team coordinates work, and the demonstration should reveal where additional procedures are needed.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Before_your_next_review\"><\/span>Before your next review<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Choose one open request and check whether a colleague can identify its owner, next action and review date without asking for help. Correct missing details in the approved record. Repeat this small check during ordinary handovers until the team can rely on the same clear information.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Discuss_your_property_workflow\"><\/span>Discuss your property workflow<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>External research should remain separate from operational approval. A provider found through <a href=\"https:\/\/jaat.co.ke\/\" target=\"_blank\" rel=\"noopener\">Jaat<\/a> still needs verification, while tools explored through <a href=\"https:\/\/zama.co.ke\/\" target=\"_blank\" rel=\"noopener\">Zama<\/a> require their own assessment. Neither a directory listing nor a software demonstration automatically authorises access to tenant records or property premises.<\/p>\n<p>Review overdue actions by identifying the actual blocker, such as missing approval, unavailable access or incomplete information. Close tasks only after the agreed completion check. Explore <a href=\"https:\/\/rentaldesk.co.ke\/features\">RentalDesk features<\/a> and confirm how your chosen plan supports the process. Keep the current list accessible to authorised colleagues during staff changes. Call <a href=\"tel:+254725345345\">0725345345<\/a> to discuss a practical workflow for the properties and responsibilities your team manages.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Property task lists help Kenyan managers turn scattered messages into clear follow-up. Record the property, unit where relevant, task owner, current status and next&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-4299","post","type-post","status-publish","format-standard","hentry","category-rental-desk"],"_links":{"self":[{"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/posts\/4299","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=4299"}],"version-history":[{"count":3,"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/posts\/4299\/revisions"}],"predecessor-version":[{"id":4311,"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/posts\/4299\/revisions\/4311"}],"wp:attachment":[{"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/media?parent=4299"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/categories?post=4299"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rentaldesk.co.ke\/blog\/wp-json\/wp\/v2\/tags?post=4299"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}