Rules of Consulting

EnergyAE rules of consulting can be boiled down into the following themes:

1. Client Communication
2. Quality Control
3. Continuous Development
4. Working Principles

THEME 1: CLIENT TRUST & COMMUNICATION

1. Always act in the best interest of the client

Acting in the client’s best interests means giving honest guidance, highlighting risks early, and protecting the long-term success of the brand, not just achieving a short-term approval outcome.

We are trusted advisors and we go beyond following simple instructions. We always advocate on behalf of the client as if we worked for their company.

2. Be very accessible & responsive to clients

Those doing the work must be in direct contact with the client to give confidence.

Responsiveness builds trust and reduces risk. Silence or delayed response creates anxiety and confusion.

Even when a full answer isn’t available yet, acknowledge promptly and provide an ETA on your response.

RFIs are high priority for clients: aim to respond to RFIs within 2 business days.

3. Build real relationships, not transactional interactions

EnergyAE is a long-term partner to product teams and manufacturers. We build trust through consistent delivery, technical credibility, and genuine respect for the client’s business. Strong relationships create ongoing work and positive referrals.

This looks like taking the time to talk to the client over the phone or arranging a Teams meeting if there is more to discuss.

It means empathising with the client if they are stressed and guiding them through difficult decisions calmly. Or communicating that their work is our top priority if time is an issue. This human connection is what builds long-term trust.

4. Always accompany results with analysis

Numbers alone are not the product. Results must come with interpretation: what the result means, why it is happening, how sensitive it is, and what should be done next (give 2-3 options and a recommendation).

We turn outputs into decisions. Data is raw material; analysis is the deliverable.

5. Maintain professional clarity — no vague language

Vagueness causes misunderstandings and rework. We avoid phrases like “should be fine,” “almost ready,” and “we’ll add it later.” We use precise language: ready/not ready, pass/fail, missing/present.

Clear communication with clients is essential for efficient projects.

6. Share bad news early

We never hide issues until the last minute. If a tank drawing is sub-par, a manual is inconsistent, or a test report non-compliant, we raise it immediately.

We never raise problems without offering structured options: provide 2-3 options and a recommendation.

THEME 2: SYSTEM-FIRST EXECUTION & QUALITY CONTROL

7. Be system-driven

Follow EnergyAE systems as closely as possible.

This relates to KMS systems, templates, company policies, checklists, and automation scripts.

Our systems must be versatile to handle the variety of different projects.

If one of these things is broken, instead of hard-coding or deviating to move forwards faster, flag the issue and discuss some options on how the system can be improved in future. Over time this will generate stronger systems and fewer errors.

8. Every data point requires evidence

Every technical detail must be backed up by evidence - whether that is a reference to a standard, regulator’s guidelines, tank drawing or schematic, or email communication.

Every data point must be backed up to a source, not memory.

Assume that every project, every model and every data point will be questioned by a strict auditor and must be defensible according to legislation & standards.

9. Every deliverable must be reviewed

Important work must be reviewed by another person. Including design work, and modelling work.

The first review must always be completed by the author. Don’t ask for a peer-review until you have checked your own work. The brain activates different zones for creating and editing, so once the creating is complete (e.g. preparing modelling or submission folders) take a break and then revisit your work with fresh eyes ready to review and edit.

Once you have reviewed your work, request a peer-review. Peer reviewers must use the Gate A and Gate B checklists, so the scope of review is explicit. Don’t request custom/bespoke/intermediate partial reviews. If additional review phases are deemed necessary, we need to build these into our structure.

10. Record notes on each project

Use Monday.com items for projects to note down important issues or points of interest. This can allow someone to pick up the project if needed. Monday.com is the central point of reference for projects.

Ensure projects are kept up to date on Monday.com and in the correct status, whether waiting on EnergyAE, the Client, or Regulators.

THEME 3: CONTINUOUS DEVELOPMENT

11. Automation is our advantage

Always try to find a faster/more accurate way of doing a task. Anything manual can be automated and enables us to deliver a better service and better cost to the client.

We use automation to reduce human error to both create final outputs as well as review deliverables.

However, we must not place too much trust in automated processes. Thorough testing of new automated features is critical, as well as ongoing spot-check review of outputs to ensure no errors have been introduced. With many connected moving parts, new updates to automations can break others.

12. Learning new skills is encouraged even if not directly profitable

Learning new skills to continue to develop is important. It is considered an investment. Develop new skills during down-time periods.

This includes building a new macro or script, learning a new programming language, studying technology related to our work.

THEME 4: PRINCIPLES FOR WORKING

13. Start Fast

Rule: Maximum 30 minutes reading before producing output.

This applies to reading background context material before starting a new project.

You do not need to understand everything before starting.

You only need to understanding enough to begin. This will create forward momentum.

After 30 minutes, you must produce one of the following that is relevant to the project:

• Project description and plan on Monday.com
• Summary of reading
• Questions for internal discussion
• Documentation or information request from the client

14. Ask Early

Rule: If stuck for more than 15 minutes, ask.

Independent problem solving is expected, but excessive time spent stuck wastes time and slows projects. Others may have already solved the same problem.

When asking, always state;

• what you believe is the problem
• what you have tried
• where you are stuck

15. Fix Root Causes

Rule: If you fix something manually twice, stop and fix the system.

Do not manually correct automated outputs - the error will re-appear the next time, and you may forget to fix it manually.

Examples:

• Update to the latest version of the TRNSYS TOOL
• fix the VBA code if simple (ask if not sure)
• update the TRNSYS template, etc.

Invest the time fixing the system.

No repeated manual fixes.

16. Check Systematically

Rule: use checklists for all review processes.

Checklists mean that we can move fast under pressure without quality dropping - everything that needs to be checked is checked.

If the checklist doesn’t exist:

• create it
• use it
• share it with the team