Hi Praveena
In principal it should work out when you follow the process properly but since you already mention people ignoring CSOL this doesn't always work out in reality.
So in reality it's always advised to keep an eye on the situation and the actual release (the team[s] involved should do this).
CSOL is a tool to help the teams out, if they ignore it while they shouldn't or they just ignore it and do not take it into account then that's their responsibility.
In terms of tracking you can leverage /TMWFLOW/TRMO and in terms of releases I would advice for the productive release to use "status dependent & selective import" strategy so the operator gets a list of transport requests before the release takes place and the change documents are only imported if they have a specific status (according to your transport strategy customizing -> status dependant & selective import).
That way it's more secure and if something shouldn't pass to production, it can still be deselected.
Downgrade protection can also help to alert on possible issue situations.
If the order then turns out wrong, the teams in question will need to figure out what is in the wrong order and the operator can even still manually import those requests in the right order (you can always go outside of CHARM if really needed).
It's not really bulletproof because in the end it also still relies on humans 
. They can have quirks from time to time 
.
Kind regards
Tom