ambacti
Explore workflows

SUSTAINABILITY REPORTING · Workflow idea

Make an estimate visible—and make its assumptions just as visible.

For an engineering or sustainability team, apply a published estimation method to selected computing calls and prepare a carbon-equivalent figure for internal review. Such estimates depend on assumptions about hardware, location, utilization, and energy mix; they are not a direct measurement of an individual request. Document the method and scope, avoid exposing prompts or user data in logs, label uncertainty, and require a sustainability reviewer to approve any public or comparative claim.

Make it yours See how it works ↓
A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
A team selects a computing activity for an impact estimate
Produces
A dated estimate with units, scope, assumptions, and sustainability review status.
Category
Reviews & approvals

01 / The starting point

A clear request.
A useful direction.

A defined measurement boundary, disclosed methodology, and approved reporting purpose

“Prepare a reproducible estimate with assumptions rather than a precise or independently measured footprint claim.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Applies a methodology to selected computing calls and prepares an estimated carbon-equivalent value for tracking or reporting.

  1. Define the measured activity and boundary

    Specify included calls, duration, infrastructure assumptions, and excluded activity.

  2. Record method and factor versions

    Keep the calculation traceable to a dated methodology and input set.

  3. Review units, inputs, and uncertainty

    Check that energy and carbon units are consistent and assumptions are disclosed.

  4. Protect prompts and user records

    Track aggregate usage where possible instead of retaining private request content.

  5. Approve claims before external reporting

    Have a sustainability reviewer verify comparisons, wording, and limits.

03 / The result

Something useful.
Something to build on.

A dated estimate with units, scope, assumptions, and sustainability review status.

AmbactiWorkflow folio · 5 steps

Review computing impact estimates

Reviews & approvals · Example outcome

The handoff

A dated estimate with units, scope, assumptions, and sustainability review status.

Keep in mind

An estimate can be mistaken for a direct measurement or used to make an unsupported environmental claim. Record assumptions, method version, and uncertainty; do not compare unlike workloads as if the values were exact.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Document assumptions and data sources

Name the method, region, hardware factors, and estimation boundaries.

Minimize user-level telemetry

Avoid copying prompt contents or personal identifiers into impact records.

Set consistent reporting units

Use comparable periods and workloads and label modeled values as estimates.

Require review of environmental claims

Do not describe an estimate as measured, certified, or proof of sustainability.

Keep exploring

Review an emissions report

Organize energy and travel figures into a traceable emissions estimate for sustainability review.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗