The six ways a visit can end, and why Recheck is not one of them.
Status at ebf7cf0: Gap — the endpoint records the outcome but does not create the required follow-up Job Log, older aliases are still accepted, and the database does not enforce the six canonical values.
The field worker ends a visit and selects exactly one Job Outcome.
| Stored value | Means |
|---|---|
complete |
Work for this visit is complete. |
sambung_kerja |
More work is required on the same Order. |
postpone |
The customer provided a return date; store it when known. |
on_hold |
No firm date exists; a reason and a follow-up action are required. |
reassign |
A different technician or team is required. |
cancel |
The customer requested order cancellation. This ends the visit only — Indoor or OE decides whether the Order may be cancelled. |
The six-outcome list matches the enum already built and documented in FEATURE-DETAILS.md ("Feature: Job outcome — six paths") and in data.md. Ruled 19 August 2026, in OE's wording. Labels are plain words in three languages per master § 2c — Sambung Kerja stays. The technician picker must show these six only, not eight.
| Field | Purpose | Values |
|---|---|---|
| Job Type | Why the visit exists | New, Continue, Recheck |
| Job Status | Where the visit is now | Scheduled, In Progress, Completed |
| Job Outcome | The field worker's conclusion | the six above |
Recheck is a Job Type, never an outcome. Changing one field must never silently rewrite the others.
sambung_kerja creates a new Draft Job Log on the same Order with no date and Waiting Schedule, so OE can arrange it. Only outcome and reason are required from the technician.reassign creates a new unscheduled draft for OE. The technician does not choose the next technician or date.cancel does not cancel the order. A technician or subcon cannot cancel an order.Story. As a Technician, I want Complete, Sambung Kerja, Postpone, On Hold, Reassign and Cancel as the only outcome choices, so that downstream work is predictable.
Acceptance. Stored values arecomplete,sambung_kerja,postpone,on_hold,reassignandcancel.
Story. As a Technician, I want help distinguishing Postpone from On Hold, so that the correct follow-up behavior starts.
Acceptance. Postpone requires a known return date when available; On Hold requires a reason and follow-up action without a firm date.
Story. As the system, I want outcome, Job Type and Job Status stored separately, so that Recheck is never confused with an outcome.
Acceptance. Changing one field does not silently rewrite the others.
The outcome endpoint records a value on the existing Job Log but does not create the required follow-up Job Log. Older aliases are still accepted and the database does not enforce the six canonical values. The code held seven internal names (postpone and reschedule were one event) and showed "Reassigned to OE".
Developer task: merge those, rename to OE's six, retire the five-row August table.
This was reported as "Operations disagrees with what we built." It was really "our own document disagrees with what we built, and Operations agrees with the build."
FEATURE-DETAILS.md line 1083 said "Sambung_kerja without proposed next date → validation error." Helmi, in the group at 14:57 on 19/08: "for continue job, system only validate the outcome + reason only." The system asks for an outcome and a reason. It does not force a next date and never did. The validation rule existed only on paper. OE's empty-date answer described what the system already did.
A written rule is not evidence that the rule was implemented. Before raising a mismatch with a developer, check the running system, not only the specification — otherwise the developer is asked to defend a rule nobody ever wrote into code.
New to these terms? See the Glossary.