Use this page to find the workflow you need. Each feature page answers five questions:
The feature page describes the required outcome. The development team decides the safe screen, database, API and test design needed to produce that outcome.
Status is against commit ebf7cf0, 18 September 2026.
| Count | Status |
|---|---|
| 5 | Aligned — implemented as approved |
| 15 | Partial — partly implemented |
| 9 | Gap — approved but not implemented |
| 1 | Context — historical information, not a feature |
| Feature | What it covers | Status |
|---|---|---|
| Order intake | Indoor creates a direct order or converts a quotation | Partial |
| Quotation | The optional official price document | Aligned |
| Pricing | Default price, floor price, one overall discount | Partial |
| Order number and identity | Two identities, minted at first dispatch | Aligned |
| Feature | What it covers | Status |
|---|---|---|
| Dispatch hard gate | Required checks before a Job Log can be dispatched | Aligned |
| Susun trip dispatch | OE plans several assignments privately, then confirms them together | Aligned |
| Ad hoc task | Internal work with no customer order | Partial |
| Dispatch notifications | Telling the technician the schedule changed | Partial |
| Helper and vehicle roster | Reading the one central fleet list | Partial |
| Daily pairing | Morning check-in: today's vehicle and helpers | Partial |
| Feature | What it covers | Status |
|---|---|---|
| Start job | Opening the visit and freezing its context | Aligned |
| Job photos and proof | Arrival and completion evidence | Partial |
| On-site itemize review | The technician adjusts what was actually done | Partial |
| Customer preview and signature | Informed consent, and the one exception to it | Gap |
| Customer identity capture | IC or licence on an unpaid visit | Partial |
| Job outcome | The six ways a visit can end | Gap |
| Recheck and continuation | Warranty returns and continued work | Gap |
| Reassign flow | Handing the visit to someone else | Gap |
| Feature | What it covers | Status |
|---|---|---|
| Record payment | Taking money, and where it goes | Partial |
| Multi-payment lifecycle | Deposits and staged collections on one order | Partial |
| Account verify and flag | Account checks the final amount and flags incorrect lines | Partial |
| OE flag handler | OE corrects the lines Account flagged | Partial |
| Account posting and AutoCount | One person requests posting and another approves it | Gap |
| Refunds | Returning money to a customer | Gap |
| Feature | What it covers | Status |
|---|---|---|
| Order cancellation and restricted deletion | Two different actions, often confused | Gap |
| Follow-up queue | Postpone, On Hold and Cancel chased consistently | Gap |
| Order detail workspace | One record of an order, not three | Gap |
| Feature | What it covers | Status |
|---|---|---|
| PBAC capability enforcement | Backend permissions controlling who can do what and for which branch | Partial |
| LG partner orders and billing | Installation work received from LG and billed monthly | Partial |
| Legacy AppSheet context | Historical data from the previous system | Context |
See also Cross-cutting requirements, which every feature inherits.