History Tab (Entity Details)

The History tab gives you one place to understand everything that’s happened with an entity over time — and to add your own context along the way.

You can find it inside Entity Details as a tab labeled History. From there, you’ll see a time-ordered series of individual events (for example: requests sent, submissions received, notes added, documents uploaded), designed to answer: What happened, when did it happen, and why?

What you’ll find in the History tab

History brings together the key “paper trail” you rely on to understand activity over time and reduce time spent piecing together context across inboxes and separate file locations.

In the History tab, you can expect to see:

• Request history — when requests were created by the TPRM platform asking an entity for a submission
• Submission history — when submissions were received from the entity, including important details like outcomes/decline reasons where applicable
• Evaluations — when an entity’s risk was fully evaluated after we process documents and you resolve any open actions
• Notes — notes your team adds for internal context
• Documents and supporting files — files your team uploads to keep important materials alongside the entity’s record
• Email notification history — a record of outbound emails sent by the platform. You’ll see one event when an email is sent (with a list of recipients, the notification type — new, expiring, or non-compliant — and whether it was an initial notification or a reminder), and separate delivery error events when an email bounces or is rejected (one event per failed email address), so you can confirm what was sent and identify which addresses need attention without searching through inboxes or asking Support.
• Pause and unpause history — when an entity is paused or unpaused, including the fact that notifications were enabled or disabled accordingly, so it’s clear why outreach may have stopped (or resumed).
• Exception history — when an exception is granted or removed, including who took the action and (when provided) a short note capturing the rationale, so decisions stay understandable over time.

A note about email open and click rates

The email notification events are designed to give you a reliable, audit-friendly record of what was sent and whether it reached the intended recipients. For that reason, Evident does not track email open or click rates in the History tab, because these metrics can be misleading (for example, mail privacy protections and automated security scanners can trigger “opens” that don’t reflect real human engagement).

Instead, the History tab focuses on high-confidence signals — like who an email was sent to, and whether any addresses bounced or were rejected — so you can take clear action when delivery issues occur.

Add documents (supporting files) directly from History

Need to attach a contract, waiver, internal form, or other supporting material? History is the home for that.

When you upload a file, it appears as its own event in the timeline, so you can always understand it in context — not just that a file exists, but when it was added and what else was happening at that time.

Documents you upload directly in History are best for internal reference and context — for example, keeping a contract, waiver, or internal form alongside an entity’s record.

These uploaded documents do not get evaluated against requirements or criteria and do not affect an entity’s compliance status.

If you need to submit a document so Evident can evaluate it on behalf of an entity (for example, you have a COI in hand), use the submission link for that entity. Submitting through the entity’s submission link ensures the document is properly processed and included in the entity’s evaluation workflow.

Add notes to capture decisions and context

Notes are ideal for capturing the “why” behind decisions and follow-ups — for example: a clarification from a vendor, an internal decision, or a reminder for future review.

Each note shows up as an individual event in History, making it easier to reference later without digging through emails or separate documents.

Use tags to keep things organized

As you add documents and notes, you can apply tags to help categorize and find information faster (for example: Contract, Waiver, Internal, Notes, etc.). Tags are intended to stay lightweight: enough structure to help with organization, without turning History into a complicated document management system.

Why this matters

• Better review experience: See request history, submission history, notes, documents, and key entity events together in one easy view.
• Stronger traceability: Understand changes, decisions, follow-ups, and outreach over time with a clear timeline of events.
• Less searching: Spend less time piecing together context across email threads and separate file locations.

Where to find it

1. Open an entity
2. Go to Entity Details
3. Click the History tab to view the timeline and add notes/documents from the same place

Definition of events in the History tab

Event Type	What This Means
Request Created	A request from the TPRM platform was created. This is distinct from when the platform sends emails to an entity; requests are created regardless of whether an entity is paused or notifications are disabled.
Response Received	We received a response from the entity, from one of your team members submitting on behalf of an entity, or from a call to our submission API endpoint.
Request Timeout	The request to the entity expired due to lack of a response. The timeout period is typically 30 days, but may differ depending on your specific setup.
Request Terminated	The request was cancelled due to changes in risk profile assignment, exceptions being applied that turn an entity from non-compliant to compliant, or other updates to an entity's current needs. If an entity's needs changed and there's still information we need from them, a new request will be created.
Evaluation Completed	The platform has completed its evaluation of the entity's most recent submission. This event occurs after the entity has responded and all actions have been resolved.
Note Added	A note was added for this entity.
Document Uploaded	A document or file was uploaded for this entity.
Email Sent	The platform sent an outbound email and recorded it as an event in the entity’s timeline. This event includes a list of recipients, the notification type (new, expiring, or non-compliant), and whether it was an initial notification or a reminder.
Email Error	An email delivery attempt failed (for example, a bounceback or rejection). This is recorded as its own event (one per failed email address), so you can identify which specific address needs to be corrected.
Verifications Paused	Verification requests were paused for this entity (emails to the entity were turned off).
Verifications Resumed	Verification requests were resumed for this entity (emails to the entity were turned back on).
Exception Granted	An exception decision was granted for the entity (or an entity-related requirement/criterion), including who took the action and (when provided) the rationale note added at the time of the decision.
Exception Removed	An exception decision was removed for the entity (or an entity-related requirement/criterion), including who took the action and (when provided) the rationale note added at the time of the decision.