Task-Boundary Mode
How task-instance boundaries are drawn from the event stream. Applies to every Task SoP, Step SoP, and Variants view.
📝 Standard Operating Procedure
Living Document
Confidence 100%
Case Advancement
Execute workflow transitions that move a case from one operational state to the next — marking a stage complete and handing off to the next team.
378
Cases Observed
1,637 events · 14 analysts
1.7 min
Median Cycle Time
Avg 698.3 min
0.05 min
Median Active Handling
Excludes >5-min idle gaps
1
Path Variants Observed
Across 1 applications
81.3
Step Adherence Score (0-100)
Weighted mean across 1 task · 1,184 instances
Tasks in this Step
1 task compose this step. Each has its own mined SoP, adherence scoring, and sub-step variant analysis — drill into any task for the detail.
Process Owner
Case Processor
Regulatory Context
Advancement events establish the audit trail for case handoffs. Must be captured accurately for downstream SLA measurement.
Why this SOP is audit-grade
Every step below is captured at the DOM element level (button labels, field IDs, section panels) — not as screenshot coordinates. Every metric is derived from 1,637 real events across 378 cases, with confidence and case evidence visible per step.
Step Journey
Click a task to see the application journey on the same case, then click an application to drill into the execution detail Pyze captured for it.
Level 2 · Application Journey
Advance Case — 10 apps touched within ±15 min of this task on the same case
Case counts per app are not mutually exclusive — a case that touched both Veeva and Phobos in this window is counted in both rows. Overlap reflects real cross-app work, not double-counted cases.
Level 3 · Execution Detail
Veeva Safety
Pyze JS captures every element interaction — button labels, field IDs, section panels.
pyzeClick
<span>
"Complete"
1943×
pyzeClick
<a>
"Show more"
476×
pyzeClick
<span>
"Narrative"
470×
pyzeClick
<span>
"Continue"
447×
pyzeClick
<button>
"Save"
422×
pyzeClick
<li>
"Narrative"
395×
pyzeClick
<span>
"Adverse Events"
349×
pyzeClick
<li>
"Details"
325×
Level 3 · Execution Detail
Phobos
Pyze JS captures every element interaction — button labels, field IDs, section panels.
pyzeClick
<button>
"Proceed"
359×
pyzeClick
<button>
"Advance"
225×
pyzeClick
<button>
"Save Comments"
183×
pyzeClick
<button>
"Send to process"
114×
pyzeClick
<select>
"Select Attachment description · Legal · Legal Pre-Sca"
102×
pyzeClick
<select>
"Select Compound · - sitagliptin phosphate Tablet (G"
94×
pyzeClick
<a>
"Cases"
85×
pyzeClick
<button>
"Send to Medical Review"
68×
Level 3 · Execution Detail
Microsoft Word
Task Mining captures the specific file open during work — file names often encode case context.
file
V-Narrative 552979 (English) (26689105_0_2_348832)
1638×
file
V-Narrative 540591 (English) (26495494_0_2_345212)
723×
file
V-Narrative 534252 (English) (26399499_0_2_343143)
572×
file
V-Narrative 549550 (English) (26643764_0_1_347593)
526×
file
V-Narrative 528191 (English) (26300681_0_1_338349)
382×
file
V-Narrative 533882 (English) (26397511_0_1_345751)
308×
file
V-Narrative 553023 (English) (26689066_0_2_351253)
257×
file
V-Narrative 542512 (English) (26522671_0_2_344761)
255×
Level 3 · Execution Detail
Acrobat
Only application name and dwell time available. Direct instrumentation would unlock deeper detail.
5,505 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.
Level 3 · Execution Detail
Microsoft Teams
Only application name and dwell time available. Direct instrumentation would unlock deeper detail.
4,239 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.
Standard Flow
Representative application journey — the dominant app-to-app transitions observed in the pilot data. Tier badge shows how deeply Pyze captures each application.
Veeva Safety
DOM
6,714 events · 378 cases
Phobos
DOM
729 events · 119 cases
Veeva Safety
DOM
6,714 events · 378 cases
Microsoft Word
Document
176 events · 50 cases
Veeva Safety
DOM
6,714 events · 378 cases
Dominant transitions chained from real observations. Specific case journeys appear as variants below. Use the Step Journey above to drill into any task.
Step Variants
Distinct task-sequence patterns observed across cases in this step. Click a variant on the left to see its task sequence, business impact, and recommended remediations on the right.
Detailed Step Reference
Full DOM element detail + case evidence for every step (1 total) — mostly for BA and RPA-developer use
Detailed Step Reference
Full DOM element detail + case evidence for every step (1 total) — mostly for BA and RPA-developer use
1
Advance Case
Complete Action
None
1,184 observations
425 cases
15 analysts
Median 60.0s
100% high confidence
Top Application Transitions
Top app-to-app hops observed during this stage. Each pair is a single swivel-chair move, ranked by frequency.
| Rank | From App | To App | Cases | Frequency | Share | |
|---|---|---|---|---|---|---|
| 1 |
Phobos
DOM
|
→ |
Veeva Safety
DOM
|
113 | 196 |
26.3%
|
| 2 |
Veeva Safety
DOM
|
→ |
Phobos
DOM
|
112 | 193 |
25.9%
|
| 3 |
Veeva Safety
DOM
|
→ |
Microsoft Word
Document
|
47 | 91 |
12.2%
|
| 4 |
Microsoft Teams
App
|
→ |
Veeva Safety
DOM
|
49 | 90 |
12.1%
|
| 5 |
Microsoft Word
Document
|
→ |
Veeva Safety
DOM
|
41 | 89 |
11.9%
|
| 6 |
Veeva Safety
DOM
|
→ |
Microsoft Teams
App
|
44 | 86 |
11.5%
|
Path Variants
Top 10 full application journeys observed through this stage (consecutive duplicates collapsed). Shows the actual end-to-end paths cases take — not just single transitions.
| Rank | Hops | Application sequence | Cases | Share of cases |
|---|---|---|---|---|
| 1 | 1 |
Veeva Safety
DOM
|
197 |
52.1%
|
| 2 | 3 |
Veeva Safety
DOM
→
Phobos
DOM
→
Veeva Safety
DOM
|
34 |
9.0%
|
| 3 | 5 |
Veeva Safety
DOM
→
Phobos
DOM
→
Veeva Safety
DOM
→
Phobos
DOM
→
Veeva Safety
DOM
|
12 |
3.2%
|
| 4 | 7 |
Veeva Safety
DOM
→
Phobos
DOM
→
Veeva Safety
DOM
→
Phobos
DOM
→
Veeva Safety
DOM
→
Phobos
DOM
→
Veeva Safety
DOM
|
8 |
2.1%
|
| 5 | 3 |
Veeva Safety
DOM
→
Microsoft Teams
App
→
Veeva Safety
DOM
|
5 |
1.3%
|
| 6 | 3 |
Veeva Safety
DOM
→
Microsoft Excel
Document
→
Veeva Safety
DOM
|
4 |
1.1%
|
| 7 | 3 |
Veeva Safety
DOM
→
Acrobat
App
→
Veeva Safety
DOM
|
4 |
1.1%
|
| 8 | 5 |
Veeva Safety
DOM
→
Microsoft Teams
App
→
Veeva Safety
DOM
→
Phobos
DOM
→
Veeva Safety
DOM
|
3 |
0.8%
|
| 9 | 3 |
Veeva Safety
DOM
→
Microsoft Word
Document
→
Veeva Safety
DOM
|
3 |
0.8%
|
| 10 | 4 |
Veeva Safety
DOM
→
Microsoft Word
Document
→
collaboration.merck.com
App
→
Veeva Safety
DOM
|
2 |
0.5%
|
A "1-hop" path means the case stayed in a single application for this stage. Longer paths indicate cross-app work — those are the ones to investigate for swivel-chair reduction opportunities.
Applications Footprint
Where work actually happens during this stage. Cross-app time flags potential integration or UX opportunities.
| Application | Capture tier | Events | Cases touched | Avg dwell per event | Total minutes in stage |
|---|---|---|---|---|---|
| Veeva Safety | DOM | 1,637 | 378 | 1.11s |
30.2 min
|
Drift Monitoring
Compares observed behavior against the published SOP. Drift signals feed compliance events and trigger automatic SOP refresh.
Drift level
High
Top path concentration
100.0%
Distinct transitions
1
Emerging steps
0
Unstable steps
0
Rare apps
8
Uneven adoption apps
6
Rare apps (used on <15% of cases)
| Application | Capture tier | Cases using | Events | % of cases | Action |
|---|---|---|---|---|---|
| Microsoft Teams | App | 52 | 146 | 13.8% | Shadow tool signal · Flag for investigation → |
| Microsoft Word | Document | 50 | 176 | 13.2% | Shadow tool signal · Flag for investigation → |
| Acrobat | App | 41 | 169 | 10.8% | Shadow tool signal · Flag for investigation → |
| Microsoft Outlook | Message | 39 | 67 | 10.3% | Shadow tool signal · Flag for investigation → |
| Microsoft Excel | Document | 34 | 57 | 9.0% | Shadow tool signal · Flag for investigation → |
| collaboration.merck.com | App | 26 | 46 | 6.9% | Shadow tool signal · Flag for investigation → |
| Notepad | App | 9 | 17 | 2.4% | Shadow tool signal · Flag for investigation → |
| olk | Message | 7 | 7 | 1.9% | Shadow tool signal · Flag for investigation → |
Uneven adoption apps (used by minority of analysts)
| Application | Analysts using | Total events | Adoption | Action |
|---|---|---|---|---|
| Microsoft Outlook | 6 | 67 | 38.0% | Training or knowledge-transfer opportunity · Review users → |
| Microsoft Excel | 5 | 57 | 31.0% | Training or knowledge-transfer opportunity · Review users → |
| apps.powerapps.com | 5 | 29 | 31.0% | Training or knowledge-transfer opportunity · Review users → |
| runtime-app.powerplatform.com | 2 | 24 | 13.0% | Training or knowledge-transfer opportunity · Review users → |
| Notepad | 1 | 17 | 6.0% | Training or knowledge-transfer opportunity · Review users → |
| evocpr01.apps.americas.cf.merck.com | 1 | 12 | 6.0% | Training or knowledge-transfer opportunity · Review users → |
Continuous monitoring active
This SOP reflects observed behavior through the 19-day pilot. In production, drift signals are checked hourly and published SOPs auto-refresh when consensus shifts. Drift events appear in the admin audit log with a diff against the previous version.