← Back to work
Web App · ESG Compliance · Live on bevolve.ai

Turning a working regulatory feed into a policy tracker sustainability teams can read at a glance.

UI/UX RedesignCoded Front EndLive & Public
Bevolve Policy Tracker compliance feed with filters, urgency tags, and source-backed policy updates

Product Bevolve Policy Tracker

Sustainability policy intelligence from Bevolve. It brings policy and regulatory developments across regions, regulators, and ESG categories into one feed, so ESG, legal, risk, and strategy teams can see what changed, where it applies, when it matters, and where it came from. Live at bevolve.ai/policy-tracker.

UI/UX design, taking the initial interface to a polished, brand-aligned product
role
Solo designer, alongside Bevolve's research and engineering teams
team
6 months
timeline
Figma, Figma Make, Claude Code
tools
Onboarding · Compliance feed · Filters · Policy reports
scope

Problem Right Data, Rough Surface

Policy changes are scattered across government websites, consultation papers, and regulatory portals. The first version of the tool already pulled them together, but its interface wasn't yet polished or brand-aligned enough to put in front of sustainability teams.

Solution Scan, Filter, Read

I reworked the initial UI/UX, from research and flows to a coded front end, into a working, brand-aligned interface: a three-step conversational setup, a compliance feed with urgency and source on every card, filters organised by region, sector, and E/S/G pillar, and a structured report for every policy.

Result Live on bevolve.ai

Shipped as part of Bevolve's product suite, with a public explore mode anyone can try from the Policy Tracker page.

3 steps
From sign-in to a tuned feed
email, country, and GICS industry sector
Live
Public on bevolve.ai
The brief

Make dense, source-backed regulation feel like a feed you can scan in seconds.

Policy changes are scattered across government websites, consultation papers and regulatory portals. Bevolve's research team had built a first version that pulled them together, but its interface was not yet ready for sustainability teams.

The brief was to take that working tool to a polished, brand-aligned product. I was the solo designer, working with Bevolve's research and engineering teams over 6 months, from research and flows to a coded front end.

Research

Start from how teams hear about regulation

and what they need before they open the full text
Stakeholder interviewsPersonasJourney mappingSketchingClient feedback

I worked with Bevolve's research team, who curate the policies, and spoke to sustainability and compliance users among Bevolve's clients about how they track regulation today.

Three insights that shaped the design
Insight 1

Teams hear about rules too late

Updates arrive through news, newsletters and consultants, often after the consultation has closed.

Insight 2

Two questions decide everything

What changed, and how urgent is it? If a card answers both, people know whether to read on.

Insight 3

No source, no trust

Compliance teams act only on summaries they can trace to the regulator, the date and the original document.

Users

The person who tracks rules, and the person who acts on them

an ESG manager and a head of legal and compliance

Two personas in the same FigJam format as the platform modules. They came from the research team's users and Bevolve's client conversations.

Persona Kavya, ESG manager at a listed manufacturer: bio and personality sliders
More about Kavya: interests, influences, goals, challenges, motivations, pain points and frustrations
Designed forA feed tuned to her country and sector, urgency on every card, and filters that match how she reports: region, sector, then E, S or G.
Journey map

Where regulation got lost

from a new rule to a team that knows what to do
HearFindCheckUnderstandAct
DoingA new rule or consultation is publishedThe team looks for the official textThey check if it applies to themThey work out what changed and whenThey brief the business
PainSpread across many sitesDifferent formats per regulatorUnclear scope by country and sectorLong documents, buried datesNo shared summary to pass on
Design responseOne feed across regions and regulatorsSource and date on every cardFilters by market, sector and ESG pillarA report with key changes and a timelineBusiness impact in every report
Reframing the problem

From "a list of policies" to "what changed, and does it matter to me"

The first version already had the data. The work was deciding what shows where, so a card answers the first question at a glance and the report answers everything else.

How might we
How might we let a sustainability team see, in seconds, which new rules apply to them and how urgent they are, with the source one click away?
In scope
  • Three-step setup
  • Compliance feed with urgency and source
  • Filters with live match counts
  • Structured policy report
  • Accuracy check on every policy
  • Public explore mode
Later
  • Change alerts for policies on a watchlist
User flow

Tune it once, then scan, filter and read

three questions, then the feed
  1. Sign inAn email to save the feed
  2. CountryWhere the team reports
  3. SectorGICS industry sector
  4. ScanThe feed, tuned and sorted
  5. FilterRegion, regulator, sector, pillar
  6. ReadThe full policy report
Sketches

The card and the report on paper first

deciding what a card shows before designing how it looks

Most of the thinking went into one card. I sketched what it must answer and in what order, then the filters and the report around it.

Sketch of the setup with country chips, a GICS sector dropdown and a progress bar
1Setup: three questions, then the feed is tuned
Sketch of a feed card annotated with what changed, urgency, summary and source line
2One policy, one card, always in the same order
Sketch of the filter panel beside the compliance feed
3Filters grouped the way teams think
Sketch of the policy report with summary, key changes, timeline, business impact and an accuracy check
4The report: same four sections for every policy
Key decisions

Three decisions that shaped the experience

Decision 1

Every card in the same order

Title and urgency first, then a two-line summary, then source, date, market and ESG pillar. The order never changes, so people learn to scan it.

Compliance feed with urgency, summary, source, date, market and ESG pillar on every card
Decision 2

Filters that match how teams report

Country, readiness status and regulator first, then sector, then the E, S and G pillars and their sub-topics. Every filter shows a live match count.

Compliance filters grouped by country, readiness, regulator, sector and ESG pillars, with match counts
Decision 3

A report that shows its source

Every report opens with the market, source authority and date of publication, then a verified summary, key changes, timeline and business impact, plus a one-tap accuracy check.

Policy report with market, source authority, publication date, ESG pillar and verified executive summary
Working with research and engineering

Solo designer, alongside the people who own the data

I redesigned the research, flows and UI, and prototyped the front end with Figma Make and Claude Code so engineering worked from code, not static files. The research team reviewed every card and report format against real policies before release.

Final design: key screens

From Setup to Source

tune it once, then scan, filter, and dig in

The first screen below is a recording of the real product: setting up the view, scanning the feed, filtering by an ESG topic, and opening a full policy report. Every screen after it is captured from the live app.

Outcome

Live on bevolve.ai, a policy changes and the team knows the same day.

The Policy Tracker is live as part of Bevolve's product suite, with a public explore mode anyone can try from the Policy Tracker page.

What I learned

When the content is dense, the design is mostly about order. Fixing the order of a card mattered more than any colour or layout choice.

What I'd do next

Add change alerts, so a team gets a nudge the day a policy on its watchlist moves, instead of having to check the feed.

A policy changes, and the right team can read what it means the same day.

Local draft: 0 highlighted lines need your confirmation before this goes live.