BIND plan vs package - shop standard?

I have read the manuals more than once and I still get this wrong in meetings. We package at collection level but install wants BIND PLAN during promote.

What does your shop do for COBOL batch and why?

Packages in QA and prod collections. Developers bind to a sandbox collection on dev. Plan only rebounds on release cutover.

Always qualify collection in BIND. Someone bound to NULLID in prod years ago and we still talk about it in onboarding.