Adding children in same process - workflow optimization

[mateoc15]

I have a data model with Visitors, Visits for those visitors, and Visit Services which are items the visitor needs during their visit. 

I'd love to make this into a single workflow. Create a new visitor, add a visit (all automatic fields like timestamp and I assume a ref to the Visitor record, but nothing for the user to enter), and then prompt the user to add Visitor Service records from a list of Services in an existing table.

I've gotten good with single tables and viewing refs, but not adding child records. What's the best way to make this flow easily for the users? 

[TeeSee1]

You may want to try this and see if you like it.

[mateoc15]

This definitely moves me in the right direction.  So when I add a new Visitor , I always want to add a new Visit, then user chooses Visit Services to attach to the Visit (multiple select kind of thing from the Services table).

Visitor 1:M Visits M:M Visit Service

Visit IsAPartOf Visitor (since there's no visit without a visitor)
Visit Service IsAPartOf Visit (since there's no visit service without a visit)

In the UI I'm still struggling to see how the user flows through this process.  Is one view type more ideal than another?  Form, something else?

[TeeSee1]

Just plain old system gen'd forms give you a NEW button to add a child record, then a grand child record associated to the child record.

Subsequent offspring records can be added by an Add button

[Aurelien]

Hi @mateoc15 

Visually, this is where to set this option: