InPolicy checks email against a company's own policies. It also has built-in checks for mistakes every company makes, which need no policy at all. The recipient check catches email going to, or written about, the wrong person. The consistency check catches a detail that doesn't match the email's own thread, such as an amount or a name, and a weekday that doesn't match its date.
We ran both checks over email from a public archive of an energy trading company, the same archive behind our energy trading case study. These are the mistakes they caught that matter most, grouped by check. Each one shows InPolicy's pink underline under the words it flagged, and the card the writer sees when they click it.
- 100 colleagues briefed on the wrong bill
- Arkansas, in a thread about Oklahoma
- Executives told "no change since June", above news of a sale
- A deadline for tomorrow that reads as two months away
- A $100,000 gap between a cover note and the email under it
- A merger-filing request that skips the day the deal was signed
Details that don't match
Bills, filings, status updates, payments and deadlines that don't match the thread or the calendar.
100 colleagues briefed on the wrong bill
During the 2001 California power crisis, the company's lobbyists sent over three pending bills. The writer summarised them for about 100 colleagues in trading, retail and legal.
attached please find the following bills: AB 1085 ... AB 57 ... SBX 18
AB18X is an emergency bill and it would create a core/noncore split in electricity similar to the one that exists in California's gas market.
“AB18X”
The thread says “SBX 18”; you wrote “AB18X”. If you’re correcting it, say so.
AB 18X was a real bill too, a different emergency bill the same team had been following since January. Sixteen minutes later the writer sent a correction to the same list, and it still said AB18X. A colleague then asked about the bill by the wrong number. The right number didn't come back until the next day.
Arkansas, in a thread about Oklahoma
One of the company's subsidiaries was suspended in Oklahoma until a missing registration booklet was filed. A colleague asked the writer whether anyone had ever filed it.
I have not file any Oklahoma initial business registration booklet before.
I've researched the Arkansas request for an intial business registration booklet. This is a new requirement and it needs to be included with the Annual Report.
“I've researched the Arkansas request for an intial business registration booklet.”
The thread says “[name]. I have more information on the status of this entity with the state of Oklahoma.”; you wrote “I've researched the Arkansas request for an intial business registration booklet.” If you’re correcting it, say so.
About an hour later the colleague wrote back to ask whether they were talking about Oklahoma. The subsidiary stayed suspended until the booklet was filed, so the mix-up cost a round of email before anyone could act.
Executives told "no change since June", above news of a sale
In the last week of November 2001, a finance executive sent four senior executives the asset list for one of the company's financing vehicles. The night before, one of them had written that he didn't know what it held.
I have attached the Statement of Investments as of June 30, 2001. Since then [investment] has been sold. Also, in August, the [loan] was paid down. The balance was $740m, but is now $691.
The list of [vehicle] assets - no change since June.
“no change since June.”
The thread says “Since then [investment] has been sold. Also, in August, the [loan] was paid down.”; you wrote “no change since June.” If you’re correcting it, say so.
The top line says nothing has changed since June. The note underneath reports a sale and a $49 million loan paydown, and the writer's own list from the day before had already dropped the sold investment. A reader who stopped at the top line would have the June picture, five days before the company filed for bankruptcy.
A deadline for tomorrow that reads as two months away
The company's general counsel forwarded a memo on its trademark registrations to the lawyers who ran each division's legal team, and asked each of them to review it.
If you have not already done so, please review the attachment on behalf of all the business enterprises(domestic and international) in your respective groups and and reply to [name] by Friday, June 27.
“Friday, June 27”
June 27, 2001 is a Wednesday, so “Friday, June 27” can’t both be right. Check the day or the date.
Sent on a Thursday, "Friday" meant the next day, while "June 27" was more than two months off. Five days later the memo's author reported that only three people had replied by "last Friday", and six recipients had to be chased. Anyone who went by the date would have thought they had until the summer.
A $100,000 gap between a cover note and the email under it
A settlements analyst forwarded a trader her March email about two transmission payments, with a one-line note on top.
January 2001 Annuity Deal # 559263 for a total of $115,579.91 ([name]'s name) ... February 2001 Annuity Deal # 559250 for a total of $ 9,068.93 ([name]'s name)
just forwading you the e-mail that I sent to you on 3-23-01 when I originally entered the annuity for $15579.91.
“originally entered the annuity for $15579.91”
The thread says “January 2001 Annuity Deal # 559263 for a total of $115,579.91 ([name]'s name)”; you wrote “originally entered the annuity for $15579.91”. If you’re correcting it, say so.
The note and the email under it give two figures for the same January payment, $100,000 apart. The archive doesn't show which one is right, so the trader was left with a record of the payment that disagrees with itself.
A merger-filing request that skips the day the deal was signed
Three days after the company signed a merger agreement, its antitrust counsel told the deal team the merger filing would go to the federal antitrust agencies the next day.
We are prepared to file the Hart-Scott-Rodino ("HSR") Form with the Federal Trade Commission and Department of Justice on Tuesday, Nov. 13th. ... Please confirm to me that since Friday, Nov. 12th, we have not prepared any additional HSR Item 4(c) documents in connection with the proposed merger ...
“Friday, Nov. 12th”
November 12, 2001 is a Monday, so “Friday, Nov. 12th” can’t both be right. Check the day or the date.
The date sets where the document window starts, for a filing due the next day. Read by the date, the window starts that Monday and leaves out the Friday the agreement was signed and the weekend after. Read by the weekday, it starts Friday the 9th. The emails don't show anything was missed, but as written the question had two answers.
Sent to the wrong people
A question for the wrong person, a reply that left people out, and a misspelt name.
A request for a second opinion, sent to the person being judged
An employee emailed two senior executives a proposal for a refinery joint venture, with two colleagues copied. One of the executives replied to the employee alone.
To: [name], [name]
cc: Owen [name], [name]
Subject: deal
Owen, what do you think of this.
“Owen”
The greeting is to Owen, who was on this thread but is not on this reply. Add them back, or check you are replying to the right thread.
The question was meant for Owen, a colleague copied on the proposal. It went to the person who wrote the proposal instead. Owen isn't on the reply, and the archive shows no resend or forward to him.
A meeting call for the whole team, sent to one
Four people were preparing a presentation together. One of them answered the group's thread with a note for everyone, but sent it only to the person whose message he was answering.
Greetings all: I'l have the financials and any other comments/suggestions done and sent to all this evening. ... What about lunch tomorrow (we're all in the city), or at 5 PM (before the ball game)? Lemme know.
“Greetings all:”
This reads as written for everyone on the thread, but it goes to [name] only. [name], [name] were on the message you are answering and will not get it. Use Reply all if they should.
The note asks the group to agree a time to meet the next day, but only one of the three people it was for got it. The other two saw it later that day, and only because the recipient happened to reply to everyone with the note quoted.
A misspelt name spellcheck will never catch
Gray, ... P lease reclass and let me know when this is complete.
“Gray”
The greeting spells the name "Gray", but the recipient writes it "Gary".
"Gray" is a real word, so spellcheck has nothing to underline. The rest of the email ("P lease") shows how fast it was typed. Only a check that knows who the email is going to can see the name is wrong.
How the checks work
The built-in checks come with InPolicy and run on every email alongside your policies. Their warnings look the same as policy warnings: an underline under the words, and a private card when the writer clicks it. The card's header names the check instead of a policy.
Recipient check
The recipient check reads the greeting for a misspelt recipient name, or a name nobody on the email has. It looks for remarks someone on the email shouldn't read, such as interview feedback with the candidate on Cc. It also catches a reply meant for everyone that goes to one person, or a private reply that goes to the whole thread, and names the people left out. Nicknames, short forms and "Hi all" are fine, and once a writer dismisses a greeting card, InPolicy remembers that the name is right for that person.
Consistency check
The consistency check compares a reply with its thread. It flags an amount, date, reference, name or decision that differs from what the thread already settled, and the card quotes the line that settled it so the writer can see which one is right. Changes made on purpose ("can we move it to Thursday instead?"), questions, and details a later message updated are fine. One part needs no thread at all: it catches a weekday next to a date that falls on a different day, so it works on a new email too.
Turning checks on and off
Every part of both checks is on until an admin turns it off. Admins can switch each part on or off on the Checks page, and InPolicy records every change. Analytics shows these cards in their own panel, separate from the policy figures, with no names attached.
How InPolicy works
InPolicy works like spellcheck for your company's policies, and for the everyday mistakes that need no policy. As someone writes an email, it puts a pink squiggly underline under anything worth a second look. Clicking the underline opens a private card, like the ones above, that explains what it found. The writer can change the email or send it anyway, and nobody else sees the warning.
About this case study
| Company profile | |
|---|---|
| Industry | Energy trading and pipeline company |
| Teams | Trading, deal operations, finance, government affairs, legal and leadership |
| Email checked | Emails from across the archive, sent from 2000 to 2001 |
| Checks | Recipient check and consistency check, every part on |
| Data source | A 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 ran the checks over email drawn from across the archive, including the random sample in our energy trading case study.
- The archive itself is unredacted. In the excerpts we removed every person's name, the company's name, and other names that could identify someone, such as business units and financing vehicles. Where the mistake is in a name, we replaced the real names with invented ones that make the same mistake. Other typos are left as they appear.
- Some of these emails were part of the email we used to develop and test the checks. The card on each one is what InPolicy produces for that email.
- The cards follow InPolicy's design. The text under "Guidance" is InPolicy's own. The titles, the backstories and the "Why it matters" notes are ours.
- The examples above are among the clearest we found. InPolicy does not catch everything, and not every warning is needed.
- 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 claim about any individual, or a claim that a warning would have changed what happened.