diff --git a/README.md b/README.md
index 00aca51..41bfc53 100644
--- a/README.md
+++ b/README.md
@@ -11,6 +11,17 @@ This allow to handle alerting and monitoring using cron scripts + send function
 
 Then each time you want to update this repos : `elab-update` from the server 
 
-## Adding a new script : 
+## Adding a new script
 
-Take exemple on the simples scripts that are in cron.daily or cron.hourly and make your own
\ No newline at end of file
+Take exemple on the simples scripts that are in cron.daily or cron.hourly and make your own
+
+## How it works
+
+The core idea behind **Elab Update** is that when you need to introduce a new supervision script across all client servers, the workflow is:
+
+1. **Create** the script in Elab Manage and test it on a dev server
+2. **Validate** it works as expected
+3. **Introduce it properly** — with the cron job pointing to the script located in `bin/`
+4. **Deploy** — the next `myc-update` on any server where Elab Manage is correctly installed will trigger Elab Update, which updates the scripts and propagates the new ones across the entire server fleet.
+
+In short: once a new script is merged into Elab Manage, it spreads **contagiously** to all servers on their next `myc-update`.
\ No newline at end of file