docs/git/Workflow.md

@@ -68,13 +68,13 @@ Some tips:
 
 # Concept Implementation
 
-Once a concise concept has been developed by the involved members, the status is changed to ~Implementation  and the issue assigned to the service provider's point of contact.
+Once a concise concept has been developed by the involved members, the status is changed to ~Implementation  and the issue assigned to either the project member responsible for the implementation or to the named point of contact at the service provider.
 
-This indicates to the contracted service provider (if relevant), that the concept is ready for their review and final implementation. This will include changes to data models, documentation or (rarely) code, depending on the contract with the provider.
+This indicates to the assignee, that the concept is ready for their review and final implementation. This will include changes to data models, documentation or code, depending on the contract with the provider.
 
 ## Concept Review 
 
-Should the developed concept not be concise or clear enough for the service provider to implement, the status is changed back to ~Concept and reassigned to the project group responsible for developing it. Ensure that the final commit message (for projects with squash merge commits) of the MR title adhere to the [Commit Guidelines](/docs/git/Commit-Guidelines). 
+Should the developed concept not be concise or clear enough for the assignee to implement, the status is changed back to ~Concept and reassigned to the project group responsible for developing it. Ensure that the final commit message (for projects with squash merge commits) or the MR title adhere to the [Commit Guidelines](/docs/git/Commit-Guidelines). 
 
 See [Danger Checks](/docs/git/Danger-Commit-Checks) for the automated process of checking commit messages on ASAM repositories. Github is still a WIP.