Does Asana or anyone in the community have a good handover template or checklist?
One thing that seems to be a gap in our PMO is a good handover strategy. Since we do not want to own the maintenance of all projects post-go live, we need to sure this stage after the full PM lifecycle.
Would love industry best practices around how this handled and tracked elsewhere.
@Stephanie_Rebels Welcome to the forums. A handover checklist from the Project Team to Operations would vary based on industry and practices within your organization. Some basic items would be to complete any documentation (reference materials, SOPs, design docs, etc.). These docs would then be handed over to Ops. This could be done either during a meeting between the Project and Ops teams or provided beforehand for review then discuss any questions or gaps in the documentation during a handoff meeting.
Another option (or in addition to) is to have some training videos created by the Project Team that would demo whatever was created. The videos could be used for troubleshooting in the future and/or training new staff when they are onboarded.
@Stephanie_Rebels welcome to the Forum 
And welcome back @Ron_Sanga , it looks like we haven’t heard from you in a while!
I agree with Ron’s approach, and just to add to it, I recommend noting down everything that was amiss in previous handovers. If any detail has created an issue, that marks a process that needs fixing, so the starting point would be analysing what went right and wrong in any past handover instances, and building from there.