Yeah this is the use case for list view (now collection view) on the parent doctype. Alternatively you could write a bit of code that on saving the new node, orders the nodes by newest first, but with many nodes this becomes and expensive operation as you’d need to replace the sort order on each node every time (you’re moving let’s say node number 1234 and putting it at sort order 1, so 1 through 1233 need to get a new sort order and each need to be saved to the database).