
Independent thinking. Connected systems.
Engineering / Field notes 001
IT services.
Thoughtfully engineered.
Built to take root.
Software, systems, and infrastructure.
Considered from the ground up.
FOREST AIR AND HEAT LTD
Clarity in the process.
Care in the details.
02 / A grounded approach
Complex work.
Clear thinking. Lasting foundations.
FOREST AIR AND HEAT LTD is an IT services and software engineering company. We help turn operational needs into well-structured software, connected workflows, and practical technical foundations.
Our work begins with understanding the problem—not prescribing a platform. From a focused internal tool to an integrated application, the aim is the same: software that makes sense for the people who use and maintain it.
Purpose before technology
Understanding before implementation
03 / Custom software development
Software shaped around the work.
When off-the-shelf products leave a gap, custom software can make your processes work as a coherent whole. We turn business requirements into maintainable applications with clear boundaries and purposeful functionality.
From requirements to working code
Application architecture, data models, tested functionality, and documentation that makes the next step understandable.

04 / Web applications & internal tools
Better tools. Less friction.
A clear place to work.
From browser-based applications to operational dashboards, we build interfaces that make complex work easier to understand. Data, permissions, and everyday tasks come together in a considered user experience.
Illustrative applications
Built around daily operations.
A records interface, an approval workflow, or a reporting dashboard can bring scattered tasks into one consistent environment. Access controls and validation are considered alongside the interface—not added as an afterthought.
05 / Integrations & automation
Connected systems. Coherent workflows.
We connect applications, data sources, and business processes so information can move with less manual handling. Integrations are designed with validation, traceability, and recovery in mind.
We consider where data originates, who owns it, and what should happen when a connection fails. The result is an integration approach with explicit mappings, observable behaviour, and documented recovery steps.

06 / Cloud infrastructure & DevOps
A dependable foundation.
Applications need a practical environment to run in. We plan cloud infrastructure and delivery workflows with repeatability, observability, and the realities of ongoing operation in mind.
Designed for operation
Consistent environments. Controlled releases. Monitoring that helps explain what is happening. Documentation for the people responsible for keeping it running.
07 / Maintenance & support
Built to keep moving.
Software changes as the work around it changes. We help maintain existing applications, investigate issues, update dependencies, and plan improvements without losing sight of the system as a whole.
Support starts with understanding the existing application and its constraints. We prioritise issues, reproduce problems, test changes, and record what has been updated. Engagement terms and support arrangements are established around the specific project.
08 / The project workflow
A considered path.
From first questions to handover.
01 / Discover
Understand the work
Clarify the users, the problem, existing systems, and constraints. Establish what success means before defining the solution.
02 / Define
Make the scope explicit
Document requirements, technical choices, delivery stages, and acceptance criteria. Surface dependencies and uncertainties early.
03 / Develop
Build, test, review
Implement in manageable increments. Review progress against agreed requirements and use testing to check the behaviours that matter.
04 / Handover
Leave a clear foundation
Deliver the agreed code, configuration, and documentation. Explain deployment, operation, and the boundaries of ongoing support.
09 / Typical deliverables
More than the final application.
A handover should make the work understandable and usable beyond its initial delivery. The exact deliverables are agreed to suit the project.
01
Requirements & architecture
A defined scope, technical decisions, and an explanation of how the system fits together.
02
Source code & configuration
The agreed application code, environment configuration, and build or deployment setup.
03
Tests & verification
Relevant automated tests and a record of the checks performed against acceptance criteria.
04
Documentation & handover
Setup instructions, operational notes, and guidance for maintaining and extending the software.
10 / Engineering principles
Care is an engineering practice.
Clarity over complexity
Choose understandable structures and document the reasoning behind consequential technical decisions.
Quality in the details
Use code review, validation, and relevant tests to check functionality, boundaries, and failure conditions.
Security by consideration
Treat permissions, data handling, dependencies, and secrets as part of the design and delivery process.
Maintainability from the start
Build with readable code, manageable dependencies, and documentation that supports future changes.
11 / Common questions
A little more context.
Can you work with an existing application?
Existing software can be reviewed before a maintenance or improvement scope is agreed. Access to code, current documentation, and a description of known issues help establish a starting point.
How is a project scoped?
Scope is developed from the business problem, user requirements, system constraints, and intended deliverables. Stages and acceptance criteria are agreed before implementation begins.
Do you choose the technology in advance?
Technology choices should follow the needs of the project, including integration requirements, operational constraints, and maintainability. There is no single prescribed stack for every engagement.
What happens at handover?
Handover covers the agreed source code, configuration, technical documentation, and relevant operational guidance. Ongoing maintenance or support is discussed separately.
12 / Project correspondence
Good engineering starts
with a clear conversation.
Company
FOREST AIR AND HEAT LTD
IT services and software engineering
Project context
Initial correspondence can outline the problem, current systems, intended users, and any important constraints. A clear starting point helps establish a considered scope.