# Using sub-workflows for assignments and notifications **URL:** \ **Category:** Sales Hub Tools\ **Tags:** workflows, notifications, enterprise, sales\ **Created:** [July 9, 2022, 6:38pm UTC](https://community.hubspot.com/t/using-sub-workflows-for-assignments-and-notifications/60642 "2022-07-09T18:38:21Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![hwagner](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/hwagner/32/6340_2.png) [@hwagner](https://community.hubspot.com/u/hwagner)\ **Post date:** [July 9, 2022, 6:38pm UTC](https://community.hubspot.com/t/using-sub-workflows-for-assignments-and-notifications/60642/1 "2022-07-09T18:38:21Z")
Hi Everyone, I’ve been working to optimize my workflows for scalability and encountering an issue that I should think is easy to solve, but can’t figure it out.. (I have Enterprise) **Old System:** - I had numerous individual workflows for all our form submissions that would then assign _new_ leads to team members based on Geography - Each workflow would send internal marketing emails to team members for _new_ leads, or would send a different internal email to team members for _existing_ leads. (Existing leads would include more details/personalization tokens compared to New leads). **New System:** - I created a subworkflow (Child) that only focuses on lead assignments (so I no longer have to re-make or make changes to in the different form submission workflows) **Challenge I’m facing:** - With this change, how I can now determine if the form submitted is from a _new_ or _existing_ lead? - Previously, it was simple to check if ‘Contact is unknown’, but that will no longer work.. and I can’t send the internal marketing emails until they’ve gone through the ‘child assignments’ workflow Any ideas? ---
**Author:** ![TitiCuisset](https://avatars.discourse-cdn.com/v4/letter/t/8baadc/32.png) [@TitiCuisset](https://community.hubspot.com/u/TitiCuisset)\ **Post date:** [July 12, 2022, 8:44am UTC](https://community.hubspot.com/t/using-sub-workflows-for-assignments-and-notifications/60642/2 "2022-07-12T08:44:40Z")
Hi @hwagner Thank you for reaching out and all these details! I want to tag some of our experts here - @Jnix284 @LMeert [@Bruno\_Teixeira](https://community.hubspot.com/t5/user/viewprofilepage/user-id/84940) do you have any thought for @hwagner on this? Thank you! Best Tiphaine ---
**Author:** ![jnix284](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jnix284/32/29_2.png) [@jnix284](https://community.hubspot.com/u/jnix284)\ **Post date:** [July 12, 2022, 2:31pm UTC](https://community.hubspot.com/t/using-sub-workflows-for-assignments-and-notifications/60642/3 "2022-07-12T14:31:02Z")
@hwagner there is likely to be a better suggestion from the others mentioned, but one thing I have done when I run into similar situations and have to set up a new workflow to replace one that is existing and differentiate whether someone is new or not is to set an if/then that says “if create date is after [today, the day I create the workflow]” then the contact is new, otherwise, they are existing. Then I handle potential lead revisits from those new leads through re-enrollment criteria. ---
**Author:** ![hwagner](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/hwagner/32/6340_2.png) [@hwagner](https://community.hubspot.com/u/hwagner)\ **Post date:** [July 12, 2022, 9:57pm UTC](https://community.hubspot.com/t/using-sub-workflows-for-assignments-and-notifications/60642/4 "2022-07-12T21:57:30Z")
Appreciate the reply, but that would only work if we had the ability to use a _relative_ ‘Today’ property… Otherwise, it leaves the potential for future leads created in other manners to submit this form (which is targeted to both new/existing leads). ---
**Author:** ![hwagner](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/hwagner/32/6340_2.png) [@hwagner](https://community.hubspot.com/u/hwagner)\ **Post date:** [July 13, 2022, 12:45am UTC](https://community.hubspot.com/t/using-sub-workflows-for-assignments-and-notifications/60642/5 "2022-07-13T00:45:09Z")
After some exploring, I was able to solve this! By using a combo of the ‘Owner Assigned Date’ and ‘Create Date’ ![hwagner_0-1657673045437.png](https://d2qpr2jzcazej7.cloudfront.net/original/1X/04eaea6f7e6cad342cda6cc20990f3542ed99a8c.png) ---
**Author:** ![jnix284](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jnix284/32/29_2.png) [@jnix284](https://community.hubspot.com/u/jnix284)\ **Post date:** [July 13, 2022, 12:57am UTC](https://community.hubspot.com/t/using-sub-workflows-for-assignments-and-notifications/60642/6 "2022-07-13T00:57:23Z")
I’m really glad you were able to find a solution @hwagner ! congrats 🙂