diff --git a/SAS/ResourceAssignment/OTDBtoRATaskStatusPropagator/doc/otdb_to_ra_task_status_propagator.md b/SAS/ResourceAssignment/OTDBtoRATaskStatusPropagator/doc/otdb_to_ra_task_status_propagator.md
index 479239be09639c7c39b51a51c9c059248ef76eec..367ee745cf7a78801bbea29adbdd871a6c2014dd 100644
--- a/SAS/ResourceAssignment/OTDBtoRATaskStatusPropagator/doc/otdb_to_ra_task_status_propagator.md
+++ b/SAS/ResourceAssignment/OTDBtoRATaskStatusPropagator/doc/otdb_to_ra_task_status_propagator.md
@@ -12,9 +12,24 @@ Due to historical reasons Lofar tracks it's tasks in three different databases:
 -  Jorrit Schaap schaap@astron.nl
 
 ### Overview
-- *Add a diagram*
-- *Add a link to the overview diagram*
-- *Add a link in the overview diagram to link back to this documentation*.
+
+TODO: do we want diagrams like this? If so, extend diagram with full sequence.
+
+@startuml
+title OTDB to RA task status propagator sequence diagram
+
+participant lofar.otdb.notification as lon
+control "OTDB to RA task status propagator" as otrtsp
+participant lofar.ra.command as lrc
+
+note over lon
+qpid exchange
+end note
+
+note over lrc
+qpid exchange
+end note
+@enduml
 
 - - -