The problem it solves
In many businesses that make, prepare or deliver things to a schedule, the schedule is a workbook. It is emailed, copied, edited and handed over through messages, and nobody can answer simple questions with confidence: Which version is current? Which items are ready for cutting or production? Who changed this, and when? Did the workbook contain an error before it was imported?
Dingo gives the business one delivery context that connects the workbook, the work items created from it, their status, the preparation steps and their history, through to the delivery run.
What it does
| Capability | What the business gets |
|---|---|
| Schedule management | Every job has a clear parent record with project context, date, code and version. |
| Excel import | Schedule rows are brought in without manual re-entry. |
| Preview and validation | Data issues are found and resolved before they affect live work. |
| Schedule items | Each row of work is visible and searchable in its schedule context. |
| Work statuses | A configurable status flow that every team shares. |
| Preparation sheets | Preparation work (for example cutting sheets) stays connected to the correct schedule. |
| History | A traceable record of imports and item activity. |
| Dashboard | Queues, in-progress work, readiness, delivery and stock indicators at a glance. |
| Business configuration | Administrators maintain import rules and the status workflow. |
The record chain
Client
-> Project
-> Schedule
-> Schedule items
-> Preparation sheets
-> Import history and item history
Principles
Validate before creating work. The import preview is a decision point, so errors are resolved before a workbook becomes live items.
Keep work in its schedule context. Items, preparation sheets, imports and histories are connected to their schedule; a row is never interpreted without the job it belongs to.
Make progress visible. Statuses and dashboard indicators give a practical view of queues, work in progress and readiness for the next team.
Preserve the audit trail. Version, lock, import and item history explain what happened, instead of relying on memory or duplicate files.
Where it came from
Dingo grew out of the same thinking as our matrix planning work for a manufacturing plant: replace circulating spreadsheets with one constrained, traceable view of the work, all the way to the delivery run.
Getting it
Dingo is in use today. If your deliveries run on schedule workbooks and hand-overs, get in touch and we will show you how it fits.