KENYA · GUIDE 0589 · EDITION 4.7
Spreadsheet dashboard building in Kenya: Delivery Planning and Acceptance Checks
Editorial update: 28 October 2026 · Business planning reference · Review scope
Plan delivery around observable acceptance
Plan the handover and acceptance record for spreadsheet dashboard building, using the specific checkpoints for the example offer.
This is a planning reference for spreadsheet dashboard building. The order below is an invented teaching case. It is not a completed customer job, an operating approval or a prediction of demand or earnings.
The example offer and its boundary
Fictional dashboard DSH-89 summarises an owner-approved sales table using four fixture rows: confirmed 500, confirmed 700, cancelled 300 and refund 200. The example definitions yield confirmed sales 1,200, refunds 200 and net 1,000; cancelled 300 is excluded. These are invented test values, not audited accounts. Output is source table, metric dictionary, three KPI cells, one monthly chart and refresh instructions. Forecasting, tax reporting, accounting assurance and live-system integration are excluded.
This page is a work-control sheet. It does not teach a qualified trade, prescribe a food process, approve equipment or replace the appropriate technical procedure. Confirm who has the competence and authority for any specialist task.
Prepare the control record
| Stage to schedule | Checkpoint from the scoped example | Actual record to complete |
|---|---|---|
| Define metrics before charts | Order value, cash received and revenue are not assumed interchangeable. | Responsible person; evidence/reference; measured result; pass/hold decision; correction owner |
| Structure inputs | Preserve leading-zero IDs and keep rejected rows visible. | Responsible person; evidence/reference; measured result; pass/hold decision; correction owner |
| Build explainable formulas | Matching sum/criteria ranges cover the same rows and the fixture returns 1,200,200,1,000. | Responsible person; evidence/reference; measured result; pass/hold decision; correction owner |
| Test refresh and filters | New rows extend the source table automatically; a filter cannot silently change the meaning of the headline KPI. | Responsible person; evidence/reference; measured result; pass/hold decision; correction owner |
| Handover source lineage | Chart period/units and last refresh are visible; owner signs off definitions before live use. | Responsible person; evidence/reference; measured result; pass/hold decision; correction owner |
Keep accepted and unresolved work separate
| Issue to watch for | Evidence question |
|---|---|
| New month missing | Check source-table expansion and chart range. |
| Net double-subtracts refund | Compare signed amounts with metric definition. |
| Zero appears for broken import | Check source row count and refresh errors. |
The issues above are prompts to investigate, not a diagnosis of a real defect. Record what was observed, isolate the affected output where appropriate, and refer the technical decision to the competent person or approved process. Do not copy a hypothetical response into a real incident without assessment.
Reconcile the handover
Use the agreed charging basis: dashboard project. Record ordered, completed, accepted, held and rejected output separately. Track rework time, changed scope, credits and collection dates against the same order reference. Chart period/units and last refresh are visible; owner signs off definitions before live use.
Proceed within a defined trial limit only after the buyer's acceptance, actual full costs and collections are recorded, and the guide's unresolved checks are addressed. The final business-specific checkpoint is: Chart period/units and last refresh are visible; owner signs off definitions before live use. Otherwise record a hold, revision or stop decision in file 10.
References and their limits
SUMIFS function — Microsoft
Conditional summation and matching range dimensions; business metric definitions remain client decisions. Reference check recorded 2026-10-26.
Keeping leading zeros and large numbers — Microsoft
Import identifier columns as text to preserve zeros and precision. Reference check recorded 2026-10-26.
Import data from data sources (Power Query)
Import preview and data-source workflow; version-specific menus may differ. Reference check recorded 2026-10-26.
Recorded references support only the scope stated beside them. They do not prove current supplier stock, a local quotation, actual buyer demand, operator competence or the feasibility of this particular business. Later editorial changes do not refresh earlier source-check dates.
Prepared by Business Starter Guides using AI-assisted drafting and desk editorial checks. Independent operator trials and specialist certification are not claimed. See the editorial method for the review scope.
Editorial method and evidence limits