Support & maintenance

Planned support for software after delivery.

Keep agreed software and delivery processes under review through a support arrangement with clear scope and expectations.

Discuss ongoing support

After launch

Software continues to change after it is released.

Requirements evolve, dependencies are updated and operational questions emerge. A planned arrangement can provide a clearer way to assess and prioritise appropriate follow-on work.

Existing systems must be reviewed before support is accepted. Suitability depends on access, maintainability, documentation and the requested coverage.

Possible areas of support

Agree the work that is useful and appropriate.

These areas are examples, not automatic inclusions. The actual arrangement is documented before it begins.

01

Issue investigation

Assess reported software or delivery problems within the agreed support scope.

02

Corrective maintenance

Plan and implement agreed fixes after the cause and effect have been reviewed.

03

Dependency updates

Review appropriate software dependency changes and the testing they require.

04

Small improvements

Assess and schedule defined enhancements outside a larger development project.

05

Delivery process upkeep

Maintain agreed pipeline or automation configuration as surrounding systems change.

06

Documentation updates

Keep agreed operating or technical guidance aligned with completed changes.

Clear expectations

Define support before relying on it.

01

Scope

Identify the software, environments and types of request included.

02

Availability

Agree when requests can be received and when work may be carried out.

03

Priorities

Define how requests are assessed and which information must be supplied.

04

Responsibilities

Clarify access, approvals, third parties, backups and decision ownership.

Important to know

Emergency cover is not included by default.

The website does not promise continuous monitoring, immediate response or round-the-clock availability. Any service level or out-of-hours arrangement must be expressly agreed in writing.

Hazel Tech cannot control the availability or behaviour of third-party providers. Responsibilities for backups, access and business continuity are defined as part of the engagement.

Have something to build or improve?

Let’s turn it into a clear next step.

Tell us what you are trying to achieve. We will review your enquiry and contact you to discuss whether Hazel Tech is a suitable fit.