---
fictional: true
sensitivity: "synthetic"
record_id: "CS-WORKFLOW-001"
record_type: "Workflow or Process"
applicable_stage: "How Work Gets Done"
knowledge_layer: "Working Knowledge"
review_state: "confirmed"
version: "1"
last_updated: "2026-09-08"
source_ids: ["SRC-001", "SRC-002", "SRC-005"]
context: "current within fictional scenario"
coverage: "partial"
---

> CONTROLLED SYNTHETIC DEMONSTRATION. Scripted fictional-owner confirmation only. Not customer evidence or technical installation guidance.

# From accepted scope to a crew visit

## Before the visit

| Step | Actor | Current practice in this scenario | Source |
| --- | --- | --- | --- |
| Define the job | Maya | Visit, measure and prepare the written project scope and price. | SRC-001 |
| Accept the scope | Homeowner | Accept the project-specific scope before scheduling. | SRC-001 |
| Coordinate the visit | Nina | Put the visit date in the calendar; keep accepted scope and job notes in the shared job folder; coordinate materials. | SRC-001, SRC-002 |
| Check what is current | Crew lead | Read the accepted scope and current job notes before the visit. A customer request is not accepted work. | SRC-002, SRC-003, SRC-005 |

## When a customer asks for an addition

1. The crew or Nina records the request and refers it to Maya.
2. Maya provides written scope and price for the addition.
3. The homeowner accepts the revised scope and price before the crew performs it.
4. Nina places the accepted change in the job folder. The crew checks that record.

There is no small-extra allowance. The old guide's under-$250 rule is superseded by Maya's explicit applicability clarification. [SRC-005]

## CS-104 shows the boundary

The utility-room threshold is recorded but not approved, priced or accepted. It stays outside the crew's included work. Material allocation does not establish collection time or an arrival promise. [SRC-002, SRC-004, SRC-005]

## Sources, confirmation and limits

[Sources](../../sources-excerpt.md) preserves the actual selected file locators. [Questions and unknowns](../../open-items-excerpt.md) preserves supplier timing, clearance and missing employee perspective.

Confirmer: Maya, fictional owner roleplayed by the operator, 2026-09-08, SRC-005. Scope: reported current company/job meaning and change-approval practice within this scenario only. This is a bounded workflow record, not a complete operating manual, SOP, new policy, diagnosis or recommendation. No independent employee participation or real business observation. Correction history: first workflow version follows explicit clarification; original August guide remains unchanged.