When the requirement has a technical layer that needs to be delivered properly.

Bring the current environment, problem and desired result. We identify what needs to be checked before implementation is treated as agreed.

AREAS OF WORK

Technical delivery starts with context, not assumptions.

Move agreed work into the intended environment and verify the result within the defined scope.

Understand source, target, dependencies, data, URLs and rollback options before moving production.

Implement defined changes without treating the domain, email or proxy layer as isolated from the rest of production.

Defined Linux, Docker or hosting work where the environment and responsibility boundary are clear.

Connect systems when access, provider limits, data flow and failure conditions are understood.

Establish what is happening before deciding whether to repair, replace or restructure.

CONTEXT

Current providerProduction dependenciesPermissionsVersion constraintsDataDNSBackupsThird-party limitsMaintenance implications

The presence of a technical request does not automatically mean the first proposed implementation is the right one.

ACCESS

We prefer delegated access, a limited technical account or an attended remote session over receiving an account owner's primary credentials.

Do not send passwords, recovery codes or payment-card information through the project forms.

CHANGE DISCIPLINE

01
Identify production
Confirm what is live, where it runs and what depends on it.
02
Preserve what matters
Identify data, configuration, email/DNS dependencies and useful backup options.
03
Define the change
Know the target state and the permitted change window.
04
Implement
Make only the agreed changes with the required access.
05
Verify
Test the production outcome that falls within our control.
06
Close or hand over
Document or return the defined responsibility; monitoring continues only if separately agreed.

NEXT STEP

Tell us what is happening now, the desired result, production impact and any constraints you already know.