Current Quality5/10?

What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for channel co-sell ?

📖 2,048 words🗓️ Published Jun 20, 2026 · Updated Jun 30, 2026

Direct Answer

What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for channel co-sell (batch 1 #239) is a gap most SaaS vendors gloss over — here is the operator-level answer.

Focus on one measurable outcome, a single RevOps owner, and fields/reports in the CRM of record. Most content online stops at definitions; execution needs audit → design → pilot → automate → measure.

flowchart TD A[Audit stack and data] --> B[Define 3-5 proof fields] B --> C[Pilot one segment] C --> D[Automate validated steps] D --> E[Report weekly Pulse metric]

flowchart TD A[Identify Stage Inflation] --> B[Map Current Stages] B --> C[Define Correct Stages] C --> D[Align CRM Fields] D --> E[Update Stage Data] E --> F[Validate Stage Accuracy] F --> G[Monitor Co-Sell Metrics] G --> H[Confirm Inflation Fixed]

Why this is under-answered online

Vendor blogs optimize for top-of-funnel keywords, not your motion, CRM, or constraint stack. Playbooks that ignore integration limits, ownership, and board metrics fail in production.

CRO SYNDICATE

What good looks like

Definition of done tied to revenue or data quality, not activity counts.
Documented rollback and a named DRI.
No shadow spreadsheets for metrics leadership reviews.

Related on PULSE

[What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for channel co-sell ?](/knowledge/q10397)
[What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for channel co-sell ?](/knowledge/q10317)
[What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for channel co-sell ?](/knowledge/q10237)
[What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for channel co-sell ?](/knowledge/q10077)
[What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for channel co-sell ?](/knowledge/q9997)
[What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for land-and-expand ?](/knowledge/q10417)

Audit Trail Fields: The Immutable Record of Stage Progression

The single most reliable indicator that stage inflation has been fixed is the presence of timestamped, user-attributed, and reason-coded stage transition logs that cannot be overwritten or backdated. In Zoho CRM, this means leveraging the "Field Audit Trail" feature (available in Professional and Enterprise plans) to capture every stage change, the user who made it, the previous stage, the new stage, and an optional reason code. Without these fields, any claim of fixing stage inflation is unverifiable.

Why this matters for channel co-sell: When a partner moves a deal from "Qualified" to "Proposal Sent" without a corresponding partner-sourced technical validation, that's stage inflation. The audit trail exposes the pattern. You need three specific custom fields to make this actionable:

Stage_Change_Reason__c (Picklist): Values like "Partner pushed," "Internal champion confirmed," "Technical validation passed," "Competitive threat," or "Other — requires manual note." This forces the user to justify every forward move.
Stage_Dwell_Days__c (Formula/Workflow): Calculates the exact number of days the deal spent in the previous stage before moving. A deal that jumps from "Discovery" to "Closed Won" in under 48 hours is a red flag.
Stage_Change_Approver__c (Lookup to User): Only required for stage moves that skip a logical sequence (e.g., from "Lead" to "Negotiation"). This creates a gating mechanism.

Implementation approach: In Zoho CRM, go to Setup → Automation → Workflow Rules → New Rule. Trigger on "Stage" field update. Condition: New stage is not empty and differs from previous stage. Action: Create a record in a custom module called "Stage Audit Logs" with the three fields above. Then build a "Stage Velocity Report" that shows average dwell time per stage per partner, filtered to the last 90 days. A healthy channel co-sell pipeline shows 14–21 days in "Discovery," 7–14 days in "Technical Validation," and 5–10 days in "Proposal." Anything faster than 3 days in any stage suggests inflation.

The proof is in the pattern: Run a weekly report titled "Stage Jumpers" — deals that moved through three or more stages in fewer than 10 days. If that report shows more than 5% of your active pipeline, you still have inflation. The audit trail fields are the only way to prove you've eliminated it, because they surface the exact moment a deal was pushed forward without justification.

Pulse Metric Fields: The Single Number That Quantifies Pipeline Health

Stage inflation is not a binary condition — it's a spectrum. The field that proves you've fixed it is a calculated Pulse Metric that normalizes pipeline value by stage velocity and partner engagement. This is not a standard Zoho field; you must build it using Custom Functions (Deluge script) or a Zoho Analytics integration. The metric is called "Pipeline Integrity Score (PIS)" and it lives as a formula field on the Deal record.

The formula logic (simplified): PIS = (Weighted Stage Value × Partner Engagement Factor) / (Days in Current Stage + 1)

Weighted Stage Value: Assign a multiplier to each stage (e.g., Discovery = 0.1, Technical Validation = 0.3, Proposal = 0.5, Negotiation = 0.7, Closed Won = 1.0). This prevents a deal in early stages from inflating your pipeline.
Partner Engagement Factor: A decimal from 0.0 to 1.0 based on partner activity in the last 7 days (email opens, document views, meeting attendance). If the partner is inactive, the factor drops to 0.2, heavily discounting the deal.
Days in Current Stage: The longer a deal sits without forward movement, the lower the score. A deal stuck in "Proposal" for 45 days gets a near-zero PIS.

Why this fixes stage inflation: When a partner pushes a deal to "Negotiation" without real engagement, the PIS drops to 0.15 or lower. It becomes visually obvious in your pipeline report. The field acts as a real-time governor — no sales rep or partner can inflate the stage without the score tanking.

Implementation in Zoho CRM:

Create a custom field PIS__c (Decimal, 4 decimal places).
Write a Deluge script in Custom Functions that:

Fetches the deal's stage history (via zoho.crm.getRelatedRecords("Stage_History")).
Queries the partner's activity log for the last 7 days (via zoho.crm.getRecord("Contacts", partnerID, "Activity_Log")).
Calculates the formula above.
Updates PIS__c on the deal.

Schedule this script to run every 6 hours via a Workflow triggered on deal update or a Cron Job in Zoho CRM.

Target ranges: A healthy channel co-sell pipeline shows PIS values between 0.4 and 0.8 for active deals. Deals below 0.3 should be flagged for review. Deals above 0.9 are either real or being gamed — cross-check with the audit trail fields. The PIS field is your single source of truth for pipeline integrity. If you can show a board deck where the PIS average is above 0.5 and trending up, you have definitively fixed stage inflation.

Partner Co-Sell Validation Fields: The External Check That Eliminates Self-Serving Stage Moves

Stage inflation in channel co-sell is often driven by partners who want to show pipeline volume to maintain tier status or earn incentives. The fix is a set of partner-facing validation fields that require the partner to confirm the deal stage before the CRM allows the move. This shifts the burden of proof from your internal team to the partner ecosystem.

The three fields you need on the Deal record:

Partner_Stage_Validation__c (Picklist, required for stage moves beyond "Qualified"): Values = "Confirmed by Partner," "Partner Disagrees," "Not Yet Asked." A workflow rule prevents the deal from moving to "Proposal" or beyond unless this field is set to "Confirmed by Partner." This forces a call or email exchange where the partner explicitly agrees the deal is ready.
Partner_Contact_Verified__c (Checkbox, updated via Zoho CRM's Web-to-Lead or Partner Portal): When a partner logs into their portal and clicks "Verify Deal," this checkbox is set to true. The portal action also records a timestamp. If the checkbox is unchecked and the deal is in "Negotiation," you have stage inflation.
Co-Sell_Deal_Score__c (Formula field, auto-calculated): Combines the partner's historical close rate (from a related custom module "Partner Performance"), the number of joint meetings held, and the technical validation status. A score below 50 out of 100 triggers an alert to the channel manager.

Why these fields are non-negotiable: Without partner validation, your internal team can move deals forward based on a single optimistic email from a partner sales rep. The validation fields create a double-blind check. For example, if a partner claims a deal is in "Technical Validation," but the Partner_Contact_Verified__c checkbox is false, the deal is automatically demoted to "Discovery" by a workflow rule.

Implementation steps:

In Zoho CRM, create a Custom Module called "Partner Deal Validations" with fields: Deal_ID__c (Lookup), Partner_ID__c (Lookup), Validation_Date__c (Date), Validation_Status__c (Picklist: Pending, Confirmed, Disputed).
Build a Partner Portal page (Zoho CRM's portal feature) where partners can see their deals and click "Confirm Stage." This action creates a record in the custom module and updates the Partner_Stage_Validation__c field on the deal.
Set up a Blueprint in Zoho CRM for the Deal module. Add a transition rule: "Stage moves from Qualified to Proposal require Partner_Stage_Validation__c = 'Confirmed by Partner'." If the condition fails, the stage move is blocked and an error message is displayed.

Measuring success: Run a monthly "Validation Compliance Report" showing the percentage of deals in each stage that have partner validation. Target: 90%+ of deals in "Proposal" and beyond should have a confirmed validation within the last 14 days. If compliance drops below 80%, you have a systemic inflation problem that the validation fields will expose. The fields themselves become the proof that you've fixed the issue — because every stage move is now externally verified.

Sources

Zoho CRM official documentation — product-specific field types, layout customization, and migration best practices
Salesforce CRM help portal — standard field mapping and stage management for co-sell scenarios
HubSpot CRM knowledge base — pipeline stages, deal properties, and inflation detection methods
Gartner CRM research reports — industry benchmarks for sales stage accuracy and pipeline hygiene
Forrester CRM technology guides — co-sell channel management and data integrity after migration
CRM industry blogs (e.g., CRM Magazine, TechTarget) — case studies and expert tips on fixing stage inflation

FAQ

What is stage inflation in Zoho CRM for channel co-sell? Stage inflation happens when deals are moved to later pipeline stages prematurely, often to make forecasts look healthier. In channel co-sell, this is common because partners may over-optimistically advance deals. You fix it by tracking field-level proof like a required "Partner Commit Confidence" score.

Which specific Zoho CRM fields should I use to detect stage inflation? Use custom fields like "Stage Change Reason" (picklist: partner push, internal audit, verified), "Deal Velocity Days" (formula), and "Partner Validation Date" (date field). These let you audit whether a stage move was justified or inflated.

How do I set up a field to require partner verification before stage advancement? Create a mandatory checkbox field called "Partner Verified" that must be true before the stage picklist allows progression. Use Zoho's workflow rules to block stage changes unless this field is checked, with an error message prompting partner confirmation.

Can I use Zoho's built-in reports to monitor stage inflation? Yes, build a custom report showing "Stage Duration vs. Expected Duration" per deal, filtered by partner. Add a column for "Last Stage Change Reason" and flag any deal where the reason is blank or "partner push" without a matching "Partner Validation Date."

What if partners resist adding these fields? Explain that these fields protect their forecast accuracy too. Offer a pilot with one top partner: show them how the fields reduce false positives in their pipeline. Most partners agree once they see cleaner data leads to better allocation of co-sell resources.

How often should I audit these fields to ensure stage inflation stays fixed? Run a weekly Pulse report checking for deals in late stages (e.g., 70%+ probability) that lack a "Partner Verified" date. Any such deal should trigger a review within 48 hours. Monthly, review the trend of stage-change reasons to spot new inflation patterns.

Bottom line

Treat as RevOps product work: prove value on one slice, then scale. Polish can deepen this entry later.

Download:

![What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for channel co](https://www.zohowebstatic.com/sites/default/files/migrate-create-field.png)

## Direct Answer

![What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for channel co](https://pulserevops.com/img/auto/q10157.svg)

What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for channel co-sell (batch 1 #239) is a gap most SaaS vendors gloss over — here is the operator-level answer.

Focus on **one measurable outcome**, a **single RevOps owner**, and fields/reports in the CRM of record. Most content online stops at definitions; execution needs audit → design → pilot → automate → measure.

```mermaid
flowchart TD
  A[Audit stack and data] --> B[Define 3-5 proof fields]
  B --> C[Pilot one segment]
  C --> D[Automate validated steps]
  D --> E[Report weekly Pulse metric]
```

```mermaid
flowchart TD
A[Identify Stage Inflation] --> B[Map Current Stages]
B --> C[Define Correct Stages]
C --> D[Align CRM Fields]
D --> E[Update Stage Data]
E --> F[Validate Stage Accuracy]
F --> G[Monitor Co-Sell Metrics]
G --> H[Confirm Inflation Fixed]
```

## Why this is under-answered online

![What CRM fields prove you fixed stage inflation after migrating to — Why this is under-answered online](https://image.pollinations.ai/prompt/high%20quality%20editorial%20business%20professional%20office%20photograph%20illustrating%20Why%20this%20is%20under-answered%20online%20What%20CRM%20fields%20prove%20you%20fixed%20stage%20inflatio%2C%20realistic%20magazine%20style%2C%20warm%20light%2C%20no%20text%2C%20no%20watermark?width=1200&height=675&nologo=true&model=flux&seed=64370)


Vendor blogs optimize for top-of-funnel keywords, not **your** motion, CRM, or constraint stack. Playbooks that ignore integration limits, ownership, and board metrics fail in production.

## What good looks like

![What CRM fields prove you fixed stage inflation after migrating to — What good looks like](https://image.pollinations.ai/prompt/high%20quality%20editorial%20business%20professional%20office%20photograph%20illustrating%20What%20good%20looks%20like%20What%20CRM%20fields%20prove%20you%20fixed%20stage%20inflation%20after%20migra%2C%20realistic%20magazine%20style%2C%20warm%20light%2C%20no%20text%2C%20no%20watermark?width=1200&height=675&nologo=true&model=flux&seed=2573)


- Definition of done tied to revenue or data quality, not activity counts.
- Documented rollback and a named DRI.
- No shadow spreadsheets for metrics leadership reviews.

<!--pillar-weave-->
## Related on PULSE

- [What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for channel co-sell ?](/knowledge/q10397)
- [What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for channel co-sell ?](/knowledge/q10317)
- [What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for channel co-sell ?](/knowledge/q10237)
- [What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for channel co-sell ?](/knowledge/q10077)
- [What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for channel co-sell ?](/knowledge/q9997)
- [What CRM fields prove you fixed stage inflation after migrating to Zoho CRM for land-and-expand ?](/knowledge/q10417)

## Audit Trail Fields: The Immutable Record of Stage Progression

The single most reliable indicator that stage inflation has been fixed is the presence of **timestamped, user-attributed, and reason-coded stage transition logs** that cannot be overwritten or backdated. In Zoho CRM, this means leveraging the **"Field Audit Trail"** feature (available in Professional and Enterprise plans) to capture every stage change, the user who made it, the previous stage, the new stage, and an optional reason code. Without these fields, any claim of fixing stage inflation is unverifiable.

**Why this matters for channel co-sell:** When a partner moves a deal from "Qualified" to "Proposal Sent" without a corresponding partner-sourced technical validation, that's stage inflation. The audit trail exposes the pattern. You need three specific custom fields to make this actionable:

1. **`Stage_Change_Reason__c`** (Picklist): Values like "Partner pushed," "Internal champion confirmed," "Technical validation passed," "Competitive threat," or "Other — requires manual note." This forces the user to justify every forward move.
2. **`Stage_Dwell_Days__c`** (Formula/Workflow): Calculates the exact number of days the deal spent in the previous stage before moving. A deal that jumps from "Discovery" to "Closed Won" in under 48 hours is a red flag.
3. **`Stage_Change_Approver__c`** (Lookup to User): Only required for stage moves that skip a logical sequence (e.g., from "Lead" to "Negotiation"). This creates a gating mechanism.

**Implementation approach:** In Zoho CRM, go to **Setup → Automation → Workflow Rules → New Rule**. Trigger on "Stage" field update. Condition: New stage is not empty and differs from previous stage. Action: Create a record in a custom module called "Stage Audit Logs" with the three fields above. Then build a **"Stage Velocity Report"** that shows average dwell time per stage per partner, filtered to the last 90 days. A healthy channel co-sell pipeline shows 14–21 days in "Discovery," 7–14 days in "Technical Validation," and 5–10 days in "Proposal." Anything faster than 3 days in any stage suggests inflation.

**The proof is in the pattern:** Run a weekly report titled "Stage Jumpers" — deals that moved through three or more stages in fewer than 10 days. If that report shows more than 5% of your active pipeline, you still have inflation. The audit trail fields are the only way to prove you've eliminated it, because they surface the exact moment a deal was pushed forward without justification.

## Pulse Metric Fields: The Single Number That Quantifies Pipeline Health

Stage inflation is not a binary condition — it's a spectrum. The field that proves you've fixed it is a **calculated Pulse Metric** that normalizes pipeline value by stage velocity and partner engagement. This is not a standard Zoho field; you must build it using **Custom Functions** (Deluge script) or a **Zoho Analytics** integration. The metric is called **"Pipeline Integrity Score (PIS)"** and it lives as a formula field on the Deal record.

**The formula logic (simplified):**
```
PIS = (Weighted Stage Value × Partner Engagement Factor) / (Days in Current Stage + 1)
```
- **Weighted Stage Value:** Assign a multiplier to each stage (e.g., Discovery = 0.1, Technical Validation = 0.3, Proposal = 0.5, Negotiation = 0.7, Closed Won = 1.0). This prevents a deal in early stages from inflating your pipeline.
- **Partner Engagement Factor:** A decimal from 0.0 to 1.0 based on partner activity in the last 7 days (email opens, document views, meeting attendance). If the partner is inactive, the factor drops to 0.2, heavily discounting the deal.
- **Days in Current Stage:** The longer a deal sits without forward movement, the lower the score. A deal stuck in "Proposal" for 45 days gets a near-zero PIS.

**Why this fixes stage inflation:** When a partner pushes a deal to "Negotiation" without real engagement, the PIS drops to 0.15 or lower. It becomes visually obvious in your pipeline report. The field acts as a real-time governor — no sales rep or partner can inflate the stage without the score tanking.

**Implementation in Zoho CRM:**
1. Create a custom field `PIS__c` (Decimal, 4 decimal places).
2. Write a Deluge script in **Custom Functions** that:
   - Fetches the deal's stage history (via `zoho.crm.getRelatedRecords("Stage_History")`).
   - Queries the partner's activity log for the last 7 days (via `zoho.crm.getRecord("Contacts", partnerID, "Activity_Log")`).
   - Calculates the formula above.
   - Updates `PIS__c` on the deal.
3. Schedule this script to run every 6 hours via a **Workflow** triggered on deal update or a **Cron Job** in Zoho CRM.

**Target ranges:** A healthy channel co-sell pipeline shows PIS values between 0.4 and 0.8 for active deals. Deals below 0.3 should be flagged for review. Deals above 0.9 are either real or being gamed — cross-check with the audit trail fields. The PIS field is your single source of truth for pipeline integrity. If you can show a board deck where the PIS average is above 0.5 and trending up, you have definitively fixed stage inflation.

## Partner Co-Sell Validation Fields: The External Check That Eliminates Self-Serving Stage Moves

Stage inflation in channel co-sell is often driven by partners who want to show pipeline volume to maintain tier status or earn incentives. The fix is a set of **partner-facing validation fields** that require the partner to confirm the deal stage before the CRM allows the move. This shifts the burden of proof from your internal team to the partner ecosystem.

**The three fields you need on the Deal record:**

1. **`Partner_Stage_Validation__c`** (Picklist, required for stage moves beyond "Qualified"): Values = "Confirmed by Partner," "Partner Disagrees," "Not Yet Asked." A workflow rule prevents the deal from moving to "Proposal" or beyond unless this field is set to "Confirmed by Partner." This forces a call or email exchange where the partner explicitly agrees the deal is ready.
2. **`Partner_Contact_Verified__c`** (Checkbox, updated via Zoho CRM's **Web-to-Lead** or **Partner Portal**): When a partner logs into their portal and clicks "Verify Deal," this checkbox is set to true. The portal action also records a timestamp. If the checkbox is unchecked and the deal is in "Negotiation," you have stage inflation.
3. **`Co-Sell_Deal_Score__c`** (Formula field, auto-calculated): Combines the partner's historical close rate (from a related custom module "Partner Performance"), the number of joint meetings held, and the technical validation status. A score below 50 out of 100 triggers an alert to the channel manager.

**Why these fields are non-negotiable:** Without partner validation, your internal team can move deals forward based on a single optimistic email from a partner sales rep. The validation fields create a double-blind check. For example, if a partner claims a deal is in "Technical Validation," but the `Partner_Contact_Verified__c` checkbox is false, the deal is automatically demoted to "Discovery" by a workflow rule.

**Implementation steps:**
- In Zoho CRM, create a **Custom Module** called "Partner Deal Validations" with fields: `Deal_ID__c` (Lookup), `Partner_ID__c` (Lookup), `Validation_Date__c` (Date), `Validation_Status__c` (Picklist: Pending, Confirmed, Disputed).
- Build a **Partner Portal** page (Zoho CRM's portal feature) where partners can see their deals and click "Confirm Stage." This action creates a record in the custom module and updates the `Partner_Stage_Validation__c` field on the deal.
- Set up a **Blueprint** in Zoho CRM for the Deal module. Add a transition rule: "Stage moves from Qualified to Proposal require Partner_Stage_Validation__c = 'Confirmed by Partner'." If the condition fails, the stage move is blocked and an error message is displayed.

**Measuring success:** Run a monthly "Validation Compliance Report" showing the percentage of deals in each stage that have partner validation. Target: 90%+ of deals in "Proposal" and beyond should have a confirmed validation within the last 14 days. If compliance drops below 80%, you have a systemic inflation problem that the validation fields will expose. The fields themselves become the proof that you've fixed the issue — because every stage move is now externally verified.

## Sources

- Zoho CRM official documentation — product-specific field types, layout customization, and migration best practices  
- Salesforce CRM help portal — standard field mapping and stage management for co-sell scenarios  
- HubSpot CRM knowledge base — pipeline stages, deal properties, and inflation detection methods  
- Gartner CRM research reports — industry benchmarks for sales stage accuracy and pipeline hygiene  
- Forrester CRM technology guides — co-sell channel management and data integrity after migration  
- CRM industry blogs (e.g., CRM Magazine, TechTarget) — case studies and expert tips on fixing stage inflation

## FAQ

**What is stage inflation in Zoho CRM for channel co-sell?**  
Stage inflation happens when deals are moved to later pipeline stages prematurely, often to make forecasts look healthier. In channel co-sell, this is common because partners may over-optimistically advance deals. You fix it by tracking field-level proof like a required "Partner Commit Confidence" score.

**Which specific Zoho CRM fields should I use to detect stage inflation?**  
Use custom fields like "Stage Change Reason" (picklist: partner push, internal audit, verified), "Deal Velocity Days" (formula), and "Partner Validation Date" (date field). These let you audit whether a stage move was justified or inflated.

**How do I set up a field to require partner verification before stage advancement?**  
Create a mandatory checkbox field called "Partner Verified" that must be true before the stage picklist allows progression. Use Zoho's workflow rules to block stage changes unless this field is checked, with an error message prompting partner confirmation.

**Can I use Zoho's built-in reports to monitor stage inflation?**  
Yes, build a custom report showing "Stage Duration vs. Expected Duration" per deal, filtered by partner. Add a column for "Last Stage Change Reason" and flag any deal where the reason is blank or "partner push" without a matching "Partner Validation Date."

**What if partners resist adding these fields?**  
Explain that these fields protect their forecast accuracy too. Offer a pilot with one top partner: show them how the fields reduce false positives in their pipeline. Most partners agree once they see cleaner data leads to better allocation of co-sell resources.

**How often should I audit these fields to ensure stage inflation stays fixed?**  
Run a weekly Pulse report checking for deals in late stages (e.g., 70%+ probability) that lack a "Partner Verified" date. Any such deal should trigger a review within 48 hours. Monthly, review the trend of stage-change reasons to spot new inflation patterns.

## Bottom line

Treat as RevOps product work: prove value on one slice, then scale. Polish can deepen this entry later.

Was this helpful?

Sources cited

Pulse RevOps — long-tail RevOps gapsPulse RevOps — long-tail RevOps gaps

⌬ Apply this in PULSE

Free CRM · Revenue IntelligenceAudit pipeline, score reps, ship the fix

Deep dive · related in the library