KENYA · GUIDE 0609 · EDITION 4.2
Desktop assembly service in Kenya: Operations and Quality Checks
Deliver the agreed result consistently
Assemble desktops around the buyer's actual workloads, agreed component list, compatibility, software licensing, upgrade needs, and support responsibilities before accepting deposits or ordering parts.
The operating sequence for this offer is:
- Translate the customer's workload into a written component specification, including ports, storage, memory and software requirements before ordering parts.
- Check component compatibility and warranty ownership, then assemble and test through a competent technician using a documented build record.
- Deliver the component inventory, licensed software details and representative workload test results, explaining upgrade limits and the agreed support period.
Put acceptance into the job record
Deliver a component inventory, test record and clear support scope without claiming performance beyond tests.
Run representative workloads and component checks, verifying ports, storage recognition, cooling behaviour, and supplied accessories against the agreed specification before the customer accepts delivery.
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 | Assemble desktops around the buyer's actual workloads, agreed component list, compatibility, software licensing, upgrade needs, and support responsibilities before accepting deposits or ordering parts. |
| During delivery | Check component compatibility and warranty ownership, then assemble and test through a competent technician using a documented build record. |
| At acceptance | Run representative workloads and component checks, verifying ports, storage recognition, cooling behaviour, and supplied accessories against the agreed specification before the customer accepts delivery. |
| At the pilot review | Keep workload brief, approved parts, compatibility decisions, supplier records, assembly notes, functional results, included licenses, and owner acceptance of any substituted component before delivery. |
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.
A powerful-looking specification disappoints when incompatible parts delay assembly or the customer cannot perform the intended work without software and accessories excluded from quotation.
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 | Check CPU socket/firmware, RAM generation/density, SSD interface and graphics support. | Physical socket fit alone does not prove firmware support. |
| 2 | Verify case form factor, clearances and PSU connectors/capacity from manufacturers. | Never open or modify a mains PSU. |
| 3 | Use ESD precautions and component-specific installation guidance. | No forced connectors or improvised spacers. |
| 4 | Check firmware detects 16GB/512GBclass storage and run appropriate diagnostics. | Record actual errors and supported OS/licence requirements. |
| 5 | Demonstrate boot, network, display and agreed office tasks. | Owner receives serials, warranty sources and recovery instructions. |
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 |
|---|---|---|
| No display | Check approved graphics path and qualified diagnostics. | Stop random swaps; follow manuals. |
| RAM not fully detected | Check compatibility/seating through competent operator. | Resolve and rerun diagnostics. |
| Case does not fit board | Compare form factors. | Correct BOM before forcing assembly. |
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.