What the AES HUB is

The AES HUB is a digital platform for UK housebuilders. It captures, stores, and reports the energy and building data for every job an energy assessor delivers on your behalf. The HUB replaces the PDF-and-spreadsheet exchange that used to sit between housebuilder and assessor with a live, structured record that both sides can interrogate at any time.

The HUB connects to the other services energy assessors run. SAP calculations, air testing, and photographic evidence (AES SiteView) all land in the HUB as files attached to the right plot, in the right job, under the right region.

Who this manual is for

This manual covers the AES HUB for all users. It is being written page by page. The topics ready today are the ones most users meet first:

• How to sign in and keep your account secure
• How jobs are organised under developers, divisions, regions, and sites
• How to find a job, read a job page, and drill into a plot
• How to draw a report and export the data

Topics for administrators (onboarding, permissions, client configuration) and for other roles will be added over time. Pages marked coming soon on the home page will appear as they are written.

What you need before you sign in

• An invite email. It comes from hubadmin@aessc.co.uk with the subject [AES HUB] You have been invited. If you have not received one, contact your administrator.
• A modern web browser on a laptop or tablet. The HUB runs in the browser, there is nothing to install.
• Permission on at least one tier. Your administrator grants this as part of onboarding. Without it the HUB will sign you in but show no jobs.

If you have all three, head to Set up your account and sign in for the first time.

Key terms you will see

The HUB uses the same small vocabulary across every page. Learn these once and the rest of the manual reads easily.

• Developer — the housebuilder at the top of the tree. Tier 1.
• Division — a grouping of regional offices inside a developer. Tier 2.
• Region — a specific regional office. Tier 3.
• Site — a named physical development delivered across several phases. Voluntary. Tier 4.
• Job — a single job or phase, owned by one energy assessor. Tier 5. Job codes carry a letter prefix that identifies the assessor (AES, AWE, FES, JSP).
• Plot — a single dwelling inside a job. Every file in the HUB is attached to a plot.
• CPN — Client Project Number. The developer’s own reference for a job.
• a.k.a. — the site’s primary alternative name, used for search.
• SAP — Standard Assessment Procedure. The UK method for calculating a dwelling’s energy performance.
• SAP 10.3 — the interim UK method for demonstrating Part L 2026 compliance, using the same monthly-average approach as earlier SAP versions updated for 2026 targets.
• HEM — Home Energy Model. The UK Government’s replacement for SAP. Uses half-hourly dynamic simulation for more accurate results on heat pumps, PV, and batteries. Expected to gain approved status around June 2027, at least three months after the Future Homes Standard goes live.
• EPC — Energy Performance Certificate. The headline A to G rating lodged for a finished plot.
• Stage — the lifecycle point a plot is at: Design, Prepare, Testing, As Built, or Completed.
• CML — Practical Completion. The date a plot is handed over. A past CML means the plot is completed and handed over; a future CML is a target date and drives the pipeline reports. CML is uploaded by developer staff. Syncing this data back to energy-assessor domains is planned for a future release.

For a deeper explanation of the tier tree, see Understanding the Tier Structure.

If you get stuck

• Email hubadmin@aessc.co.uk
• Phone 01884 242050

The 👍 / 👎 buttons at the bottom of every page send feedback straight to the team.

What next

• Your first report, end to end (coming soon)
• Set up your account and sign in for the first time
• Your dashboard
• Understanding the Tier Structure

Feedback

Was this page helpful?

Before you start

• Your admin has invited you. Check your inbox for an email from AES HUB Portal Admin with the subject [AES HUB] You have been invited.
• The invite contains your username and a one-time password.
• Use the invite within one week. After that, the credentials expire and your admin will need to send a new invite.
• The invite link works for the web, the iOS app, and the Android app. For drawing reports, use the web. The apps are designed for on-site photo capture.

Steps

1. Open the welcome email and click the PC link to open the sign-in page in your browser.

   

2. Type your email address and the one-time password from the invite, then click Login.

3. On the password setup screen, type a new personal password.

   

   Tip. Use three random words joined together, for example correct-horse-battery. Memorable for you, hard to guess for anyone else. See the NCSC three random words guidance for worked examples. Save the password in your password manager or browser if it is safe to do so.

4. Watch the strength bar under the password field. Keep typing until it reaches at least Acceptable.

5. Retype the password in Confirm Password. A green tick confirms the two match.

6. Click Login.

   

7. You are now back at the sign-in screen. Enter your email and your new password, then click Login.

8. The HUB emails you a 6-digit PIN from no-reply@aes-hub.co.uk.

9. Type the PIN into the six boxes on screen, then click Login.

   

10. Read the End User Licence Agreement and Privacy Policy, then click Agree.

    

    Warning. Clicking Do not agree ends your registration. You cannot use the HUB without agreeing to the EULA and Privacy Policy.

11. You land on the HUB dashboard. Registration is complete.

    Tip. Your session stays signed in for 7 days on this device. You will not need to sign in again during that window, unless we release an update or you sign out manually. Each device (laptop, tablet, phone) counts as a separate session.

Tips

• If your invite is older than a week, ask your admin to send a new one. The one-time password and the invitation expire together.
• You only see the Terms & Conditions screen once. The exception: if you previously had an account on HUB 1.0 and have been migrated to HUB 2.0, you will see it once more on your first HUB 2.0 sign-in.
• The 6-digit PIN appears in the email subject line so you can read it from a notification preview. Treat it like a password and do not share it.

What next

• Sign in (returning user)
• Your first report, end to end

Feedback

Was this page helpful?

Before you start

• Your account is already set up. If this is your first time, see Set up your account and sign in for the first time instead.
• You have your email and password to hand.
• You have access to the inbox you registered with (the 2FA PIN is emailed to that address).

Steps

1. Open the HUB sign-in page in your browser.

   

2. Type your email address and password, then click Login.

   Tip. Forgot your password? See Reset your forgotten password.

3. The HUB emails you a 6-digit PIN from no-reply@aes-hub.co.uk.

4. Type the PIN into the six boxes on screen, then click Login.

   

   Tip. PIN not arriving? Wait 1 to 2 minutes, then check your spam folder. If it still has not arrived, click Back to login page and try again to trigger a new PIN.

5. You land on the HUB dashboard.

   Tip. Your session stays signed in for 7 days on this device. You will not need to sign in again during that window, unless we release an update or you sign out manually.

What next

• Reset your forgotten password
• Understanding the Tier Structure

Feedback

Was this page helpful?

Before you start

• You can read the inbox of the email address you registered with.
• You know your registered email address.

Steps

1. On the sign-in screen, click Forgot password?.

   

2. Type your registered email address, then click Next.

   

3. The HUB confirms your request on screen. Close the browser tab and open your inbox.

   

4. Open the email from AES-HUB with the subject AES HUB - Password Reset and click Reset your password.

   Warning. The reset link expires 1 hour after the email is sent. If it expires, repeat steps 1 to 3 to trigger a new one.

5. Type a new password. The strength meter must reach Acceptable. Confirm it in the second field.

   

   Tip. You can reuse your old password if you want to. The HUB does not block password reuse.

6. Click Login. You land back at the sign-in screen. Sign in using your email and the password you just set.

Tips

• If the email does not arrive, wait 1 to 2 minutes, then check your spam folder. If it still has not arrived, repeat step 1 to trigger a new one.
• The reset link is one-use. Once clicked, it cannot be used again.
• Resetting your password does not end any other signed-in sessions you have on other devices.

What next

• Sign in
• Understanding the Tier Structure

Feedback

Was this page helpful?

Before you start

• Your administrator has invited you to the HUB. The welcome email should be in your inbox already.
• You have permission to see at least one job. (For this tutorial, replace AES7770 with a job code you have access to.)
• A modern web browser, Chrome, Edge, or Safari, on a laptop or desktop. Nothing to install.

Steps

1. Open the welcome email and click the activation link.

   

   The email comes from hubadmin@aessc.co.uk with the subject [AES HUB] You have been invited. Click the activation link inside.

   See Set up your account and sign in for the first time for the full first-time-setup detail, including what to do if the invite has expired.

2. Set your password and confirm.

   

   The activation link opens a password-setup screen. Type a strong password, confirm it, then click Login. The strength meter should reach Acceptable at minimum, Great for a passphrase such as three random words.

   See Set up your account for password tips and the National Cyber Security Centre’s “three random words” approach.

3. Sign in with the 6-digit PIN.

   

   Re-enter your email and new password. The HUB emails you a 6-digit PIN from no-reply@aes-hub.co.uk. Type the PIN into the six boxes and click Login. On first sign-in only you also accept the Terms and Conditions.

   See Sign in for the routine sign-in flow you will use from now on, and what to do if the PIN does not arrive.

4. Find AES7770 from the dashboard.

   

   You land on the dashboard. The fastest route to a known job is the main search bar at the top of the page: type AES7770 and click the matching result.

   Alternatively you can browse the Jobs list (cogwheel → Jobs) or walk down the tier tree from a developer to a region to a job. See Your dashboard, Finding a job, and Understanding the Tier Structure for those paths.

5. Open Analytics on the job page and pick the Completions Report.

   

   The job page for AES7770 opens. In the header, click the arrow next to Analytics to open the reports dropdown. Pick Completions Report.

   See The job page for everything else on this page (Key Facts, Plot List, files), and Drawing a report for the Analytics mechanic at every tier.

6. Accept the default filters and click Apply.

   

   The Completions Report opens with a Filter Settings panel on the left. The defaults are sensible for a first run: EPC mode, last 3 months for the date range, 2021 for Part L Building Regulations, AES7770 already loaded under Jobs.

   Click Apply at the bottom of the panel. The HUB runs the report. For a single job this returns in seconds.

   See Adjusting filters for what each filter does and how to combine them when you want a narrower or wider cut.

7. Read your first report on screen.

   

   The table fills the right-hand pane. Each row is a plot in AES7770. The headline columns to read first are the three pass-mark percentages: DER TER %-impr., DPER TPER %-impr., and DFEE TFEE %-impr. Positive numbers mean the plot is passing.

   See Completions Report for what every column means, and Shared middle columns for the actual-vs-notional building concept that sits behind DER, TER, and the rest of the D / T pairs.

8. Click XLSX to export to Excel.

   At the top of the report page, click the XLSX button. The HUB downloads a .xlsx file to your browser’s download folder. Open it in Excel. The same data you saw on screen is now yours to share, sort, or chart.

   Click Back at the top of the report page to return to the AES7770 job page when you are done.

Tips

• The dashboard remembers where you were. Next time you sign in, your most recent jobs sit at the top — no need to search again.
• Stay on the page while a report runs. A single-job Completions Report is fast (seconds), but Tier 1 reports across very large datasets can take 2 to 3 minutes. Navigating away cancels the run.
• The default filters are a starting point, not a rule. As you get familiar with the HUB you will reach for Adjusting filters to narrow or widen the cut.

What next

• Drawing a report, the same mechanic at every tier
• Adjusting filters, the panel that sits in front of every report
• Reports summary, the gateway to the rest of the report types
• Getting help and giving feedback, where to go if something goes wrong

Feedback

Was this page helpful?

Before you start

• You are signed in to the HUB. If not, see Sign in.
• You have been granted access to at least one job, region, or developer. If your dashboard is empty, contact your administrator.

Steps

1. Sign in. You land on the dashboard.

   

   The dashboard has three areas: the top bar (visible on every screen), the Job Results block, and the Notification List block.

2. Look at the top bar. It is visible on every screen in the HUB.

   

   Left to right: main search field, AES HUB logo, plus icon, notifications icon, cogwheel, user chip (your initials).

   Note. The set of icons shown may vary depending on your user permissions and your organisation’s subscription. The baseline set above is present for every user.

3. Use the main search field to find anything in the HUB.

   

   It searches across the whole HUB and returns matches for job numbers, client project numbers, site names, and any registered alternative names for a site.

   Why alternative names matter. Construction sites often carry several names: a planning name, a project name, a sales name, and so on. The site is logged in the HUB under the name the regional assessor chose, which may not be the name the developer uses. Alternative names bridge this gap so the site is findable by any of its known names.

   Top tip. If you want an alternative name added to a site, contact your assessor.

4. Click the AES HUB logo from anywhere in the HUB to return to this landing page.

5. Click the plus icon to open a Create section.

   

   Create is a section heading. The actions that sit under it are permission-based and only available to registered assessors. For most users the heading is visible but no actions appear underneath.

6. The notifications icon is a shortcut to your Notification List (the same list shown at the bottom of the dashboard).

   Notifications are raised when:

   • A BREL needs your signature
   • A file has been shared with you
   • A photo has been uploaded in SiteView or FireView (if your organisation uses them)

7. Click the cogwheel to open the Manage section.

   

   Manage is a section heading. Grouped under it are Jobs (the full jobs list) and Clients (the full clients list).

8. Click the user chip (your initials) to open your account menu.

   

   The menu shows your full name at the top, followed by Profile (link to your profile page) and Sign out.

   Stay signed in for 7 days. On your own device, you do not need to sign out each time. Your session remains active for 7 days, even if you close the browser. This is by design to save you from re-entering your password and PIN every day.

   When to sign out. If you are working on a computer or device that is not your own (a shared machine, a colleague’s laptop, a public terminal), always use Sign out when you finish. Only a hard sign out ends the session. Closing the browser does not.

9. Scroll to the Job Results block. It is a preview of the jobs you have access to.

   

   The table has five columns: Job, CPN, Plots, Developer/Region/Site, Actions. The Developer/Region/Site column shows where each job sits in the Tier Structure. See The Tier Structure for what each tier means.

   Note. The Status and Type filters above the table are being developed. You can ignore them for now. The Search field on the filter row already works and searches within the current job list.

10. Navigate to a job from here in one of three ways:

    

    • Type a job number, job name, or site name into the main search at the top of the screen (recommended for a specific job)
    • Click Show all to open the full Jobs list (recommended when browsing)
    • Go to a region first, which narrows the list of jobs shown

    Tip. Do not flip through pagination page by page. The list can run to dozens of pages. Use search or region-based navigation instead.

11. Scroll to the Notification List block.

    

    This is the same list reached from the notifications icon in the top bar. The default filters show unread messages from the last month. See Working with notifications (coming soon) for detail.

Tips

• The top bar is present on every screen in the HUB, so the logo, main search, notifications, cogwheel, and user chip are always one click away.
• The dashboard is a preview, not a navigation surface. Use main search, Show all, or region navigation to reach individual jobs.
• Your session lasts 7 days on this device. If you share a computer, sign out explicitly when you finish.

What next

• Understanding the Tier Structure
• Finding a job
• Drawing a report
• Adjusting filters
• Signing a BREL (coming soon)

Feedback

Was this page helpful?

Before you start

• You are signed in to the HUB.
• You have been granted access to at least one tier. If you have no access, contact your administrator.

The five tiers

The HUB organises every job under a five-tier hierarchy. Each tier groups the one below it.

Why the Site tier exists. Phases of the same development are often commissioned one at a time, sometimes with different energy assessors working on each phase. To the developer it is one site; in the HUB each phase is an independent job. The Site tier groups those sibling-phase jobs so they read as a single development. Site is voluntary. A job can sit directly under a Region with no Site in between.

Permissions and roles

Two separate systems decide what you can do in the HUB.

• Permissions = where you can act. They follow the tier tree like branches. Sit on Tier 1 and you see every branch below. Sit on Tier 3 and you see one region and everything under it. Sit on Tier 5 and you see one job.
• Roles = what you can do. An Analyst role can draw reports and sign BRELs. An Admin role can also edit or delete jobs. The role is the same wherever you go; the permissions decide where the role applies.

The two combine. A user with the Analyst role and Tier 3 permission on North Thames can draw reports for any job in North Thames, but cannot see jobs in other regions.

Steps

1. Click the cogwheel in the top bar, then Clients.

   

   The Clients page is the main entry point to the Tier Structure. It lists every tier you have access to.

2. Look at the Clients list.

   

   Each row represents a tier. Columns are Client (the tier name with its breadcrumb lineage), Type (Developer, Division, Region, or Site), and Actions.

   The Roman numeral on the left of each row shows the tier level: I for Developer, II for Division, III for Region, IV for Site.

   What you will see. Your view is scoped by permission. If you sit on one Region, you see your Region and everything below it. Tiers above your permission are shown in the breadcrumb for context but are not clickable.

3. Filter the list by Type to show a single tier level.

   

   Tier 5 (Job) is not listed here. Use the Jobs page (cogwheel → Jobs) or the dashboard for job-level work.

4. Use the task bar to refine the view.

   

   • Search filters the list by name.
   • Display count (10 / 25 / All) sets how many rows show per page.
   • Display format (lines / columns / squares) changes the layout. This feature is most useful for reports and is available on many HUB pages.

5. Click any row to open that tier’s detail page. A tier detail page has two parts.

   Top. Key information for the tier (E-mail, Post Code, Town, Address) and two action buttons: Back to clients and Analytics.

   

   Bottom. The child tiers and jobs attributed to this tier, split across two tabs: Clients (n) and Jobs (n).

   

   Note on the Clients tab. The tab is always labelled Clients, whether the child tiers beneath it are Divisions, Regions, or Sites. The label does not rename itself to match the child tier.

6. Walk down the tree by clicking a child in the Clients tab.

   

   Each click narrows the scope. In this example a Region shows Clients (0) and Jobs (9), no Sites beneath it, and nine jobs allocated directly to the Region.

7. Walk up the tree by clicking a segment of the breadcrumb at the top of the page.

   Each segment is a link. Clicking takes you to that tier’s detail page.

8. Use the Analytics button to draw a report at the current tier.

   

   Reports are grouped under the arrow. The reports available to you depend on your subscription, role, and permissions. See Drawing a report for how to use them.

   Reports at higher tiers take longer. A report on a single job takes seconds; a Tier 1 report on a very large dataset can take 2 to 3 minutes. A banner on the HUB turns green when the run is complete. Stay on the page while the report is running.

9. Edit or delete actions are permission-gated.

   The Actions column on the Clients list and the edit controls on detail pages are available only to Administrator roles. This protects the tier data from accidental loss.

10. Alternative entry: click a breadcrumb from the dashboard.

    

    On the dashboard’s Job Results block, the Developer/Region/Site column shows the full breadcrumb for each job. Each segment is a link. Click any segment to jump straight to that tier’s detail page without going through the Clients list.

Tips

• Think of the Tier Structure as a tree. Permissions are which branch you sit on. Everything below your branch is visible to you; everything above is context only.
• Roles and permissions answer different questions. Roles answer what you can do, permissions answer where you can do it. You need both to act.
• The Site tier is voluntary. Do not assume every job has one. When no Site exists, the job sits directly under a Region.
• Reports at high tiers are slow by nature. Start the report and carry on with other work. The banner tells you when it is ready.

What next

• Finding a job
• The job page
• The plot page
• Drawing a report
• Adjusting filters

Feedback

Was this page helpful?

Before you start

• You are signed in to the HUB.
• You have been granted access to at least one job. If you have no access, contact your administrator.
• You have read Understanding the Tier Structure. The Jobs list uses the same breadcrumb lineage.

When to use the Jobs list

The Jobs list is the full, permission-scoped inventory of every job you can see. Use it when you want to browse or scan rather than look up a specific job.

For a single known job, the main search at the top of the HUB is faster. See Your dashboard for the main search.

Steps

1. Click the cogwheel in the top bar, then Jobs.

   

   The Jobs page is the full list of jobs you have permission to see.

2. Look at the Jobs list.

   

   Columns are:

   • Job — the job code and name (for example, AES2391 Collaton St Mary, Torbay).
   • CPN — Client Project Number, the developer’s own reference for the job (for example, HM-13115).
   • Plots — the number of plots on the job.
   • Developer / Region / Site — the full breadcrumb showing where the job sits in the Tier Structure.
   • Actions — edit and delete controls, gated to Administrator roles.

   The # chip on the left of each row is the Tier 5 marker, the Job-level equivalent of the Roman numerals (I, II, III, IV) you saw on the Clients list.

   Reading a job code. The letter prefix in front of the number identifies the energy-assessor firm that owns the job.

   • AES_nnnn_, a job by AES Sustainability Consultants (for example, AES2391).
   • AWE_nnnnn_, a job by Award Energy (for example, AWE10101). Award does not run its own numbering system, so these numbers are assigned automatically by the HUB.
   • FES_nnnnnn_, a job by The FES Group (for example, FES008429).
   • JSP_nnnnn_, a job by JSP Sustainability (for example, JSP20859).

3. Use the task bar to refine the list.

   

   • Status filters jobs by lifecycle state (for example, created). Not fully implemented yet, you can ignore it for now.
   • Type filters jobs by category. Not fully implemented yet, you can ignore it for now.
   • Search filters the list by name, job code, or CPN.
   • Display count (30 / 90 / All) sets how many rows show per page. The Jobs list uses higher numbers than the Clients list (10 / 25 / All) because most users have far more jobs than clients.

   Note. The Search, display count, and pagination controls behave the same way on every list page in the HUB. See Understanding the Tier Structure for the reference walk-through.

4. Scroll to the bottom of the list to reach pagination and the total count.

   

   • Pagination sits centred below the table. Click a number or the arrows to step through pages.
   • Count indicator sits below pagination (for example, 1 to 30 of 190 jobs). It shows the current range and the total number of jobs in your permission scope.

   Tip. Do not flip through pagination page by page on a long list. Use Search, the display count, or the Tier Structure to narrow the view first.

5. Click a job row to open that job’s detail page. The detail page covers everything attached to the job: reports, photos, BRELs, and more. See The job page.

6. Click any segment of the breadcrumb in the Developer/Region/Site column to jump to that tier’s detail page.

   Each segment is a link. Clicking the Developer name opens that Developer page; clicking the Region name opens that Region page. This is the same breadcrumb behaviour as the dashboard Job Results block.

7. Edit or delete actions are permission-gated.

   The Actions column is available only to Administrator roles. This protects the job data from accidental loss.

Tips

• The Jobs list is scoped by permission. You see every job on every branch at or below your tier, and nothing else. If a job you expect to see is missing, check your permissions before assuming the job does not exist.
• For a specific, known job, the main search at the top of the HUB is faster than the Jobs list.
• The # chip marks a Tier 5 row. Roman numerals (I to IV) mark tiers on the Clients list. Together they give a consistent visual cue across the HUB.

What next

• Drawing a report

Feedback

Was this page helpful?

Before you start

• You are signed in to the HUB.
• You have permission to see at least one job.
• You have read Finding a job. This page picks up the moment you click a job row in the Jobs list, or a job segment in a breadcrumb anywhere in the HUB.

When to use the job page

The job page is the single source of truth for a job. It shows where the job sits in the Tier Structure, who it belongs to, what it contains at plot level, and what reports can be drawn on it. Use the job page when you need plot-level files, Part L performance numbers, or any job-level report.

Steps

1. Land on the job page.

   

   The top of the page shows:

   • Breadcrumb — the full tier lineage above the job. Each segment is a link. See Understanding the Tier Structure for how breadcrumbs behave.
   • Job name — the job code and full site name (for example, Job #AES7770 East Hill, Chatham).
   • CPN — Client Project Number, the developer’s own reference for the job (for example, HM-21974).
   • a.k.a. — the site’s primary alternative name. See Your dashboard for why alternative names exist and how they help with search.
   • Back to Jobs — returns to the full Jobs list.
   • Analytics — opens the job-level reports dropdown. See Drawing a report.

   Below the header sit two collapsible blocks: Key Facts and Plot List. They are unfolded by default when you land on the page. Click the + or − next to a block name to fold or unfold it. Folding a block you are not using keeps the page tidy.

2. Read the Key Facts block.

   

   Key Facts is an at-a-glance summary of the whole job.

   • Building Type — icons with counts for every building type present on the job. The example above shows Detached (26), Semi-Detached (62), Mid-terrace (1), End-Terrace (2). Only types present on the job are shown. Other types (for example, bungalows or flats) would appear only if the job contained plots of that type.

   • Heating — icons with counts for every main heating type present. The example shows Mains Gas (68) and Electricity (23). Same rule: only types present are shown.

   • Carbon (DER ▸ TER), Fabric (DFEE ▸ TFEE), and Primary (DPER ▸ TPER), the three Part L performance KPIs, aggregated across the whole job. Each tile shows the designed value, the target value, and the percentage by which the job beats the target.

     Jobs assessed under Welsh or Scottish regulations show a different KPI set. The KPIs on these tiles always match the regulation that applies to the job.

   • SAP rating — a dynamic bar graph showing how plot SAP ratings are distributed across the job. The graph uses a finer gradation than the headline EPC bands (A to G), splitting the top bands into sub-ranges (A 101+, A 95 to 100, A 92 to 94, B 88 to 91, B 85 to 87, B 81 to 84) so differences between plots are easier to see. The graph extends downwards as lower bands are needed.

   • Avg SAP Rating — the average SAP EPC rating across the whole job. The example shows B 90.

3. Use the Plot List block.

   

   The Plot List is a row-per-plot table of every plot allocated to the job.

   Pagination and the count indicator sit centred below the table (for example, 1 to 20 of 91 plots).

   Task bar.

   

   • Stage — narrows the list by lifecycle stage. Values are explained below.
   • Block — shown only if the assessor has grouped plots into blocks, for example a block of apartments or a row of terraces. If no plots are grouped, the Block filter is not displayed.
   • Search — filters the list by plot number or text in the row.
   • Display count (20 / 50 / All), sets how many rows show per page.

   Stage values.

   

   • All — every plot, regardless of stage.
   • Design — plots at design stage. Design documents live here (Design SAP, Design PEA, Design BREL or Design BRWL, and related files).
   • Prepare — the interim stage between Design and As Built, used to capture changes (heating design changes, PV design changes, and so on) before an EPC is lodged.
   • Testing — plots with an air test certificate. Depending on your contract with the energy assessor, other commissioning certificates may be available here.
   • As Built — plots with every document required for an EPC. Typically the signed BREL or BRWL, the Photo Evidence report, and the As Built SAP.
   • Completed — plots flagged as complete. Completed is a manual trigger at plot level and also propagates automatically when the whole job is marked complete.

   Columns.

   

   • Plot — the plot number. Click it to open the plot’s own page. See The plot page.
   • Stage — the plot’s current stage, inferred from the documents uploaded to it.
   • Block — populated only for plots that have been grouped into a block.
   • Files — the number of documents uploaded to the plot. Read it together with Stage. For example, Testing with 1 file means the air test certificate is uploaded. As Built with 3 files typically means the As Built SAP, the EPC, and the BREL are all in place.
   • Building Reg. — the building regulation under which the plot is assessed. Values are Part L 2009, Part L 2013, Part L 2021, and FHS (Future Homes Standard). Welsh and Scottish regulations are grouped under their English counterpart and appear here with the English label.
   • Actions — edit and delete controls, available only to Administrator roles.

Tips

• Key Facts and Plot List are foldable. If you are only working with the plot table, fold Key Facts to keep the page tidy.
• The Files column on the Plot List is the quickest read of how far a plot has progressed. The Stage label plus the file count tells you which documents have arrived.
• Completed is not triggered by uploaded documents. It is a manual flag at plot level, set at the latest when the whole job is marked complete.

What next

• The plot page
• Drawing a report

Feedback

Was this page helpful?

Before you start

• You are signed in to the HUB.
• You have permission to see the parent job. You reached the plot page by clicking a plot number on The job page.

When to use the plot page

The plot page is the single source of truth for one plot. It shows the plot’s key facts and performance numbers at every stage captured for it, and gives access to every file uploaded against it. Use the plot page when you need plot-specific detail: air test results, uploaded documents, or the EPC certificate number.

Steps

1. Land on the plot page.

   

   The top of the page shows:

   • Breadcrumb — the parent job and the plot (for example, #AES7770 › ●001). The job segment is a link back to The job page. The ● before the plot number is decorative.
   • Plot header — the plot number followed by the stage currently being viewed (for example, Plot ●001 As Built).
   • Left / right arrows — step to the previous or next plot in the job, in plot-number order. Any filters you set on the parent job’s Plot List (Stage, Block, Search) are respected, so the arrows step only through plots that match those filters.
   • Back to Job — returns to the parent job page.
   • Stage pills — Design, Prepare, Testing, As Built, Completed. Pills are colour-coded:
     • Red — the stage has data captured for it. Click the pill to switch to that stage’s data.
     • Purple — the stage is currently being viewed. This can be any stage with data, not just the most recent.
     • Grey — the stage has no data captured for it. Grey pills are not selectable.

     The stage pills are an interactive selector. Switching pill changes what shows in Key Facts, Key Performance Indicators, and File List. The plot header updates to name the stage you are viewing.

   Below the header sit three collapsible blocks: Key Facts, Key Performance Indicators, and File List. They are unfolded by default when you land on the page. Click the + or − next to a block name to fold or unfold it.

2. Read the Key Facts block.

   

   Key Facts is the plot-specific version of the job-page Key Facts. Every tile refers to this single plot at the currently selected stage.

   • Building Type, Heating, Carbon (DER ▸ TER), Fabric (DFEE ▸ TFEE), Primary (DPER ▸ TPER), and SAP rating, as on The job page, but for one plot. Jobs assessed under Welsh or Scottish regulations show the matching KPI set here too.
   • Air Pressure — the air-tightness result for the plot.
     • Before a test has been uploaded, the tile shows the Design A/P target only.
     • Once an air test is uploaded, the tile expands to show Actual ▸ Design (the tested value against the design target).

     Failed air test. If the Actual value is higher than the Design target, the plot has failed the air test. A retest is typically done until the design target is met.

   • Solar — the plot’s installed solar capacity in kWp. This is an aggregated figure for the plot and does not break out individual arrays. For array-level detail, see the PV Pipeline Report (coming soon).

3. Read the Key Performance Indicators block.

   

   The KPI block is a grid of reference values for the plot at the selected stage. Which items populate depends on the stage: some items (for example, the EPC number and date) only appear once the plot is completed.

   • EPC Date — the date the EPC was lodged.
   • EPC — the EPC certificate number (for example, 7436-6434-0100-0453-1296). Enter this number on the government’s Find an energy certificate service to pull up the full certificate.
   • No. Storeys — the number of storeys in the plot.
   • Building Regulations — the regulation under which the plot is assessed (for example, SAP 2021). Welsh and Scottish regulations are grouped under their English counterpart.
   • Calculation Type — the SAP calculation mode (for example, NewBuildAsBuilt).
   • Address — the plot’s full postal address.
   • Construction Type — the main wall construction for the plot (for example, Cavity Wall).
   • Ventilation System Type — the main ventilation system (for example, Continuous Mechanical Extracts).

4. Use the File List block.

   

   The File List shows every file uploaded against the plot at the selected stage. Columns are:

   • Type — the file’s category (for example, SAP PDF, EPC Report, BREL Report (signed)). The set of available types varies by stage. See File types (coming soon) for a walk-through of each type.
   • Filename — the full file name as uploaded.
   • Rev — the revision number. When a file has more than one revision, each revision is viewable in the preview overlay as its own tab.
   • Actions — a download button for the current revision.

   Accepted formats. The HUB accepts PDFs and common image formats (JPG, PNG) only. Nothing else can be uploaded.

   Click the file type to open the file in the File Preview overlay.

   

   The preview overlay shows:

   • Rev pill — marks the revision currently being viewed. If the file has multiple revisions, each is available as its own tab at the top of the overlay. Click a tab to flip to that revision.
   • Download — saves the currently viewed revision to your computer.
   • Close — returns you to the plot page.
   • Viewer — renders PDFs and image files natively. Standard PDF controls (page through, zoom, search, print) are available for PDF files.

Tips

• The stage pills are the fastest way to compare design against as-built on a single plot. Switch to Design to see the designed numbers, switch to As Built to see what was delivered.
• Use the left / right arrows to scan through a batch of plots without going back to the job page. Set a filter on the parent Plot List first if you want to walk only a specific set of plots (for example, only Testing stage).
• The EPC number is a direct key into the government’s Find an energy certificate service. Keep a note of it if you plan to reference the full EPC later.

What next

• File types (coming soon)
• Drawing a report

Feedback

Was this page helpful?

Before you start

• You are signed in to the HUB.
• You have permission on at least one tier.
• You have read Understanding the Tier Structure. Drawing a report at Tier 1 aggregates every job beneath it; drawing at Tier 5 aggregates a single job.

When to use this page

Use this page when you need a report for a developer, a division, a region, a site, or a single job. The Analytics button and the reports behind it are the same on every tier detail page. Only two things change as you move down the tree: the scope of the report, and which reports appear in the dropdown.

Steps

1. Open Analytics on the tier you want to report on.

   Navigate to the detail page for the developer, division, region, site, or job you want. See Understanding the Tier Structure for how to walk the tree, or The job page for the job detail page.

   Click the arrow next to Analytics to open the reports dropdown.

   

   Which reports appear depends on three things combined:

   • Subscription — what your organisation has bought.
   • Role — what your role is allowed to do.
   • Permissions — which tier you sit on.

   A report listed for one user may not appear for another on the same tier.

   Data by Site is above-job-only. The Data by Site report lists every job beneath the current tier. It appears at Tiers 1 to 4 (Developer, Division, Region, Site) and is hidden at Tier 5 (Job), because a job already is the unit the report would return. The other reports are the same list at every tier.

2. Pick a report.

   Click the report you want. The HUB opens a new page for that report with a Filter Settings panel on the left and an empty main pane showing Please set filters.

   

   The filter panel is tailored to the report. Common filter groups include Report type (Design / As Built / Hybrid), Part L Building Regulations, SAP Region, Lodgement Date Range, Client, Jobs, Building Connotation, and Main Construction.

   See Adjusting filters for what each filter does, the defaults, and how they combine.

3. Apply the filters to run the report.

   At the bottom of the Filter Settings panel, click Apply. The HUB runs the report and the table paints in the main pane. Click Reset to clear the panel and start again.

   • Job level returns in seconds.
   • Region and Division are typically fast.
   • Developer level on a very large dataset (12,000 plots or more) can take 2 to 3 minutes.

   Stay on the page while the report is running. A banner on the HUB turns green when the run is complete. Do not use the browser’s Back button or navigate away until the table has painted.

4. Work with the table, or export to Excel.

   Once the table is in the main pane you can scroll, sort, and interrogate it on screen. To take the same data out of the HUB, click XLSX at the top of the page to download an Excel copy.

   To leave the report, click Back at the top of the page to return to the tier you drew the report from.

Tips

• The mechanic is the same at every tier. Pick the tier, click Analytics, pick the report, set filters, Apply. Only the scope changes.
• Higher tiers return bigger tables. Use the filter panel to scope what you need before clicking Apply.
• The green banner confirms the run is complete. If it has not turned green, the report is still building.
• Export to XLSX when you need to share or archive. Interrogate on screen when you are still deciding what to look at.

What next

• Adjusting filters
• Reports section (coming soon)

Feedback

Was this page helpful?

Before you start

Four rules apply across every filter group on this page. Learn them once and the rest reads easily.

• Nothing chosen means no exclusion. If you leave a filter group untouched, every plot is included. There is no “all” to tick by default.
• Some groups arrive with a pre-selection. The screenshots on this page show the as-landed state. Where a pill looks highlighted, that is the HUB’s starting point, not a change we made for the screenshot.
• Select All toggles the whole group. Every group with a Select All switch turns all its chips on or off at once. Hand-picking chips updates the toggle to match.
• Filters combine as OR within a group, AND across groups. Picking PV and Battery in Renewables returns plots with either. Picking Gas in Heating Fuel and 2021 in Part L returns plots that are both gas and 2021-band.

When to use this

Every time you open a report at the Developer, Division, Region, or Site tier. The plot page is the only place in the HUB where a report can run without the filter panel.

Steps

1. Open a report. Click a report from the Analytics dropdown on a tier page. The filter panel appears on the left. The right-hand canvas shows Please set filters until you apply. See Drawing a report for how to reach the panel.

2. Check the defaults on landing. When you arrive on the panel:

   • Lodgement Date Range is set to EPC mode, last 3 months.
   • Part L Building Regulations has 2021 pre-selected (the current live regs).
   • If you launched from a job page, that job is already in Jobs. If you launched from a higher tier, the scope inherits from the breadcrumb.
   • Everything else is empty.

   The defaults are a sensible starting point for most jobs. Change whatever does not fit your question.

3. Pick your filters. The fourteen filter groups below run top to bottom in the panel. Use the subsections as a reference, you only need the groups relevant to your question.

   ### Report type

   Three pills at the top of the panel, Design / As Built / Hybrid, controlling which plot stages feed the report.

   • Design — plots at Design and Prepare stages (modelled, pre-construction figures).
   • As Built — plots at Testing, As Built, and Completed stages (actual figures captured after construction).
   • Hybrid — both together, combining design-stage figures for plots that have not yet been built out with as-built figures for those that have.

   Default: Hybrid. Unlike the rest of the panel, Report type is single-select, clicking another pill replaces the current choice rather than adding to it.

   ### Part L Building Regulations

   

   Four pills for the SAP methodology / building-regulations band:

   Pill	SAP version	England	Wales	Scotland
   2010	SAP 9.90	Part L 2010	n/a	Section 6 (2010)
   2013	SAP 9.92	Part L 2013	Part L 2014	Section 6 (2015)
   2021	SAP 10.2	Part L 2021	Part L 2022	Section 6 (2022)
   FHS	SAP 10.3	Part L 2026	TBC	TBC

   Scottish and Welsh equivalents are rolled under the English year labels for simplicity. If you are looking for Wales’s 2014 regs or Scotland’s 2015 regs, both sit behind the 2013 pill.

   FHS is a placeholder for the Future Homes Standard. It lights up when the first FHS design data lands. See Key terms for the SAP 10.3 vs HEM distinction.

   Default: 2021 selected. Flip Select All for all four pills at once.

   ### SAP Region

   

   Three icons: England, Scotland, Wales. The HUB reads the region from the SAP (or future HEM) document.

   Default: nothing selected (all regions included).

   ### Lodgement Date Range

   

   One filter group with two modes, toggled EPC / CML.

   EPC mode filters by the date the EPC was lodged on the official register (gov.uk for England, Scottish EPC Register). If a certificate has been re-lodged (for example to fix an address), the latest date wins. EPC dates are always historic, the pills are 3 / 6 / 12 / All / Custom months back.

   

   CML mode filters by Practical Completion date. A past CML means the plot is completed and handed over; a future CML is a target date, the basis of every pipeline report. The pills go both backwards and forwards: -3 / -6 / -12 / +3 / +6 / +12 / All / Custom. See Key terms for the full CML definition.

   CML data is entered by the housebuilder, not by AES or the energy assessor. AES does not control the timing or accuracy of these dates. For queries about missing or incorrect CMLs, contact your technical departments or portal admins.

   Using Custom. Click Custom to open a calendar picker. Click the start date, then the end date, or drag to select a range.

   

   Default: EPC mode, 3 months selected, the last 3 months of EPC lodgements.

   Design-stage plots have no EPC lodgement yet. If you are looking at design-stage data, leave the EPC pills unselected, otherwise the report will return zero results for design-stage plots.

   ### Client and Jobs

   

   Two free-text fields with type-ahead search.

   • Client — search by developer name. If you serve more than one developer you can add several clients to combine them in one report.
   • Jobs — search by job code (AES2391) or site name (Collaton St Mary). Add as many as you need; the report combines them. You see only jobs for which you have permission on the tier tree.

   When you launch a report from a job page, that job is pre-loaded in Jobs. Remove it with the bin icon to broaden the scope, or add more jobs to combine them.

   Default: whatever the launch context pre-loads. Empty elsewhere.

   Competitive neutrality. Energy assessors serving multiple developers can combine their own clients here. Developers are confined to their own data and cannot add a rival developer. See Where your data lives.

   ### Building Connotation

   

   Six built-form icons, read from the Built Form field on the SAP document:

   • Detached
   • Semi-detached
   • Mid-terrace
   • End-terrace
   • Bungalow
   • Apartment

   Every plot in the HUB is classified under one of these six. The filter is exhaustive, even where the plot card shows a free-text variant.

   ### Main Construction Type

   

   Six materials for the plot’s primary external wall. Read from the SAP document:

   • Timber — timber frame
   • Cavity — masonry cavity wall
   • Solid — solid wall (brick, block, stone)
   • Steel — steel frame
   • System — system build (SIPs, panelised)
   • Curtain — curtain walling

   ### Construction Type

   

   Same six materials, but looking at every external wall on the plot, including the primary one. Useful when a plot has mixed walls and you want to catch it under any of its materials, not only the dominant one.

   Main vs Construction Type. Pick Timber in Main to find plots where timber is the primary wall. Pick Timber in Construction Type to find any plot with timber walls somewhere, primary or secondary.

   ### Heating Fuel

   

   Five fuel categories, read from the SAP Main Heating 1 field, or the communal heating fuel where a communal system is in place:

   • Gas
   • Solid — solid fuel (wood, biomass, coal)
   • Oil
   • Electricity — electricity feeding the main heating
   • None — no on-plot heating fuel at all (rare but possible)

   None is a genuine “no fuel”, not a communal plot. Communal systems still record the fuel powering the energy centre.

   Main Heating 2 (for example a log burner on top of a main boiler) and secondary heating are not read by this filter.

   ### Heating Type

   

   Four system-type buckets. Same source as Heating Fuel, the SAP main or communal heating:

   • Boiler — gas, oil, or solid-fuel boilers
   • Electric — direct electric heating (panel heaters, electric boilers, storage heaters)
   • Heat Pump — air-source, ground-source, water-source
   • Other — anything not in the three above

   The top three buckets cover the vast majority of plots. If Other is returning a lot of results, flag it, we can spin it into its own filter.

   ### Heating Emitter

   

   Four emitter types for the plot’s main heating system:

   • Radiators — wall-mounted wet radiators
   • Underfloor — underfloor heating only
   • Fan Coil Units — fan-assisted emitters, typical with heat pumps
   • Rad. / UFH — both radiators and underfloor on the same plot

   Communal plots won’t match emitter filters. SAP does not record emitter data for communal heating systems. If you pick any emitter here, communal-heating plots are excluded from the result.

   ### Ventilation

   

   Six ventilation system types:

   • PIV — Positive Input Ventilation (typically a loft-mounted fresh air fan)
   • Intermittent — intermittent extract fans in wet rooms
   • dMEV — Decentralised Mechanical Extract Ventilation (one continuous fan per wet room)
   • cMEV — Centralised Mechanical Extract Ventilation (single central fan, ducted)
   • MVHR — Mechanical Ventilation with Heat Recovery (supply and extract, recovers heat)
   • Other — anything not in the five above

   ### Renewables

   

   Four on-plot renewable technologies. A plot can have any combination; the filter matches any of your picks (OR within the group):

   • PV — photovoltaic solar panels
   • SHW — Solar Hot Water (thermal)
   • WWHR — Waste Water Heat Recovery
   • Battery — battery storage

   Pick PV and Battery to find plots with either or both. To find plots with both at the same time, combine this group with a different narrowing filter elsewhere, or export to XLSX and cross-filter there.

4. Apply or Reset. When your filters are set, use the two buttons at the foot of the panel:

   

   • Apply — runs the report against your filters.
   • Reset — clears every filter, including the defaults (EPC + 3 months, Part L 2021). Use it for a clean slate.

   Reset is scorched-earth. If you Apply immediately after a Reset, the report runs against the full dataset in your permission tree. Expect a larger result and a longer run time. If you only want to change a few filters, edit them in place, don’t Reset.

5. Review, amend, or export. The right-hand canvas changes based on what Apply returns.

   Before you Apply, the canvas shows a guidance prompt, “Please set filters”, reminding you the report is waiting for your selections. The XLSX button is greyed out. See the hero at the top of this page for the full view.

   

   If your filters are too narrow, the report runs but returns zero rows, the canvas shows 0 Plots. XLSX stays greyed out. Widen a filter (for example move the EPC pill from 3 to 12 months), click Apply again, and the report re-runs.

   When results come back, the table fills the canvas and XLSX activates. Review on screen, or download to Excel to interrogate further. See Drawing a report for the table and XLSX detail.

Tips

• Start from the defaults. EPC + 3 months + 2021 Part L covers the most common question, “what’s been lodged recently?”. Only change filters you have a reason to change.
• Narrow with groups, not with Reset. Adding a group (say SAP Region: England) narrows the result. Reset wipes everything and makes you start over.
• Stay on the page while the report runs. Large reports (Tier 1, twelve thousand plots) take 2 to 3 minutes. Navigating away cancels the run. Lower tiers return in seconds.
• Export and cross-filter in Excel. The filter panel gives you the headline cut. For “plots with PV and Battery at the same time”, export the PV result to XLSX and cross-filter there.

What next

• Drawing a report
• Your dashboard
• Getting help and giving feedback

Feedback

Was this page helpful?

What a HUB report is

A report is an Excel-style table that aggregates every plot beneath the tier you run it from, filtered by the choices you set in the filter panel. Reports are launched from the Analytics dropdown on any tier detail page. See Drawing a report for the launch mechanics and Adjusting filters for the panel that sits in front of every report.

Reports fall into two families:

• Data by Site — a job-level summary. One row per job, twelve columns, a bird’s-eye view of the portfolio beneath your current tier. Available at Tiers 1 to 4 only. See Data by Site.
• Plot-level reports — one row per plot, with all the SAP / HEM data behind it. This is where most of your reporting time will go. There are six of these: Completions, Energy, M&E Pipeline, PV Pipeline, Fabric Pipeline, and NextGen EUI.

How every plot-level report is shaped

Open any of the six plot-level reports side by side and you will see the same three-part structure.

Static front — identity. The first block is always the same core set of columns that tell you which plot and job the row belongs to. The core eight are always present:

• Plot-Ref.
• Stage
• Revision
• Revision Date
• Client Job-Nr. (the developer’s CPN)
• Job-Name
• Plot
• Developer

Between Developer and the report-specific data sit the tier columns for whichever tiers exist in your developer’s tree: Division (T2), Region (T3), Site (T4). A small single-tier developer will see none of these. A large housebuilder with a full tree will see all three. In the worked examples used throughout this manual you will typically see Developer plus Division plus Region, three tier columns in addition to the core eight.

After the tier columns come three plot-descriptor columns, House Reference, House Type, and Connotation. These close out the static front. The total static front therefore runs from 11 columns (single-tier developer) to 14 columns (full Developer / Division / Region / Site tree).

Middle — report-specific. Every report carries its own payload here. Completions gives you the headline EPC and BREL performance numbers; Energy gives you the end-use energy breakdowns; M&E, PV, and Fabric give you the respective component detail; NextGen gives you the end-use intensity split. Some columns repeat across reports (for example, DER and TER appear in both Completions and NextGen) — those are documented once in Shared middle columns so each report page does not repeat the definition.

Static rear — two dates. Every plot-level report closes with the same two date columns:

• EPC Lodgement Date — the date the EPC was lodged on the register, blank until a plot is certified.
• CML Date — Practical Completion date, past or target. See Key terms for the full CML definition.

Where to go next

• Data by Site, the outlier
• Shared middle columns, cross-report columns documented once
• Completions Report
• Energy Report
• M&E Pipeline Report
• PV Pipeline Report
• Fabric Pipeline Report
• NextGen EUI Report

What next

• Drawing a report
• Adjusting filters

Feedback

Was this page helpful?

If you hit a problem

Contact the AES support team by email or phone.

• Email hubadmin@aessc.co.uk
• Phone 01884 242050

When you email, include as much as you can: the page you were on, the job number, what you were trying to do, and a screenshot if the problem is visual. It helps us work the issue faster.

What happens next. Every email and phone call is logged as a ticket in Zoho Desk, our helpdesk system. Zoho Desk assigns each ticket a number so you and the AES team can track status, history, and any follow-ups in one place. You will get an email confirmation with the ticket number when your request is logged.

How quickly we respond

• Working hours: Monday to Friday, 08:00 to 18:00 UK time.
• During working hours: we respond within 5 hours.
• Outside working hours: we respond by 12:00 on the next working day.

Once we have the ticket we let you know how long we expect a fix to take. We aim to resolve most issues within one working day of the initial report. Saturday, Sunday, and UK public holidays do not count as working days.

Planned maintenance

The HUB runs two kinds of maintenance.

• Nightly housekeeping. Every night the HUB runs a silent update to refresh aggregated data and tidy up deleted items. If you log in overnight you may briefly see a System maintenance in progress banner with a predicted completion time (for example, 04:00 UTC). Housekeeping only touches summaries and cleanup, so new plots and files uploaded during the day are available immediately, not held back until morning.
• Significant planned outages. Rare. Where we can, we schedule them outside working hours to limit disruption. For any significant outage the AES team will email affected users in advance.

Supported browsers and devices

The HUB runs in a modern web browser on a laptop or desktop. There is nothing to install. The table below shows what we test against. Older browsers may work with reduced feature support.

Mobile apps are coming. The HUB is web-only for now. Native iPhone and Android apps will arrive in the App Store and Play Store in a future release.

Giving feedback on the manual

Every page in this manual ends with 👍 / 👎 buttons. The button opens a pre-filled email to the team. A thumbs-up tells us what landed well; a thumbs-down tells us what needs work. If your point does not fit a single page, email hubadmin@aessc.co.uk with “Manual feedback” in the subject.

We use feedback to decide what to write next. It is the fastest way to shape the manual.

Where your data lives

• Location. The HUB runs on an ISO27001-certified data centre in Nuremberg, Germany. The servers are reserved to the HUB and sit on a separate internal network.
• Backups. Data is replicated automatically across multiple servers, with a full weekly back-up and twice-daily incremental back-ups.
• Offsite backup. A second copy of the data is held in a geo-redundant data centre in Zurich, Switzerland. Everything is encrypted both in transit and at rest.
• Encryption. All data is encrypted using Advanced Encryption Standards (AES-256 in counter mode, with Poly1305-AES for authentication).
• ISO27001. AES Sustainability Consultants does not hold ISO27001 directly, but the data centre that holds the data is certified to it.
• Uptime target. The HUB is engineered to a 99.5% monthly uptime target.
• Recovery targets. For infrastructure incidents, the HUB is typically back within 4 hours. In a full disaster-recovery scenario, restoration may take up to 24 hours.
• Competitive neutrality. Multiple energy-assessor firms share the HUB platform, including direct competitors. Each organisation has its own stand-alone domain, so one tenant cannot see another’s data. The AES support team cannot access the full detail of your data, such as the raw XML job files, without your explicit consent, and that access is strictly time-bound.

What personal data we hold

We hold the information tied to your user account: your name, job role, and email address. Optionally you can add a photograph, a mobile number, and a digital signature to enable digital BREL signing. All of this is encrypted on the same basis as the rest of your data.

We use it for two things only:

• An audit trail, so we can show where a piece of information or a file came from.
• To communicate with you about the service (for example, a planned outage).

We do not use your personal data for marketing.

Who builds and runs the HUB. The HUB is developed and maintained by Burg Eins GmbH, AES’s software partner. Your personal data is shared with Burg Eins solely to run and maintain the HUB.

How long data is kept

All data is retained for 15 years following completion of the property the data relates to.

Asking for your data back

You can request a data extraction at any time. The service is free of charge within 12 months of the termination of your contract. After 12 months, a fee applies. Email hubadmin@aessc.co.uk with “Data extraction request” in the subject to start one.

For day-to-day data exports (a single report to Excel, for example), use the XLSX button inside a report. See Drawing a report.

What next

• Before you start
• Your dashboard
• Drawing a report

Feedback

Was this page helpful?

When to use this

Data by Site is the overview dashboard for the tier you launch from, a one-row-per-job summary of everything happening underneath. Use it whenever you want to step back from the per-plot detail and answer planning-and-status questions:

• How many jobs are running under this region?
• How many plots does each site cover?
• How far through is each job, 5% (just started), 90% (almost wrapping up), 99% (the last few plots)?
• Which Building Regulations band is each job sitting on?

Use a plot-level report instead when you want the technical detail behind those jobs.

A note on Percentage Completion. A job’s completion figure is driven by the EPC Lodgement Date. A plot only counts towards completion once its EPC has been uploaded. Two situations to watch for:

• A job stuck at 99% for months when you expected it to wrap up, the most likely cause is one or more plots missing their EPC upload. Worth chasing the assessor.
• A job reading 100% when the site is clearly only part-built, most often seen during the transition onto the HUB, when assessors first upload only their completed plots and have not yet caught up with the not-yet-finished design plots. The figure self-corrects once the full dataset is uploaded.

Data upload is the assessor’s responsibility, not AES’s. AES provides the platform; the assessors upload the data. If you spot incomplete uploads or missing sites, your first contact is your assessor. For technical issues with the platform itself, email hubadmin@aessc.co.uk.

Where Data by Site is available

Data by Site appears in the Analytics dropdown at Tiers 1 to 4: Developer, Division, Region, and Site. It is hidden at Tier 5 (Job) because a job is already a single Data by Site row, there is nothing to summarise. See Drawing a report for how to launch it from any tier.

What you see in the table

Twelve columns, one row per job under the tier you launched from.

There is no plot-level data on this report. To drill into the plots inside any of these jobs, click the job number in the Jobs list or run a plot-level report scoped to that job.

How the rows are aggregated for a developer

A developer running Data by Site sees every job in their portfolio beneath the tier they launched from, regardless of which energy assessor delivered it. If a developer has bought licences for several assessor firms (for example AES, AWE, FES, and JSP), Data by Site combines all four assessors’ jobs for that developer into one table.

The view stops at the developer’s own boundary. Another developer’s data never appears, even if both developers happen to use the same assessor firm. See Where your data lives for the full data-isolation model.

Tips

• Use Data by Site to plan, not to analyse. It is a planning view: what is happening, how many plots, where are we on completion. The technical detail lives in the plot-level reports.
• Sort the export by Job Status or by Percentage Completion to see what is finishing soonest, or by CML Date to see practical-completion targets.
• Empty tier columns are correct, not missing data. A small developer with only Tier 1 will have blank Division, Region, and Site cells on every row.

What next

• Reports summary
• Drawing a report
• Adjusting filters
• Shared middle columns

Feedback

Was this page helpful?

How to read this page

Each column is described once with three things:

• What it is — the underlying data point in plain English.
• Unit — what the cell value is measured in.
• Where it appears — which reports carry the column.

The descriptions below are enough to read the report. For the deep SAP / HEM derivation behind any column, contact the AES support team, see Getting help and giving feedback.

TFA, Total Floor Area

• What it is — the total internal floor area of the dwelling, in square metres.
• Unit — m².
• Where it appears — Energy, M&E Pipeline, PV Pipeline, Fabric Pipeline, NextGen EUI.

TFA is the denominator for any per-area metric (kWh/m², kgCO₂/m²/year). Used widely in the energy and EUI reports.

Actual vs notional building

Every SAP calculation runs in parallel for two buildings: the actual dwelling as designed and built, and a regulation-defined notional dwelling. The notional dwelling is the yardstick, the actual must beat it on each compliance metric for the dwelling to pass Building Regulations.

Performance summary cluster (Completions + NextGen EUI)

These six columns are the headline EPC and air-test numbers that appear at the top of the Completions Report and again as a summary block on the NextGen EUI Report.

Main Heating System 1 and 2 (M&E Pipeline + NextGen EUI)

The HUB models up to two main heating systems per plot. MHS1 is the primary system. MHS2 is the secondary system on plots that have one, typically a log burner or similar alongside a primary boiler or heat pump. Each system carries the same four-column block.

Energy DER PV (Energy Report + PV Pipeline)

• What it is — the contribution of the on-plot PV array to the dwelling’s DER calculation. This is the negative emissions saving in kWh-equivalent terms that PV brings to the SAP balance.
• Unit — kWh/year, rounded to 4 decimal places. Note the value is shown as a positive number even though the underlying SAP figure is negative (PV is a saving).
• Where it appears — Energy Report, PV Pipeline Report.

What next

• Reports summary
• Data by Site
• Completions Report
• Energy Report
• M&E Pipeline Report
• PV Pipeline Report
• Fabric Pipeline Report
• NextGen EUI Report

Feedback

Was this page helpful?

When to use this

The Completions Report is designed and optimised for completed plots, it gives you the headline overview most often needed for reporting, audit, and handover. It pulls together each plot’s as-built EPC data, air-test results, and pass margins against the regulatory targets in one row.

The report is not restricted to completed plots, it works for any plot, but the columns it carries are most meaningful once a plot has been lodged on the EPC register and air-tested.

Typical questions it answers:

• Is this plot passing the three Building Regulations comparisons (DER vs TER, DPER vs TPER, DFEE vs TFEE)?
• What air-test result did this plot achieve, and how does it compare with design?
• What SAP rating and emissions figure are recorded on the as-built EPC?
• Across the development, how many plots are passing comfortably and how many are passing by the skin of their teeth?

Structure

• Static front and rear — see Reports summary for the columns shared with every plot-level report.
• Shared middle — six performance columns also appear on the NextGen EUI Report. Documented once in Shared middle columns: DER, TER, AAP, SAP Rating, PV kWh, PV kWp.
• Unique middle (16 cols) — described below.

Address and location

The plot’s full lodgement address. Three columns:

• Address — the street address line.
• Town — the town or city.
• Postcode — the lodged postcode.

These appear on the EPC certificate when the plot is lodged on the register.

Building information

Four columns describing the dwelling and its compliance band.

• Building Reg. — the Part L band the plot was assessed under (Part L 2010, 2013, 2021, FHS). See Adjusting filters for how the bands map to England, Wales, and Scotland.
• Floor Area — the lodged floor area in m². For most reports the equivalent number is TFA (Total Floor Area, see Shared middle columns). On the Completions Report it is named Floor Area for parity with EPC register wording.
• Environmental Rating — the EPC’s environmental impact rating (similar A to G band as the SAP rating but emissions-led).
• EPC CO2 Emissions — the emissions figure as printed on the EPC, in kgCO₂/year.

Performance summary (Completions-only)

The remaining nine columns are the calculated performance numbers Completions exposes on top of the shared cluster. They are grouped by what they tell you.

Air pressure (1 col):

• DAP — Design Air Pressure. The design SAP figure for air permeability in m³/h·m² @ 50 Pa. DAP pairs with AAP (Actual Air Pressure, see Shared middle columns) as the design vs measured comparison. Pass criterion: AAP ≤ DAP.

Heat-loss parameter (1 col):

• HLP — Heat Loss Parameter. The dwelling’s heat loss per unit floor area in W/m²·K. Lower is better.

Carbon emissions — DER vs TER comparison (3 cols):

• DER — Dwelling Emission Rate, in kgCO₂/m²/year. The dwelling’s modelled CO₂ output. Full definition in Shared middle columns.
• TER — Target Emission Rate, in kgCO₂/m²/year. The regulatory CO₂ target. Full definition in Shared middle columns.
• DER TER %-impr. — the percentage by which DER beats TER. Positive means a pass with that margin.

Primary energy — DPER vs TPER comparison (3 cols):

• DPER — Dwelling Primary Energy Rate, in kWh/m²/year. The dwelling’s modelled primary energy demand.
• TPER — Target Primary Energy Rate, in kWh/m²/year. The regulatory primary-energy target.
• DPER TPER %-impr. — the percentage by which DPER beats TPER. Same shape as the carbon comparison above, but measured in primary energy rather than carbon.

Fabric energy efficiency (3 cols):

• DFEE — Dwelling Fabric Energy Efficiency, the modelled fabric performance.
• TFEE — Target Fabric Energy Efficiency, the regulatory target.
• DFEE TFEE %-impr. — the percentage by which DFEE beats TFEE.

DFEE / TFEE are how the dwelling’s fabric (walls, roof, windows, floors) is judged on its own merits, separate from the heating system’s contribution.

Tips

• Read the three %-impr. columns first for a quick at-a-glance pass mark across the three lenses (CO₂, primary energy, fabric).
• Pair DAP with AAP for the air-test result. AAP without DAP is meaningless; DAP without AAP means the plot has not been air-tested yet.
• Floor Area vs TFA are typically the same number on a completed plot. If they differ, treat the SAP-side TFA as the source of truth.

What next

• Reports summary
• Shared middle columns
• NextGen EUI Report, the closest sibling, shares the headline performance cluster
• The plot page, for the same data viewed at a single-plot level

Feedback

Was this page helpful?

When to use this

Use the Energy Report when you need to see where the energy goes in a dwelling, broken down by end use. The report is used at two points in a plot’s lifecycle:

• At design stage, it shows the modelled demand for the dwelling, how much heating, hot water, lighting, pumps and fans, and cooling the design will require. Useful for design iterations: spotting which end use dominates, sense-checking heating-system sizing against demand, and seeing how PV will offset the load.
• Post-completion, the same report re-checks the as-built figures against the original design demand, confirming the dwelling is performing as expected.

Typical questions it answers:

• Which end use dominates the dwelling’s energy demand?
• Where is the dwelling beating or missing the regulatory target?
• How much PV is offsetting demand vs being exported?

It is the natural companion to the M&E Pipeline Report and the PV Pipeline Report, they describe the systems, this one tells you what the systems are using in modelled energy terms.

Structure

• Static front and rear — see Reports summary.
• Shared middle — TFA and Energy DER PV are documented in Shared middle columns.
• Unique middle — three logical blocks: Actual (before losses), DER components (after losses, modelled), TER components (after losses, target).

A small reading note: the header kWh/m² appears more than once in this report. Each instance is the per-area version of the column immediately before it. The header will become more specific in a future release.

Why each end-use figure appears twice

Space heating and hot water demand are reported in two places on this report, once as the actual demand of the dwelling (before any system losses), and again inside the DER and TER blocks as the delivered energy (after the heating system’s losses are applied). Both figures matter for different reasons.

The actual demand is what the dwelling fabric and the occupants ask for: the heat the building needs to keep warm, the hot water the household consumes. It is independent of the heating system. The delivered figure is what the heating system has to put in to meet that demand, accounting for how efficiently the system converts fuel or electricity into heat.

A worked example for a 5,000 kWh actual space-heating demand:

• A gas boiler at 96% efficiency needs to put in 5,000 ÷ 0.96 = 5,208 kWh of fuel, the extra 208 kWh is lost up the flue. The DER figure will sit a little above the actual.
• A heat pump with a COP of 3 needs to put in 5,000 ÷ 3 = 1,667 kWh of electricity, one unit of electricity moves three units of heat. The DER figure will sit well below the actual.

Showing both numbers makes the underlying demand directly comparable across heating systems, while the DER and TER figures show what each system has to deliver.

Actual energy demand, before losses (4 cols)

The first block is the dwelling’s actual demand, before any heating-system losses.

• Energy Space Heating Actual — annual space-heating demand in kWh/year.
• kWh/m² — the same figure divided by TFA (m²).
• Energy Water Heating Actual — annual hot-water demand in kWh/year.
• kWh/m² — the same figure divided by TFA (m²).

These two end uses are the largest contributors to a typical dwelling’s demand and are reported first.

DER components, after losses (10 cols)

The middle block is the DER (Dwelling Emission Rate) breakdown, the modelled delivered energy by source, after each system’s efficiency losses are applied.

Space heating sub-totals (3 cols):

• MHS1 DER Space Heating — energy from the primary main heating system.
• MHS2 DER Space Heating — energy from the secondary main heating system, where present.
• SHS DER Space Heating — energy from the secondary heating system (e.g. a log burner alongside the main heating).

These three sum into the dwelling’s total space-heating demand.

End-use components (5 cols):

• Energy DER Water Heating — annual hot-water energy.
• Energy DER Space Cooling — annual cooling energy.
• Energy DER Pumps & Fans — energy used by circulation pumps and ventilation fans.
• Energy DER Lighting — fixed lighting energy.
• Energy DER PV — the on-plot PV contribution. See Shared middle columns for the full definition.

Totals (2 cols):

• Total Delivered Energy — the DER total in kWh/year.
• kWh/m² — that total per TFA.

TER components, after losses, target (9 cols)

The third block mirrors the DER block but with the regulatory target figures (the notional dwelling). Same after-losses framing as DER. One fewer column because there is no MHS2 row at the TER side.

Space heating sub-totals (2 cols):

• MHS1 TER Space Heating
• SHS TER Space Heating

End-use components (5 cols):

• Energy TER Water Heating
• Energy TER Space Cooling
• Energy TER Pumps & Fans
• Energy TER Lighting
• Energy TER PV

Totals (2 cols):

• Total Delivered Energy — the TER total.
• kWh/m² — that total per TFA.

Tips

• Read DER vs TER as a pair. A passing dwelling shows DER total ≤ TER total. Compare the per-end-use rows to find where the gain or shortfall sits.
• Negative or zero PV is normal where a plot has no PV array. The DER PV column is taken as a positive number even though SAP treats PV as a negative contribution to the rate, see Shared middle columns.
• Use TFA from the shared block as the consistent denominator if you want to recalculate per-area values.

What next

• Reports summary
• Shared middle columns
• PV Pipeline Report, for the systems behind Energy DER PV
• M&E Pipeline Report, for the systems behind the heating end uses
• NextGen EUI Report, for end-use intensity in a different format

Feedback

Was this page helpful?

When to use this

Use the M&E Report when you need to know what is installed in the dwelling, not just how much energy it uses. The report can be used heavily across two scenarios:

• For plots already finished, you see what is actually installed on each plot, useful for as-built verification, warranty handover, and answering procurement queries after the fact.
• For plots still in the pipeline (provided the housebuilder has entered the CML date), set the CML date filter to +3 months and the report tells you how many boilers, cylinders, WWHR units, or PV systems you need across the next quarter. Break the result down per region or per site to scope procurement.

Typical questions it answers:

• Which boilers, heat pumps, and cylinders are specified across this site?
• What ventilation strategy is in use?
• How does the hot-water spec vary plot to plot?
• Are the controls and emitters compatible with the heating type?

Structure

• Static front and rear — see Reports summary.
• Shared middle — TFA plus the MHS1 and MHS2 four-column blocks (Fuel / Type / Manufacturer / Model) are in Shared middle columns.
• Unique middle — described below by sub-block.

Main Heating System 1, extra detail (5 cols)

After the shared MHS1 block, the M&E report adds the controls and emitter detail.

• Emitters — radiators, underfloor, fan coils, or a mix. See Adjusting filters for the full emitter taxonomy.
• Flow Temperature — design flow temperature (°C). Lower flow temperatures are typical for heat-pump systems, higher for boilers.
• Controls — the heating-control category (e.g. weather compensator, programmer + room stat).
• PCDF Heating Controls — the PCDF-registered controls product, where present.
• PCDF Compensator — the PCDF-registered compensator product, where present.

Hot water and cylinder (9 cols)

Everything about how the dwelling makes and stores hot water.

• Water Heating — the hot-water source (combi, separate cylinder, system boiler with cylinder, etc.).
• Storage Type — the cylinder type if any (vented, unvented, thermal store, none).
• Cylinder Volume (L) — capacity in litres.
• Cylinder Measured Heat Loss (kWh/24hrs) — the standing heat loss test value.
• Cylinder Heat Transfer Area — coil contact area in m², matters for cylinder-to-heat-pump pairings.
• Time Control — type of cylinder time control.
• Cylinder Stat — type of cylinder thermostat.
• Cylinder in heated space — whether the cylinder sits inside the heated envelope.
• Pipework insulation — the insulation specification on the primary pipework.

Main Heating System 2, extra detail

The MHS2 four-column block (Fuel / Type / Manufacturer / Model) is in Shared middle columns. M&E does not add MHS2-specific detail beyond that.

Communal and cooling (2 cols)

• Communal Heating — flag for plots on a community / district heating system.
• SAP Plot Cooling — the dwelling’s space-cooling provision, in kWh/year. Most UK dwellings show zero.

Ventilation (5 cols)

• Wet Rooms — the count of rooms with extract requirements (kitchen excluded). See the kitchen-extract rules in Adjusting filters.
• Ventilation System — the system type (PIV, Intermittent, dMEV, cMEV, MVHR, Other).
• Ventilation Manufacturer — the manufacturer name.
• Ventilation System Name — the model name.
• Duct Type — rigid or flexible duct, where applicable.

Manufacturer and System Name follow the same source rules as MHS1. PCDB-registered units pull automatically; non-PCDB units rely on the assessor’s manual entry in SAP, otherwise the cells stay blank. See the MHS1 section in Shared middle columns for the three SAP entry modes.

Showers and waste-water heat recovery (10 cols)

Part L 2021 only. Showers and WWHR are captured for Part L 2021 plots. Earlier regs (2009/2013) do not populate these columns.

The HUB models up to three showers per plot. Each shower carries the same three-column block:

• Shower Type N — electric, mixer, or none.
• Shower Description N — the shower category (low-flow, regular, etc.).
• Flow rate (l/s) OR Rated power (kW) N — flow rate for mixers, rated power for electric.

Three sets of Shower Type / Description / Flow rate (showers 1, 2, 3) make up nine columns. The tenth is:

• WWHR Model 1 — the Waste Water Heat Recovery model, where one is fitted.

Tips

• Pair MHS1 with the controls and emitter detail to sanity-check the system. A heat pump on radiators with a high flow temperature is a flag for review.
• Pipework insulation and Cylinder Heat Loss matter most for plots with a stored cylinder, combi systems will show blanks here.
• Flow rate column header is long but precise. It carries flow rate for mixer showers and rated power for electric showers in the same cell, so the unit changes by row.

What next

• Reports summary
• Shared middle columns
• Energy Report, for the energy figures behind these systems
• NextGen EUI Report, for the same MHS1/MHS2 cluster

Feedback

Was this page helpful?

When to use this

Use the PV Pipeline Report when you need to know what solar is installed or planned on each plot. The report can be used heavily across two scenarios:

• For plots already finished, you see what is actually installed on each plot, useful for as-built verification (kWp, orientation, elevation, overshading), checking the meter setup, and answering procurement queries after the fact.
• For plots still in the pipeline (provided the housebuilder has entered the CML date), set the CML date filter to +3 months and the report tells you how many kWp of panels and how many smart / export-capable meters you need across the next quarter. Break the result down per region or per site to scope procurement.

Typical questions it answers:

• How many kWp are going to be installed across the next quarter of completions?
• How much of the generated PV is used in the dwelling vs exported to the grid?
• Are the arrays oriented and tilted to design intent?

Structure

• Static front and rear — see Reports summary.
• Shared middle — TFA and Energy DER PV are documented in Shared middle columns.
• Unique middle — described below by sub-block.

PV Type (1 col)

• PV Type — the kind of PV system (rooftop, building-integrated, ground-mounted, none).

PV Array detail (5 cols per array)

The HUB carries one array block per array installed on the plot. A plot with one array has just one block; a plot with two has two blocks; the report scales as needed. Each array block carries the same five-column set:

• PV Array kWp N — the installed peak capacity of array N. See Shared middle columns for the PV kWp definition; here it is repeated per array.
• PV Array Orientation N — compass orientation in degrees from north.
• PV Installation N — installation method (in-roof, on-roof, etc.).
• PV Array Elevation N — tilt angle from horizontal.
• PV Array Overshading N — overshading category (none, modest, significant, heavy).

For multi-array plots, each subsequent block (* 2, * 3, …) repeats with the same five attributes for that array’s specs.

Energy contribution (3 cols)

The PV report adds two PV-specific energy columns alongside the shared Energy DER PV total.

• Energy DER PV — the total annual generation contributing to DER. See Shared middle columns.
• Energy DER PV Used — the part of the generation used inside the dwelling, in kWh/year.
• Energy DER PV Exported — the part exported to the grid, in kWh/year.

The two split out the headline generation: Used + Exported = Energy DER PV.

Install attributes (5 cols)

The remaining columns describe the metering and tariff setup.

• PV Diverter — whether a diverter is fitted (typically routes excess PV to immersion heating).
• Export Capable Meter — whether the plot has an export-capable meter.
• Connected To Dwelling Electricity Meter — whether the PV is connected to the dwelling’s main meter.
• Electricity Tariff — the tariff type registered against the meter.
• Smart Electricity Meter — whether a smart meter is fitted.

Tips

• The Used vs Exported split is the most actionable PV data. A high export percentage may signal a sizing or scheduling opportunity (e.g. fitting a diverter or recommending a battery).
• Empty array-block columns are correct for plots with fewer arrays than the report’s widest row. Do not flag them as missing data.
• Combine PV with Energy Report to see PV’s contribution to the dwelling’s overall DER and TER.

What next

• Reports summary
• Shared middle columns
• Energy Report, for PV’s contribution to the energy balance
• Completions Report, for PV kWh and PV kWp at the headline level

Feedback

Was this page helpful?

When to use this

Use the Fabric Pipeline Report when you need to know what materials make up the dwelling envelope, for procurement, material take-offs, and design verification. The report can be used heavily across two scenarios:

• For plots already finished, you see what is actually installed across the heated envelope, useful for as-built verification of constructions and U-values, and for retrospective material take-offs.
• For plots still in the pipeline (provided the housebuilder has entered the CML date), set the CML date filter to +3 months and the report tells you the m² of blockwork (broken down by type, aerated, lightweight aggregate, dense, timber frame, etc.), the count and m² of windows and doors, and the wall / roof / floor element areas you need across the next quarter. Break the result down per region or per site to scope procurement.

Read the m² figures with two caveats in mind. SAP measures dimensions on the inside of the dwelling, so element areas can undercount external corners and overcount internal corners. SAP also only assesses the heated envelope, there is no data on the cold roof above a plane ceiling, no roof tile counts, no garage walls, nothing outside the warm shell. For materials sitting outside the heated envelope, take-offs must come from the architect’s drawings, not from this report.

Typical questions it answers:

• What U-values are being delivered across the development?
• Which wall types are specified across this site, and what Net Area do they cover?
• How does Plot A’s fabric differ from Plot B’s?
• How many m² of blockwork do we need across the next quarter of completions, broken down by type?

Structure

• Static front and rear — see Reports summary.
• No shared middle. Fabric does not share its middle columns with any other report.
• Middle — element groupings described below.

How a Fabric grouping works

Every fabric element follows the same pattern: each element type can have multiple instances per plot, and each instance carries the same fixed set of attributes. The instance count varies by element (most plots will not use every available slot).

For example, a plot with three different external wall constructions will populate External Wall 1, External Wall 2, and External Wall 3, each with the same attribute set, and leave External Wall 4 blank.

The element groupings

The Fabric report covers the categories of building element listed below. The number of instances of each element is set by the SAP file, if a plot has six external wall constructions, you will see External Wall 1 through External Wall 6, each with the full attribute set; if it has one, the others sit blank. The total column count therefore varies plot to plot and report to report.

Walls, roofs, floors, and windows carry the most variation because a plot will commonly have several distinct constructions of each (for example, a typical house often has three external wall types depending on which face, and several windows in different rooms). Doors are simpler.

Tips

• Sort by U-value within an element type to find the worst-performing parts of the envelope first.
• Compare Gross vs Net Area on External Walls to sanity-check the openings tally, Net Area is what carries the U-value loss; Gross Area is the full wall.
• Empty instance slots are correct, not missing data. A plot using two wall types will have External Wall 3 and External Wall 4 entirely blank.
• Open Fabric in Excel and freeze the static front columns (Pane Freeze at the first non-static column), without that, scrolling through the many element columns loses the row identity.

What next

• Reports summary
• Shared middle columns
• Energy Report, for the energy implications of the fabric performance
• Completions Report, for DFEE and TFEE, the fabric performance summary metrics

Feedback

Was this page helpful?

When to use this

Use the NextGen EUI Report for analytics and benchmarking, when you want a single, clean view of each plot’s Energy Use Intensity (EUI) and the end-use breakdown that sits behind it. Typical questions it answers:

• What EUI is this development achieving, and how does it compare with industry targets such as LETI’s 35 kWh/m²/year for new homes?
• How does each end use (heating, hot water, lighting, pumps and fans, cooling) contribute to the total?
• Where does this plot sit on EUI compared with similar plots elsewhere in the development?
• Is this dwelling on track for Net Zero or Future Homes Standard reporting?

NextGen sits one step beyond Energy: it expresses energy as intensity per area and adds regulated vs total context.

Regulated vs unregulated energy

The HUB pulls all regulated energy values directly from SAP, that is heating, hot water, lighting, pumps and fans, and cooling. Regulated energy is everything that Building Regulations consider when calculating compliance.

Unregulated energy is everything else the household consumes, white goods, plug-in appliances, cookers, IT equipment, EV charging in some scenarios. Building Regulations do not test or limit unregulated energy, but it forms a significant part of a dwelling’s true Energy Use Intensity. The HUB calculates the unregulated component using established external methodologies:

• LETI (London Energy Transformation Initiative), an industry group whose Climate Emergency Design Guide sets EUI targets for new buildings. For new homes, LETI targets a total EUI of 35 kWh/m²/year and a separate space-heating demand of 15 kWh/m²/year. The 35 figure is regulated plus unregulated energy, the dwelling’s full operational energy use, measured against Gross Internal Area (GIA) and excluding the contribution of any on-site renewable generation. For the purposes of this manual you can treat GIA (used by LETI) and TFA (used by SAP and the HUB) as the same number: both measure the heated internal floor area.
• PHPP (Passive House Planning Package), the calculation tool behind Passivhaus and EnerPHit design. PHPP is the standard way to model unregulated energy at design stage and is accepted by LETI as a route to its EUI targets.

When the unregulated portion is missing, the Total Energy column shows the suffix “(Incomplete)”. The cause is almost always that the developer has not yet supplied the fit-out specification, what white goods will be installed, what plug-load assumptions apply, etc. Once that information lands, the suffix drops and the total becomes the dwelling’s complete EUI.

Structure

• Static front and rear — see Reports summary.
• Shared middle — NextGen carries the most shared columns of any report. The headline performance cluster (DER, TER, AAP, SAP Rating, PV kWp, PV kWh) is shared with Completions; the MHS1 and MHS2 four-column blocks are shared with M&E. All documented once in Shared middle columns.
• Unique middle — sixteen columns described below.

Design context (4 cols)

NextGen leads its middle with two design-context columns sitting just before the descriptor block, plus the EI Rating sibling to SAP Rating, plus a SAP-internal box reference.

• Construction — the dwelling’s headline construction category (e.g. masonry, timber frame, SIPs).
• Form Factor — the ratio of envelope area to floor area, a key heat-loss indicator. Lower form factor means a more compact dwelling.
• EI Rating — Environmental Impact Rating. The CO₂-led equivalent of the SAP Rating, also displayed as a number plus letter band.
• BOX 99 — the dwelling’s heating demand before losses — the demand the fabric and ventilation actually need, before the heating system’s efficiency or COP is applied. Same definition as the Actual energy demand block in the Energy Report; see that page for the worked example.

Ventilation (4 cols)

NextGen reports the ventilation system the same way as M&E, plus the fan count.

• Ventilation System Type — PIV, Intermittent, dMEV, cMEV, MVHR, Other.
• Ventilation System Manufacturer — the manufacturer name.
• Ventilation System Model — the model name.
• Number of Fans installed — the aggregate fan count for the dwelling. The kitchen fan counts as a separate fan only for cMEV and MVHR systems.

End-use energy intensity (5 cols)

This is where NextGen earns its name, the dwelling’s end-use energy by category, in kWh/year terms feeding the EUI total.

• Space Heating — the combined delivered heating demand across MHS1, MHS2, and any secondary heating.
• Hot Water — annual hot-water energy.
• Pumps and Fans — energy used by circulation pumps and ventilation fans.
• Lighting — fixed lighting energy.
• Cooling — annual cooling energy. Most UK dwellings show zero.

The order matches the SAP design output, so you can read the NextGen end-use block alongside a SAP printout in the same sequence.

Totals and EUI (3 cols)

The closing block of the unique middle is the totals.

• Regulated Energy (SAP Section 12) — the regulated total as printed in SAP Section 12. See Regulated vs unregulated energy above for what counts as regulated.
• Total Energy (Incomplete) — the dwelling’s total annual energy use, regulated plus unregulated. The “(Incomplete)” suffix means the unregulated portion has not yet been calculated — usually because the developer has not supplied the fit-out specification. Once supplied, the suffix drops. See Regulated vs unregulated energy above.
• Total Energy per m² — the EUI itself, in kWh/m²/year.

Tips

• Read EUI (Total Energy per m²) as the headline number. Everything else on this report supports that figure.
• Form Factor sits at the start of the middle because it is the strongest single predictor of fabric heat loss. Use it as a quick benchmark when comparing plots.
• Total Energy is currently flagged Incomplete until unregulated loads are added. Treat the Regulated Energy figure as the firm number for now.
• For the systems behind the heating end-uses, combine NextGen with the M&E Pipeline Report which carries the same MHS1 and MHS2 cluster.

What next

• Reports summary
• Shared middle columns
• Completions Report, shares the headline performance cluster
• Energy Report, the absolute energy view alongside this intensity view
• M&E Pipeline Report, for the systems behind the end-uses

Feedback

Was this page helpful?

Before you start

• You must be signed in to the HUB.
• You must have a role that grants the view roles permission. Without it, Roles does not appear in your cogwheel menu.
• Only AES HUB Portal Admin can add, edit, duplicate, or delete roles. If you have any other admin role, the list is read-only.

Open the Roles list

1. Click the cogwheel in the top bar.

   

   The Manage menu opens with four entries: Jobs, Clients, Users, Roles.

2. Click Roles.

   

   The Roles list opens. Each row is one role.

What you see

• Name. The role label, followed by a permission count in the form (n/60). A role tagged (10/60) grants 10 of the 60 possible permissions in the HUB. The higher the number, the broader the role.
• Status. Active roles can be assigned to users. Roles no longer needed can be set inactive.
• Actions. When your role permits it, each row shows Edit, Duplicate, and Delete. If your role does not, the column is empty.
• + Role. A button top right, visible only when your role permits role creation.
• Status filter. Top left of the list. Defaults to All. Switch to view only active or only inactive roles.
• Search. Top right. Type-ahead filter on the role name.
• Global members. Red button near the top of the page. Opens the Global members view: a list of users assigned at the global scope, the level that sits above Tier 1 (Developer). A global assignment grants access across every Tier 1 the customer holds in one stroke, instead of repeating the same assignment on each Tier 1 separately. This is a shortcut into a slice of User assignments, where the full mechanic of user + role + scope is documented.

Note. What you see on this page is itself shaped by your role. An admin without role-management permission sees only the list. An admin with full role-management permission also sees + Role, Edit, Duplicate, and Delete. The page is the worked example of role-driven visibility.

How roles are managed

• Predefined. AES maintains the master role catalogue. Out of the box your HUB ships with the roles AES considers standard for your subscription.
• Customised together. AES works with each customer to define and fine-tune roles to match how the customer’s teams actually work. New role requests go to AES support.
• Add, edit, duplicate, delete. Only AES HUB Portal Admin can create a role, change a role’s permissions, duplicate one as the starting point for a new variant, or delete a role outright.
• Active or inactive. Roles you no longer use can be set inactive without being deleted, so they stay in the list for reference.

Note. Permissions are about what a user can do. They sit alongside the where dimension covered in Understanding the Tier Structure. A user’s effective access is the intersection of the two.

Tips

• Ask AES support before requesting a brand-new role. Often the permission you need is already in an existing role and a quick reassignment is faster than a new role build.
• If Roles is missing from your cogwheel menu, you do not have the view-roles permission. Speak to your portal admin.

What next

• Users, the master list of every user on the HUB
• User groups, how users are bundled together for assignment
• User assignments, where roles, groups, and users are tied to tiers and jobs
• Understanding the Tier Structure, the where dimension that pairs with role-based what
• Getting help and giving feedback, to request a new role or amendment

Feedback

Was this page helpful?

Before you start

• You must be signed in to the HUB.
• You must have a role that grants the view users permission. Without it, Users does not appear in your cogwheel menu.
• User management (create, edit, deactivate, reactivate) is held by AES HUB Portal Admin by default. The same actions are available to any client user whose role grants the corresponding permission, typically a client admin set up during onboarding.

Open the User List

1. Click the cogwheel in the top bar.

   

   The Manage menu opens. Click Users.

2. The User Management page opens. Scroll past User Groups at the top to reach the User List section.

   

   Each section can be collapsed by clicking the small − next to its heading.

What you see

• User chip. Two-letter coloured tile in front of each name. The two letters are the user’s initials, the colour is inherited from their user group. Ungrouped users get a default chip colour.
• Name. Click the name to open the user detail page.
• Group. The group the user belongs to, or ungrouped.
• Status. One of four states. See the User statuses and actions table further down this page.
• Actions. Edit is always shown when your role permits user editing. The second action depends on the user’s status.
• Status filter. Top left. Defaults to All. Filter to one status to focus on, for example, only Invited users to chase first-time sign-ins.
• Group filter. Top left. Defaults to All. Filter the list to a single group.
• Search. Type-ahead filter on the user’s name.
• + User. Top right, visible only when your role permits user creation. Opens the Add New User form.
• Display modes. Three icons top right of the section, list, columns, and tiles. Switch to suit your preference, the data is the same in each.
• Page size. Toggle between 10 users per page and All.
• Pagination. When the list runs over a page, page links appear at the bottom with a 1 to 10 of n users counter.

User statuses and actions

A user moves through up to four states in their lifetime on the HUB. The Actions column shifts to match.

Note. Users are never deleted. A user may have uploaded photos in SiteView or FireView, signed BREL paperwork, or carry historical notifications. Deactivation locks the account without losing any of that history. If access is needed again, click Reactivate and the user’s prior assignments resume.

Create a new user

Provided your role grants the create-users permission, click + User at the top of the User List to open the Add New User form.

Fill in the form:

• Name. Required.
• Surname. Required.
• E-mail. Required. This is the address the invitation, password resets, and 6-digit PIN emails will be sent to.
• User Group. Optional dropdown. Pick a group, or leave unset for ungrouped.
• Landline Phone Number. Optional.
• Mobile Phone Number. Optional.

Click Create Account to save, or Cancel to discard.

Important. Creating an account does not send an invitation email. The new user lands on the User List with status Created. To actually invite them, find the row and click Send Invite in the Actions column. This two-step design lets you stage several accounts and invite them in a controlled wave.

Edit a user

Click a user’s name on the User List, or Edit in the Actions column, to open the user detail page.

The detail page shows every field on the user record:

• Name, Surname, E-mail. The required identifying fields.
• Initials. Auto-generated from the first letters of Name and Surname. The chip on the User List uses these letters.
• User group. The group the user belongs to. Edit this field to move the user between groups, or to ungrouped.
• Landline phone number, Mobile phone number. Optional contact fields.

To change anything, click the Edit button at the top of the page. Make your changes and click Save changes, or Cancel to discard.

The Back to user management button returns you to the User Management screen.

See where a user is assigned

The user detail page is the canonical place to see all of a user’s assignments. Scroll to the Assigned Roles section at the bottom of the page.

Each row is one assignment, showing:

• Name. The user themselves (the chip and name repeat for clarity).
• User Status. The user’s overall status (Active, Invited, etc.).
• Role. The role attached to this assignment.
• Source. The scope of the assignment. global means the user holds this role at the level above Tier 1, covering every Tier 1 in your tree. A tier name (for example a developer name) means the assignment is scoped to that tier and everything beneath it.

A user with multiple assignments shows multiple rows. The user’s effective permissions on any tier are the union of every role that applies to that scope.

Note. Assignments are read-only on this page. To add, edit, or remove an assignment, go to User assignments. The User account view is the user-up perspective (where is this user assigned). The tier views (cogwheel → Clients, then drill down) give the tier-down perspective (which users sit under this tier).

How user accounts are managed

• No deletion, only deactivation. Historical data tied to the user (notifications, photos, signatures) is preserved. Deactivated users keep their record but lose sign-in.
• Two-step onboarding. Create the account first, then send the invite. This lets you batch invitations or hold them until the user is ready.
• Group is set on the user. Group membership lives here, not on the user group page.
• Roles are not set here. Role assignments are managed on User assignments, where the user is tied to a role and a scope.

Tips

• Use the Status filter set to Invited to chase users who have not yet signed in for the first time. Click Resend Invite on stale rows.
• Use the Group filter to bulk-check that everyone in a particular team has been onboarded.
• If Users is missing from your cogwheel menu, your role does not include the view-users permission. Speak to your portal admin.
• A user’s chip colour is a quick visual cue for their group, scan the list for outliers if you suspect someone is on the wrong group.

What next

• Set up your account and sign in for the first time, what the user sees after you click Send Invite
• User groups, the bundles users belong to
• User roles, the permission catalogue
• User assignments, where users, roles, and scope tie together
• Understanding the Tier Structure, the tier-down perspective on assignments
• Getting help and giving feedback, to request a permission change or report an issue

Feedback

Was this page helpful?

Before you start

• You must be signed in to the HUB.
• You must have a role that grants the view groups permission. Without it, Users does not appear in your cogwheel menu.
• Group management (create, edit, delete) is usually held by AES HUB Portal Admin. The permission can be delegated to one or two client admins during onboarding, scaled to the size of the customer.

Open the User Groups list

1. Click the cogwheel in the top bar.

   

   The Manage menu opens. Click Users.

2. The User Management page opens with two collapsible sections: User Groups at the top and User List below.

   

   Each section can be collapsed by clicking the small − next to its heading.

What you see

• Group chip. A two-letter coloured tile in front of each group name. The two letters are auto-generated from the group name (e.g. HU for HUB Admin), the colour is set on the group itself.
• Group Name. The group label. Click the name to open the group detail page.
• Users. Count of users currently in the group.
• Actions. When your role permits it, each row shows Edit. If your role does not, the column is empty.
• + Group. A button top right, visible only when your role permits group creation.
• Search. Type-ahead filter on the group name.

Note. A user inherits their group’s colour on the User List below. That is why every chip on a user row carries the colour of the group the user belongs to. Initials on a user chip are the user’s own initials, not the group’s.

Open a group’s detail page

Click a group name on the User Groups list to open its detail page.

The detail page shows:

• Group colour. The hex value driving every chip in this group.
• User List. The same User List as on the parent page, pre-filtered to this group. Use it to see who is in the group at a glance.
• Back to users. Red button at the top, returns you to the User Management page.

Create a new group

Provided your role grants the create-groups permission, click + Group at the top of the User Groups list to open the New User Group form. If you do not see the + Group button, your role does not allow group creation.

Fill in the two required fields:

• Name. The display label for the group. The two-letter chip is auto-generated from the first two letters of the name.
• Colour. A hexadecimal colour code (e.g. #D66E3F). This drives every chip carrying the group, including every user inside it.

Click Create group to save, or Cancel to discard. The new group appears immediately on the User Groups list.

Edit an existing group

Provided your role grants the edit-groups permission, click Edit on a group row to open the group’s edit form. If the Actions column is empty for that row, your role does not allow group editing.

The form is the same shape as the create form, with the existing values pre-filled:

• Name. Rename the group. Memberships and assignments follow the rename automatically.
• Colour. Change the hex value to recolour every chip in the group, including its users.

Click Save changes to commit, or Cancel to discard.

How users join a group

Group membership is set on the user record, not on the group itself.

1. Open the user card from the User List and click Edit.
2. On the user form, find the User group dropdown.
3. Pick a group, or pick ungrouped to leave the user out of any group.
4. Click Save changes.

The user immediately picks up the new group’s colour on the User List.

How groups are managed

• One per user, or ungrouped. A user belongs to exactly one group, or to none. To split a user across teams, use multiple user roles, not multiple groups.
• Optional but useful. Groups exist to make role assignment quicker. If you only have a handful of users, you can leave them ungrouped and assign roles per user. As the user list grows, groups pay off fast.
• Membership lives on the user. Adding or removing a user from a group is done from the user record, not from the group page.
• Renames are safe. Renaming a group does not break existing assignments or memberships.

Note. Groups themselves do not carry permissions. Permissions live on user roles, and roles are tied to users (and groups) via user assignments.

Tips

• Mirror your real-world teams when naming groups. If you have a Housebuilder team and a Maintenance team, name the groups the same way.
• Pick group colours that are easy to tell apart on screen. The colour shows up everywhere users appear, so a strong contrast helps admins scan the list.
• If Users is missing from your cogwheel menu, you do not have the view-groups permission. Speak to your portal admin.

What next

• Users, the master list of every user on the HUB
• User assignments, where groups, users, and roles are tied to tiers
• User roles, the permission bundles that define what a user can do
• Understanding the Tier Structure, the where dimension that pairs with the what of a role
• Getting help and giving feedback, to request a permission delegation or report an issue

Feedback

Was this page helpful?

Before you start

• You must be signed in to the HUB.
• You must have a role that grants the assign and unassign permissions for the scope you are working at. Without them the + Assignment button and Delete action are hidden.
• Assignment management is held by AES HUB Portal Admin by default. The same actions are available to any client user whose role grants the corresponding permissions, typically a client admin set up during onboarding.

The shape of an assignment

Every assignment is a triple:

• Subject — one or more users, or one or more groups. Mixing a user and a group inside the same assignment is not supported, but you can repeat the modal to assign both.
• Role — exactly one role per assignment. To grant a person two roles at the same scope, run the +Assignment flow twice.
• Scope — global (covers every Tier 1 in your tree) or any specific tier from Tier 1 (Developer) all the way down to Tier 5 (a single Job). The page you launch the modal from sets the scope.

Effective access for a user on a tier is the union of every assignment that applies. Multiple roles overlap and stack, which is exactly the flexibility the system is designed to give.

Where assignments are made

Three entry points, all using the same +Assignment modal and the same list shape. Pick the one that matches the scope of access you want to grant.

1. Global

Open the Roles list (cogwheel → Roles), then click Global members at the top.

The page that opens is called Persons in charge.

Anyone assigned here gains the assigned role across every Tier 1 the customer holds. Use it for portal admins and any role that should follow the user wherever they go in the tree.

2. Any tier

Open the tier detail page (cogwheel → Clients, then drill in until you land on the Developer, Division, Region, or Site you need; see Understanding the Tier Structure for the navigation pattern). Click Members in the header.

The page that opens is called Permission management (prefixed with the tier name).

Anyone assigned here gains the role at this tier and everything below it. Use it for divisional directors at Tier 2, regional directors / admins / analysts at Tier 3, site-level admins at Tier 4, and any role that should be scoped to one branch of the tree.

Important. Assignments are removed where they were created. To remove a row whose Source is global, you must go to the global Persons in charge page and delete it there. To remove a row whose Source is a tier name (e.g. Taylor Wimpey), click the link in the Source column to navigate to that tier and delete from there. The same rule applies at every scope: delete on a job page only removes assignments made at that job.

3. A single job

Open the job page and click Members in the header.

Same name as the tier-level screen, just scoped to one job.

Use it for technical managers, site managers, and any role that needs access to one job only.

---

Add an assignment

The + Assignment button on any of the three screens opens the same three-step modal.

Assign a single person (or several)

1. Step 1, Select type. Click Single person.
2. Step 2, Select person(s). Start typing a name. Pick a user from the dropdown. They appear as a chip below the field. Repeat to add more users to the same assignment.
3. Step 3, Select role. Start typing a role name and pick one from the dropdown. One role per assignment. To grant the same people a second role, run the modal again.
4. Click Assign to commit, or Cancel to discard.

Note. If a person you expect to find does not appear in the typeahead, they may not have accepted their HUB invitation yet. Check the Users list and click Resend Invite if their status is still Invited.

Assign a whole group (or several)

1. Step 1, Select type. Click Group.
2. Step 2, Select user group(s). Start typing a group name. Pick a group from the dropdown. Repeat to add more groups.
3. Step 3, Select role. Pick the single role.
4. Click Assign.

Important. Group membership is captured at the moment you assign. If a new user is added to that group later, they do not automatically inherit existing assignments. Re-run the +Assignment flow when you onboard a user who needs to step into existing group access.

---

What you see on a permissions list

The list shape is the same across global, tier, and job views.

• Name. The user, with their group-coloured chip and initials. A user inherited from a higher scope still shows here.
• User Status. The user’s overall account status (Active, Invited, etc.), see the Users page.
• Role. The role this assignment grants.
• Source. Where the assignment was made. global means it was made on the Persons in charge page and covers every Tier 1. A clickable tier or job name (for example Taylor Wimpey) means it was made at that scope. Click the name to jump to that scope’s permission management.
• Actions. Delete appears only on assignments made at the current scope. Inherited rows have no Delete here, because the assignment lives elsewhere. Follow the Source link to find the scope where Delete is available.

The bottom of the list shows pagination and a counter (11 to 16 of 16 members).

Source and inheritance

Inheritance flows downward through the tree:

• Global assignments appear on every scope (every Tier 1 to Tier 5 row), with Source = global.
• A Tier 1 assignment appears on every Tier 2, Tier 3, Tier 4, and Tier 5 beneath it, with the Tier 1 name in Source.
• A Tier 2 assignment appears on every Tier 3 / 4 / 5 beneath it, and so on down.
• A Job assignment appears only on that one job.

Delete only ever sits on the row at the scope of origin. To remove an inherited row, click the link in Source to navigate to where it was made.

Remove an assignment

Click Delete on the row to unassign. The user (or group) loses the role at this scope and every scope below that inherited from it.

There is no in-place edit. To change a role, delete the existing assignment and create a fresh one with the new role.

Note. Removing a group assignment does not delete the underlying user records or the group itself. It only severs the role link at this scope.

Worked roles by scope

The same +Assignment mechanic supports very different operational profiles. A few examples to anchor the concept:

• Global, Portal Admin. Full HUB access for AES support and senior client admins. One assignment at the global level lights up every Tier 1 and below.
• Tier 1 (Developer), Group Admin. A housebuilder’s central team gets visibility across the developer’s whole portfolio. Use a group assignment so everyone in the central team is granted at once.
• Tier 2 (Division), Divisional Director. Director sees their division and everything below, nothing else.
• Tier 3 (Region), Regional Director / Admin / Analyst. Regional staff see their region only.
• Tier 4 (Site). Site-level admin or analyst.
• Tier 5 (Job), Technical Manager / Site Manager. Single-job access for a project lead. Multiple jobs simply means multiple assignments at Tier 5.

The flexibility comes from layering: a regional analyst with one Tier 3 assignment can be lifted to a divisional analyst with a Tier 2 assignment without anyone touching the Tier 3 record.

Tips

• Start broad, narrow as needed. A global Portal Admin assignment is one click; per-tier assignments multiply. Use the tightest scope that still covers the user’s job.
• Group assignments save effort, but watch the dynamic-membership trap. Onboarding a user into a group does not back-fill them into earlier group assignments. Plan for re-runs.
• The Source column is your debugging tool. When a user has unexpected access, check Source to find the originating scope, navigate there, and Delete to remove.
• Multiple roles at the same scope are fine. Run the modal twice with the same subject and a different role.

What next

• User roles, the catalogue of permissions a role can hold
• Users, the master list of people who can be assigned
• User groups, the bundles you can assign in one shot
• Understanding the Tier Structure, the where dimension you scope assignments to
• The job page, entry point to job-level (Tier 5) assignments
• Getting help and giving feedback, to request permission changes you cannot make yourself

Feedback

Was this page helpful?

Before you start

• You must be signed in to the HUB.
• You must have permission to view the relevant plot through your role and assignment.

The four stages at a glance

The Stage pills on the plot page switch the File List between four canonical sets. The voluntary entries are italicised.

Note. BR(W)EL is one document with regional naming. England calls it BREL (Building Regulations England Lodgement). Wales calls it BRWL (Building Regulations Wales Lodgement). Scotland has no equivalent and nothing is uploaded for Scottish plots in this slot.

Design stage

The pre-construction snapshot. Documents are produced by the energy assessor from the property’s design specification.

• Design SAP PDF. The full SAP calculation printout at the design stage. Shows the Dwelling Emission Rate (DER), Target Emission Rate (TER), Primary Energy figures, Fabric Energy Efficiency figures, and every input that produced them. The first place to look when a plot’s headline numbers need explaining.
• Design SAP PEA. Predicted Energy Assessment. Provides an indicative EPC rating for marketing and pre-completion sales material, before the EPC itself can be lodged. Uses the same calculation engine as the EPC but flagged as predicted.
• Design SAP BR(W)EL. Building Regulations Lodgement report. The compliance evidence statement that goes to Building Control. England files it as a BREL, Wales as a BRWL. Scotland does not use this lodgement model.
• Design SAP XML. The machine-readable SAP file (sap10 schema). The HUB extracts every KPI you see in reports from this file. Assessor-only: XMLs are not synced to housebuilder clones, for competitive neutrality and GDPR.
• Block compliance PDF. Voluntary. See Block compliance below.

Prepare stage

The voluntary in-between stage. AES uses Prepare to capture changes that have come in after the design issue but before the plot is genuinely As Built and ready for EPC lodgement. Typical examples: late address confirmations, revised heating designs, late-arriving PV designs.

The aim is to head off surprises on the day before CML, especially when changes shift KPIs in the wrong direction or threaten compliance.

• As Built SAP PDF (reduced). A reduced-dataset SAP printout reflecting the latest known design state. Enough to extract refreshed KPIs, not a full re-issue.
• As Built SAP XML (reduced). Matching machine-readable file, again assessor-only.

Note. No new PEA or BREL is needed at Prepare. Those are issued at Design and re-issued at As Built.

Testing stage

Compliance evidence from on-site testing. The plot is built but not yet lodged.

• Air Test Certificate. Pressure test result for the plot. Records actual air permeability against the design target. A failed test triggers remedials and a re-test until the target is met.
• MCS Certificate. Microgeneration Certification Scheme certificate. Issued for installed renewable technology (most commonly PV, sometimes heat pumps or solar thermal). Not mandatory on the HUB, but a useful artefact for warranty and customer handover.

As Built stage

The final, lodgement-ready set. This is what the plot looks like once construction is complete and the energy assessment has been signed off.

• As Built SAP PDF. Full SAP calculation printout reflecting the property as constructed. Source of the values that flow through to the EPC.
• As Built BR(W)EL (signed). The signed compliance lodgement report. The (signed) suffix in the file label is the visual cue that the assessor has formally completed it. England uses BREL, Wales uses BRWL, Scotland has no equivalent.
• As Built SAP XML. Machine-readable as-built data. Powers reporting on completed plots. Assessor-only, same competitive-neutrality and GDPR rules as Design and Prepare.
• EPC. Energy Performance Certificate. The public-facing rating document, lodged with the central register (gov.uk in England and Wales, the Scottish EPC Register in Scotland). The EPC Lodgement Date drives the Completed percentage on the Data by Site report.
• Photo Evidence Report (PE Report). A PDF compiled from photographic evidence captured on site. Most commonly generated by AES SiteView, but the HUB accepts a PE Report from any photo evidence platform. Filename prefix PER is the giveaway.
• Block compliance PDF. Voluntary. See Block compliance below.

Block compliance

A Block compliance PDF is the floor-area-weighted compliance calculation for a building that contains more than one dwelling, for example a block of flats or a terrace. Instead of demonstrating compliance plot by plot, the average target rates are calculated across the dwellings using a floor-area weighting.

The document is not mandatory and is not always needed. Upload it where it improves the audit trail.

The HUB has a useful side effect when one is uploaded: it creates a Block and groups the affected plots together. After upload, the Block filter at the top of the Plot List becomes a quick way to see all plots that share a compliance grouping. Only one upload is needed per block, attached to one of the affected plots.

Cross-cutting notes

• XMLs are assessor-only. Design, Prepare, and As Built XMLs do not sync to housebuilder clones. The split keeps competing assessors apart on shared infrastructure and respects GDPR boundaries.
• Regional variants. BREL (England) and BRWL (Wales) are the same document under different regulatory frames. Scotland uses neither and uploads no equivalent.
• Voluntary versus required. Italics in the at-a-glance table mark voluntary documents. Everything else is expected to land in its slot for a plot to be considered complete at that stage.
• Accepted file formats. PDFs and common images (JPG, PNG) only, plus XML at the assessor side. See The plot page for the file preview overlay and how revisions are tabbed.

Tips

• Use the Stage pills on the plot page to flip between sets quickly. Purple = currently viewed stage, red = stage with data, grey = no data.
• If a KPI looks off, open the SAP XML at the relevant stage. The XML is the source of truth for every reported figure.
• Upload a Block compliance PDF early when you have a multi-dwelling building. The Block filter pays back the effort across every later report run.
• Photo Evidence Reports filed PER_*.pdf are searchable by filename in the File List type ahead.

What next

• The plot page, the place files are viewed and downloaded
• Drawing a report, where the XML data feeds the analytics
• Reports summary, the full catalogue of reports
• File sharing, coming soon
• BREL signing, coming soon
• Getting help and giving feedback, to flag a missing or incorrect file

Feedback

Was this page helpful?