Be prepared! The workload is dropped up to 6 weeks out. Know what's coming long before it gets here. Have things mapped early. I am an advocate for pre-tieing as much as you can. Have your adjacencies printed out and make sure your GMTLs know their areas and have a map, as well. They should be managing their DBOs workload as far as Revisions and Salesplans are concerned, but the more you're aware of it, the better you'll be about managing your workload too. TWT (transition workload tool) is a major asset and helps track the weekly progress of what is tied and isn't.
The sad reality is; TWT is going away. The company wants us to use the Set Workload Tool in MyWork as our primary tool for pre-ties, tieing and making sure the workload is done. It may be the single most frustrating tool to date. Definitely designed by an engineer and had zero user feedback in development (seriously, it's a mess of a tool).
Work with the Inbound lead to capture and sort transition whenever possible. Work with area GMTLs to let them know big transitions are coming and that they need to prepare (work out d-code, do EOL and PC batches, and complete pricing workload early...) If they help you before you get there, half the frustration of getting rid of stuff will be done. Setting a nearly empty aisle is always better than setting an aisle full of clearance and then having to find a place for that clearance.
Know who your strong setters are and who can work independently. If you aren't around to "lead", knowing you have a team that can be self-lead is important. Then when you are around, you can spend time with the weaker players to get them up to that level. I'm a GM2, so my time is not in setting, it's in planning and delegating. I check on my transition team, but I have a department to manage too. My hours are under GM, not presentation, for that reason. I try to be as prepared as much as I can, so I'm not surprised. Check Early Set notes on workbench as well and keep up with the Store Weekly and Addendums. There is a lot of useful information in them for what's coming and what might have been overlooked.
Luckily I don't have a department but who knows that can change soon. EOL batches is something that I tend to forget and will have to utilize going forward.
