diff --git a/doc/interop-test-descriptions.md b/doc/interop-test-descriptions.md
index 15ba013ca54..4a361c7185f 100755
--- a/doc/interop-test-descriptions.md
+++ b/doc/interop-test-descriptions.md
@@ -1152,12 +1152,12 @@ Procedures:
       }
     }
     ```
-2. After getting a response, client waits up to 5 seconds to receive a OOB load 
-report that matches the requested load report in step 1. To wait for load 
-report, client may inject a callback to the custom LB policy, or poll the result
-by doing empty unary call that carries a reference, e.g. using 
-CallOptions, that will be filled in by the custom LB policy as part of the 
-`OrcaOobReportListener` API.
+2. After getting a response, client waits up to 10 seconds (or a total of 30s
+for the entire test case) to receive an OOB load report that matches the
+requested load report in step 1. To wait for load report, client may inject a
+callback to the custom LB policy, or poll the result by doing empty unary call
+that carries a reference, e.g. using CallOptions, that will be filled in by the
+custom LB policy as part of the `OrcaOobReportListener` API.
 3. Then client sends: 
     ```
     {
@@ -1173,8 +1173,9 @@ CallOptions, that will be filled in by the custom LB policy as part of the
       }
     }
     ```
-4. After getting a response, client waits up to 5 seconds to receive a OOB load
-report that matches the requested load report in step 3. Similar to step 2.
+4. After getting a response, client waits up to 10 seconds (or a total of 30s
+for the entire test case) to receive an OOB load report that matches the
+requested load report in step 3. Similar to step 2.
 5. Client half closes the stream, and asserts the streaming call is successful. 
 
 ### Experimental Tests