diff --git a/docs/dc-userguide.md b/docs/dc-userguide.md
index eaa2703..a70ec3a 100644
--- a/docs/dc-userguide.md
+++ b/docs/dc-userguide.md
@@ -12,14 +12,19 @@ A Target Table is a physical table, such as a SAS dataset or a Table in a databa
 Alternatives to using the Data Controller for performing data updates include:
 
 1 - Writing SAS or SQL code yourself to perform data updates
+
 2 - Asking your DBA to to perform updates (following a change mangement process)
+
 3 - Saving CSVs / data on a shared-visibility network drive and building / running jobs to perform uploads in batch
+
 4 - Opening (and therefore locking) datasets in Enterprise Guide or SAS® Table Viewer to perform direct updates
+
 5 - Building a custom web application yourself to perform secure updates
 
 Problems with the above approaches include one or more of the following:
 
  - Risk of manual error / data corruption
+ - End users requiring direct write access to critical data sources in production
  - Breaches due to unnecessary parties having access to the data
  - Inability to trace who made the change, when, and why
  - Reliance on key individuals to perform updates
@@ -29,5 +34,9 @@ Problems with the above approaches include one or more of the following:
 
 The Data Controller for SAS® solves the issues above.
 
+## How does it work?
+
+From the Editor tab, a user selects a library and table for editing. Data can then be edited directly, or a uploaded from a file.  After submitting the change, the data is loaded to a secure staging area, and the approvers are notified.  The approver (wich may also be the editor, depeneding on cconfiguration) reviews the changes and accepts / or rejects. If accepted, the changes are applied to the target table by the system account, and the history of that change is recorded.
+