Governance · Policy

Quality Policy | StackTrack Governance

Governing entity
Servana Managed Services Ltd
Framework
StackTrack Governance
Effective date
13 August 2026
Version
2026-08-13
Document owner
Managing Director
Next review
13 August 2027

This document describes standard governance controls. Customer-specific contractual commitments are defined in the applicable service agreement.

Objective

Servana Managed Services Ltd aims to help customers build, operate and improve reliable software systems.

Achieving this requires our services, engineering work and operational processes to be consistent, dependable and appropriate to customer requirements.

This policy defines the principles used by Servana to manage quality across the services delivered under the StackTrack brand.

Quality management

Servana maintains a Quality Management System (QMS) appropriate to the nature and scale of the organisation.

The QMS provides a structured approach to:

  • understanding customer requirements;
  • defining and improving business processes;
  • identifying and managing risks and opportunities;
  • measuring service and operational performance;
  • investigating problems and preventing recurrence;
  • managing supplier quality;
  • maintaining personnel competence; and
  • continually improving the effectiveness of the organisation and its services.

Where applicable, the QMS is designed and operated with reference to the requirements and principles of ISO 9001.

Quality principles

Servana is committed to:

  • delivering services that meet agreed customer requirements;
  • understanding the intended outcomes of the systems and services we operate;
  • maintaining clear and repeatable operational processes;
  • making changes deliberately and with appropriate controls;
  • measuring the effectiveness of important business and service processes;
  • learning from incidents, complaints, failures and customer feedback;
  • continually improving the quality and reliability of our services;
  • maintaining appropriate technical and operational competence;
  • working with suppliers capable of supporting our service requirements; and
  • complying with applicable legal, regulatory and contractual obligations.

Customer focus

Customer requirements are a primary input into the design, delivery and improvement of StackTrack services.

Servana seeks to understand:

  • the outcomes customers are trying to achieve;
  • applicable technical and operational requirements;
  • security and resilience requirements;
  • contractual commitments;
  • relevant service levels;
  • business constraints; and
  • changes in customer needs over time.

Services should be designed and operated to satisfy agreed requirements rather than applying technology or process without a clear purpose.

Quality objectives

Servana establishes measurable quality and business objectives that are consistent with:

  • the organisation's strategic direction;
  • customer requirements;
  • identified risks and opportunities;
  • service performance;
  • security and resilience objectives; and
  • opportunities for improvement.

Objectives should be measurable where reasonably practicable and reviewed periodically.

Quality objectives may include measures relating to:

  • customer satisfaction;
  • service reliability;
  • incident performance;
  • service requests;
  • change success;
  • recovery performance;
  • customer feedback;
  • delivery quality;
  • process effectiveness; and
  • continual improvement.

Service quality

StackTrack services should be delivered consistently and in accordance with applicable service definitions, Statements of Work and Service Level Agreements.

Servana seeks to maintain service quality through controls including:

  • defined service responsibilities;
  • infrastructure automation;
  • standardised configurations;
  • monitoring and observability;
  • change management;
  • backup and recovery;
  • security controls;
  • incident management;
  • documented operational processes; and
  • periodic service review.

Automation should be used where it improves repeatability, reliability and the ability to verify outcomes.

Engineering quality

Engineering work should be appropriate to its purpose, maintainable and consistent with the architecture and operational requirements of the system concerned.

Where relevant, engineering work should consider:

  • security;
  • reliability;
  • maintainability;
  • repeatability;
  • observability;
  • recoverability;
  • performance;
  • operational complexity;
  • lifecycle management; and
  • future change.

The objective is not merely to complete a technical change, but to leave the affected system in an appropriate and supportable operational state.

Secure by Design

Quality and security are closely related.

StackTrack's Secure by Design approach requires security considerations to be incorporated into infrastructure, automation and operational processes rather than treated solely as a later review activity.

Quality controls should therefore consider both whether a service functions as intended and whether it does so with appropriate:

  • access control;
  • cryptographic protection;
  • resilience;
  • monitoring;
  • change control;
  • recovery capability; and
  • lifecycle management.

Customer feedback

Servana actively seeks and considers feedback regarding its services.

Feedback may be obtained through:

  • service reviews;
  • support interactions;
  • customer meetings;
  • surveys;
  • complaints;
  • project retrospectives; and
  • direct customer communication.

Relevant feedback should be evaluated to identify:

  • service issues;
  • recurring problems;
  • unmet requirements;
  • opportunities for improvement; and
  • changes in customer expectations.

Material findings should be incorporated into improvement activities where appropriate.

Complaints and problems

Customer complaints and material service problems must be assessed appropriately.

Where a material or recurring problem is identified, Servana should seek to understand:

  • what happened;
  • the impact;
  • the underlying or contributing causes;
  • whether similar conditions exist elsewhere;
  • whether corrective action is required; and
  • whether changes to processes, technology or controls could reduce the likelihood of recurrence.

Corrective actions should be proportionate to the significance and risk of the issue.

The objective is to address causes where practicable rather than repeatedly treating symptoms.

Incidents and learning

Operational incidents provide an important source of information about service quality.

Significant incidents should be reviewed at a level appropriate to their impact and complexity.

Reviews may consider:

  • technical causes;
  • operational causes;
  • monitoring effectiveness;
  • change controls;
  • architecture;
  • documentation;
  • communication;
  • customer dependencies; and
  • opportunities for preventative improvement.

Incident reviews should support organisational learning rather than simply attributing individual fault.

Change management

Changes to managed systems and services must be planned and controlled according to their risk and potential impact.

Appropriate change controls may include:

  • technical review;
  • automated testing;
  • peer review;
  • infrastructure-as-code;
  • staged deployment;
  • rollback planning;
  • maintenance scheduling;
  • monitoring; and
  • post-change verification.

The level of control should be proportionate to the risk of the change.

Measurement and monitoring

Servana monitors and measures appropriate aspects of service and business performance to determine whether processes and controls are operating effectively.

Measures should provide useful information rather than being collected solely for reporting purposes.

Where appropriate, performance information may be used to:

  • identify trends;
  • detect recurring issues;
  • prioritise improvements;
  • assess quality objectives;
  • evaluate service performance; and
  • support management review.

Internal review

The effectiveness of relevant business and service processes is periodically reviewed.

Review activities may include:

  • internal audits;
  • management reviews;
  • control assessments;
  • service reviews;
  • incident reviews;
  • customer feedback analysis; and
  • performance analysis.

Findings should be recorded and addressed according to their significance.

Suppliers

Servana relies on cloud platforms, software providers and other suppliers to deliver parts of its services.

Material suppliers should be selected and managed with consideration for their ability to support applicable:

  • quality requirements;
  • reliability requirements;
  • security requirements;
  • service availability;
  • data protection requirements;
  • technical capabilities; and
  • contractual commitments.

Supplier performance should be reviewed where the supplier has a material influence on the quality or reliability of StackTrack services.

Supplier-management activities are further defined by the Supplier Policy.

Competence and development

Personnel performing work that may affect service quality must have appropriate knowledge, skills and experience for their responsibilities.

Servana supports continued professional development through activities that may include:

  • technical training;
  • professional certification;
  • practical experience;
  • knowledge sharing;
  • documentation;
  • peer review; and
  • participation in relevant engineering and operational communities.

Training and development requirements should reflect both current responsibilities and foreseeable changes in technology and services.

Employee involvement

Continual improvement depends on the participation of personnel throughout the organisation.

Personnel are encouraged to:

  • identify problems;
  • challenge inefficient processes;
  • identify unnecessary operational complexity;
  • suggest improvements;
  • report risks;
  • improve documentation;
  • automate repetitive work where appropriate; and
  • share relevant knowledge.

Quality is a shared responsibility and forms part of normal engineering and operational work.

Servana must comply with applicable legal, regulatory, contractual and other requirements relevant to the services it provides.

Quality controls must take account of customer commitments and other obligations affecting how services are designed, operated and changed.

Where requirements conflict or create material operational risk, they must be appropriately assessed and escalated.

Continual improvement

Servana is committed to continually improving its services, processes and Quality Management System.

Improvement may be driven by:

  • customer feedback;
  • operational incidents;
  • audit findings;
  • performance trends;
  • employee suggestions;
  • supplier changes;
  • technological developments;
  • changes in customer requirements; and
  • identified risks and opportunities.

Improvements should be prioritised according to their expected effect on customers, reliability, security, operational effectiveness and business objectives.

Responsibilities

The Directors of Servana are responsible for:

  • establishing and supporting quality objectives;
  • ensuring appropriate resources are available;
  • reviewing the effectiveness of the Quality Management System;
  • supporting continual improvement; and
  • ensuring quality remains aligned with the organisation's strategic direction.

All personnel are responsible for:

  • understanding the quality requirements relevant to their work;
  • following applicable processes and controls;
  • identifying and reporting problems;
  • contributing to continual improvement; and
  • maintaining appropriate competence for their responsibilities.

Policy availability

This policy is publicly available as part of StackTrack's Governance documentation.

Publication supports transparency regarding the principles Servana uses to manage service quality and continual improvement.

Policy review

This policy is reviewed at least annually and following significant changes to:

  • Servana's services;
  • customer requirements;
  • business processes;
  • the Quality Management System;
  • applicable legal or contractual requirements; or
  • the organisation's strategic direction.

Material changes will be published as a new version of this policy.

Related governance