{"id":2160,"date":"2026-10-22T11:20:11","date_gmt":"2026-10-22T08:20:11","guid":{"rendered":"https:\/\/pawa.co.ke\/blog\/?p=2160"},"modified":"2026-10-22T11:20:12","modified_gmt":"2026-10-22T08:20:12","slug":"network-documentation-software-in-kenya","status":"publish","type":"post","link":"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/","title":{"rendered":"Network Documentation Software in Kenya: Every Circuit Mapped"},"content":{"rendered":"<h2><a href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/smart-networks-start-with-pawa\/\" rel=\"attachment wp-att-2175\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2175\" src=\"https:\/\/pawa.co.ke\/blog\/wp-content\/uploads\/2026\/10\/Smart-Networks-Start-With-PAWA.png\" alt=\"network documentation software in Kenya\" width=\"1254\" height=\"1254\" srcset=\"https:\/\/pawa.co.ke\/blog\/wp-content\/uploads\/2026\/10\/Smart-Networks-Start-With-PAWA.png 1254w, https:\/\/pawa.co.ke\/blog\/wp-content\/uploads\/2026\/10\/Smart-Networks-Start-With-PAWA-300x300.png 300w, https:\/\/pawa.co.ke\/blog\/wp-content\/uploads\/2026\/10\/Smart-Networks-Start-With-PAWA-1024x1024.png 1024w, https:\/\/pawa.co.ke\/blog\/wp-content\/uploads\/2026\/10\/Smart-Networks-Start-With-PAWA-150x150.png 150w, https:\/\/pawa.co.ke\/blog\/wp-content\/uploads\/2026\/10\/Smart-Networks-Start-With-PAWA-768x768.png 768w\" sizes=\"auto, (max-width: 1254px) 100vw, 1254px\" \/><\/a><\/h2>\n<p><a href=\"https:\/\/pawa.co.ke\">Network documentation software in Kenya<\/a> records every route, joint, splitter, port, IP address, and device in a network, and keeps that record current as the network grows, so an engineer can find a fault without guessing.<\/p>\n<p>A Kenyan ISP builds fast, and the paperwork usually arrives last, if it arrives at all. The result is a network that works and cannot be explained.<\/p>\n<p><a href=\"https:\/\/zama.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> turns that knowledge into a shared map rather than a set of notebooks and one engineer&#8217;s memory.<\/p>\n<p>For an operator with three hundred kilometres of fibre, <a href=\"https:\/\/dexa.co.ke\" target=\"_blank\" rel=\"noopener\">network documentation software in Kenya<\/a> is what makes a fault a twenty-minute job instead of a day of digging.<\/p>\n<p>A smaller provider gains too, because <a href=\"https:\/\/pawa.co.ke\">network documentation software in Kenya<\/a> makes a single technician&#8217;s knowledge available to the whole team, including the person on night shift.<\/p>\n<p>This article explains what documentation actually needs to hold, where it breaks down, and how to keep it alive.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_85 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:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#What_Network_Documentation_Software_in_Kenya_Covers\" >What Network Documentation Software in Kenya Covers<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#What_Undocumented_Networks_Cost\" >What Undocumented Networks Cost<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Routes_Joints_and_Fibre_Records\" >Routes, Joints and Fibre Records<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Seasons_and_the_Documentation_Calendar\" >Seasons and the Documentation Calendar<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Field_Capture_Photos_and_Checks\" >Field Capture, Photos and Checks<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Talking_to_Field_Teams_and_Planners\" >Talking to Field Teams and Planners<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#As-Builts_Variations_and_Exceptions\" >As-Builts, Variations and Exceptions<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Records_Handover_and_Audit\" >Records, Handover and Audit<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Linking_Documentation_to_Operations\" >Linking Documentation to Operations<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Live_Views_of_Network_State\" >Live Views of Network State<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Multiple_Teams_and_Contractors\" >Multiple Teams and Contractors<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Reports_That_Show_Documentation_Health\" >Reports That Show Documentation Health<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Choosing_a_Documentation_Platform\" >Choosing a Documentation Platform<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Rolling_Out_Documentation\" >Rolling Out Documentation<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Where_Documentation_Fails\" >Where Documentation Fails<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#The_Value_of_a_Map_in_a_Dispute\" >The Value of a Map in a Dispute<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Documentation_and_Network_Value\" >Documentation and Network Value<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#A_Closing_Note_on_Memory\" >A Closing Note on Memory<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-19\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#IP_Addressing_and_Documentation\" >IP Addressing and Documentation<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-20\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Device_Configuration_Records\" >Device Configuration Records<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-21\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Customer_Premises_Records\" >Customer Premises Records<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-22\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Documentation_During_a_Build\" >Documentation During a Build<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-23\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#The_Cost_of_a_Wrong_Dig\" >The Cost of a Wrong Dig<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-24\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Documentation_and_Insurance\" >Documentation and Insurance<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-25\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Working_With_Contractors\" >Working With Contractors<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-26\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Documentation_for_Regulatory_Filings\" >Documentation for Regulatory Filings<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-27\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Keeping_the_Map_Alive\" >Keeping the Map Alive<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-28\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Documentation_and_Team_Morale\" >Documentation and Team Morale<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-29\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#A_Closing_Note_on_Simplicity\" >A Closing Note on Simplicity<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-30\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Documentation_and_Spare_Capacity\" >Documentation and Spare Capacity<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-31\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Documentation_and_Fault_History\" >Documentation and Fault History<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-32\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Documentation_and_Network_Planning\" >Documentation and Network Planning<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-33\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#The_Human_Side_of_Records\" >The Human Side of Records<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-34\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Documentation_for_New_Hires\" >Documentation for New Hires<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-35\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Working_With_Landlords_and_Wayleaves\" >Working With Landlords and Wayleaves<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-36\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Documentation_and_Customer_Communication\" >Documentation and Customer Communication<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-37\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#Documentation_as_a_Habit\" >Documentation as a Habit<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-38\" href=\"https:\/\/pawa.co.ke\/blog\/network-documentation-software-in-kenya\/#A_Final_Word_on_Scale\" >A Final Word on Scale<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"What_Network_Documentation_Software_in_Kenya_Covers\"><\/span>What Network Documentation Software in Kenya Covers<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Documentation is a chain of design, build, record, and update, and the update is the part everyone skips.<\/p>\n<p>Design comes first, because a route planned on a whiteboard is a route that will be built differently. <a href=\"https:\/\/pms.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> stores the intended design, which is what the as-built is compared against.<\/p>\n<p>Build follows, since the trench, the duct, and the joint are physical facts that need recording while the crew is on site. <a href=\"https:\/\/estateadmin.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> captures them at installation, which is the only moment they are easy to capture.<\/p>\n<p>Record comes next, because a document that lives in a folder on one laptop is not a shared asset. <a href=\"https:\/\/churchesadmin.com\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> puts it in one place that the field team can open.<\/p>\n<p>Update closes the chain, since every repair changes the network slightly. <a href=\"https:\/\/vega.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> makes the update part of the repair, which is the only way it happens.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"What_Undocumented_Networks_Cost\"><\/span>What Undocumented Networks Cost<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>An undocumented network is not a mystery for long; it becomes a recurring expense that nobody can remove.<\/p>\n<p>The first cost is the fault hunt, because a technician who does not know where the joint is will dig in the wrong place. <a href=\"https:\/\/dereva.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> shows the route, the joint, and the fibre count, which is usually enough to locate the problem.<\/p>\n<p>The second is the duplicate build, where a new customer is connected through a route that already exists fifty metres away. <a href=\"https:\/\/jaat.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> shows the spare capacity, which turns a build into a connection.<\/p>\n<p>The third is the handover, because an engineer who leaves takes the network&#8217;s memory with them. <a href=\"https:\/\/wito.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> preserves it, which is the difference between a week of confusion and a day of reading.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Routes_Joints_and_Fibre_Records\"><\/span>Routes, Joints and Fibre Records<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A fibre record is only useful when it describes the physical path, and most documentation starts too abstractly.<\/p>\n<p>A route should have a geometry, because a line on a map with no distance cannot be maintained. <a href=\"https:\/\/awasam.com\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> records the path and the length, which is what a contractor prices against.<\/p>\n<p>A joint should have a location, since a joint box under a driveway is a repair that needs permission. <a href=\"https:\/\/saseni.com\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> stores the coordinates and an access note, which saves an argument at the gate.<\/p>\n<p>A fibre should have a colour and a tube, because a splice tray with twelve fibres needs a numbering scheme to be usable. <a href=\"https:\/\/prim.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> records the core, which is what makes a repair a splice rather than an investigation.<\/p>\n<p>A record should be dated, since a route that was built in 2019 may have been moved twice since. <a href=\"https:\/\/rentaldesk.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> keeps the history, which is what makes the current map trustworthy.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Seasons_and_the_Documentation_Calendar\"><\/span>Seasons and the Documentation Calendar<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Documentation work follows the build season, and a team that only documents in the dry months will always be behind.<\/p>\n<p>The dry season is when trenches open and routes change, which is exactly when records must be captured. <a href=\"https:\/\/fama.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> supports field capture, which is the only way to keep up with a build.<\/p>\n<p>The long rains slow construction and shift attention to repairs, and each repair alters the network. <a href=\"https:\/\/spacekits.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> makes the repair update a single step, which is how the record survives the wet months.<\/p>\n<p>The festive season brings new connections and higher utilisation, which is a good time to review capacity and update the plan. <a href=\"https:\/\/zamacore.com\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> connects the record to the plan, which is what makes the review meaningful.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Field_Capture_Photos_and_Checks\"><\/span>Field Capture, Photos and Checks<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A record created in the office a week later is a reconstruction, and reconstructions are always partly wrong.<\/p>\n<p>A field capture should be quick, because a technician standing in a trench will not fill a long form. <a href=\"https:\/\/mystayorbit.com\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> keeps the entry to a few taps, which is the difference between a record and a rumour.<\/p>\n<p>A photo should be attached, since a joint closure and a splice tray are easier to photograph than to describe. <a href=\"https:\/\/dexa.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> stores the image against the asset, which is what a new technician needs.<\/p>\n<p>A check should follow, because a map that is never compared with the field drifts within a season. <a href=\"https:\/\/zama.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> supports a periodic audit, which is cheaper than a wrong dig.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Talking_to_Field_Teams_and_Planners\"><\/span>Talking to Field Teams and Planners<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Documentation is a field tool, and it fails when it is treated as an office obligation.<\/p>\n<p>A technician should be able to open it offline, because a basement, a trench, and a far estate rarely have signal. <a href=\"https:\/\/pawa.co.ke\">Network documentation software in Kenya<\/a> works offline and syncs, which is the only design that survives a Kenyan build.<\/p>\n<p>A planner should see spare capacity, because a new customer should be connected to an existing fibre where possible. <a href=\"https:\/\/pms.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> shows it, which turns a build decision into a query.<\/p>\n<p>A manager should see gaps, since a network with unrecorded sections is a network with unknown risk. <a href=\"https:\/\/estateadmin.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> reports completeness, which is the metric that keeps the record alive.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"As-Builts_Variations_and_Exceptions\"><\/span>As-Builts, Variations and Exceptions<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The as-built is the document a contractor is paid against, and the difference between it and the design is where money leaks.<\/p>\n<p>A variation should be recorded, because a route that moved twenty metres may cost more or less than the contract. <a href=\"https:\/\/churchesadmin.com\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> captures it, which is what makes a final account defensible.<\/p>\n<p>A deviation should be approved, since a change made on site without a record becomes a dispute at handover. <a href=\"https:\/\/vega.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> routes the approval, which is cheaper than a rework.<\/p>\n<p>A missing section should be flagged, because a gap in the as-built is a gap in the maintenance plan. <a href=\"https:\/\/dereva.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> highlights it, which is what an auditor will ask about.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Records_Handover_and_Audit\"><\/span>Records, Handover and Audit<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A network passes through many hands, and each handover is a test of whether the record is real.<\/p>\n<p>A handover should include the documentation, because a new operator inherits the network and its risks. <a href=\"https:\/\/jaat.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> packages it, which is what makes due diligence possible.<\/p>\n<p>An audit should compare the record with the field, since a map that is ninety per cent right is a map that wastes ten per cent of every dig. <a href=\"https:\/\/wito.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> supports sampling, which is enough to estimate the gap.<\/p>\n<p>A licence application may require a route plan, and a provider that can produce one moves faster. <a href=\"https:\/\/awasam.com\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> generates it, which is a quiet commercial advantage.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Linking_Documentation_to_Operations\"><\/span>Linking Documentation to Operations<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A documentation system that stands alone becomes a second job, so integration is what makes it survive.<\/p>\n<p>A fault ticket should open the map, because a technician needs the route before leaving the depot. <a href=\"https:\/\/saseni.com\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> links the two, which cuts travel time on every job.<\/p>\n<p>A new connection should update the record, since a customer installed without a documented port is a customer who will be hard to support. <a href=\"https:\/\/prim.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> updates it, which keeps the map honest.<\/p>\n<p>A capacity report should draw on the map, because a route at eighty per cent utilisation needs a plan rather than a surprise. <a href=\"https:\/\/rentaldesk.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> produces it, which is what makes the upgrade decision early.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Live_Views_of_Network_State\"><\/span>Live Views of Network State<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Someone has to know what is where and what is spare, and the answer should be immediate.<\/p>\n<p>A map view is the starting point, because a network is a physical object before it is a spreadsheet. <a href=\"https:\/\/fama.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> shows it, which is what makes the tool approachable.<\/p>\n<p>A filter by route, estate, or device turns the map into a diagnostic tool, since a fault in Kasarani should not require scrolling through Mombasa. <a href=\"https:\/\/spacekits.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> answers that question.<\/p>\n<p>An alert on an unrecorded asset prevents a shadow network from growing, which is common when contractors work unsupervised. <a href=\"https:\/\/zamacore.com\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> raises it, which is the control that keeps the record complete.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Multiple_Teams_and_Contractors\"><\/span>Multiple Teams and Contractors<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Once several crews and contractors work on the same network, documentation becomes a coordination problem rather than a filing one.<\/p>\n<p>Each crew should update its own section, because a central team cannot chase every trench. <a href=\"https:\/\/mystayorbit.com\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> assigns sections, which is what makes the update realistic.<\/p>\n<p>A contractor should see the standard, since a splice recorded in a different format is a splice that will be misread. <a href=\"https:\/\/dexa.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> enforces one template, which is what keeps the map readable.<\/p>\n<p>A group view should exist, because a manager needs the whole network without merging five files. <a href=\"https:\/\/zama.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> consolidates it, which is what makes a weekly review possible.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Reports_That_Show_Documentation_Health\"><\/span>Reports That Show Documentation Health<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A documentation report is useful when it measures completeness rather than activity.<\/p>\n<p>Assets recorded against assets built is the first number, because a network at seventy per cent documented is a network with thirty per cent unknown risk. <a href=\"https:\/\/pawa.co.ke\">Network documentation software in Kenya<\/a> calculates it by route.<\/p>\n<p>Time since last field check is the second, since a route that has not been verified in two years is probably wrong. <a href=\"https:\/\/pms.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> reports it, which prompts a rewalk.<\/p>\n<p>Faults resolved without a dig is the third, and it shows whether the map is actually being used. <a href=\"https:\/\/estateadmin.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> tracks it, which is the outcome that matters.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Choosing_a_Documentation_Platform\"><\/span>Choosing a Documentation Platform<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The right platform depends on the network and the team, and there is no single answer.<\/p>\n<p>Match the tool to the network type, because a wireless operator and a fibre builder need different objects. <a href=\"https:\/\/churchesadmin.com\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> vendors who understand both are rare and worth finding.<\/p>\n<p>Check the offline behaviour, since the field is where the data is created and the field is where signal fails. <a href=\"https:\/\/vega.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> that captures offline is the only kind that works.<\/p>\n<p>Consider the export, because a map that cannot be taken to another system is a hostage rather than an asset. A platform that exports cleanly protects the operator.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Rolling_Out_Documentation\"><\/span>Rolling Out Documentation<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A documentation programme should start with the part of the network that hurts most, not with the whole map.<\/p>\n<p>Begin with the routes that generate the most faults, where a good record saves the most time. <a href=\"https:\/\/jaat.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> supports that narrow start, and a fast fault resolution sells the idea to the team.<\/p>\n<p>Add field capture next, because the record only stays current if it is updated in the field. <a href=\"https:\/\/wito.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> makes it quick, which is what makes it happen.<\/p>\n<p>Then widen to the whole network, letting each crew copy a proven routine. <a href=\"https:\/\/awasam.com\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> makes that expansion repeatable, which is how a pilot becomes a standard.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Where_Documentation_Fails\"><\/span>Where Documentation Fails<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Documentation fails for cultural reasons, and the software is rarely the cause.<\/p>\n<p>It fails when the map is owned by one person, because a single owner becomes a bottleneck and then a single point of failure. <a href=\"https:\/\/saseni.com\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> needs a shared owner, which is a management decision rather than a feature.<\/p>\n<p>It fails when it is updated monthly, since a monthly update is a monthly reconstruction. <a href=\"https:\/\/prim.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> works when the update is part of the job, not an extra task.<\/p>\n<p>It fails when nobody checks, because a record that is never compared with reality drifts into fiction. <a href=\"https:\/\/fama.co.ke\" target=\"_blank\" rel=\"noopener\">Network documentation software in Kenya<\/a> that supports a field audit is the one that stays true.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"The_Value_of_a_Map_in_a_Dispute\"><\/span>The Value of a Map in a Dispute<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A network dispute, with a landlord, a contractor, or a county, usually turns on where something is and when it was built.<\/p>\n<p>A dated map with photographs answers both questions, and it does so without relying on anyone&#8217;s memory. That is a defensive asset that costs almost nothing to maintain once the routine exists.<\/p>\n<p>Providers who document well tend to win these disputes quietly, and the cost of losing one is usually higher than a year of the software.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Documentation_and_Network_Value\"><\/span>Documentation and Network Value<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A network is valued on its ability to serve customers, and documentation is part of that ability. A buyer pays more for a network that can be understood, because the risk of the unknown is priced in.<\/p>\n<p>That is why documentation appears in due diligence, and why a missing map reduces an offer. The record is not administrative; it is part of the asset.<\/p>\n<p>Operators who plan to sell, or to raise money, should treat documentation as a balance sheet item rather than a chore.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"A_Closing_Note_on_Memory\"><\/span>A Closing Note on Memory<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Every network has a memory. The question is whether it lives in a system or in a few people&#8217;s heads.<\/p>\n<p>A system survives resignations, expands with the network, and can be read by a newcomer. A memory does not.<\/p>\n<p>The providers that grow beyond a single town are almost always the ones that wrote things down.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"IP_Addressing_and_Documentation\"><\/span>IP Addressing and Documentation<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>An IP plan is documentation of a different kind, and it fails in the same way: an address assigned without a record becomes a conflict six months later.<\/p>\n<p>A simple register of subnets, gateways, and DHCP ranges prevents the duplicate that takes a whole estate offline. It also makes a device replacement a five-minute job rather than an afternoon of guessing.<\/p>\n<p>A documentation platform that holds addresses beside circuits gives one place to look when a customer reports a problem that is neither fibre nor radio.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Device_Configuration_Records\"><\/span>Device Configuration Records<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A router&#8217;s configuration is part of the network, and a configuration that exists only on the device is lost when the device fails.<\/p>\n<p>A stored configuration, with a date and a version, turns a replacement into a restore rather than a rebuild. That is the difference between an hour and a day.<\/p>\n<p>The same record answers the question every audit asks: what changed, when, and who approved it.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Customer_Premises_Records\"><\/span>Customer Premises Records<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A customer record should include the drop, the port, the CPE serial, and the splitter, because support begins with those four facts.<\/p>\n<p>Without them, a fault call starts with a search across three systems and a phone call to the installer. With them, the technician leaves with the right equipment and the right address.<\/p>\n<p>That record also protects the operator at churn, when the equipment must be recovered rather than written off.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Documentation_During_a_Build\"><\/span>Documentation During a Build<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A build is the best and worst time to document: the information is available, and the crew is busy.<\/p>\n<p>Capturing at the moment of installation is the only method that works, which means the process must be faster than the alternative. A photo and three taps is faster than a note that gets typed later.<\/p>\n<p>A supervisor who checks the record before signing off the day&#8217;s work changes the habit within a week.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"The_Cost_of_a_Wrong_Dig\"><\/span>The Cost of a Wrong Dig<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A wrong dig is expensive in a way that is easy to underestimate: the trench, the reinstatement, the angry landlord, and the day lost.<\/p>\n<p>Most wrong digs come from a map that is out of date rather than from a missing map. That distinction matters, because it means the fix is a routine, not a project.<\/p>\n<p>A record updated on the day of the repair is worth more than a perfect record updated annually.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Documentation_and_Insurance\"><\/span>Documentation and Insurance<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A network is insured, and a claim after a fire or a theft needs an asset list with values.<\/p>\n<p>A documentation platform that holds assets and costs produces that list in minutes. A provider without one negotiates from memory, which is a weak position.<\/p>\n<p>The same list supports a valuation at sale, which is a second reason to keep it current.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Working_With_Contractors\"><\/span>Working With Contractors<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A contractor builds to a design and is paid against an as-built, and the gap between the two is where disputes live.<\/p>\n<p>A shared platform removes the gap, because the contractor records what was built and the client sees it immediately. That is faster than a monthly submission and far less adversarial.<\/p>\n<p>It also gives the contractor a record of variations, which is protection when the client disputes an invoice.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Documentation_for_Regulatory_Filings\"><\/span>Documentation for Regulatory Filings<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A licence application or a compliance return often needs a network diagram and a route description.<\/p>\n<p>A platform that generates both turns a week of drafting into an afternoon. Providers who file regularly learn to keep the record in the shape the regulator expects.<\/p>\n<p>That is not a reason to document, but it is a useful side effect.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Keeping_the_Map_Alive\"><\/span>Keeping the Map Alive<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A map stays alive through three habits: capture at the point of work, review at the end of the week, and audit at the end of the quarter.<\/p>\n<p>Each habit is small, and together they replace the annual reconstruction that most providers endure. The annual reconstruction is expensive, inaccurate, and usually triggered by a crisis.<\/p>\n<p>A provider that does the three habits never needs the reconstruction.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Documentation_and_Team_Morale\"><\/span>Documentation and Team Morale<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>An engineer who can find the answer is an engineer who feels competent, and competence is what keeps technical staff.<\/p>\n<p>The opposite is also true: an engineer who spends a day digging in the wrong place starts looking for another employer. Documentation is a retention tool disguised as administration.<\/p>\n<p>That is worth saying plainly, because it is rarely counted in the business case.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"A_Closing_Note_on_Simplicity\"><\/span>A Closing Note on Simplicity<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A documentation system should be simple enough to use in a trench and rich enough to answer a planner&#8217;s question.<\/p>\n<p>That balance is achievable, and it is the difference between a tool that is used and a tool that is admired. The test is not the feature list but whether the last technician opened it.<\/p>\n<p>If they did, the network is documented. If they did not, it is not.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Documentation_and_Spare_Capacity\"><\/span>Documentation and Spare Capacity<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A map that shows what is used is half a map; the valuable half is what is free.<\/p>\n<p>A route with four spare fibres can serve a new customer without a new trench, and that is a commercial advantage. A provider that cannot see the spare capacity will build unnecessarily and quote a higher price.<\/p>\n<p>Recording utilisation at the port and the fibre level makes the difference visible, and it turns a sales question into a technical answer within minutes.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Documentation_and_Fault_History\"><\/span>Documentation and Fault History<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A fault history attached to the asset is a maintenance tool, because a joint that fails twice a year needs replacing rather than repairing.<\/p>\n<p>A record that shows the last five faults on a route, with dates and causes, turns a recurring problem into a decision. Without it, the same repair is repeated until someone loses patience.<\/p>\n<p>That pattern is most visible at joints and at crossings, which are the two places where water and traffic do the most damage.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Documentation_and_Network_Planning\"><\/span>Documentation and Network Planning<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A plan that starts from a blank page ignores what the network already covers.<\/p>\n<p>A map that shows coverage, capacity, and demand together produces a plan that extends rather than duplicates. That is the difference between a build that reaches new customers and one that overbuilds an existing estate.<\/p>\n<p>The planning view does not need to be sophisticated; it needs to be current.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"The_Human_Side_of_Records\"><\/span>The Human Side of Records<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A record survives only if someone updates it when tired, at the end of a long day, with a queue of faults waiting.<\/p>\n<p>That is the real design constraint, and it explains why simple tools outperform comprehensive ones. A field form that takes thirty seconds will be used; one that takes five minutes will be skipped.<\/p>\n<p>The best documentation systems are built around that thirty seconds.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Documentation_for_New_Hires\"><\/span>Documentation for New Hires<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A new technician&#8217;s first week is a test of the network&#8217;s memory. With a map, they can be productive in days; without one, they follow someone around for a month.<\/p>\n<p>That onboarding cost is rarely counted, and it is one of the clearest returns on documentation. A provider that hires twice a year feels it directly.<\/p>\n<p>A good map also shortens the handover when an engineer resigns, which is the moment documentation pays for itself.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Working_With_Landlords_and_Wayleaves\"><\/span>Working With Landlords and Wayleaves<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A route through private land needs a wayleave, and a wayleave needs a description of what was built.<\/p>\n<p>A map with coordinates, lengths, and photographs supports that description, which speeds approval and reduces disputes. A provider that can show exactly where the cable runs is easier to trust.<\/p>\n<p>The same record helps when a landlord changes and the new owner asks what is buried on the property.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Documentation_and_Customer_Communication\"><\/span>Documentation and Customer Communication<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A customer who reports a fault wants a time, not a promise. A technician who can see the route and the joint can give one.<\/p>\n<p>That small certainty reduces repeat calls and improves satisfaction, and it costs nothing beyond an accurate map. Support quality is often a documentation problem in disguise.<\/p>\n<p>The clearest sign of a well-documented network is a support team that answers with specifics.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Documentation_as_a_Habit\"><\/span>Documentation as a Habit<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Documentation is a habit before it is a tool, and habits are built by making the right action the easy one.<\/p>\n<p>A capture step embedded in the repair process is a habit; a separate documentation session is a chore. The difference is entirely in the design of the workflow.<\/p>\n<p>A manager who checks the record as part of the job closes the loop, and the loop is what keeps the network knowable.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"A_Final_Word_on_Scale\"><\/span>A Final Word on Scale<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A network of ten sites can be held in one person&#8217;s head. A network of a hundred cannot.<\/p>\n<p>The transition between those two states is where most providers lose control, and documentation is the bridge. Building it early is cheap; rebuilding it later is expensive.<\/p>\n<p>The providers that make the transition well are the ones that wrote things down while it was still easy.<\/p>\n<p>A map drawn while the trench is open costs an hour. The same map reconstructed two years later costs a week, and it is never quite right.<\/p>\n<p>That comparison is the whole argument, and it is worth making to anyone who still keeps the network in their head.<\/p>\n<p>A network that can be explained in a meeting is easier to fund, easier to sell, and easier to repair. A network that cannot is a set of assumptions held together by one person&#8217;s availability.<\/p>\n<p>Documentation is how a provider turns a private understanding into a shared asset.<\/p>\n<p>That asset has a measurable value at sale, at financing, and at the moment a key engineer resigns. Providers who document are paid for a network that can be understood, not just for one that works.<\/p>\n<p>The cost of building the record is small compared with the discount a buyer applies to a network nobody can explain.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Network documentation software in Kenya records every route, joint, splitter, port, IP address, and device in a network, and keeps that record current as the network grows, so an engineer can find a fault without guessing. A Kenyan ISP builds fast, and the paperwork usually arrives last, if it arrives at all. The result is [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[46,34,4,3,5,2,37,8,21,7],"tags":[209],"class_list":["post-2160","post","type-post","status-publish","format-standard","hentry","category-hotspot-hardware-fix","category-hotspot-requrements","category-isp-billing","category-mikrotik-hotspot","category-pawa-updates","category-wifi-billing","category-wifi-billing-software","category-wifi-billing-systems","category-wifi-business-solutions","category-wifi-hotspot","tag-network-documentation-software-in-kenya"],"_links":{"self":[{"href":"https:\/\/pawa.co.ke\/blog\/wp-json\/wp\/v2\/posts\/2160","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pawa.co.ke\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pawa.co.ke\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pawa.co.ke\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/pawa.co.ke\/blog\/wp-json\/wp\/v2\/comments?post=2160"}],"version-history":[{"count":4,"href":"https:\/\/pawa.co.ke\/blog\/wp-json\/wp\/v2\/posts\/2160\/revisions"}],"predecessor-version":[{"id":2177,"href":"https:\/\/pawa.co.ke\/blog\/wp-json\/wp\/v2\/posts\/2160\/revisions\/2177"}],"wp:attachment":[{"href":"https:\/\/pawa.co.ke\/blog\/wp-json\/wp\/v2\/media?parent=2160"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pawa.co.ke\/blog\/wp-json\/wp\/v2\/categories?post=2160"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pawa.co.ke\/blog\/wp-json\/wp\/v2\/tags?post=2160"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}