diff --git a/docs/deep-dive-into-hyperexecute-yaml.md b/docs/deep-dive-into-hyperexecute-yaml.md
index 5ddc089e..fb6e185f 100644
--- a/docs/deep-dive-into-hyperexecute-yaml.md
+++ b/docs/deep-dive-into-hyperexecute-yaml.md
@@ -1755,25 +1755,21 @@ framework:
     - "-Dplatname=win"
 ```
 
-<!-- GENERAL ENDED-->
-
-
-<nav aria-label="breadcrumbs">
-  <ul className="breadcrumbs">
-    <li className="breadcrumbs__item">
-      <a className="breadcrumbs__link" target="_self" href="https://www.lambdatest.com">
-        Home
-      </a>
-    </li>
-    <li className="breadcrumbs__item">
-      <a className="breadcrumbs__link" target="_self" href="https://www.lambdatest.com/support/docs/">
-        Support
-      </a>
-    </li>
-    <li className="breadcrumbs__item breadcrumbs__item--active">
-      <span className="breadcrumbs__link">
-      Deep Dive into HyperExecute YAML
-      </span>
-    </li>
-  </ul>
-</nav>
+### `syncStart`
+By default, parallel tasks in autosplit or matrix mode begin execution as soon as the VM is allocated. However, in certain situations (e.g., benchmarking or comparative analysis), you may want all VMs to start tasks at the same time.
+
+To support this, HyperExecute provides the `syncStart` directive in the job YAML.
+
+```yaml
+execution:
+  syncStart: true
+```
+
+- When `syncStart` is enabled, the job ensures that all VMs are allocated and ready before starting scenario execution i.e. tests.
+- The system waits for up to 15 minutes for all required VMs to become available.
+  - If all VMs are allocated within this window → tasks start together.
+  - If some VMs are still pending after 15 minutes → the job proceeds with the allocated VMs.
+
+> This feature is supported only in [`autosplit`](/support/docs/deep-dive-into-hyperexecute-yaml/#autosplit) and [`matrix`](/support/docs/deep-dive-into-hyperexecute-yaml/#matrix) mode and not in hybrid mode
+
+<!-- GENERAL ENDED-->
\ No newline at end of file
diff --git a/docs/hyperexecute-yaml-parameters.md b/docs/hyperexecute-yaml-parameters.md
index 2229c8f4..2dd639ca 100644
--- a/docs/hyperexecute-yaml-parameters.md
+++ b/docs/hyperexecute-yaml-parameters.md
@@ -165,6 +165,7 @@ The **HyperExecute YAML** file serves as the foundational component for test exe
 | [project](/support/docs/deep-dive-into-hyperexecute-yaml/#project) | String | Segregate data at a project/repo level |
 | [slackChannel](/support/docs/deep-dive-into-hyperexecute-yaml/#slackchannel) | String | Allows you to receive notifications of your Job updates directly in your preferred Slack channel. |
 | [afterEachScenario](/support/docs/deep-dive-into-hyperexecute-yaml/#aftereachscenario) | List of Strings | Allows you to trigger your define tasks after each test scenario. |
+| [syncStart](/support/docs/deep-dive-into-hyperexecute-yaml/#execution) | Map | Ensures all VMs are ready before starting parallel tasks. |
 
 <nav aria-label="breadcrumbs">
   <ul className="breadcrumbs">