HOW IT WORKS

Approve the sources. Evoke does the rest.

When someone leaves, what only they knew leaves too. Evoke captures it from the sources you approve, checks it with them, and hands it on with the evidence attached.

BG Image
Dashboard Image
BG Image
Dashboard Image
  • Brand Image
  • Brand Image
  • Brand Image
  • Brand Image
  • Brand Image
  • Brand Image
  • Brand Image
  • Brand Image
  • Brand Image
  • Brand Image
  • Brand Image
  • Brand Image
  • Brand Image
  • Brand Image

THE PROBLEM

A handover is usually a folder, a rushed call, and a hope that nothing important was missed

BG Image

APPROVED SOURCES

3 approved

Slack

#cs-team, #accounts

Google Drive

Account plans

HubSpot

Sarah's accounts

Direct messages

excluded

Personal drives

excluded

SCOPE

0 sources approved

BG Image

APPROVED SOURCES

3 approved

Slack

#cs-team, #accounts

Google Drive

Account plans

HubSpot

Sarah's accounts

Direct messages

excluded

Personal drives

excluded

SCOPE

0 sources approved

Pick what Evoke can see

Connect the channels, folders and records that matter for the role, and nothing else. Evoke reads only what you switch on, and it can never touch a direct message, because it never asks for the permission that would let it.

You see the full scope before anything runs, and so does the person handing over.

BG Image

what evoke found

12

Open commitments

9

Gaps to ask about

2

Sources disagree

Northwind renewal terms were never written down

Gap

Nobody else runs the monthly usage report

Gap

Priya is the real contact, not the one listed

Confirmed

Renewal deadline is 30 September

Confirmed

BG Image

what evoke found

12

Open commitments

9

Gaps to ask about

2

Sources disagree

Northwind renewal terms were never written down

Gap

Nobody else runs the monthly usage report

Gap

Priya is the real contact, not the one listed

Confirmed

Renewal deadline is 30 September

Confirmed

Evoke finds what was never written down

From the approved sources, Evoke builds a picture of what the role handles, decides and owns. Then it surfaces the gaps: the commitment with no owner, the deadline only one person knew, the two sources that disagree.

This is the part a leaving checklist always misses, because nobody writes down what they assume everyone knows.

BG Image

GAP SESSION · SARAH CHEN

Your account plan says the Northwind renewal is on track, but a Slack thread mentions an unresolved security review. Which is right?

The review is real. It slips unless Priya signs off before August 10

Captured · Northwind renewal

Blocker: Priya's sign-off Deadline: August 10

Awaiting Sarah's confirmation

Next gap: two loose ends on Sagepoint

BG Image

GAP SESSION · SARAH CHEN

Your account plan says the Northwind renewal is on track, but a Slack thread mentions an unresolved security review. Which is right?

The review is real. It slips unless Priya signs off before August 10

Captured · Northwind renewal

Blocker: Priya's sign-off Deadline: August 10

Awaiting Sarah's confirmation

Next gap: two loose ends on Sagepoint

BG Image

GAP SESSION · SARAH CHEN

Your account plan says the Northwind renewal is on track, but a Slack thread mentions an unresolved security review. Which is right?

The review is real. It slips unless Priya signs off before August 10

Captured · Northwind renewal

Blocker: Priya's sign-off Deadline: August 10

Awaiting Sarah's confirmation

Next gap: two loose ends on Sagepoint

Checked by the person who knows

Evoke asks the person handing over about only the gaps, not their whole job. Around 25 minutes, in their own time, by typing or voice. Nothing is saved until they have read it and confirmed it, and they can correct anything that is wrong.

They leave with a record of what they contributed. It is theirs to keep.

BG Image

DANIEL'S HANDOFF · NORTHWIND

Aug 10

Renewal deadline

Priya

Needs to sign off

1

Conflict flagged

Answered from 3 sources

Sarah's session

Confirmed

Slack · #cs-team

2 threads

Google Drive · Account plans

1 document

BG Image

DANIEL'S HANDOFF · NORTHWIND

Aug 10

Renewal deadline

Priya

Needs to sign off

1

Conflict flagged

Answered from 3 sources

Sarah's session

Confirmed

Slack · #cs-team

2 threads

Google Drive · Account plans

1 document

The next person can just ask

When the successor arrives, they do not get a folder to decode. They ask a question and get an answer with its source attached, drawn only from what was approved and what the person confirmed.

And if Evoke has been running all year rather than starting at the exit, it already holds years of that context, ready on their first day instead of their first quarter.

image

Evidence trail

12 months at current rate

Slack #northwind · Call 21 Jul

Confirmed by Sarah, 9 Sept

Approved sources

3 approved

3

Switched on

2

Excluded

What Evoke can read

Slack · #cs-team, #accounts

Google Drive · Account plans

HubSpot · Sarah's accounts

Card Image

WHY IT WORKS

Answers you can actually rely on

Connects to your tools

Slack, Google Drive, HubSpot, Teams and more. Evoke reads only the sources you approve, so what it captures comes from where the work actually happened.

Every answer carries its evidence

Nothing the next person sees is a guess. Each answer shows the source it came from, and when two sources disagree, Evoke flags it rather than picking one.

Evoke sees only what you allow

You approve every channel and folder, and Evoke never asks for the permission that would let it read a direct message. Switch any source off whenever you want.

image

Evidence trail

12 months at current rate

Slack #northwind · Call 21 Jul

Confirmed by Sarah, 9 Sept

Approved sources

3 approved

3

Switched on

2

Excluded

What Evoke can read

Slack · #cs-team, #accounts

Google Drive · Account plans

HubSpot · Sarah's accounts

Card Image

WHY IT WORKS

Answers you can actually rely on

Connects to your tools

Slack, Google Drive, HubSpot, Teams and more. Evoke reads only the sources you approve, so what it captures comes from where the work actually happened.

Every answer carries its evidence

Nothing the next person sees is a guess. Each answer shows the source it came from, and when two sources disagree, Evoke flags it rather than picking one.

Evoke sees only what you allow

You approve every channel and folder, and Evoke never asks for the permission that would let it read a direct message. Switch any source off whenever you want.

image

Evidence trail

12 months at current rate

Slack #northwind · Call 21 Jul

Confirmed by Sarah, 9 Sept

Approved sources

3 approved

3

Switched on

2

Excluded

What Evoke can read

Slack · #cs-team, #accounts

Google Drive · Account plans

HubSpot · Sarah's accounts

WHY IT WORKS

Answers you can actually rely on

Connects to your tools

Slack, Google Drive, HubSpot, Teams and more. Evoke reads only the sources you approve, so what it captures comes from where the work actually happened.

Every answer carries its evidence

Nothing the next person sees is a guess. Each answer shows the source it came from, and when two sources disagree, Evoke flags it rather than picking one.

Evoke sees only what you allow

You approve every channel and folder, and Evoke never asks for the permission that would let it read a direct message. Switch any source off whenever you want.

What can Evoke actually see?

Only the channels, folders, and records you approve during setup. Nothing outside that list is reachable, and your team sees the same scope you do.

Does this only work when someone leaves the company?

No. It works the same way when someone moves to another team inside your company. Both are handovers, and internal moves are just as easy to get wrong.

Can it read direct messages?

No. Evoke never requests the permission that would allow it, so it cannot see them. It can send someone a message without being able to read theirs.

How much time does this take my team?

Setup is about twenty minutes, once. After that most people spend a few seconds confirming an entry when it comes up, plus one short session a quarter.

What if Evoke captures something wrong?

The person whose work it is corrects it, and it stops being treated as fact. Disputes stay visible, so nobody acts on something that has been challenged.

Does any of this feed into performance reviews?

No. Evoke records work and never rates workers. There are no scores, rankings, or productivity reports, and there never will be.

What if someone leaves without notice?

That is the case Evoke is built for. Because it works from the day someone joins, most of the handoff already exists before anyone hands in their notice.

What if the person handing over will not cooperate?

Most of what Evoke captures comes from your own approved sources, not from them, so you get the picture either way. The session only asks about the gaps nobody wrote down, takes around 25 minutes, and they keep a record of what they contributed. In practice people take part, because leaving things in good shape is how they want to be remembered.

What happens to our data if we cancel?

You can export everything at any time. On cancellation it is permanently deleted and you get a record confirming it.

What can Evoke actually see?

Only the channels, folders, and records you approve during setup. Nothing outside that list is reachable, and your team sees the same scope you do.

Does this only work when someone leaves the company?

No. It works the same way when someone moves to another team inside your company. Both are handovers, and internal moves are just as easy to get wrong.

Can it read direct messages?

No. Evoke never requests the permission that would allow it, so it cannot see them. It can send someone a message without being able to read theirs.

How much time does this take my team?

Setup is about twenty minutes, once. After that most people spend a few seconds confirming an entry when it comes up, plus one short session a quarter.

What if Evoke captures something wrong?

The person whose work it is corrects it, and it stops being treated as fact. Disputes stay visible, so nobody acts on something that has been challenged.

Does any of this feed into performance reviews?

No. Evoke records work and never rates workers. There are no scores, rankings, or productivity reports, and there never will be.

What if someone leaves without notice?

That is the case Evoke is built for. Because it works from the day someone joins, most of the handoff already exists before anyone hands in their notice.

What if the person handing over will not cooperate?

Most of what Evoke captures comes from your own approved sources, not from them, so you get the picture either way. The session only asks about the gaps nobody wrote down, takes around 25 minutes, and they keep a record of what they contributed. In practice people take part, because leaving things in good shape is how they want to be remembered.

What happens to our data if we cancel?

You can export everything at any time. On cancellation it is permanently deleted and you get a record confirming it.

What can Evoke actually see?

Only the channels, folders, and records you approve during setup. Nothing outside that list is reachable, and your team sees the same scope you do.

Does this only work when someone leaves the company?

No. It works the same way when someone moves to another team inside your company. Both are handovers, and internal moves are just as easy to get wrong.

Can it read direct messages?

No. Evoke never requests the permission that would allow it, so it cannot see them. It can send someone a message without being able to read theirs.

How much time does this take my team?

Setup is about twenty minutes, once. After that most people spend a few seconds confirming an entry when it comes up, plus one short session a quarter.

What if Evoke captures something wrong?

The person whose work it is corrects it, and it stops being treated as fact. Disputes stay visible, so nobody acts on something that has been challenged.

Does any of this feed into performance reviews?

No. Evoke records work and never rates workers. There are no scores, rankings, or productivity reports, and there never will be.

What if someone leaves without notice?

That is the case Evoke is built for. Because it works from the day someone joins, most of the handoff already exists before anyone hands in their notice.

What if the person handing over will not cooperate?

Most of what Evoke captures comes from your own approved sources, not from them, so you get the picture either way. The session only asks about the gaps nobody wrote down, takes around 25 minutes, and they keep a record of what they contributed. In practice people take part, because leaving things in good shape is how they want to be remembered.

What happens to our data if we cancel?

You can export everything at any time. On cancellation it is permanently deleted and you get a record confirming it.