{ "schema_version": "core-reviewed-term-ai-handoff-v1", "version": "core-reviewed-term-ai-handoff-v1", "contract_status": "preview", "distribution": "per_term_read_only_ai_handoff", "no_write_operations": true, "canonical": { "url": "https://core.yogoq.com/en-US/core/reference-customer-backlog-rate", "slug": "reference-customer-backlog-rate", "locale": "en-US" }, "summary": { "schema_version": "core-reviewed-term-summary-v1", "term_id": "ca44460f-1f23-5b40-abde-009cdc924d2e", "canonical_slug": "reference-customer-backlog-rate", "canonical_url": "https://core.yogoq.com/en-US/core/reference-customer-backlog-rate", "locale": "en-US", "display_name": "Reference Customer Backlog Rate", "english_name": null, "abbreviation": null, "short_definition": "Reference Customer Backlog Rate is useful when a team needs a shared decision language, not just a definition.", "quality": "reviewed", "publication_status": "published_reviewed", "version": "core-reviewed-term-summary-v1", "last_reviewed_at": "2026-05-16T00:00:00.000Z", "sources_count": 2, "limitations_key": "core-trust-policy-v1-2026-06-22" }, "content": { "definition": { "key": "definition", "title": "一言でいうと", "text": "Reference Customer Backlog Rate is useful when a team needs a shared decision language, not just a definition.", "items": [] }, "formula": { "key": "formula", "title": "計算の考え方", "text": "Reference Customer Backlog Rate should be calculated with a stable numerator, denominator, and time window. Formula | Reference Customer Backlog Rate = events or value meeting the definition / eligible base in the same period | Use Reference Customer Backlog Rate after fixing the time window, eligible base, and accountable operating boundary. Time window | Use the same period for every comparison | Prevents artificial movement Segment | Calculate by plan, market, cohort, or owner when useful | Reveals where the change came from", "items": [ "Formula | Reference Customer Backlog Rate = events or value meeting the definition / eligible base in the same period | Use Reference Customer Backlog Rate after fixing the time window, eligible base, and accountable operating boundary.", "Time window | Use the same period for every comparison | Prevents artificial movement", "Segment | Calculate by plan, market, cohort, or owner when useful | Reveals where the change came from" ] }, "boundary": { "key": "boundary", "title": "含めるもの / 含めないもの", "text": "The boundary of Reference Customer Backlog Rate must be written before it is used as a KPI. Include | Recurring and comparable inputs that match the definition | Keeps trend analysis reliable Exclude | One-off, unmatched, or non-comparable items | Avoids inflated or misleading movement Document | Data source, owner, refresh timing, and exception rules | Makes reviews reproducible", "items": [ "Include | Recurring and comparable inputs that match the definition | Keeps trend analysis reliable", "Exclude | One-off, unmatched, or non-comparable items | Avoids inflated or misleading movement", "Document | Data source, owner, refresh timing, and exception rules | Makes reviews reproducible" ] }, "usage": [ { "key": "meaning", "title": "意味", "text": "Reference Customer Backlog Rate describes a practical concept that helps teams frame a situation, compare options, and decide the next operating move. The value is not the label itself; it is the discipline of defining scope, evidence, owner, and decision consequence before the team acts.", "items": [] }, { "key": "usage", "title": "役立つ場面", "text": "Reference Customer Backlog Rate affects priorities, resource allocation, communication, and accountability. Priority | Clarifies what matters now | Prevents scattered execution Ownership | Makes the responsible team explicit | Reduces handoff ambiguity Evidence | Connects the concept to observable facts | Keeps decisions from becoming opinion-driven", "items": [ "Priority | Clarifies what matters now | Prevents scattered execution", "Ownership | Makes the responsible team explicit | Reduces handoff ambiguity", "Evidence | Connects the concept to observable facts | Keeps decisions from becoming opinion-driven" ] }, { "key": "usage", "title": "使い方のポイント", "text": null, "items": [ "Define the scope before comparing alternatives.", "Separate facts, assumptions, and open questions.", "Tie the concept to a decision, not only to a vocabulary explanation.", "Review the definition when the customer, market, or operating context changes." ] }, { "key": "drivers", "title": "何が数字を動かすか", "text": "Reference Customer Backlog Rate changes because the underlying operating drivers change. Volume | More or fewer units, users, customers, or transactions | Explains scale effects Mix | Change in segment, plan, product, or channel composition | Explains quality of growth or decline Efficiency | Better conversion, retention, cost control, or process discipline | Explains operating improvement", "items": [ "Volume | More or fewer units, users, customers, or transactions | Explains scale effects", "Mix | Change in segment, plan, product, or channel composition | Explains quality of growth or decline", "Efficiency | Better conversion, retention, cost control, or process discipline | Explains operating improvement" ] } ], "misunderstandings": [ { "key": "misunderstandings", "title": "判断するときの注意点", "text": "Do not read Reference Customer Backlog Rate alone. Compare with companion metrics before changing budget or targets. Check whether the movement came from real performance or definition drift. Avoid optimizing the metric in a way that harms customer quality or long-term value.", "items": [ "Compare with companion metrics before changing budget or targets.", "Check whether the movement came from real performance or definition drift.", "Avoid optimizing the metric in a way that harms customer quality or long-term value." ] }, { "key": "misunderstandings", "title": "よくある誤解 / 落とし穴", "text": null, "items": [ "Misconception | It is only a dictionary term | In practice it should change a decision or operating behavior", "Misconception | Everyone means the same thing | Teams should write the scope and assumptions", "Misconception | It is always positive | The term can reveal constraints, risks, or reasons not to act" ] } ], "examples": [ { "key": "examples", "title": "最小例", "text": "A team discussing Reference Customer Backlog Rate first writes the decision it needs to make, the evidence it has, and the trade-off it is willing to accept. After that, the team compares options and records why one path is better for the current quarter. This makes the term useful in planning, review, and handoff conversations.", "items": [] } ], "comparisons": [ { "key": "comparisons", "title": "似ている言葉との違い", "text": "Compare Reference Customer Backlog Rate with adjacent concepts before deciding. Reference Customer Backlog Rate | Current concept | Use when the team needs the primary decision lens Adjacent metric or framework | Supporting lens | Use when the team needs evidence or process detail General vocabulary | Broad explanation | Use only for orientation, not final decision-making", "items": [ "Reference Customer Backlog Rate | Current concept | Use when the team needs the primary decision lens", "Adjacent metric or framework | Supporting lens | Use when the team needs evidence or process detail", "General vocabulary | Broad explanation | Use only for orientation, not final decision-making" ] }, { "key": "related_metrics", "title": "一緒に見る指標", "text": "Read Reference Customer Backlog Rate together with metrics that explain quality, scale, and risk. Growth metric | Shows direction | Explains whether the trend is improving Efficiency metric | Shows cost or effort | Explains whether the result is economical Risk metric | Shows volatility or concentration | Explains whether the result is durable", "items": [ "Growth metric | Shows direction | Explains whether the trend is improving", "Efficiency metric | Shows cost or effort | Explains whether the result is economical", "Risk metric | Shows volatility or concentration | Explains whether the result is durable" ] } ], "faq": [ { "question": "When should I use Reference Customer Backlog Rate?", "answer": "Use it when the team needs to decide scope, priority, owner, or trade-off, not when it only needs a short definition." }, { "question": "What makes Reference Customer Backlog Rate useful in practice?", "answer": "It becomes useful when it is tied to evidence, a decision owner, and a concrete next operating choice." }, { "question": "What should I avoid?", "answer": "Avoid using the term as a label without clarifying assumptions, boundaries, and how success will be judged." } ] }, "sources": { "source_refs": [ "concept:reference-customer-backlog-rate:en-US", "concept:reference-customer-backlog-rate:ja-JP", "core-term-page-1000-06:concept:reference-customer-backlog-rate" ], "visible_sources": [ { "label": "Principles of Marketing (Open Textbook Library)", "url": "https://open.umn.edu/opentextbooks/textbooks/principles-of-marketing", "kind": "tier_s" }, { "label": "Principles of Management (OpenStax)", "url": "https://openstax.org/details/books/principles-management", "kind": "tier_s" } ] }, "related_terms": [ { "topic_id": "f56f8133-267a-56e4-974a-55a24e82e390", "canonical_slug": "reference-customer-stability-score", "canonical_url": "https://core.yogoq.com/en-US/core/reference-customer-stability-score", "title": "Reference Customer Stability Score", "relation_type": "next" }, { "topic_id": "022d8a26-6602-50a6-ba49-6be93199021d", "canonical_slug": "reference-customer-signal-coverage", "canonical_url": "https://core.yogoq.com/en-US/core/reference-customer-signal-coverage", "title": "Reference Customer Signal Coverage", "relation_type": "used_together" }, { "topic_id": "23ae1de6-61ee-53fd-b317-765149fc3f16", "canonical_slug": "account-expansion-risk-score", "canonical_url": "https://core.yogoq.com/en-US/core/account-expansion-risk-score", "title": "Account Expansion Risk Score", "relation_type": "used_together" }, { "topic_id": "bbdae946-f09f-579c-9eef-751a6314db34", "canonical_slug": "account-expansion-signal-coverage", "canonical_url": "https://core.yogoq.com/en-US/core/account-expansion-signal-coverage", "title": "Account Expansion Signal Coverage", "relation_type": "used_together" } ], "quality": { "quality": "reviewed", "publication_status": "published_reviewed", "source_count": 2, "last_reviewed_at": "2026-05-16T00:00:00.000Z", "trust_policy_version": "core-trust-policy-v1-2026-06-22" }, "limitations": { "policy_version": "core-trust-policy-v1-2026-06-22", "professional_advice_boundary": "reference_only_not_professional_advice", "text": "This page is reference information for research and learning. For accounting, legal, finance, health, security, or other individual decisions, confirm against primary sources or qualified professionals.", "items": [ "Public pages support general understanding and practical context; they are not professional advice for individual cases.", "Fast-changing information such as regulations, accounting standards, prices, product specs, and legal requirements should be checked against primary sources before final decisions.", "Even when AI-assisted drafting or audit is used, publication relies on quality gates and human-readable evidence." ] } }