KENYA · GUIDE 0540 · EDITION 4.2
Local directory listing cleanup in Kenya: Operations and Quality Checks
Deliver the agreed result consistently
Clean up a defined list of directory profiles, establishing the business's approved name, contact details, location wording, opening hours, ownership access, and duplicate-handling priorities before editing.
The operating sequence for this offer is:
- Compile the relevant directories and current owner-verified business details, then identify supported corrections and any ownership-verification steps required.
- Submit only authorized factual updates, keep a change register and avoid paying or disclosing credentials to suspicious directory solicitations.
- Report accepted, rejected and pending changes separately, return any account control and do not promise universal removal of outdated listings.
Put acceptance into the job record
Only genuine business facts are changed; verification outcomes remain visible.
Ask the owner to check sampled live listings and follow contact links, distinguishing changes actually published from correction requests that the directory has not accepted yet.
Inspect at the point where a correction is still possible, then again at handover. Record rejected or incomplete output separately from accepted output. A completed task is not automatically an accepted task, and an invoice does not establish that the customer received the right result.
Measure real capacity
Time preparation, the main operation, transport, cleaning, approvals and correction as applicable. The slowest stage determines how much you can promise. Where two orders need the same person, space or equipment at the same time, resolve the conflict before confirming both deadlines. An additional enquiry should not erase a commitment already made.
| Operating checkpoint | Evidence for this business |
|---|---|
| Before starting | Clean up a defined list of directory profiles, establishing the business's approved name, contact details, location wording, opening hours, ownership access, and duplicate-handling priorities before editing. |
| During delivery | Submit only authorized factual updates, keep a change register and avoid paying or disclosing credentials to suspicious directory solicitations. |
| At acceptance | Ask the owner to check sampled live listings and follow contact links, distinguishing changes actually published from correction requests that the directory has not accepted yet. |
| At the pilot review | Record directory URLs, ownership status, original inaccuracies, requested edits, submission dates, published changes, unresolved duplicates, and owner verification of the final customer-facing contact information in each profile. |
Keep a correction and escalation rule
When inputs, access, specifications or customer instructions change, pause the affected work and confirm the effect on time and cost. Do not quietly lower the acceptance standard to avoid a delayed delivery. Keep rework caused by your error distinct from a customer-requested change of scope and agree the remedy clearly.
An incomplete cleanup can confuse customers when one prominent listing still shows an old phone number, even though less visible profiles have all been corrected successfully.
Retain the minimum records needed to investigate a complaint without disclosing unrelated personal information. Use measured delivery and actual acceptance as the basis for expanding capacity, rather than the maximum theoretical output of a tool or production line.
Operating control points for this exact offer
| Sequence | Work method | Release checkpoint |
|---|---|---|
| 1 | Record three listing URLs and check whether duplicates or similarly named businesses are being confused. | Only the client's actual entries enter the correction scope. |
| 2 | Have the owner approve real-world name, phone, website, hours and service area. | Do not add town names or keywords to a registered/displayed name for search manipulation. |
| 3 | Use owner-managed access or each directory's official correction route and obtain written consent. | No pre-emptive claim is made to force the business to become a customer. |
| 4 | Record old/new field values, submission date and platform response separately for each site. | A submitted request is not reported as accepted; Google-specific rules are not assumed to govern unrelated directories. |
| 5 | Compare visible entries with the approved source and list remaining conflicts. | Client receives access/handover instructions and any unresolved ownership problem rather than a false all-clean result. |
Do not substitute a tick for an observation: record the count, measurement, approved sample or evidence reference used at each checkpoint. Mark unresolved work as held and identify who can approve the recheck.
Diagnose a failure before repeating it
| Observed symptom to investigate | Check the cause | Proposed response |
|---|---|---|
| Another firm's entry selected | Compare address, phone and ownership history. | Remove it from scope and locate the correct client record. |
| Correction reverts | Check platform update notices and the authoritative source information. | Document the conflict and use the directory's official support route. |
| Client wants a fake local address | Check whether the firm actually operates there under applicable platform rules. | Decline the unsupported location and propose truthful service-area information. |
These are diagnostic prompts, not proof of the cause in a real incident. Separate suspect output, record any correction and repeat the relevant acceptance check. Link rejected units, rework time, replacement materials, customer credits and collection delays to the actual job result.