Why Share SOPs?

BFF’s modular content architecture means SOPs are independent, reusable documents. A single SOP can be linked to many tasks, which means:

  • No duplication — write once, use everywhere
  • Automatic consistency — update once, everyone gets the update
  • Cascade tracking — BFF knows every task affected by a change

Linking an SOP to Multiple Tasks

From the SOP View

  1. Open the SOP
  2. Look for the “Linked Tasks” section
  3. Click “Link to Task”
  4. Search and select additional tasks
  5. The SOP is now shared across those tasks

From the Task View

  1. Open any task
  2. Go to the Linked Content section
  3. Click “Link SOP”
  4. Search for the shared SOP
  5. Attach it

Viewing Where an SOP is Used

  1. Open the SOP detail view
  2. The “Linked Tasks” section shows every task using this SOP
  3. This also shows the team members assigned to those tasks

The Cascade Benefit

When you publish an update to a shared SOP, the Impact Cascade Engine traces every linked task and then every person and AI agent assigned to those tasks. Everyone gets notified.

Example

Your “Handling Customer Data Requests” SOP is linked to 5 tasks:

  • Email Handling
  • Customer Data Entry
  • Report Generation
  • Client Onboarding
  • Data Backup

When you publish an update to this SOP, all 5 tasks are flagged, and every team member working on those tasks receives a notification.

Linking SOPs to Other Documents

SOPs can also be linked to other controlled documents — for example, the Policy an SOP implements, or the Work Instructions that detail its steps. These doc↔doc dependency links are what the cascade walks when a linked document is republished. See Linking Documents.

Best practice: Company-wide rules (security, communication, quality) belong in the Policy tier, not in SOPs. Write SOPs for the procedures that implement those policies, link each SOP to its parent Policy, and link SOPs broadly across the tasks that follow them.