{
  "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/business-continuity-planning",
    "slug": "business-continuity-planning",
    "locale": "en-US"
  },
  "summary": {
    "schema_version": "core-reviewed-term-summary-v1",
    "term_id": "4ad4bace-2386-58d0-a02a-bc2814cd69bf",
    "canonical_slug": "business-continuity-planning",
    "canonical_url": "https://core.yogoq.com/en-US/core/business-continuity-planning",
    "locale": "en-US",
    "display_name": "Business Continuity Planning",
    "english_name": null,
    "abbreviation": "BCP",
    "short_definition": "Business Continuity Planning is the planning practice that decides which business activities must continue, at what minimum level, and through which recovery path during disruption. It is used for minimum viable continu…",
    "quality": "reviewed",
    "publication_status": "published_reviewed",
    "version": "core-reviewed-term-summary-v1",
    "last_reviewed_at": "2026-05-14T00:00:00.000Z",
    "sources_count": 2,
    "limitations_key": "core-trust-policy-v1-2026-06-22"
  },
  "content": {
    "definition": {
      "key": "definition",
      "title": "一言でいうと",
      "text": "Business Continuity Planning is the planning practice that decides which business activities must continue, at what minimum level, and through which recovery path during disruption. It is used for minimum viable continuity plan by reading business impact, recovery time objective, recovery point objective, staffing fallback, and supplier readiness and deciding what must be protected first when normal operations cannot continue.",
      "items": []
    },
    "formula": null,
    "boundary": {
      "key": "boundary",
      "title": "含めるもの / 含めないもの",
      "text": "Keep the inclusion and exclusion rules stable so decisions can be compared over time. Include | critical activities, minimum service level, recovery objectives, owner roster | These decide what survives the disruption Exclude | nice-to-have projects, unranked task lists, outdated contact trees | They slow action when capacity is limited Define explicitly | RTO, RPO, manual workaround, external communication owner | The plan must say what to do before normal operations return",
      "items": [
        "Include | critical activities, minimum service level, recovery objectives, owner roster | These decide what survives the disruption",
        "Exclude | nice-to-have projects, unranked task lists, outdated contact trees | They slow action when capacity is limited",
        "Define explicitly | RTO, RPO, manual workaround, external communication owner | The plan must say what to do before normal operations return"
      ]
    },
    "usage": [
      {
        "key": "meaning",
        "title": "意味",
        "text": "Business Continuity Planning is a practical concept for improving operating, risk, and organization decisions. It makes business impact, recovery time objective, recovery point objective, staffing fallback, and supplier readiness visible under shared assumptions so teams can decide what must be protected first when normal operations cannot continue. Without clear business continuity planning boundaries, owners, and review cadence, teams can improve one local view while moving business continuity planning pressure elsewhere.",
        "items": []
      },
      {
        "key": "usage",
        "title": "役立つ場面",
        "text": "Business Continuity Planning changes decisions by turning business impact, recovery time objective, recovery point objective, staffing fallback, and supplier readiness into evidence for where scarce capacity and budget should go. It sets boundaries so improvement, control, resilience, and customer impact can be weighed in the same review. It makes what must be protected first when normal operations cannot continue operational by naming owners, triggers, and review cadence instead of leaving the concept as a discussion point.",
        "items": [
          "Business Continuity Planning changes decisions by turning business impact, recovery time objective, recovery point objective, staffing fallback, and supplier readiness into evidence for where scarce capacity and budget should go.",
          "It sets boundaries so improvement, control, resilience, and customer impact can be weighed in the same review.",
          "It makes what must be protected first when normal operations cannot continue operational by naming owners, triggers, and review cadence instead of leaving the concept as a discussion point."
        ]
      },
      {
        "key": "usage",
        "title": "使い方のポイント",
        "text": null,
        "items": [
          "Rank activities by customer, cash, legal, safety, and reputation impact.",
          "Define minimum service levels before writing long recovery procedures.",
          "Assign owners for people, workplace, systems, supplier, and communication workstreams.",
          "Run scenario exercises that prove the plan can be used under stress.",
          "In every Business Continuity Planning review, record the customer impact, risk tradeoff, accountable owner, and next review date alongside the metric movement."
        ]
      },
      {
        "key": "drivers",
        "title": "何が数字を動かすか",
        "text": "Breaking the topic into drivers shows which operating action is likely to move the result. Business impact | Higher customer or cash impact raises priority | Use scenario loss, not only department preference Recovery dependency | Missing data, people, or supplier capacity delays restart | Test the weakest dependency Plan freshness | Stale contacts and tools break execution | Review after org, vendor, or system changes",
        "items": [
          "Business impact | Higher customer or cash impact raises priority | Use scenario loss, not only department preference",
          "Recovery dependency | Missing data, people, or supplier capacity delays restart | Test the weakest dependency",
          "Plan freshness | Stale contacts and tools break execution | Review after org, vendor, or system changes"
        ]
      }
    ],
    "misunderstandings": [
      {
        "key": "misunderstandings",
        "title": "よくある誤解 / 落とし穴",
        "text": null,
        "items": [
          "A thick continuity document is weak if teams have not practiced the handoffs.",
          "Restoring systems is not enough when staffing or supplier capacity is unavailable.",
          "Every activity cannot be equally critical during a severe disruption."
        ]
      }
    ],
    "examples": [
      {
        "key": "examples",
        "title": "最小例",
        "text": "A subscription company ranks billing, support intake, and security response above new feature releases. It defines a minimum viable continuity plan, assigns owners, tests a cloud-region outage, and finds that supplier notification is missing. The plan is revised before the next exercise. In this example, Business Continuity Planning is treated as an operating decision that connects constraints, ownership, measurement, and review, so the team can reassess the change using the same evidence later.",
        "items": []
      }
    ],
    "comparisons": [
      {
        "key": "comparisons",
        "title": "似ている言葉との違い",
        "text": "Operational resilience planning | Starts from service impact tolerance | BCP translates continuity priorities into practical workstreams Disaster recovery | Restores technology | BCP also covers people, suppliers, workplace, and communications Enterprise risk management | Prioritizes risk exposure | BCP prepares the operating response to selected disruptions",
        "items": [
          "Operational resilience planning | Starts from service impact tolerance | BCP translates continuity priorities into practical workstreams",
          "Disaster recovery | Restores technology | BCP also covers people, suppliers, workplace, and communications",
          "Enterprise risk management | Prioritizes risk exposure | BCP prepares the operating response to selected disruptions"
        ]
      }
    ],
    "faq": [
      {
        "question": "What should be in the first version?",
        "answer": "Critical activities, minimum service levels, recovery objectives, owners, dependencies, and communication triggers."
      },
      {
        "question": "How is BCP tested?",
        "answer": "Use realistic scenarios that force teams to use fallback owners, manual paths, and supplier communication."
      },
      {
        "question": "Who owns BCP?",
        "answer": "Executive ownership is needed, but each critical activity needs a named operating owner."
      }
    ]
  },
  "sources": {
    "source_refs": [
      "concept:business-concept-0213:en-US",
      "concept:business-concept-0213:ja-JP",
      "manual_promotion_packet:synthetic-business-concepts-batch3-2026-04-28"
    ],
    "visible_sources": [
      {
        "label": "Principles of Management (OpenStax)",
        "url": "https://openstax.org/details/books/principles-management",
        "kind": "tier_s"
      },
      {
        "label": "Wikipedia reference: Business Continuity Planning",
        "url": "https://en.wikipedia.org/wiki/Business_continuity_planning",
        "kind": "supplemental"
      }
    ]
  },
  "related_terms": [
    {
      "topic_id": "14819475-3f6b-5bb7-a400-b81abc5e1885",
      "canonical_slug": "enterprise-risk-management",
      "canonical_url": "https://core.yogoq.com/en-US/core/enterprise-risk-management",
      "title": "Enterprise Risk Management (ERM)",
      "relation_type": "used_together"
    },
    {
      "topic_id": "4a7b1b00-8946-55da-aa15-d82d45c7a650",
      "canonical_slug": "service-recovery-design",
      "canonical_url": "https://core.yogoq.com/en-US/core/service-recovery-design",
      "title": "Service Recovery Design",
      "relation_type": "used_together"
    },
    {
      "topic_id": "ab1f0540-c8c2-5299-bddb-850807e0c369",
      "canonical_slug": "operational-resilience-planning",
      "canonical_url": "https://core.yogoq.com/en-US/core/operational-resilience-planning",
      "title": "Operational Resilience Planning",
      "relation_type": "related"
    }
  ],
  "quality": {
    "quality": "reviewed",
    "publication_status": "published_reviewed",
    "source_count": 2,
    "last_reviewed_at": "2026-05-14T00: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."
    ]
  }
}
