Keep a one-time task specific
A useful task describes an observable result: a form reaches the CRM, a domain routes to the intended service or an update passes agreed checks. If the cause is unknown, begin with diagnosis before promising a fixed repair. Additional findings are discussed separately so the scope does not silently expand.
Bound one task to a result
One-time support suits a defined form error, DNS change, update or runtime problem. Diagnosis can reveal dependencies requiring a revised scope. State the expected outcome before deciding what work is included.
- Share symptoms, stack and recent changes.
- Agree work, access and completion checks.
- Approve additional scope explicitly.
- Review results and supplier dependencies.
Acceptance checks and possible scope changes
One-time work is separate from ongoing care and urgent standby. Third-party charges remain separate. With insufficient evidence, a scoped assessment may be the responsible next task instead of promising unlimited repair at the starting price.
| Task | Acceptance | Extra scope |
|---|---|---|
| Form | Destination receives test | Unsupported API replacement |
| DNS | Agreed hostname works | Full zone migration |
| Runtime | Function and job succeed | Legacy code repair |
Example: a supplier renewal blocks the final result
A configuration fix reveals an expired paid integration. The handover distinguishes the completed change from the renewal the owner must arrange. This is an illustrative scenario, not a customer case or a promised result.