Document Management SOP — Pyze Execution Intelligence

Task-Boundary Mode How task-instance boundaries are drawn from the event stream. Applies to every Task SoP, Step SoP, and Variants view.

419

Cases Observed

975 events · 15 analysts

3.3 min

Median Cycle Time

Avg 862.2 min

0.00 min

Median Active Handling

Excludes >5-min idle gaps

Path Variants Observed

Across 1 applications

80.1

Step Adherence Score (0-100)

Weighted mean across 2 tasks · 917 instances

Tasks in this Step

2 tasks compose this step. Each has its own mined SoP, adherence scoring, and sub-step variant analysis — drill into any task for the detail.

Select Document Details

470 instances 11 analysts 20.4 min avg

Adherence 80.0

Open Document Manager

447 instances 13 analysts 22.4 min avg

Adherence 80.3

Process Owner

Case Processor

📝 Download Word SOP ⭳ Export BPMN 2.0

Regulatory Context Complete document chains are required for audit readiness. Missing or misfiled source documents trigger inspection findings.

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 975 real events across 419 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

Select Document Details — 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

DOM-level capture

Pyze JS captures every element interaction — button labels, field IDs, section panels.

pyzeClick <li> "Details" 531×

pyzeClick <span> "Complete" 530×

pyzeClick <li> "Narrative" 339×

pyzeClick <a> "Show more" 274×

pyzeClick <button> "Create" 146×

pyzeClick <li> "Patient" 125×

pyzeClick <span> "Adverse Events" 123×

pyzeClick <span> "Submissions & Distributions" 121×

Level 3 · Execution Detail

Phobos

DOM-level capture

Pyze JS captures every element interaction — button labels, field IDs, section panels.

pyzeClick <button> "Proceed" 145×

pyzeClick <button> "Advance" 107×

pyzeClick <button> "Save Comments" 72×

pyzeClick <select> "Select Compound · - sitagliptin phosphate Tablet (G" 56×

pyzeClick <select> "Select Attachment description · Legal · Legal Pre-Sca" 53×

pyzeClick <div> "Please reply to “Request Information" using dropd" 50×

pyzeClick <button> "Send to process" 40×

pyzeClick <a> "Cases" 37×

Level 3 · Execution Detail

Microsoft Word

Document-level capture

Task Mining captures the specific file open during work — file names often encode case context.

file V-Narrative 534252 (English) (26399499_0_2_343143) 572×

file V-Narrative 540591 (English) (26495494_0_2_345212) 429×

file V-Narrative 528191 (English) (26300681_0_1_338349) 382×

file V-Narrative 525025 (English) (26253159_0_3_342205) 320×

file V-Narrative 549428 (English) (26642399_0_2_349187) 253×

file V-Narrative 533936 (English) (26397592_0_1_338360) 233×

file V-Narrative 533882 (English) (26397511_0_1_345751) 230×

file V-Narrative 552979 (English) (26689105_0_2_348832) 226×

Level 3 · Execution Detail

Microsoft Teams

App-level capture

Only application name and dwell time available. Direct instrumentation would unlock deeper detail.

2,391 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

Acrobat

App-level capture

Only application name and dwell time available. Direct instrumentation would unlock deeper detail.

2,565 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 2 · Application Journey

Open Document Manager — 10 apps touched within ±15 min of this task on the same case

Level 3 · Execution Detail

Veeva Safety

DOM-level capture

Pyze JS captures every element interaction — button labels, field IDs, section panels.

pyzeClick <span> "Documents" 484×

pyzeClick <span> "Complete" 275×

pyzeClick <span> "Narrative" 258×

pyzeClick <span> "Adverse Events" 222×

pyzeClick <span> "Products" 166×

pyzeClick <a> "Show more" 148×

pyzeClick <span> "Details" 116×

pyzeClick <button> "Save" 115×

Level 3 · Execution Detail

Phobos

DOM-level capture

Pyze JS captures every element interaction — button labels, field IDs, section panels.

pyzeClick <button> "Proceed" 85×

pyzeClick <select> "Select Attachment description · Legal · Legal Pre-Sca" 60×

pyzeClick <button> "Save Comments" 53×

pyzeClick <select> "Select Compound · - sitagliptin phosphate Tablet (G" 39×

pyzeClick <button> "Advance" 34×

inputld <select> "Select Attachment description · Legal · Legal Pre-Sca" 33×

pyzeClick <button> "Send to process" 32×

pyzeClick <a> "Cases" 23×

Level 3 · Execution Detail

Acrobat

App-level capture

Only application name and dwell time available. Direct instrumentation would unlock deeper detail.

2,725 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

Document-level capture

Task Mining captures the specific file open during work — file names often encode case context.

file V-Narrative 533533 (English) (26384397_0_2_337752) 361×

file V-Narrative 540358 (English) (26494608_0_2_342069) 197×

file V-Narrative 555782 (English) (26733642_0_2_350941) 174×

file Narrative 479307 (English) 173×

file V-Narrative 542162 (English) (26518018_0_1_342783) 170×

file Narrative 497939 (English) 142×

file Narrative 547833 (English) 123×

file V-Narrative 513978 (English) (26062717_0_1_339936) 106×

Level 3 · Execution Detail

Microsoft Teams

App-level capture

Only application name and dwell time available. Direct instrumentation would unlock deeper detail.

1,493 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

7,757 events · 419 cases

Phobos

DOM

827 events · 100 cases

Veeva Safety

DOM

7,757 events · 419 cases

Microsoft Word

Document

317 events · 71 cases

Veeva Safety

DOM

7,757 events · 419 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.

Reference Document Management (step-level) Reference Path 182 cases · 11 analysts

Task Sequence

1. Open Document Manager

Automated Explanation rule-based

This is the mined reference path — 182 instances across 11 analysts follow this exact sequence. Treat as the proposed Standard Operating Procedure for Document Management (step-level).

Reviewer Sweep Reviewer Verification Pass 168 cases · 10 analysts

Task Sequence

1. Select Document Details

Automated Explanation rule-based

Reviewer Sweep — a viewing-heavy pattern with 8.7 avg sub-steps and zero edits captured. Consistent with a downstream reviewer re-opening the task to verify earlier work rather than progressing new data. 10 analysts across 168 cases.

Time

324 hrs/yr

Cost

$24,300/yr

At 1,000

19,059 hrs/yr

Reviewer Sweep Reviewer Verification Pass 32 cases · 8 analysts

Task Sequence

1. Open Document Manager → 2. Select Document Details

Automated Explanation rule-based

Reviewer Sweep — a viewing-heavy pattern with 9.7 avg sub-steps and zero edits captured. Consistent with a downstream reviewer re-opening the task to verify earlier work rather than progressing new data. 8 analysts across 32 cases.

Reviewer Sweep Reviewer Verification Pass 12 cases · 3 analysts · 2× same-task rework

Task Sequence

1. Open Document Manager → 2. Select Document Details → 3. Open Document Manager

Automated Explanation rule-based

Reviewer Sweep — a viewing-heavy pattern with 12.8 avg sub-steps and zero edits captured. Consistent with a downstream reviewer re-opening the task to verify earlier work rather than progressing new data. 3 analysts across 12 cases.

Reviewer Sweep Reviewer Verification Pass 11 cases · 5 analysts · 2× same-task rework

Task Sequence

1. Select Document Details → 2. Open Document Manager → 3. Select Document Details

Automated Explanation rule-based

Reviewer Sweep — a viewing-heavy pattern with 14.5 avg sub-steps and zero edits captured. Consistent with a downstream reviewer re-opening the task to verify earlier work rather than progressing new data. 5 analysts across 11 cases.

Time

801 hrs/yr

Cost

$60,075/yr

At 1,000

47,118 hrs/yr

Reviewer Sweep Reviewer Verification Pass 10 cases · 4 analysts

Task Sequence

1. Select Document Details → 2. Open Document Manager

Automated Explanation rule-based

Reviewer Sweep — a viewing-heavy pattern with 7.5 avg sub-steps and zero edits captured. Consistent with a downstream reviewer re-opening the task to verify earlier work rather than progressing new data. 4 analysts across 10 cases.

Reviewer Sweep Reviewer Verification Pass 2 cases · 2 analysts · 2× same-task rework

Task Sequence

1. Open Document Manager → 2. Select Document Details → 3. Open Document Manager → 4. Select Document Details

Automated Explanation rule-based

Reviewer Sweep — a viewing-heavy pattern with 34.5 avg sub-steps and zero edits captured. Consistent with a downstream reviewer re-opening the task to verify earlier work rather than progressing new data. 2 analysts across 2 cases.

Time

801 hrs/yr

Cost

$60,075/yr

At 1,000

47,118 hrs/yr

Backfill Loop Mid-Flow Data Backfill 2 cases · 1 analysts · 6× same-task rework

Task Sequence

1. Open Document Manager → 2. Select Document Details → 3. Open Document Manager → 4. Select Document Details → 5. Open Document Manager

Automated Explanation rule-based

Backfill Loop — instances revisit the same activity 6.0× on average, consistent with mid-flow detours to fetch or enter data that wasn't ready at the right step. Ordering issue, not an app issue — 1 analysts across 2 cases. Suggests upstream data readiness or UX sequencing is at fault.

Time

334 hrs/yr

Cost

$25,050/yr

At 1,000

19,647 hrs/yr

📄

Detailed Step Reference

Full DOM element detail + case evidence for every step (2 total) — mostly for BA and RPA-developer use

Select Document Details

Select Details None

470 observations 237 cases 11 analysts Median 24.0s 100% high confidence

Open Document Manager

Open Documents Section None

447 observations 251 cases 13 analysts Median 37.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	96	182	19.1%
2	Veeva Safety DOM	→	Phobos DOM	91	178	18.6%
3	Microsoft Word Document	→	Veeva Safety DOM	67	169	17.7%
4	Veeva Safety DOM	→	Microsoft Word Document	64	152	15.9%
5	Veeva Safety DOM	→	Microsoft Teams App	62	138	14.5%
6	Microsoft Teams App	→	Veeva Safety DOM	59	136	14.2%

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	263	62.8%
2	3	Veeva Safety DOM → Phobos DOM → Veeva Safety DOM	16	3.8%
3	5	Veeva Safety DOM → Phobos DOM → Veeva Safety DOM → Phobos DOM → Veeva Safety DOM	8	1.9%
4	3	Veeva Safety DOM → Quality Vault DOM → Veeva Safety DOM	6	1.4%
5	7	Veeva Safety DOM → Phobos DOM → Veeva Safety DOM → Phobos DOM → Veeva Safety DOM → Phobos DOM → Veeva Safety DOM	5	1.2%
6	3	Veeva Safety DOM → Microsoft Word Document → Veeva Safety DOM	2	0.5%
7	3	Veeva Safety DOM → Microsoft Outlook Message → Veeva Safety DOM	2	0.5%
8	10	Veeva Safety DOM → Microsoft Excel Document → Microsoft Outlook Message → Veeva Safety DOM → Microsoft Teams App → Veeva Safety DOM → newtab App → collaboration.merck.com App → Microsoft Teams App → Veeva Safety DOM	1	0.2%
9	9	Veeva Safety DOM → RIM Vault DOM → Veeva Safety DOM → Phobos DOM → Veeva Safety DOM → Microsoft Excel Document → Veeva Safety DOM → Phobos DOM → Veeva Safety DOM	1	0.2%
10	33	Veeva Safety DOM → Microsoft Excel Document → Veeva Safety DOM → newtab App → Veeva Safety DOM → gpteal.merck.com DOM → Veeva Safety DOM → gpteal.merck.com DOM → MEDDRABROWSERWIN App → gpteal.merck.com DOM → Veeva Safety DOM → olk Message → Microsoft Teams App → Veeva Safety DOM → Microsoft Excel Document → Veeva Safety DOM → olk Message → Microsoft Word Document → Veeva Safety DOM → gpteal.merck.com DOM → Microsoft Word Document → gpteal.merck.com DOM → Microsoft Word Document → Veeva Safety DOM → newtab App → phobos.merck.com App → Veeva Safety DOM → Microsoft Word Document → Veeva Safety DOM → muse.merck.com App → Veeva Safety DOM → collaboration.merck.com App → Veeva Safety DOM	1	0.2%

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	975	419	0.04s	0.6 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

47.5%

Distinct transitions

Emerging steps

Unstable steps

Rare apps

Uneven adoption apps

Rare apps (used on <15% of cases)

Application	Capture tier	Cases using	Events	% of cases	Action
Acrobat	App	52	223	12.4%	Shadow tool signal · Flag for investigation →
Microsoft Outlook	Message	47	101	11.2%	Shadow tool signal · Flag for investigation →
Microsoft Excel	Document	37	75	8.8%	Shadow tool signal · Flag for investigation →
collaboration.merck.com	App	29	47	6.9%	Shadow tool signal · Flag for investigation →
Notepad	App	20	40	4.8%	Shadow tool signal · Flag for investigation →
ONENOTE	Document	17	20	4.1%	Shadow tool signal · Flag for investigation →
gpteal.merck.com	DOM	15	32	3.6%	Shadow tool signal · Flag for investigation →
Quality Vault	DOM	14	20	3.3%	Shadow tool signal · Flag for investigation →

Uneven adoption apps (used by minority of analysts)

Application	Analysts using	Total events	Adoption	Action
Microsoft Outlook	6	101	38.0%	Training or knowledge-transfer opportunity · Review users →
Microsoft Excel	6	75	38.0%	Training or knowledge-transfer opportunity · Review users →
apps.powerapps.com	3	41	19.0%	Training or knowledge-transfer opportunity · Review users →
Notepad	1	40	6.0%	Training or knowledge-transfer opportunity · Review users →
runtime-app.powerplatform.com	2	35	13.0%	Training or knowledge-transfer opportunity · Review users →
gpteal.merck.com	5	32	31.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.

Document Management

Tasks in this Step

Publish to QualityDocs

Step Journey

Standard Flow

Step Variants

Select Document Details

Open Document Manager

Top Application Transitions

Path Variants

Applications Footprint

Drift Monitoring

Rare apps (used on <15% of cases)

Uneven adoption apps (used by minority of analysts)