Adding a visit estimate to a job form creates a question about every job already in the app: what should the new field say when nobody has answered it? A default of zero can make the table look complete while hiding unanswered work.
This optional Part 4 guide, Test the app you built, uses six fictional service jobs to prepare a field change for an existing app. You will separate an unanswered estimate from a confirmed zero, compare every old record and define the behavior to test on old and new screens. The example specifies expected results; it does not change a database or demonstrate a completed migration.
For the native steps, use adding a field to an existing data table. Keep that help page beside the evidence review below.
1. Define the answer before choosing a default
Our proposed field is estimated_visit_minutes: an optional whole number of minutes, zero or greater. Its meaning is specific to this example:
Scroll horizontally to compare all columns.
| Stored value | Declared meaning | Evidence needed |
|---|---|---|
30 |
A 30-minute estimate | An explicit estimate for this job |
0 |
No on-site visit is needed | Explicit confirmation of no visit |
null |
The estimate has not been established | Keep the reason unresolved beside the source evidence |
The six original records have no estimated_visit_minutes field. The first proposed stage adds the field with null for all six; the next stage fills only values supported by the fictional evidence. These are acceptance targets to review and test, not a claim about what adding a field automatically does in your app.
Do not use a job's name, Completed label or empty response to invent an estimate. “Quick” also supplies no number of minutes. Preserve that response as evidence without converting it into a guessed number.
In JSON, an absent field and a field containing null are different representations. The business meaning of null comes from your declared rule. The JSON Schema reference explains the representation; it cannot decide what an unanswered job means for your team.
2. Trace each proposed value to its evidence
All jobs, responses and speakers in this example are fictional. The evidence inventory has seven rows because J104 has two conflicting estimates.
Scroll horizontally to compare all columns.
| Job | Supplied evidence | Proposed estimate | Decision |
|---|---|---|---|
| J101 | E101 explicitly estimates 30 minutes | 30 |
Use the established estimate |
| J102 | E102 explicitly confirms no on-site visit | 0 |
Keep the confirmed zero |
| J103 | E103 records no reply | null |
Unanswered |
| J104 | E104A says 30; E104B says 45 | null |
Hold the conflict for clarification |
| J105 | E105 says “quick” | null |
No numeric estimate established |
| J106 | E106 records an empty response | null |
Unanswered |
J104 does not become 37.5 minutes by averaging the responses. That would create a new answer neither source supplied. J105 and J106 do not become zero through type conversion. Keep the raw evidence and its disposition, even when several different problems share the same unresolved stored value.
The resulting report should say two of six jobs have established estimates; their subtotal is 30 minutes; the total for all six jobs is unknown. The confirmed zero contributes to coverage even though it adds nothing to the subtotal.
Now compare a rejected proposal that replaces the four unresolved values with zero. The subtotal is still 30. The apparent coverage changes from 2/6 to 6/6, falsely presenting four unanswered jobs as confirmed no-visit jobs. Checking the sum alone would miss this error. Review identities, meanings and coverage alongside arithmetic.
3. Compare complete records, not just the new column
Keep three review stages separate: original records, field added with unresolved values, and values proposed from evidence. For this example, the first comparison should show only the new field; the second should change only J101 to 30 and J102 to zero.
Check all six jobs and their three referenced clients. Preserve job IDs, client links, labels, notes, whitespace and tags exactly. A matching row count does not show that relationships or text survived. A preview containing only the two populated estimates cannot establish what happened to the four unresolved jobs.
Before making a real change, identify an authorized isolated test surface and verify its isolation. Overskill's Data editing help explains that Preview and the live app share the app database. Opening Preview alone does not isolate a data change.
If you use an export for comparison, check its contents and limits with the app-export guide. An export file does not establish that every record, relationship or file can be restored. Keep those checks separate from the new field's meaning.
Compare the field-change evidence
One new field, three different questions
estimated_visit_minutes accepts a nonnegative whole number of minutes or null. In this example, null means no estimate has been established. Zero means someone explicitly confirmed no on-site visit.
Diagram in words
- Original: six jobs; no estimate field. Preserve every ID, client link, label, note, space and tag.
- Field shape: the proposed optional-field stage adds six nulls. 0/6 estimates established; subtotal unavailable; all-job total unknown.
- Separate evidence: seven fictional sources contain a number, confirmed zero, no reply, a conflict, vague text and an empty response.
- Proposed answers: J101 is 30, J102 is 0, and J103–J106 remain null with different reasons. Coverage 2/6; known subtotal 30 minutes; all-job total unknown.
- Screen checks: each of six independent cases starts from that same proposal. Compare the complete expected records. Actual results are Not tested.
A required/default zero is a policy choice, not evidence for older records.
Two established estimates. Four unresolved.
| Job | Source | Proposed value | Reason |
|---|---|---|---|
| J101 | E101 | 30 | Explicit numeric estimate. |
| J102 | E102 | 0 | Explicit confirmation of no on-site visit. |
| J103 | E103 | null | No reply establishes no value. |
| J104 | E104A, E104B | null | Unresolved 30 versus 45; do not average or choose by order. |
| J105 | E105 | null | Quick has no numeric rule; do not coerce. |
| J106 | E106 | null | Empty answer is not zero. |
View the seven fictional evidence records (CSV) →
The CSV preserves the source responses as text. E101 and E102 include explicit confirmation, units and context for the proposed numeric values. This is not a general text-to-number import rule.
Open the complete examples
Each view contains all six jobs and all three clients. Quotes in JSON preserve leading and trailing spaces; \n represents the original line break. Check J101’s trailing note space and J105’s spaces, accented character, line break and empty tags.
Original records — complete records
Six jobs and three clients. The estimate field is absent.
View original records JSON →{
"fixture_kind": "Entirely authored fictional service-job records; not an account export or observed customer data.",
"authored_at": "2026-11-09T18:35:44.454665+00:00",
"snapshot_label": "N47 fictional job record set",
"clients": [
{
"id": "C101",
"name": "North Hall"
},
{
"id": "C102",
"name": "Orchard Workshop"
},
{
"id": "C103",
"name": "Willow Rooms"
}
],
"jobs": [
{
"id": "J101",
"label": "Replace lobby light",
"client_id": "C101",
"assigned_staff_id": "S01",
"status": "Scheduled",
"notes": "Keep this original note. ",
"tags": [
"lighting",
"lobby"
]
},
{
"id": "J102",
"label": "Remote sensor check",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "The old label is not proof of a visit estimate.",
"tags": [
"sensor"
]
},
{
"id": "J103",
"label": "Annual inspection",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Completed",
"notes": "Completed does not answer the new question.",
"tags": [
"inspection"
]
},
{
"id": "J104",
"label": "Fit door closer",
"client_id": "C101",
"assigned_staff_id": "S02",
"status": "Scheduled",
"notes": "Keep both later estimates for review.",
"tags": [
"door"
]
},
{
"id": "J105",
"label": " Café sign check ",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "Café sign\nSecond original line.",
"tags": []
},
{
"id": "J106",
"label": "Leak follow-up",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Open",
"notes": "",
"tags": [
"follow-up"
]
}
]
}Proposed optional-field stage — complete records
Six null estimates. 0/6 established. Subtotal unavailable; all-job total unknown.
View proposed optional-field stage JSON →{
"status": "AUTHORED_EXPECTED_STATE_ONLY_NOT_AN_EXECUTED_MIGRATION",
"record_set": {
"fixture_kind": "Entirely authored fictional service-job records; not an account export or observed customer data.",
"authored_at": "2026-11-09T18:35:44.454665+00:00",
"snapshot_label": "N47 fictional job record set",
"clients": [
{
"id": "C101",
"name": "North Hall"
},
{
"id": "C102",
"name": "Orchard Workshop"
},
{
"id": "C103",
"name": "Willow Rooms"
}
],
"jobs": [
{
"id": "J101",
"label": "Replace lobby light",
"client_id": "C101",
"assigned_staff_id": "S01",
"status": "Scheduled",
"notes": "Keep this original note. ",
"tags": [
"lighting",
"lobby"
],
"estimated_visit_minutes": null
},
{
"id": "J102",
"label": "Remote sensor check",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "The old label is not proof of a visit estimate.",
"tags": [
"sensor"
],
"estimated_visit_minutes": null
},
{
"id": "J103",
"label": "Annual inspection",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Completed",
"notes": "Completed does not answer the new question.",
"tags": [
"inspection"
],
"estimated_visit_minutes": null
},
{
"id": "J104",
"label": "Fit door closer",
"client_id": "C101",
"assigned_staff_id": "S02",
"status": "Scheduled",
"notes": "Keep both later estimates for review.",
"tags": [
"door"
],
"estimated_visit_minutes": null
},
{
"id": "J105",
"label": " Café sign check ",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "Café sign\nSecond original line.",
"tags": [],
"estimated_visit_minutes": null
},
{
"id": "J106",
"label": "Leak follow-up",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Open",
"notes": "",
"tags": [
"follow-up"
],
"estimated_visit_minutes": null
}
]
},
"coverage": {
"known": 0,
"denominator": 6,
"unresolved": 6,
"known_subtotal_minutes": null,
"display": "No established estimates; subtotal unavailable."
}
}Evidence-supported proposal — complete records
J101 is 30; J102 is 0; four estimates are unresolved. 2/6 established; known subtotal 30 minutes; all-job total unknown.
View evidence-supported proposal JSON →{
"status": "NON_WRITING_AUTHORED_PROPOSAL",
"before_stage": "visit-field-added-baseline.json",
"decisions": [
{
"job_id": "J101",
"proposed_estimated_visit_minutes": 30,
"disposition": "known_estimate",
"source_ids": [
"E101"
],
"reason": "Explicit numeric estimate."
},
{
"job_id": "J102",
"proposed_estimated_visit_minutes": 0,
"disposition": "known_zero",
"source_ids": [
"E102"
],
"reason": "Explicit confirmation of no on-site visit."
},
{
"job_id": "J103",
"proposed_estimated_visit_minutes": null,
"disposition": "unknown_no_response",
"source_ids": [
"E103"
],
"reason": "No reply establishes no value."
},
{
"job_id": "J104",
"proposed_estimated_visit_minutes": null,
"disposition": "hold_conflict",
"source_ids": [
"E104A",
"E104B"
],
"reason": "Unresolved 30 versus 45; do not average or choose by order."
},
{
"job_id": "J105",
"proposed_estimated_visit_minutes": null,
"disposition": "hold_invalid_type",
"source_ids": [
"E105"
],
"reason": "Quick has no numeric rule; do not coerce."
},
{
"job_id": "J106",
"proposed_estimated_visit_minutes": null,
"disposition": "unknown_empty_response",
"source_ids": [
"E106"
],
"reason": "Empty answer is not zero."
}
],
"expected_record_set": {
"fixture_kind": "Entirely authored fictional service-job records; not an account export or observed customer data.",
"authored_at": "2026-11-09T18:35:44.454665+00:00",
"snapshot_label": "N47 fictional job record set",
"clients": [
{
"id": "C101",
"name": "North Hall"
},
{
"id": "C102",
"name": "Orchard Workshop"
},
{
"id": "C103",
"name": "Willow Rooms"
}
],
"jobs": [
{
"id": "J101",
"label": "Replace lobby light",
"client_id": "C101",
"assigned_staff_id": "S01",
"status": "Scheduled",
"notes": "Keep this original note. ",
"tags": [
"lighting",
"lobby"
],
"estimated_visit_minutes": 30
},
{
"id": "J102",
"label": "Remote sensor check",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "The old label is not proof of a visit estimate.",
"tags": [
"sensor"
],
"estimated_visit_minutes": 0
},
{
"id": "J103",
"label": "Annual inspection",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Completed",
"notes": "Completed does not answer the new question.",
"tags": [
"inspection"
],
"estimated_visit_minutes": null
},
{
"id": "J104",
"label": "Fit door closer",
"client_id": "C101",
"assigned_staff_id": "S02",
"status": "Scheduled",
"notes": "Keep both later estimates for review.",
"tags": [
"door"
],
"estimated_visit_minutes": null
},
{
"id": "J105",
"label": " Café sign check ",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "Café sign\nSecond original line.",
"tags": [],
"estimated_visit_minutes": null
},
{
"id": "J106",
"label": "Leak follow-up",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Open",
"notes": "",
"tags": [
"follow-up"
],
"estimated_visit_minutes": null
}
]
},
"expected_coverage": {
"known": 2,
"denominator": 6,
"unresolved": 4,
"known_subtotal_minutes": 30,
"total_workload_minutes": null,
"display": "30 known minutes across 2 of 6 jobs; 4 unresolved. All-job total unknown."
},
"preservation": "All original job/client IDs and all pre-existing field values, nested arrays, whitespace and relationship pointers remain exact. Only new estimated_visit_minutes values differ from the initial null stage."
}Six independent screen cases
These cases are not a sequence. Every case starts from the same evidence-supported six-job proposal. Omitting a field and explicitly clearing it are different intended actions; confirm the app’s actual request, stored value and reopened screen.
In C02, clearing J101 leaves one established estimate: J102’s confirmed zero. The known subtotal is 0, but the total across all six jobs is still unknown.
C01 · Old screen omits new field
Start again from the six-job proposal. Expected: accept only the stated change.
J101.label; estimate stays 30
Expected coverage: 2/6 · known subtotal: 30 minutes · 4 unresolved · all-job total: unknown.
Actual application result: Not tested.
Proposed intent
{
"target_job": "J101",
"operation": "update_fields",
"submitted_fields": {
"label": "Replace lobby light — access confirmed"
},
"estimated_visit_minutes_presence": "absent"
}Complete expected record set
{
"fixture_kind": "Entirely authored fictional service-job records; not an account export or observed customer data.",
"authored_at": "2026-11-09T18:35:44.454665+00:00",
"snapshot_label": "N47 fictional job record set",
"clients": [
{
"id": "C101",
"name": "North Hall"
},
{
"id": "C102",
"name": "Orchard Workshop"
},
{
"id": "C103",
"name": "Willow Rooms"
}
],
"jobs": [
{
"id": "J101",
"label": "Replace lobby light — access confirmed",
"client_id": "C101",
"assigned_staff_id": "S01",
"status": "Scheduled",
"notes": "Keep this original note. ",
"tags": [
"lighting",
"lobby"
],
"estimated_visit_minutes": 30
},
{
"id": "J102",
"label": "Remote sensor check",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "The old label is not proof of a visit estimate.",
"tags": [
"sensor"
],
"estimated_visit_minutes": 0
},
{
"id": "J103",
"label": "Annual inspection",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Completed",
"notes": "Completed does not answer the new question.",
"tags": [
"inspection"
],
"estimated_visit_minutes": null
},
{
"id": "J104",
"label": "Fit door closer",
"client_id": "C101",
"assigned_staff_id": "S02",
"status": "Scheduled",
"notes": "Keep both later estimates for review.",
"tags": [
"door"
],
"estimated_visit_minutes": null
},
{
"id": "J105",
"label": " Café sign check ",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "Café sign\nSecond original line.",
"tags": [],
"estimated_visit_minutes": null
},
{
"id": "J106",
"label": "Leak follow-up",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Open",
"notes": "",
"tags": [
"follow-up"
],
"estimated_visit_minutes": null
}
]
}C02 · New screen explicitly clears estimate
Start again from the six-job proposal. Expected: accept only the stated change.
J101.estimated_visit_minutes:30→null
Expected coverage: 1/6 · known subtotal: 0 minutes · 5 unresolved · all-job total: unknown.
Actual application result: Not tested.
Proposed intent
{
"target_job": "J101",
"operation": "clear_estimate",
"value": null
}Complete expected record set
{
"fixture_kind": "Entirely authored fictional service-job records; not an account export or observed customer data.",
"authored_at": "2026-11-09T18:35:44.454665+00:00",
"snapshot_label": "N47 fictional job record set",
"clients": [
{
"id": "C101",
"name": "North Hall"
},
{
"id": "C102",
"name": "Orchard Workshop"
},
{
"id": "C103",
"name": "Willow Rooms"
}
],
"jobs": [
{
"id": "J101",
"label": "Replace lobby light",
"client_id": "C101",
"assigned_staff_id": "S01",
"status": "Scheduled",
"notes": "Keep this original note. ",
"tags": [
"lighting",
"lobby"
],
"estimated_visit_minutes": null
},
{
"id": "J102",
"label": "Remote sensor check",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "The old label is not proof of a visit estimate.",
"tags": [
"sensor"
],
"estimated_visit_minutes": 0
},
{
"id": "J103",
"label": "Annual inspection",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Completed",
"notes": "Completed does not answer the new question.",
"tags": [
"inspection"
],
"estimated_visit_minutes": null
},
{
"id": "J104",
"label": "Fit door closer",
"client_id": "C101",
"assigned_staff_id": "S02",
"status": "Scheduled",
"notes": "Keep both later estimates for review.",
"tags": [
"door"
],
"estimated_visit_minutes": null
},
{
"id": "J105",
"label": " Café sign check ",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "Café sign\nSecond original line.",
"tags": [],
"estimated_visit_minutes": null
},
{
"id": "J106",
"label": "Leak follow-up",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Open",
"notes": "",
"tags": [
"follow-up"
],
"estimated_visit_minutes": null
}
]
}C03 · New job carries numeric 20
Start again from the six-job proposal. Expected: accept only the stated change.
append J107 only; six original jobs and clients exact
Expected coverage: 3/7 · known subtotal: 50 minutes · 4 unresolved · all-job total: unknown.
Actual application result: Not tested.
Proposed intent
{
"operation": "create_job",
"record": {
"id": "J107",
"label": "New switch check",
"client_id": "C101",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "New fictional row for this case only.",
"tags": [],
"estimated_visit_minutes": 20
}
}Complete expected record set
{
"fixture_kind": "Entirely authored fictional service-job records; not an account export or observed customer data.",
"authored_at": "2026-11-09T18:35:44.454665+00:00",
"snapshot_label": "N47 fictional job record set",
"clients": [
{
"id": "C101",
"name": "North Hall"
},
{
"id": "C102",
"name": "Orchard Workshop"
},
{
"id": "C103",
"name": "Willow Rooms"
}
],
"jobs": [
{
"id": "J101",
"label": "Replace lobby light",
"client_id": "C101",
"assigned_staff_id": "S01",
"status": "Scheduled",
"notes": "Keep this original note. ",
"tags": [
"lighting",
"lobby"
],
"estimated_visit_minutes": 30
},
{
"id": "J102",
"label": "Remote sensor check",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "The old label is not proof of a visit estimate.",
"tags": [
"sensor"
],
"estimated_visit_minutes": 0
},
{
"id": "J103",
"label": "Annual inspection",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Completed",
"notes": "Completed does not answer the new question.",
"tags": [
"inspection"
],
"estimated_visit_minutes": null
},
{
"id": "J104",
"label": "Fit door closer",
"client_id": "C101",
"assigned_staff_id": "S02",
"status": "Scheduled",
"notes": "Keep both later estimates for review.",
"tags": [
"door"
],
"estimated_visit_minutes": null
},
{
"id": "J105",
"label": " Café sign check ",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "Café sign\nSecond original line.",
"tags": [],
"estimated_visit_minutes": null
},
{
"id": "J106",
"label": "Leak follow-up",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Open",
"notes": "",
"tags": [
"follow-up"
],
"estimated_visit_minutes": null
},
{
"id": "J107",
"label": "New switch check",
"client_id": "C101",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "New fictional row for this case only.",
"tags": [],
"estimated_visit_minutes": 20
}
]
}C04 · Reject a negative estimate
Start again from the six-job proposal. Expected: reject the negative estimate; create no record.
No record changes.
Expected coverage: 2/6 · known subtotal: 30 minutes · 4 unresolved · all-job total: unknown.
Actual application result: Not tested.
Proposed intent
{
"operation": "create_job",
"record": {
"id": "J107",
"label": "New switch check",
"client_id": "C101",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "New fictional row for this case only.",
"tags": [],
"estimated_visit_minutes": -5
}
}Complete expected record set
{
"fixture_kind": "Entirely authored fictional service-job records; not an account export or observed customer data.",
"authored_at": "2026-11-09T18:35:44.454665+00:00",
"snapshot_label": "N47 fictional job record set",
"clients": [
{
"id": "C101",
"name": "North Hall"
},
{
"id": "C102",
"name": "Orchard Workshop"
},
{
"id": "C103",
"name": "Willow Rooms"
}
],
"jobs": [
{
"id": "J101",
"label": "Replace lobby light",
"client_id": "C101",
"assigned_staff_id": "S01",
"status": "Scheduled",
"notes": "Keep this original note. ",
"tags": [
"lighting",
"lobby"
],
"estimated_visit_minutes": 30
},
{
"id": "J102",
"label": "Remote sensor check",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "The old label is not proof of a visit estimate.",
"tags": [
"sensor"
],
"estimated_visit_minutes": 0
},
{
"id": "J103",
"label": "Annual inspection",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Completed",
"notes": "Completed does not answer the new question.",
"tags": [
"inspection"
],
"estimated_visit_minutes": null
},
{
"id": "J104",
"label": "Fit door closer",
"client_id": "C101",
"assigned_staff_id": "S02",
"status": "Scheduled",
"notes": "Keep both later estimates for review.",
"tags": [
"door"
],
"estimated_visit_minutes": null
},
{
"id": "J105",
"label": " Café sign check ",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "Café sign\nSecond original line.",
"tags": [],
"estimated_visit_minutes": null
},
{
"id": "J106",
"label": "Leak follow-up",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Open",
"notes": "",
"tags": [
"follow-up"
],
"estimated_visit_minutes": null
}
]
}C05 · Optional unanswered new estimate
Start again from the six-job proposal. Expected: accept only the stated change.
append J107 with null only; original six and clients exact
Expected coverage: 2/7 · known subtotal: 30 minutes · 5 unresolved · all-job total: unknown.
Actual application result: Not tested.
Proposed intent
{
"operation": "create_job",
"record": {
"id": "J107",
"label": "New switch check",
"client_id": "C101",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "New fictional row for this case only.",
"tags": [],
"estimated_visit_minutes": null
}
}Complete expected record set
{
"fixture_kind": "Entirely authored fictional service-job records; not an account export or observed customer data.",
"authored_at": "2026-11-09T18:35:44.454665+00:00",
"snapshot_label": "N47 fictional job record set",
"clients": [
{
"id": "C101",
"name": "North Hall"
},
{
"id": "C102",
"name": "Orchard Workshop"
},
{
"id": "C103",
"name": "Willow Rooms"
}
],
"jobs": [
{
"id": "J101",
"label": "Replace lobby light",
"client_id": "C101",
"assigned_staff_id": "S01",
"status": "Scheduled",
"notes": "Keep this original note. ",
"tags": [
"lighting",
"lobby"
],
"estimated_visit_minutes": 30
},
{
"id": "J102",
"label": "Remote sensor check",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "The old label is not proof of a visit estimate.",
"tags": [
"sensor"
],
"estimated_visit_minutes": 0
},
{
"id": "J103",
"label": "Annual inspection",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Completed",
"notes": "Completed does not answer the new question.",
"tags": [
"inspection"
],
"estimated_visit_minutes": null
},
{
"id": "J104",
"label": "Fit door closer",
"client_id": "C101",
"assigned_staff_id": "S02",
"status": "Scheduled",
"notes": "Keep both later estimates for review.",
"tags": [
"door"
],
"estimated_visit_minutes": null
},
{
"id": "J105",
"label": " Café sign check ",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "Café sign\nSecond original line.",
"tags": [],
"estimated_visit_minutes": null
},
{
"id": "J106",
"label": "Leak follow-up",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Open",
"notes": "",
"tags": [
"follow-up"
],
"estimated_visit_minutes": null
},
{
"id": "J107",
"label": "New switch check",
"client_id": "C101",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "New fictional row for this case only.",
"tags": [],
"estimated_visit_minutes": null
}
]
}C06 · Hold a mandatory default-zero redesign
Start again from the six-job proposal. Expected: hold the redesign if it cannot represent unknown estimates.
No record changes.
Expected coverage: 2/6 · known subtotal: 30 minutes · 4 unresolved · all-job total: unknown.
Actual application result: Not tested.
Proposed intent
{
"operation": "propose_required_field_with_default",
"default": 0,
"intent": "No actual update authorized by this exercise"
}Complete expected record set
{
"fixture_kind": "Entirely authored fictional service-job records; not an account export or observed customer data.",
"authored_at": "2026-11-09T18:35:44.454665+00:00",
"snapshot_label": "N47 fictional job record set",
"clients": [
{
"id": "C101",
"name": "North Hall"
},
{
"id": "C102",
"name": "Orchard Workshop"
},
{
"id": "C103",
"name": "Willow Rooms"
}
],
"jobs": [
{
"id": "J101",
"label": "Replace lobby light",
"client_id": "C101",
"assigned_staff_id": "S01",
"status": "Scheduled",
"notes": "Keep this original note. ",
"tags": [
"lighting",
"lobby"
],
"estimated_visit_minutes": 30
},
{
"id": "J102",
"label": "Remote sensor check",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "The old label is not proof of a visit estimate.",
"tags": [
"sensor"
],
"estimated_visit_minutes": 0
},
{
"id": "J103",
"label": "Annual inspection",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Completed",
"notes": "Completed does not answer the new question.",
"tags": [
"inspection"
],
"estimated_visit_minutes": null
},
{
"id": "J104",
"label": "Fit door closer",
"client_id": "C101",
"assigned_staff_id": "S02",
"status": "Scheduled",
"notes": "Keep both later estimates for review.",
"tags": [
"door"
],
"estimated_visit_minutes": null
},
{
"id": "J105",
"label": " Café sign check ",
"client_id": "C102",
"assigned_staff_id": "S01",
"status": "Open",
"notes": "Café sign\nSecond original line.",
"tags": [],
"estimated_visit_minutes": null
},
{
"id": "J106",
"label": "Leak follow-up",
"client_id": "C103",
"assigned_staff_id": "S02",
"status": "Open",
"notes": "",
"tags": [
"follow-up"
],
"estimated_visit_minutes": null
}
]
}Filled example and blank review card
Use the filled example as a reference, then copy the blank section for your own field. Leave actual results as “Not tested” until you have authorized, isolated test evidence.
Read or select the complete card
# Field-change review card — filled example and blank review All records and speakers are fictional. This is a non-writing expected-result sheet, not an executed schema change or an Overskill product test. Nothing in this packet connects to a database or applies the proposal. ## Filled example Proposed field: estimated_visit_minutes, optional nonnegative integral number. Null means not established under this example's policy. The six old records initially have no such key; the proposed field-added stage represents all six as null. That representation is an acceptance target, not proof of a native migration. | Job | Authored evidence | Proposed value | Interpretation | | --- | --- | --- | --- | | J101 | E101 explicitly estimates 30 minutes | 30 | Known estimate | | J102 | E102 explicitly confirms no on-site visit | 0 | Known zero | | J103 | E103 records no reply | null | Unknown | | J104 | E104A says 30; E104B says 45 | null | Hold conflict; no averaging | | J105 | E105 says quick | null | Hold invalid type; no coercion | | J106 | E106 records an empty response | null | Unknown; not zero | Known coverage is 2/6. Their subtotal is 30 minutes. The total for all six remains unknown. Keep the original IDs, client links, labels, notes, whitespace and tags. The comparison files include every row, not just the two populated values. Every compatibility case starts independently from this backfill baseline. An old label-only update should retain J101's 30. An explicit clear should set J101 to null, leaving coverage 1/6 and known subtotal 0 (one confirmed zero, five unresolved). Adding J107 with numeric20 produces coverage3/7 and subtotal50. Reject a negative new estimate without adding or changing a row. An optional unanswered J107 produces coverage2/7 and subtotal30. A required/default-zero design is held if it cannot represent unresolved answers. These are desired app-intent rules. An omitted field and an explicit null may behave differently across update formats; the resulting app's actual request, stored result and old screens need testing. Do not infer transport semantics from these JSON files. ## Blank review - Existing app/table and exact revision: ______ - Authorized isolated test surface and evidence of isolation: ______ (Unknown is not isolated.) - New field, unit, allowed type, unanswered meaning and explicit-zero meaning: ______ - Existing record IDs/count and complete original-value snapshot: ______ - Evidence source for each proposed non-null value; conflicts/unknowns retained: ______ - Known numerator / full denominator / known subtotal / all-record total status: ______ - Exact before/after diff and untouched relationships: ______ - Old screen omits field; explicit clear; valid new row; invalid new row; optional unanswered row: expected ______ / actual **Not tested**. - Required/default decision and unresolved cases: ______ - Reopen/readback and independent comparison result: **Not tested**. Requested next work: review the field meaning, unresolved evidence and non-writing comparison first. Preserve existing rows and related identities; specify and test the old/new screen behavior before relying on the field. Keep native add-field steps with the existing help owner. Preview is not proof of a separate database, and an export is not proof of complete restoration. ## Review the complete worked records These are authored expectations, not an executed migration or observed app results. - [Original six jobs and three clients](visit-jobs-before.json): the new field is absent. - [Proposed optional-field stage](visit-field-added-baseline.json): all six estimates are null; 0/6 established; subtotal unavailable; all-job total unknown. - [Evidence-supported proposal](visit-field-proposal.json): 2/6 established; known subtotal 30 minutes; all-job total unknown. - [Seven fictional evidence records](visit-estimate-evidence.csv). CSV cells contain text; explicit confirmation, units and context support the proposed numeric values. This is not a general import conversion rule. - [Six independent screen cases and their complete expected records](independent-screen-cases.json). ### Expected coverage after each independent case Each case restarts from the six-job evidence-supported proposal. Actual application result: **Not tested** for every case. | Case | Established estimates | Known subtotal | Unresolved | All-job total | Actual app result | | --- | --- | --- | --- | --- | --- | | C01: old screen omits field | 2/6 | 30 minutes | 4 | Unknown | Not tested | | C02: deliberately clear J101 | 1/6 | 0 minutes, from confirmed J102 | 5 | Unknown | Not tested | | C03: new J107 has 20 minutes | 3/7 | 50 minutes | 4 | Unknown | Not tested | | C04: reject negative estimate | 2/6 | 30 minutes | 4 | Unknown | Not tested | | C05: new J107 is unanswered | 2/7 | 30 minutes | 5 | Unknown | Not tested | | C06: hold default-zero redesign | 2/6 | 30 minutes | 4 | Unknown | Not tested | The all-null stage has no established estimate, so its subtotal is unavailable. C02 has a known subtotal of zero because J102 remains explicitly confirmed; it still leaves five unanswered estimates.
Verify the test environment’s isolation before any real write. Preview is not proof of isolation, and an export is not proof that a restore will work.
4. Test old screens and new answers independently
Each case below starts from the same reviewed six-job baseline: J101 is 30, J102 is zero and four estimates are unresolved. Do not run them as a sequence and carry one case's changes into the next expected result.
Scroll horizontally to compare all columns.
| Case | Intended action | Expected result to verify in your app |
|---|---|---|
| Old screen | Change J101's label without supplying the new field | The intended label changes; its estimate remains 30; other fields and rows remain exact |
| Explicit clear | Deliberately clear J101's estimate | J101 becomes unresolved; coverage is 1/6 and the known subtotal is zero from J102's confirmed answer |
| Valid new answer | Add J107 with numeric 20 | Coverage is 3/7 and the known subtotal is 50; all six older jobs remain exact |
| Invalid new answer | Attempt a negative estimate of -5 | No job is added and no existing row changes |
| Optional unanswered job | Add J107 without an established estimate | J107 remains unresolved; coverage is 2/7 and the known subtotal stays 30 |
| Required-field design | Require an answer and use zero for unresolved jobs | Hold the design if it cannot represent unresolved answers |
These are desired app behaviors. The actual save request, stored result and reopened screen still need to be inspected. An omitted field and an explicit clear must not be assumed equivalent. Their transport representation also depends on the implementation: for example, JSON Merge Patch uses null to remove a member. It does not universally mean “store a null estimate.” Ask for the intended behavior, then verify the resulting app's implementation.
A default is another separate mechanism. A form hint, validation annotation and database default can do different things. In particular, a JSON Schema default annotation does not itself fill missing values during validation. None of these mechanisms establishes that an old job's owner supplied an answer.
5. Request the non-writing comparison first
In the affected app's AI Prompt Builder, adapt this request before applying a field change:
Review a proposed optional
estimated_visit_minutesfield for my existing job records. Define whole minutes, confirmed zero and unresolved answers explicitly. Prepare a comparison without changing schema or records yet.Preserve every existing ID, client relationship and original field. Show the full original records, the proposed field-added stage and the proposed evidence-supported values. Keep missing replies, conflicts and invalid responses unresolved; do not infer zero or average conflicting answers.
Show established-answer coverage and its denominator separately from the known subtotal. Keep the all-job total unknown while estimates remain unresolved. Describe how old screens that omit the field, deliberate clears, valid new answers and invalid answers should behave. Identify the isolated test path and the actual checks still required before any write.
Record the app revision, field rule, evidence source for each proposed answer, exact before/after differences and expected screen behavior. Leave actual results marked Not tested until observed. After an authorized implementation, repeat the checks against saved records and reopened screens, including jobs that still have no estimate. The field is useful when its meaning survives those paths, including an honest unanswered state.