When I build a solution for a repetitive process, here is how I handle it.  

• Have 1 list that triggers the process, in this case it is your intake form list.
• Build a template list that has all the steps to your processes, as well as the order and any other details.  In your case you'd also have the subject that the steps go with.
• The 3rd list will be the workflow task list.  This is how you'll track the actual completion for each step related to each intake form.

Whenever a new intake form is submitted, your workflow will query the template list for all the tasks that have the same subject.  It will then get create a task for each of those items (steps) from the template list in the workflow task list.  Then you'll have all your tasks for that subject/intake form.  If you wanted to update some value on the intake form to track the progress, you could have a 2nd workflow on the task list that could do that as the tasks are completed.  

Brendan, Sorry for the delay in response.  This looks like a great idea and I am about to try it.  But, quick question -- I just came across a SharePoint web part called "Tasks".  Do you think this would help, or should I just proceed with your first explanation using Custom List? 

Do you mean using a task list as the template list?  You can if you want.  A task list is just a special type of custom list. 

Hi,

I have created an "Intake"  list and a "Task Steps" list per the suggestion above.   After I query the "Task Steps" for all the tasks with the same subject, how do I create a task for each of these steps in the workflow task list?  And, once I do create a task for each step in the workflow task list, it seems like all of the tasks for all the requests will be mixed together in the workflow task list.  How do I track only the tasks for 1 specific request?  

When you query the template task list, store the results in a collection variable.  Normally I store the ID's of the matching tasks because I need to do a 2nd lookup when I create the actual tasks. After you get your collection of tasks IDs, you use a For Each action to go through each item in the collection.  So the For Each would grab the first task ID from the collection.  I would then query my template list again for that task and get all the information I would need to create the new task: subject, comments, etc.  Store those fields in variables.  Then the next action would be to create your workflow task using the information in the variables from your task template.  The For Each will loop through each task in the collection and create a task for it.

When you create a workflow task, the system creates a related content field that associates the task to the item that generated it.  That's how you will know which tasks go with which item.

Susie Shaffer‌, the June Mission was based on your question.  There have been a number of good responses you should check out to see if any help with your scenario.