One event, one ledger
Organisers and venues read the event boundary, collection progress and accounting on one ledger. Day-to-day venue energy stays in zero-carbon buildings. Offset evidence comes from a qualified channel; this page records the source and whether it is filed.
From the event file to the declaration draft
The MICE path runs as file, boundary, collection, accounting, offset filing and draft. The certification decision stays with the assurance body.
Event file
Register the organiser, venue, dates and event type on one event file.
Boundary and sources
Setup, show days and strike are listed apart. Each source returns to a stage and a role.
Role-based collection
The venue, exhibitors and suppliers file by task, with a trail. Missing figures stay on the list.
Event accounting
Results are listed by stage and source. This page records the structure and does not state a tonne target.
Offset filing
Record the credit source and whether a retirement note is on file. Until it is complete, the status stays in preparation or to-complete.
Declaration draft
Boundary, collection, accounting and offset are arranged as the declaration file structure. The certification decision stays with the assurance body.
File, collection, accounting, offset, draft
Event managers and venues read whether the boundary is clear, collection is complete, and the draft can be matched, on one MICE ledger.
Event file
Organiser, venue, dates and stage scope are fixed first, so later collection and accounting share one method.
Emissions collection
Venue, exhibitors and suppliers file by task. Evidence and returns keep a trail. Missing figures stay on the list.
Event accounting
Setup, show days and strike are listed apart. Results return to a source. This page does not state a tonne target.
Offset process
Credit source and retirement notes are registered. Evidence comes from a qualified channel. Until it is complete, the status stays to-complete.
Declaration draft
Boundary, collection, accounting and offset are arranged as the file structure for internal briefings and filing preparation.
Event boundary, collection progress, declaration draft
Three desks match what an organiser checks day to day. Statuses on the cards are samples.
Event boundary
Setup, show days and strike are listed by stage. Each row returns to a venue or a source.
Collection progress
Venue, exhibitor and supplier tasks stay apart. Gaps and items awaiting review are marked on the list.
Declaration draft
Boundary, collection, accounting and offset are listed apart. Until the offset is complete, the status stays to-complete.
Eight capabilities along the event carbon ledger
From the event file to the declaration draft, work stays with one show. Organisation inventory, the credit ledger and day-to-day venue energy open from the linked products.
Event file and boundary
Register event type and stage scope by organiser, venue and dates, as the shared method for collection and accounting.
Write down which event and which stages are in scope, so later tables can be matched.
- The event file records organiser, operator and venue, and changes remain traceable.
- Setup, show days and strike are registered apart from the venue’s year-round energy.
- A multi-event year starts with one demonstration show. The annual comparison follows after that ledger is clear.
- Organiser
- Venue
- Dates
- Stages
Source list
List transport, energy, materials, waste and catering by stage, and name who files each one.
The list answers which sources this show collects, and who owns each row.
- Each row has a stage and a filing role.
- Factor values are cited from the platform accounting capability. This page does not keep a factor library.
- Sources left out stay on a gap list before strike.
- Transport
- Energy
- Materials
- Waste
Role-based collection
Tasks are generated from sources. The venue, exhibitors and suppliers file and upload evidence.
Who filed, who returned a row, and which column is still empty, stay on one progress list.
- Tasks are assigned by role. Gaps are visible before the deadline.
- Approved rows lock. Returns keep a trail.
- Attendee point rules stay in carbon benefit. This page keeps the event-side collection tasks.
- Tasks
- Filing
- Evidence
- Review
Low-carbon operations list
Waste reduction, material loops and on-site actions are registered as a list, with whether each item has landed.
The list records which arrangements are on file. This page does not state an abatement percentage.
- Each item has a stage and a current status.
- Unfinished items stay to-complete, apart from the accounting result.
- Site control stays in the venue’s specialist system. This page records whether the action is on file.
- Waste
- Materials
- Actions
- Gaps
Exhibitor collaboration
Exhibitors and suppliers file stand materials, build and take-back, as the green-collaboration progress.
Collaboration shows who has filed, and which material still lacks evidence.
- Stand materials and take-back are listed apart from the organiser’s own sources.
- Supplier filings return to the matching exhibitor.
- Scoring notes stay in the event file. This page shows filing status.
- Exhibitors
- Materials
- Take-back
- To complete
Event accounting
Roll up reviewed activity data by stage and source into a traceable ledger.
The event ledger is listed by stage and source, so it can be matched to collection tasks.
- Preview and final accounting are listed apart. Unlocked columns stay to-check.
- The organisation inventory is completed in carbon inventory. This page cites the result after it is inside the event boundary.
- This page records the structure and does not state a tonne target.
- Setup
- Show days
- Strike
- Listed apart
Offset process
Register the credit source proposed for this event, and whether a retirement note is filed.
Until the evidence is complete, the status stays in preparation or to-complete. The certificate comes from a qualified channel.
- The credit ledger and retirement stay in carbon assets. This page cites sources already registered.
- An offset with an unknown source is not marked as filed.
- Until the offset is complete, the declaration file does not use a completed wording.
- Source
- Evidence
- Filed
- To complete
Declaration draft and results
Boundary, collection, accounting and offset are arranged as the declaration and briefing file structure.
The draft aligns the file structure. The certification decision stays with the assurance body.
- The list covers five drafts: boundary, collection, accounting, offset and declaration.
- Missing items are marked on the list before the filing window.
- Public result drafts come from the same event ledger as the three desks.
- File list
- Missing items
- Result draft
Detail ledgers stay where they are
This page takes the event boundary, collection progress and declaration file structure. The products below keep their own ledgers or adjacent work.
Adjacent pages by what the organiser needs next
The product is the event carbon ledger. Industry narrative, venue energy and association operations live on the solution pages.
See whether this show can sit on one ledger
Tell us the organiser, the venue and the dates. We arrange a trial or a demo and say how far the ledger can go.