diff --git a/docs/assets/coretime/coretime-collation-bulk.png b/docs/assets/coretime/coretime-collation-bulk.png
new file mode 100644
index 000000000000..6d725a8787b1
Binary files /dev/null and b/docs/assets/coretime/coretime-collation-bulk.png differ
diff --git a/docs/assets/coretime/lastic-assign-core.png b/docs/assets/coretime/lastic-assign-core.png
new file mode 100644
index 000000000000..6b5b03034765
Binary files /dev/null and b/docs/assets/coretime/lastic-assign-core.png differ
diff --git a/docs/learn/learn-guides-coretime-parachains.md b/docs/learn/learn-guides-coretime-parachains.md
index 55a04fa57a6e..9bba736b792a 100644
--- a/docs/learn/learn-guides-coretime-parachains.md
+++ b/docs/learn/learn-guides-coretime-parachains.md
@@ -77,6 +77,17 @@ sync with the specified relaychain.
 
 ```
 
+Now, you can purchase bulk coretime on [Coretime chain](./learn-guides-coretime-marketplaces.md) and
+assign the purchased core to the registered `ParaID`. The snapshot below is from
+[Lastic](https://test.lastic.xyz/) interface.
+
+![coretime-bulk-assign-lastic](../assets/coretime/lastic-assign-core.png)
+
+After successful assignment of the core, the `adder-collator` logs show new collations at regular
+intervals, gradually incrementing the state by `2`.
+
+![coretime-collation-bulk](../assets/coretime/coretime-collation-bulk.png)
+
 ## Run a Parachain with On-demand Coretime
 
 The first step is to register a `ParaID`for the on-demand parachain. This can be done through