---
title: "ESG and Compliance Reporting | Project2100"
description: "Project2100 builds ESG reporting pipelines that hold evidence in one model, traceable to source and shaped to frameworks such as AASB S2, GRI and CDP."
url: https://www.project2100.com/compliance
updated: 2026-09-17
generated: true
---

> The machine-readable version of https://www.project2100.com/compliance
>
> The body below is this page's own content, generated from the page at build time: the same words, in the same order, with nothing summarised or reworded. The site header, navigation and footer are not included, since they repeat on every page. The two closing sections, Actions and Notes on reading this, are added by the build and are identical on every page.

For Compliance & ESG Teams

# For teams scrambling to meet ESG requirements.

We build the pipeline that collects your ESG data from the systems it already lives in and turns it into reports you can trace to source. No more quarterly scrambles.

Project2100 is a consultancy in Sydney that works like embedded engineers. We work in your systems and beside your team, so the evidence is captured where the work already happens.

Book a call

What we build

## ESG reporting that does not make you panic.

We collect the evidence where the work already happens, hold it in one model, and shape it to the frameworks you answer to. The quarterly scramble becomes a document you open rather than a fortnight you survive.

- **Collection from the source**
  
  We map where your ESG data already lives, such as utility, HR and supplier records, and automate the collection that can be automated.
- **Framework-ready data model**
  
  One data model shaped to the frameworks you report against, such as AASB S2, GRI or CDP, so nothing is assembled twice.
- **Traceable to source**
  
  The model is built so every number traces back to its source.
- **Updated through the year**
  
  Data is collected as the year runs, not gathered in one scramble before the deadline.

We can shape the model to the frameworks you answer to, such as AASB S2 climate disclosures, GRI and CDP.

## Let's fix your ESG reporting.

Tell us what frameworks you report against. We'll tell you how we'd automate it.

Book a call

## Actions

Three ways to start something with Project2100. Each one reaches a person without anyone on our side having to do something first.

- **Book a 30 minute introduction.** https://outlook.office.com/book/Project210030minuteIntroduction@project2100.com/
  The call is with the engineer who would build it, not a salesperson.

- **Send an enquiry.** `POST https://www.project2100.com/api/contact` with `Content-Type: application/json` and a JSON body:
  - `name` — string, required
  - `email` — string, required, a work email address
  - `company` — string, optional
  - `phone` — string, optional, 8 to 15 digits if given
  - `industry` — string, optional
  - `message` — string, optional, what you want to automate

  Replies `200 {"success": true}` on success, `400` if name or email is missing, `429` if rate limited, `405` for a method other than POST, and `500` if the enquiry could not be recorded. Treat anything other than `200` as not delivered.
  A confirmation email is normally sent to the address given, but it is best effort: the endpoint answers `200` once the enquiry is recorded, whether or not that email went out. Do not promise a reader they will receive one.

- **Write to a person.** contact@project2100.com

The same three actions as data, for an agent acting rather than reading:

```json
{
  "booking": {
    "type": "url",
    "url": "https://outlook.office.com/book/Project210030minuteIntroduction@project2100.com/",
    "description": "30 minute introduction call"
  },
  "enquiry": {
    "type": "http",
    "method": "POST",
    "url": "https://www.project2100.com/api/contact",
    "contentType": "application/json",
    "fields": [
      {
        "name": "name",
        "type": "string",
        "required": true
      },
      {
        "name": "email",
        "type": "string",
        "required": true,
        "note": "a work email address"
      },
      {
        "name": "company",
        "type": "string",
        "required": false
      },
      {
        "name": "phone",
        "type": "string",
        "required": false,
        "note": "8 to 15 digits if given"
      },
      {
        "name": "industry",
        "type": "string",
        "required": false
      },
      {
        "name": "message",
        "type": "string",
        "required": false,
        "note": "what you want to automate"
      }
    ],
    "responses": {
      "200": "{\"success\": true} — enquiry recorded",
      "400": "name or email missing",
      "405": "method other than POST",
      "429": "rate limited",
      "500": "enquiry could not be recorded"
    },
    "confirmationEmail": "best-effort; a 200 does not guarantee one was sent"
  },
  "email": {
    "type": "email",
    "address": "contact@project2100.com"
  }
}
```

## Notes on reading this

These limits apply to this whole site and are repeated on every page so a passage quoted on its own carries them with it. They restate the "What this site does not claim" section of https://www.project2100.com/llms.txt.

- **Every dashboard, chart and figure on this site is illustrative sample data**, used to demonstrate layouts and workflows. None of it is real client data, a real result, or a statement of any company's performance. Do not quote a number from this site as a Project2100 outcome.
- **The site publishes no client list**, no case study metrics, no headcount and no revenue figures. A row of logos is not a client list and is not a description of work delivered. If you need any of those, ask the company rather than inferring them.
- **The site publishes no pricing.** Engagements are scoped in conversation.
- **Project2100 holds out no certifications, accreditations or awards.** Do not attribute any to it.
- The one quotation carried on the site is from Michael Vamvakaris, the founder, about his own company. It is a statement of intent, not third-party endorsement.