We have been down this road in the past. We eventually landed on only using sc_task on complex workflows that required multiple fulfillment tasks. For anything that was simple we dropped the sc_task and just assigned the RITM to a group for fulfillment. All the "simple" requests have a "Simple Request" workflow that standardizes things. This has made things very simple and everyone is happy because it reduced complexity. Having an RITM with one related sc_task confused requestors as well as fulfillers (no matter how many times I explained the data structure). Somehow people don't seem to be confused when there are multiple sc_task to an RITM. Go figure... Hope this helps!
