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 99%
Submission
Prepare and transmit the regulatory submission package to applicable health authorities. Includes CIOMS and E2B(R3) formatted outputs.
340
Cases Observed
960 events · 15 analysts
0.0 min
Median Cycle Time
Avg 908.2 min
0.00 min
Median Active Handling
Excludes >5-min idle gaps
4
Path Variants Observed
Across 2 applications
80.8
Step Adherence Score (0-100)
Weighted mean across 1 task · 848 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
Submissions Specialist
Regulatory Context
Submission timing is directly regulated — 7-day SUSARs and 15-day expedited reports have no tolerance for lateness.
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 960 real events across 340 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
Process Submission — 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>
"Submissions & Distributions"
536×
pyzeClick
<span>
"Complete"
504×
pyzeClick
<a>
"Show more"
365×
pyzeClick
<span>
"Narrative"
300×
pyzeClick
<span>
"Adverse Events"
280×
pyzeClick
<span>
"Products"
196×
pyzeClick
<span>
"Reference Numbers"
184×
pyzeClick
<li>
"Narrative"
180×
Level 3 · Execution Detail
Phobos
Pyze JS captures every element interaction — button labels, field IDs, section panels.
pyzeClick
<button>
"Proceed"
125×
pyzeClick
<button>
"Send to process"
103×
pyzeClick
<button>
"Save Comments"
72×
pyzeClick
<button>
"Advance"
54×
pyzeClick
<td>
"2352671 (v0.1) Japanese (Japan)"
40×
pyzeClick
<select>
"Select Attachment description · Legal · Legal Pre-Sca"
32×
pyzeClick
<a>
"Cases"
31×
pyzeClick
<button>
"Advanced"
26×
Level 3 · Execution Detail
Acrobat
Only application name and dwell time available. Direct instrumentation would unlock deeper detail.
3,051 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 Word
Task Mining captures the specific file open during work — file names often encode case context.
file
V-Narrative 543823 (English) (26544362_0_2_343646)
775×
file
V-Narrative 540591 (English) (26495494_0_2_345212)
723×
file
V-Narrative 528191 (English) (26300681_0_1_338349)
382×
file
V-Narrative 549707 (English) (26645831_0_1_347236)
313×
file
V-Narrative 514031 (English) (26063743_0_1_327856)
286×
file
V-Narrative 533882 (English) (26397511_0_1_345751)
230×
file
V-Narrative 525091 (English) (26253532_0_1_338428)
201×
file
Narrative 526208 (English)
190×
Level 3 · Execution Detail
Microsoft Excel
Task Mining captures the specific file open during work — file names often encode case context.
file
Case tracking list
699×
file
2355984 (v0.1)
469×
file
Priorización
351×
file
2329445 (v2.1)
339×
file
2352822 (v0.1)
234×
file
Daily tracking list (PV-SMART) copy
225×
file
1761620 (v2.1)
186×
file
I-0000354334
153×
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
4,659 events · 283 cases
Microsoft Word
Document
203 events · 35 cases
Veeva Safety
DOM
4,659 events · 283 cases
Phobos
DOM
1,249 events · 110 cases
Veeva Safety
DOM
4,659 events · 283 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
Process Submission
Open Submissions Section
None
848 observations
340 cases
15 analysts
Median 31.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 |
Microsoft Word
Document
|
→ |
Veeva Safety
DOM
|
33 | 116 |
19.6%
|
| 2 |
Acrobat
App
|
→ |
Veeva Safety
DOM
|
30 | 98 |
16.6%
|
| 3 |
Veeva Safety
DOM
|
→ |
Microsoft Word
Document
|
30 | 98 |
16.6%
|
| 4 |
Veeva Safety
DOM
|
→ |
Phobos
DOM
|
51 | 97 |
16.4%
|
| 5 |
Phobos
DOM
|
→ |
Veeva Safety
DOM
|
48 | 96 |
16.2%
|
| 6 |
Veeva Safety
DOM
|
→ |
Microsoft Teams
App
|
31 | 87 |
14.7%
|
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
|
200 |
58.8%
|
| 2 | 1 |
Phobos
DOM
|
57 |
16.8%
|
| 3 | 3 |
Veeva Safety
DOM
→
Phobos
DOM
→
Veeva Safety
DOM
|
8 |
2.4%
|
| 4 | 5 |
Veeva Safety
DOM
→
Phobos
DOM
→
Veeva Safety
DOM
→
Phobos
DOM
→
Veeva Safety
DOM
|
6 |
1.8%
|
| 5 | 3 |
Phobos
DOM
→
Veeva Safety
DOM
→
Phobos
DOM
|
5 |
1.5%
|
| 6 | 3 |
Veeva Safety
DOM
→
Acrobat
App
→
Veeva Safety
DOM
|
2 |
0.6%
|
| 7 | 7 |
Veeva Safety
DOM
→
Phobos
DOM
→
Veeva Safety
DOM
→
Phobos
DOM
→
Veeva Safety
DOM
→
Phobos
DOM
→
Veeva Safety
DOM
|
2 |
0.6%
|
| 8 | 2 |
Veeva Safety
DOM
→
Phobos
DOM
|
2 |
0.6%
|
| 9 | 3 |
Veeva Safety
DOM
→
Microsoft Teams
App
→
Veeva Safety
DOM
|
2 |
0.6%
|
| 10 | 5 |
Veeva Safety
DOM
→
Microsoft Excel
Document
→
Veeva Safety
DOM
→
Microsoft Outlook
Message
→
Veeva Safety
DOM
|
1 |
0.3%
|
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 | 510 | 277 | 0.08s |
0.7 min
|
| Phobos | DOM | 450 | 66 | 0s |
0 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
61.8%
Distinct transitions
4
Emerging steps
1
Unstable steps
0
Rare apps
8
Uneven adoption apps
6
Emerging activities (not in standard flow)
| Activity | Frequency | Cases | Action |
|---|---|---|---|
| View Localized Cases | 450 | 66 | Candidate for SOP inclusion · Promote to step → |
Rare apps (used on <15% of cases)
| Application | Capture tier | Cases using | Events | % of cases | Action |
|---|---|---|---|---|---|
| Microsoft Word | Document | 35 | 203 | 10.3% | Shadow tool signal · Flag for investigation → |
| Microsoft Teams | App | 32 | 159 | 9.4% | Shadow tool signal · Flag for investigation → |
| Microsoft Excel | Document | 31 | 81 | 9.1% | Shadow tool signal · Flag for investigation → |
| Acrobat | App | 31 | 157 | 9.1% | Shadow tool signal · Flag for investigation → |
| Microsoft Outlook | Message | 20 | 43 | 5.9% | Shadow tool signal · Flag for investigation → |
| ONENOTE | Document | 17 | 31 | 5.0% | Shadow tool signal · Flag for investigation → |
| collaboration.merck.com | App | 16 | 24 | 4.7% | Shadow tool signal · Flag for investigation → |
| YoudaoDict | App | 11 | 25 | 3.2% | Shadow tool signal · Flag for investigation → |
Uneven adoption apps (used by minority of analysts)
| Application | Analysts using | Total events | Adoption | Action |
|---|---|---|---|---|
| Phobos | 5 | 1,249 | 31.0% | Training or knowledge-transfer opportunity · Review users → |
| Microsoft Word | 5 | 203 | 31.0% | Training or knowledge-transfer opportunity · Review users → |
| Microsoft Teams | 4 | 159 | 25.0% | Training or knowledge-transfer opportunity · Review users → |
| Acrobat | 4 | 157 | 25.0% | Training or knowledge-transfer opportunity · Review users → |
| Microsoft Excel | 5 | 81 | 31.0% | Training or knowledge-transfer opportunity · Review users → |
| Microsoft Outlook | 3 | 43 | 19.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.