1. Home
  2. Process mapping without event logs

Comparison

Process mapping for the work event logs do not reach.

Process mining gives a clear, data-driven view of work that runs inside one or two systems. Facilitated capture extends that view to the email, spreadsheets and portals where much of a regulated operation happens, so every process can be mapped and scored.

One journey, two kinds of trace

Some steps leave a log. Others live in an inbox.

A typical investor onboarding runs across a transfer agency platform, a document store, email threads and a counterparty portal. Facilitated capture records every step with the people who do the work.

  • Recorded in a system of record
  • Recorded in the validated map
  • No system trace
Investor onboardingIllustrative example
Illustrative investor onboarding journey showing which steps leave a system record and which are recorded in the validated map
Step and where it happensSystem recordValidated map
Register the applicationTransfer agency platform
File identity documentsDocument store
Request missing detailsEmail thread
Confirm with the counterpartyCounterparty portal
Resolve the queryEmail thread
Steps with a system record 2 of 5Steps in the validated map 5 of 5
On this page
  1. How process mining works
  2. Where regulated work runs
  3. Dark work
  4. Structured capture with provenance
  5. When process mining is the right answer

In brief

  • Process mining works well where a process runs end to end inside one or two systems with complete event logs.
  • In regulated operations, much of the most expensive work runs across email, spreadsheets and portals, which leave no usable log.
  • Facilitated capture, validated by a named person and carrying provenance, maps those steps so they can be scored consistently.

How process mining works

Process mining reconstructs a process from event logs, the timestamped records that transactional systems produce as work moves through them. Given a case identifier, an activity name and a timestamp, it can rebuild the real path work took, show variants, and quantify where time is lost.

Where a process runs end to end inside one or two systems, this is genuinely excellent. Order-to-cash in a single ERP. A claims workflow in one claims platform. The data is there, it is complete, and the analysis is close to objective.

Where regulated work runs

Now consider the processes that typically cost a fund administrator or a specialist insurer the most.

Investor onboarding runs across a transfer agency platform, a document store, three email threads and a counterparty portal. AML periodic refresh is tracked in a spreadsheet one person maintains. Dealing exceptions are worked from a shared mailbox with no queue and no ageing. Client reporting is assembled from four extracts and finished by hand.

Those steps produce no usable event log. There is no case identifier that spans the whole journey, no activity names, and no timestamps for the parts that happen in someone's inbox.

Typically, the processes with the largest prize run across inboxes, spreadsheets and portals. That is where facilitated capture adds the most coverage.

Dark work

A useful term here is dark work: activity that consumes real capacity but leaves no trace in any system of record.

  • The shared mailbox that three people work without a queue, an ageing report or a record of who resolved what.
  • The spreadsheet that tracks a rolling population and would take some explaining to a regulator.
  • The chase-up call, the workaround that exists because two systems do not talk, the check somebody does because of something that went wrong in 2019.
  • The exception path, which is where the cost concentrates and which seldom appears in the documented procedure.

Dark work is where rework, risk and capacity loss cluster. It is also where the AI opportunity is largest, because the work is manual precisely where no system was ever built for it. This is why an AI opportunity assessment works best when it covers the whole process, including the steps that system data does not show.

Structured capture with provenance

Where the data is yet to exist, create it deliberately, with the people who do the work.

  1. Facilitated capture with the people who do the work day to day. Activities, actors, systems, handoffs, controls, volumes, cycle times, exception rates and, critically, where the work waits.
  2. Validation by a named person for each process, recorded. That signature is what makes the map stand up to scrutiny later.
  3. Evidence carries provenance. Where a procedure document is used as a starting draft, it is marked as such, with a confidence flag, and where observed practice differs the divergence is recorded in full. That divergence is frequently the most valuable finding in the engagement.
  4. A structured record. The output is queryable, scoreable, re-runnable and comparable. A diagram is a photograph of a moving object; a structured record keeps up with the work. Once it is structured, every step can be scored consistently.

When process mining is the right answer

Helpful guidance

If your highest-cost processes run end to end inside one or two systems, and you have the data engineering capacity to support it, process mining will serve you better on precision and on ongoing cost, and we will say so.

If an enterprise implementation is already under way, completing it first usually makes sense, and that is what we would recommend.

Where each approach fits

Each approach has its place.

Many firms use more than one. The question is which parts of the operation each one can see.

Process mining

Works well where the work lives in systems.

It rebuilds the real path from event logs, shows variants and quantifies where time is lost.

Best suited to

  • Processes that run end to end inside one or two systems
  • Complete event logs with a case identifier, activity and timestamp
  • Firms with data engineering capacity to support it
Facilitated capture

Adds the work that runs between systems.

It maps each step with the people who do it, validated by a named person and scored against the evidence.

Best suited to

  • Work across email, spreadsheets, shared mailboxes and counterparty portals
  • Exception paths and the places where work waits
  • Firms that want every step mapped, scored and re-runnable

Four common approaches, side by side

ApproachWhere it works wellWhat to plan for
Process miningProcesses inside one or two systems with complete event logs. Precise and close to objective.Needs event logs, which the highest-cost processes often lack, and a data-engineering phase before the first insight.
Task miningDesktop activity, closing part of the gap. A useful supplement to structured capture.Screens often show client data. It captures the happy path more reliably than the exceptions that break automations, and shows what happened more than why.
Procedure documentsHow work is intended to be done. A good starting draft, marked with a confidence flag.The divergence between the document and actual practice is usually the finding.
A workshop and a whiteboardCaptures the real path and builds quick alignment.Add a consistent scoring method, a baseline and an evidence trail, so the board can see how each choice was made.

Questions

Common questions.

Where does process mining fit in fund administration or insurance operations?

Process mining reconstructs a process from event logs produced by systems of record, and it works well where the whole process runs inside one or two transactional systems. In fund administration, insurance operations and specialist banking, much of the most expensive work runs across email, spreadsheets, shared mailboxes and counterparty portals, which generate no usable event log. Facilitated capture maps those steps, so the processes with the largest prize can be mapped and scored as well.

What is dark work?

Dark work is activity that consumes real capacity but leaves no trace in any system of record: the shared mailbox, the spreadsheet that tracks a cycle, the chase-up call, the workaround that exists because two systems do not talk. It is typically where cost, risk and rework concentrate, and tools that rely on system data have no record of it.

Can task mining help?

Task mining captures desktop activity and closes part of the gap. In regulated firms it brings points to plan for: it records screens that often show client data, it captures the happy path more reliably than the exceptions that break automations, and it shows what happened with less insight into why. It works well as a supplement to structured capture.

How does PinpointProof sit alongside process mining?

Usually as a complement. A firm with a mature process mining implementation already has a tool, a team and event-log coverage of its core systems. The firms we work with typically find that their highest-cost processes run outside any system that produces a usable log, which is where facilitated capture helps. If an enterprise mining programme is already under way, completing it first usually makes sense.

See it on your own process.

Bring one process you would describe as expensive. In thirty minutes you will see what its map and scores look like.