diff --git a/docs/_static/ARC_Workflow.jpg b/docs/_static/ARC_Workflow.jpg
new file mode 100644
index 0000000..a7032df
Binary files /dev/null and b/docs/_static/ARC_Workflow.jpg differ
diff --git a/docs/index.rst b/docs/index.rst
index 2fca175..70b03ba 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -16,6 +16,7 @@ submitted.
 Contents:
 
 .. toctree::
-   :maxdepth: 2
+    :maxdepth: 2
 
-   arc_names
+    workflow
+    arc_names
diff --git a/docs/workflow.rst b/docs/workflow.rst
new file mode 100644
index 0000000..9892107
--- /dev/null
+++ b/docs/workflow.rst
@@ -0,0 +1,31 @@
+Workflow
+========
+
+The ARC teams does the investigation work on the
+`initiatives <https://docs.fedoraproject.org/en-US/cpe/initiatives/>`_ proposed
+to the CPE team.
+
+Here belows is a schemas explaining its workflow.
+
+.. image:: _static/ARC_Workflow.jpg
+        :target: _images/ARC_Workflow.jpg
+
+The workflow can be summarized as follow:
+
+* Initiatives are submitted to CPE's project owner who will review them.
+* If the initiatives are deemed in scope for the CPE team, they will be accepted.
+* The CPE team will prioritize the initiatives against each other, leading to a
+  prioritized backlog of initiatives.
+* The ARC team will take the backlog in that order and for each initiative it will:
+
+  * Reach out to the CPE team and its communities (as needed) for input on potential
+    solution to implement the initiative
+  * Do the investigation/prototyping
+  * Report to the CPE team and its communities (as needed) its finding together
+    with a recommendation
+
+* The initiative will then be scheduled for the next prioritization meeting with
+  its stakeholders.
+* When the initiative is scheduled, the CPE team will take it and implement it
+  using the information, experiment and prototypes gathered and built by the ARC
+  team.