diff --git a/docs/reference/joins-and-exits/pool-exits.md b/docs/reference/joins-and-exits/pool-exits.md
index 17dd0881..46725136 100644
--- a/docs/reference/joins-and-exits/pool-exits.md
+++ b/docs/reference/joins-and-exits/pool-exits.md
@@ -52,6 +52,9 @@ Let's say that you want to allow a 1% slippage. After computing how many tokens
 ### `userData`
 
 userData is a highly versatile field; as such, it needs to be encoded for its specific use case. For exits, userData encodes a `ExitKind` to tell the pool what style of exit you're performing. Since pool types are customizable, not every pool necessarily uses the same `ExitKind`, so it's important to keep track of what each pool type can handle.
+::: info 
+When encoding `userData` for pools that include their own BPT as part of the pool's tokens, the BPT are not included in the `userData`.
+:::
 
 #### WeightedPool ExitKinds
 
diff --git a/docs/reference/joins-and-exits/pool-joins.md b/docs/reference/joins-and-exits/pool-joins.md
index 5a457848..79e7bb5a 100644
--- a/docs/reference/joins-and-exits/pool-joins.md
+++ b/docs/reference/joins-and-exits/pool-joins.md
@@ -52,6 +52,9 @@ Let's say that you want to allow a 1% slippage. After computing how many tokens
 ### `userData`
 
 userData is a highly versatile field; as such, it needs to be encoded for its specific use case. For joins, userData encodes a `JoinKind` to tell the pool what style of join you're performing. Not every pool uses every `JoinKind`, so it's important to keep track of what each pool type can handle.
+::: info 
+When encoding `userData` for pools that include their own BPT as part of the pool's tokens, the BPT are not included in the `userData`, except for `INIT` joins where they need to be included.
+:::
 
 #### WeightedPool JoinKinds