Case Study12 min read

InPolicy Case Study: Energy Trading Company

InPolicy Research

We ran InPolicy over a random sample of an energy trading company's email, taken from a public archive. These are the emails it flagged that matter most, grouped by the executive who would want to see them. Each one shows InPolicy's pink underline under the words it flagged, and the card the writer sees when they click it.

For the Chief Compliance Officer

Earnings, the risk system and trading positions.

Financial reporting

A plan to move expenses "without too much visibility"

Finance memo on potential write-offs · August 2000

This is a follow-up on our efforts to identify potential write-offs in 2000 to utilize the possible availability of non-recurring earnings at the Corporate level. ... However, reviewing the spreadsheets reminded us that we have DOT safety user fees due in December (~$1.1MM) and a $1.5MM annual payment to [counterparty] due by 1/1/2001. While both of these items would more appropriately be charged to expense in 2001, we could probably accelerate them into 2000 without too much visibility.

Policy matchOnly you

“we could probably accelerate them into 2000 without too much visibility”

Guidance

The policy prohibits accelerating or deferring costs and expenses to reach a target or utilize non-recurring earnings rather than reflecting when they appropriately occur.

Don't adjust entries or estimates to hit a target
Why this policy exists

Expenses belong in the period they relate to. Pulling them into the current year to use up one-off earnings makes this year look worse and next year better than it really is. The SEC has brought enforcement cases over earnings smoothing, including a 1999 settlement over reserves a company held back to hit its earnings targets.

Risk systems

"Do not reflect the option in the system"

The signed confirmation for a new deal with a state agency included an option. The deal desk asked how to book it.

Senior trader to the deal desk · February 2001

do not reflect the option in the system. we will take care of that if we exercise the option. it would be good to get the proper transaction execution date in there.

Policy matchOnly you

“do not reflect the option in the system”

Guidance

This policy prohibits leaving a trade, option, or amendment out of [company]'s deal-capture and risk systems.

Don't keep a trade out of the risk system or book it late
Why this policy exists

The risk system is where the company's limits, valuations and credit exposure are measured. A signed option that isn't in it is invisible to all three, so the books describe a different deal from the one the company actually agreed.

Trading information

Positions, shared with a bank's trader

Gas trader to a trader at a bank · August 2001 · one of several like it

flat price me thinks we go nowhere for a while. think the next push down doesnt come again until late october. im buying z 300/250 put spread for 11. still looking for 3.1 by end of season.

Policy matchOnly you

“im buying z 300/250 put spread for 11”

Guidance

This sentence discloses your active trading strategy and open positions to an external recipient at [bank], which violates our policy against sharing trading information outside [company].

Don't reveal the company's positions, bids or results to outsiders
Why this policy exists

A trading company's positions and plans are among its most sensitive information. Sharing them with a trader at another firm hands that firm an edge, and two traders swapping positions and market views can draw questions about coordination.

For the General Counsel

A borrowed login, a signature by someone else, and a buyer running the business before the deal closed.

Access controls

A colleague's login, used to cancel deals

Less than two weeks after the company filed for bankruptcy.

To colleagues · December 2001

[name] asked us to kill all the deals between her portfolio and other portfolio due to the bankruptcy. For this reason, I used [name]'s ID (because I did not have access) to access about 20 deals, and I killed these deals.

Policy matchOnly you

“I used [name]'s ID (because I did not have access) to access about 20 deals”

Guidance

You accessed a computer system using another employee's login credentials because you did not have authorized access yourself, which violates our security policy.

Don't use a system or account you aren't authorized to use
Why this policy exists

Everything done under a login is recorded as that person's work, so the system now shows a colleague cancelling deals they never touched. Using someone else's ID also gets around the access controls that decided who could change those deals.

Signatures

"Sign her name to the reports"

Colleagues working out how someone could sign on a manager's behalf.

Reply on signature authority · October 2000

I think the easiest way is a power of attorney. ... As for the expense account, I figure she can just tell [name] to sign her name to the reports. ANy other ideas?

Policy matchOnly you

“As for the expense account, I figure she can just tell [name] to sign her name”

Guidance

This suggests having someone else sign another person's name on an expense report, which violates the policy against signing someone else's name or asking someone to sign yours.

Don't sign with another person's name
Why this policy exists

A signature on an expense report says the signer reviewed and approved it. Having someone else sign that name removes the check and makes the signature false. The proper route is the one the same email starts with: a formal delegation, such as a power of attorney.

Mergers

The buyer, running the business before closing

The company was selling a pipeline business to another energy company, and the deal hadn't closed.

Internal email on the handover · May 2001

Since the bidweek procedures we are proposing include [buyer] directing [pipeline unit] activities for June during bidweek if we determine that close will occur June 1st, then it seems only logical that we should start operating as [trading unit] at the same time.

Policy matchOnly you

“[buyer] directing [pipeline unit] activities for June during bidweek”

Guidance

This proposal allows the acquiring party ([buyer]) to direct [pipeline unit]'s business activities before the transaction has officially closed, which violates the policy against pre-merger coordination and gun-jumping.

Don't let a buyer or merger partner run the business before closing
Why this policy exists

Until a deal closes, buyer and seller are still separate companies, and here both were in the gas business. A buyer directing the seller's day-to-day business before then can be "gun-jumping." US antitrust agencies have fined buyers for taking that kind of control early, including an energy company over a power plant it was buying (2017).

For the Chief HR Officer

Pressure from the top, performance ratings, and what employees send home or forward.

Charitable giving

Pledges for the boss's charity ride

Chief executive's assistant, from his account, to 22 senior executives · April 2001

I know how incredibly busy you all are, so I'm sure that making a pledge to [name] for the MS150 has simply slipped your mind. Well the ride is this weekend, time is running out and we need you!
[company]'s goal is to raise $700,000, and [name]'s personal goal is to raise $50,000. As of today, we are a little better than half way there.

Policy matchOnly you

“making a pledge to [name] for the MS150 has simply slipped your mind. Well the ride is this weekend, time is…”

Guidance

This email pressures colleagues to donate to a specific fundraiser and follows up on who has not yet pledged, which violates the policy requiring fundraising to remain strictly voluntary and free from pressure.

Keep fundraising voluntary, with no pressure on colleagues
Why this policy exists

A request that comes from the chief executive's office is hard to turn down. Chasing senior people for pledges toward the boss's personal fundraising goal turns a voluntary gift into something that feels like part of the job, and invites questions about who gave and who didn't.

Performance reviews

A rating, and "his being Bavarian"

Manager's appeal of a team member's rating · June 2001

I will only make this pitch once, but did want to pass along some thoughts after reflecting on what I understand to be [name]'s rating at yesterday's functional PRC. First, I have no issue with the criticism of his behaviours and interpersonal skills. ... While some account should be taken of his being "Bavarian", I do not think that is an excuse or cover for what is clearly an area for improvement.

Policy matchOnly you

“some account should be taken of his being "Bavarian"”

Guidance

This sentence refers to an employee's national origin or cultural background ('Bavarian') when discussing their performance rating and behavioral feedback.

Keep protected characteristics out of employment decisions
Why this policy exists

A performance rating is an employment decision, and where someone comes from has no place in it, even as an excuse. The US Equal Employment Opportunity Commission counts being from "a particular country or part of the world" as national origin, and UK law at the time protected national and ethnic origins too. A stereotype written into a rating discussion is the kind of line that turns up later as evidence.

Personal mailboxes

Pay proposals, sent to a home inbox

Manager sending pay proposals · January 2001 · one of several like it

I am sending you an Excel spreadsheet with proposed merit and equity increases. ... Please, let me know if there are any questions. I am forwarding a copy of the spreadsheet to my home address so I can work on it tonight, if necessary.

Policy matchOnly you

“forwarding a copy of the spreadsheet to my home address”

Guidance

The policy strictly prohibits forwarding company documents or spreadsheets to a personal email address, even for the purpose of working on them later.

Don't send company files to personal accounts or devices
Why this policy exists

Pay data is some of the most sensitive information a company holds. A copy in a home mailbox sits outside the company's security, access controls and retention rules, and nobody can pull it back if that account is breached or the employee leaves.

Workplace conduct

"Why don't chicks think like us"

His own line on a forwarded joke, to two colleagues · November 2001 · one of dozens like it

Why don't chicks think like us....wouldn't the world be a better place?

Policy matchOnly you

“Why don't chicks think like us”

Guidance

This sentence uses a gender-based generalization and a patronizing term ('chicks') to stereotype women's thinking patterns, which violates our policy against gender-based stereotypes and slurs.

No slurs, stereotypes or jokes about protected characteristics
Why this policy exists

A joke about women in a work email carries the company's name. One is a lapse. A steady stream of them, and this sample holds dozens of flagged sexual and stereotype jokes, is the raw material of a hostile-environment claim.

How the policies were built

306 policies, built from public sources
50 of them fired at least once
~65% of all warnings came from just ten policies

InPolicy checked every email against 306 policies. We built them with the same process we use to put together a starting policy set for a prospective customer, working from the public record as it stood in mid-2000: the company's own code of ethics, the laws and market rules in force at the time (including the California power market's rules, the federal energy regulator's orders, and securities and employment law), and archived pages from the company's trading website.

191 of the policies are specific to this company and its business. The other 115 are general policies, on subjects such as workplace conduct, data security and confidential information, that almost every company has. We built all of them without looking at a single email in the archive, and without using anything published after 2001.

How often they fired

50 of the 306 policies fired at least once. The busiest one, on passwords typed into email, accounted for about one warning in eight, and ten policies produced about two in three. Seventeen fired exactly once. That's the view a compliance team gets in InPolicy: a short list of policies doing most of the work, which points straight at the workflows worth fixing.

Your policies, your edits

Customers don't have to start from scratch, and they aren't stuck with what we build. InPolicy can turn your existing policy documents (PDFs, Word files, slide decks, Google Docs) into individual policies, or start you from a pre-built pack. You can edit any policy, scope it to particular teams, divisions or countries, set how sensitive it should be, or point it at a live web page so it stays current when the page changes. Every change goes through a draft, review and publish workflow, with a full history.

How InPolicy works

InPolicy works like spellcheck for your company's policies. As someone writes an email, it checks the text against your policies and puts a pink squiggly underline under anything that crosses a line. Clicking the underline opens a private card, like the ones above, that explains which policy applies and why. The writer can change the email or send it anyway, and nobody else sees the warning. Compliance sees which policies come up most often, and on which teams, with no names attached.

~1–2% of everyday email gets a flag
1–2 sec typical time from writing to a warning
0 emails blocked. Only the writer sees the warning

What to expect at your company

Across the everyday email we test on, around 1 to 2 emails in 100 get a flag. This company's email came in at the top of that range, mostly because of forwarded jokes and passwords typed into email.

  • For someone who sends 20 emails a day, that works out to one or two flags a week.
  • Warnings typically appear 1 to 2 seconds after the sentence that triggers them is written.

About this case study

Company profile
IndustryEnergy trading and pipeline company
TeamsTrading, deal operations, finance, government affairs, legal, HR and leadership
Email reviewed~14k emails, sampled at random from July 2000 to December 2001
Policies306, covering trading and risk controls, power-market rules, financial integrity, records, confidentiality, workplace conduct and security
Data sourceA public archive of the company's email
  • The company is an energy trading company whose internal email was made public by a federal regulator during an investigation of Western energy markets, and later released by a university for research. It was never an InPolicy customer, and we are not affiliated with the regulator or the university.
  • We sampled ~14k emails at random, from July 2000 to December 2001, leaving out automated mail, company-wide announcements, duplicates and emails with none of the writer's own words.
  • The archive itself is unredacted. In the excerpts we removed every name, the company's name, and other names that could identify someone, such as places, business units and partner companies. Typos are left as they appear.
  • Job descriptions in the excerpts come from the emails themselves or from the public record of the person's role. Dates such as the bankruptcy filing are public history. The policies didn't use them.
  • We built the policies recently, knowing how the company's story ended, so some hindsight is possible even though we limited ourselves to sources from the period.
  • None of these emails was used to build or tune InPolicy. Other email from this company has been.
  • The cards follow InPolicy's design. The text under "Guidance" is InPolicy's own explanation from our run. The policy names on the cards and the "Why this policy exists" notes are our plain-language summaries for this article and are not legal advice.
  • The examples above are among the clearest we found. Most warnings are less dramatic.
  • The everyday-email range comes from our wider testing on random samples of ordinary work email. InPolicy does not catch everything, and not every warning is needed.
  • The 20-emails-a-day example is an illustration, not a measurement. The 1-to-2-second figure is how long a warning typically takes to appear in the product as someone writes.
  • Nothing here is a legal conclusion or a claim about any individual.

See InPolicy in action

Pre-send enforcement and agentic AI governance — built for General Counsel and CCOs.

Book a call