Task-Boundary Mode How task-instance boundaries are drawn from the event stream. Applies to every Task SoP, Step SoP, and Variants view.
Dashboard / Task Inventory / Intake / Verify Routing
Intake 📝 Task SoP Mined from 262 instances

Verify Routing

How 7 analysts execute this task across 122 cases — auto-generated Standard Operating Procedure with adherence scoring.

81.1
Avg Adherence Score (0-100)
Median 82.5 · Range 57.5–82.5
13.0 min
Avg Task Duration
0.0 min median
1.3
Avg Sub-Steps per Instance
20.2% have multiple sub-steps
0.4%
Reference Path Coverage
Instances following mined SoP exactly
Reference Baseline 0.4% of instances follow this exactly

Verify Routing — Mined SoP

The most common sub-step sequence observed across 262 task instances. Use the dropdown on the right to compare any deviation to this baseline.

1
View Intake Routed
0.0s Phobos 100%
2
collaboration.merck.com
0.0s collaboration.merck.com 1%
Variant Explorer
Genuine Complexity Complex-Case Execution Path 239 instances · 7 analysts · Δ adherence +1.1
Observed Sequence (vs Reference SoP on left)
differs from reference matches reference
1
View Intake Routed
×
collaboration.merck.com
skipped — this reference step was not executed
Genuine Complexity — this sequence differs from the reference path (1 sub-steps vs 2 in reference) but shows no strong pain-point signals: adherence score 82.2 vs reference 81.1 (delta +1.1). Likely a legitimate case-complexity path — not an automation candidate, but worth cataloging.

Application Mix

Which applications analysts touch while executing this task, measured by event count and active dwell time.

Application Events Event Share Dwell Share
Phobos 298 90.9% 0.0%
Veeva Safety 19 5.8% 100.0%
Microsoft Teams 3 0.9% 0.0%
Microsoft Excel 3 0.9% 0.0%
collaboration.merck.com 2 0.6% 0.0%
Microsoft Outlook 2 0.6% 0.0%
Acrobat 1 0.3% 0.0%

Top Cross-App Transitions (within task instance)

Consecutive events that cross application boundaries within a task instance — the signal where swivel-chair patterns live.

From To Transitions
Phobos Veeva Safety 17
Phobos collaboration.merck.com 2
Veeva Safety Microsoft Teams 1
Veeva Safety Microsoft Excel 1
Veeva Safety Microsoft Outlook 1
Veeva Safety Phobos 1
Microsoft Excel Microsoft Teams 1
Microsoft Teams Microsoft Excel 1
Phobos Acrobat 1
Phobos Microsoft Teams 1

On-Case Application Journey (±15 min around anchor)

Apps the same analyst touched on the same case within ±15 minutes of the task anchor. Captures work that spans task boundaries — the Veeva/Acrobat/Outlook/Word context surrounding the anchor click.

Case counts per app are not mutually exclusive — a case that touched Veeva AND Phobos in this window is counted in both rows. Overlap reflects real cross-app work, not double-counted cases.
Phobos DOM 1,579 events 122 cases 36.9 min
DOM-level capture
Pyze JS captures every element interaction — button labels, field IDs, section panels.
pyzeClick <select> "Select Attachment description · Legal · Legal Pre-Sca" 191×
pyzeClick <button> "Proceed" 130×
pyzeClick <button> "Send to process" 117×
pyzeClick <button> "Save Comments" 110×
inputld <select> "Select Attachment description · Legal · Legal Pre-Sca" 109×
pyzeClick <a> "Inbox" 85×
pyzeClick <a> "Cases" 80×
pyzeClick <a> "Inbox Coordinator" 76×
Veeva Safety DOM 1,021 events 99 cases 13.8 min
DOM-level capture
Pyze JS captures every element interaction — button labels, field IDs, section panels.
pyzeClick <span> "Complete" 81×
pyzeClick <a> "Show more" 51×
pyzeClick <span> "Narrative" 50×
pyzeClick <span> "Adverse Events" 45×
pyzeClick <span> "Case Assessment Results" 34×
pyzeClick <span> "Submissions & Distributions" 33×
pyzeClick <div> "Case: 2353948 (v0.1) - SAE - pembrolizumab Soluti" 31×
pyzeClick <span> "Products" 31×
collaboration.merck.com App 31 events 11 cases
App-level capture
Only application name and dwell time available. Direct instrumentation would unlock deeper detail.
106 granular events captured, but no DOM, document, or message-level metadata is available for this application. Instrumenting this app directly with Pyze would unlock element-level detail.
Microsoft Outlook Message 31 events 13 cases
Message-level capture
Task Mining captures email subjects. Case numbers frequently appear in the subject line.
subj <Due today><Void request><GPVCM POLAND> Case # 2326062 23×
subj FW: [Confidential] <BP Clarification> Case Number 2345589; MCN PY2012025US0056; BP: Pyxis Oncology ; Country 4×
subj <Due today><Void request><GPVCM POLAND> Case # 4×
subj ivermectin license in Portugal 2×
Microsoft Teams App 23 events 18 cases
App-level capture
Only application name and dwell time available. Direct instrumentation would unlock deeper detail.
401 granular events captured, but no DOM, document, or message-level metadata is available for this application. Instrumenting this app directly with Pyze would unlock element-level detail.
Acrobat App 20 events 8 cases
App-level capture
Only application name and dwell time available. Direct instrumentation would unlock deeper detail.
319 granular events captured, but no DOM, document, or message-level metadata is available for this application. Instrumenting this app directly with Pyze would unlock element-level detail.
usc-excel.officeapps.live.com Document 18 events 3 cases
Document-level capture
Task Mining captures the specific file open during work — file names often encode case context.
Microsoft Word Document 16 events 7 cases
Document-level capture
Task Mining captures the specific file open during work — file names often encode case context.
Microsoft Excel Document 14 events 7 cases
Document-level capture
Task Mining captures the specific file open during work — file names often encode case context.
RIM Vault DOM 12 events 2 cases 0.1 min
DOM-level capture
Pyze JS captures every element interaction — button labels, field IDs, section panels.