AI uses for records
Approvals made in email: finding decision records outside your systems
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Approvals in email are decision records that never reached your systems: discount sign-offs, change orders, purchase approvals and exceptions agreed in a reply. Find them with targeted search patterns, then link each one back to its system record through an ID in the subject or body. An email approval counts only when request, approver and outcome connect.
Key takeaways
- Systems often record the final state of a deal, job or order, while the email thread records who approved it and why.
- Identifiers in subject lines, such as quote, PO, job and ticket numbers, are the most reliable bridge back to system records.
- Search by phrasing, sender role and identifier pattern together, because any one alone returns too much noise.
- Keep each email's Message-ID as the link key so every match can be traced and checked later.
- Set aside privileged legal threads and messages dominated by personal matters before any further review.
Why so many approvals happen in email#
Approvals happen in email because email is faster than the system and works from a phone. A sales manager replies 'approved' to a discount request between meetings. An owner okays a change order from a job site. A controller signs off on a vendor credit while traveling.
Many systems also lack a step for the decision. A CRM may record the final price but not who allowed the exception. A field service platform may show an added line item without the customer's written authorization. An ERP may show a released purchase order without the conversation that preceded it.
The result is a split record. The system shows what happened; the inbox shows who decided and why. For audits, disputes and any later use of the records, both halves matter.
Which approvals hide in inboxes?#
The approvals that hide in inboxes cluster around money, scope and exceptions. Each type tends to carry a recognizable signal and a natural system record to link to.
| Approval type | Typical email signal | System record to link |
|---|---|---|
| Discount or pricing exception | Quote number, 'ok to go at', 'approved for this deal' | Opportunity or quote in Salesforce or HubSpot |
| Purchase or spend approval | PO number, vendor name, 'please approve' | Purchase order in the ERP |
| Change order | Job or project number, 'CO', 'authorize the extra work' | Job in ServiceTitan or project in Procore |
| Credit memo or refund | Invoice number, 'credit them', 'waive the fee' | Invoice and credit memo in accounting |
| Hotfix or release go-ahead | Ticket key, 'ship it', 'go for release' | Issue in Jira or a pull request |
| Warranty or policy exception | Serial number, claim number, 'one-time exception' | Warranty claim or service case |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
Search patterns that find approvals#
Search patterns work best when they combine wording, people and identifiers. Wording alone returns thousands of casual replies, and identifiers alone return every message that mentions an order.
Tools matter less than the patterns. Microsoft Purview content search, Google Vault or a mail archive's search can run them, depending on your plan and permissions. If you use Purview eDiscovery, Microsoft says search exports expire 14 days after creation, so download each package promptly. Involve whoever is responsible for email governance, because these searches touch everyone's mail.
- Approval phrasing: approved, go ahead, ok to proceed, signed off, you have my approval, make an exception, per our call.
- Sender roles: replies from owners, executives, controllers and department heads to requests from their teams.
- Identifier patterns: the quote, PO, job, invoice and ticket number formats your systems use, matched with regular expressions.
- Mailbox scope: shared approval aliases, finance and purchasing mailboxes, and the mailboxes of people with approval authority.
- Attachments: replies carrying quotes, change order forms or signed PDFs.
- Date windows: periods around month-end, contract renewals and major project milestones.
How to link an email approval to the system record#
Linking an email approval to its system record works in a fixed order: exact identifier first, then a combination of customer, amount and date, then manual review. Record which method produced each link.
The crosswalk is the real deliverable. It turns a scattered inbox into a table that says which decision belongs to which record, and anyone can check it later.
- Extract identifiers from subjects, bodies and attachment names.
- Match exact identifiers to system records and mark these links as high confidence.
- For the rest, match on customer or vendor, amount and a narrow date window, and mark these as medium confidence.
- Send unmatched approvals that look important to someone who knows the account.
- Store the result as a crosswalk: email Message-ID, system record ID, match method and reviewer.
Which email approvals are usable and which are not#
An email approval is usable when the request, the approver, the decision and the eventual outcome can all be connected. A reply saying 'fine' to a forwarded screenshot, with no identifier and no follow-up, is a curiosity rather than a record.
Some threads should be set aside regardless of quality. Messages with outside counsel or in-house lawyers may be privileged. Approvals that are really a client's instructions may be the client's confidential information. Threads mixing business with personal or medical matters carry more privacy burden than they are worth.
Going forward, the cheapest fix is a habit: put the record number in the subject line, and paste the approval into the system's notes field or attach the email to the record.
What a complete approval record looks like#
A complete approval record pulls six elements together, usually from two or three places. When one element is missing, note it in the crosswalk rather than guessing, because a partial record with an honest gap is more useful than a filled-in one that may be wrong.
| Element | Where it usually comes from | What to check |
|---|---|---|
| Request | The first email in the thread or a system note | That it states what was asked and why |
| Approver and authority | The reply sender and your approval matrix or org chart | That the person had authority at that date |
| Decision and conditions | The approving reply | Any limits, such as 'this order only' |
| Reason | The thread body or attached quote | That the reason is stated, not implied |
| Linked record | The crosswalk to the CRM, ERP or job system | Match method and confidence |
| Outcome | Invoice, shipment, closed job or released code | That the outcome followed the approval |
Illustrative: a roofing contractor's change orders#
Illustrative: a fictional commercial roofing contractor runs jobs in ServiceTitan. Field supervisors propose extra work on site, and the owner approves larger change orders by email reply, often from a phone. The job record shows the added invoice lines but not who approved them or why.
The operations manager searched the owner's mailbox and the estimating alias for the company's job number format and approval phrasing, then matched each approval to its job and final invoice. Threads that also involved property owners' personal details were set aside for privacy review.
The outcome was a crosswalk linking most change orders to their approval, reason and billed result. The company also added a required approval field for change orders, so future decisions land in the job record directly.
How SourceX treats email-based decision records#
SourceX treats mailbox records as both valuable and burdensome. In the Supply step of the SourceX five-step transaction, the fit check asks where approvals live and whether system records carry identifiers, without collecting any email. Scope then stays narrow: matched threads linked to system records, not whole mailboxes.
The Rights step reviews email policies, employee notices and client confidentiality, and Preparation replaces names and contact details. The provenance section of the SourceX Evidence Packet records which mailboxes, date ranges and search criteria produced the set, so the selection can be reproduced and audited.
Frequently asked questions
Do we need employees' permission to search their mailboxes?
That depends on your email and acceptable-use policies, employee notices, and the laws where staff work. Company mail is often subject to company review, but rules vary. Involve HR and counsel before searching, document the purpose and limit the search to business approvals.
Should we also search Slack or Teams for approvals?
Yes, if decisions are made there. The same approach applies: combine approval phrasing, approver roles and identifier patterns, then link matches to system records. Chat exports usually keep channel, sender and time, which helps matching, but check that thread replies were included.
How much email should be exported?
Only what the matched approvals require: the thread containing the request and the decision, plus enough context to show the outcome. Exporting whole mailboxes multiplies privacy and review work without adding much value.
Can approvals by text message be recovered the same way?
Sometimes. Texts on company-managed phones or business messaging platforms may be exportable, while texts on personal phones usually are not and raise separate privacy questions. Going forward, ask approvers to confirm text approvals in email or in the system record.
What if the approver no longer works here?
Their mailbox may still exist under a retention policy, or it may already be deleted. Check offboarding and mailbox retention settings before assuming the approvals are gone, and preserve a departing approver's mailbox before deletion if important decisions live there.
Sources
- Microsoft states that Purview eDiscovery search exports expire 14 days after creation, so export packages must be downloaded before they are automatically deleted. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.