Using Pipelines to generate a Historical Status table with a start and end date/time for status changes

Will it be an issue if you don't have history? If you're ok with this going forward - a simple solution would be to: 

1. In your relationship between parent and status changes - summarize the MAX record ID# of your status change.
2. In your child table - create a new relationship to itself ( a looped relationship ) and rename the related field to 'Related Next Status Change'
3. In your Pipeline - when you create the status change record - include the value from (1) and push into into the related field from (2). 
4. In your relationship from (2) - add a summary field of 'Date Created' and rename the field to 'Next Status Change'.
5. Make a formula that does [Next Status Change] - [Date Created]

In effect what you're doing is directly relating to status changes together to where you can summarize when it leaves that status - and then calculate the gap between when it entered and then left that status. 

------------------------------
Chayce Duncan
------------------------------