Start with a comparable lid-closed baseline
Record the charge, time, power connection, external display state, and attached accessories before closing the lid. Reopen it after a similar interval and record the same details. Repeat across several ordinary sessions. A handful of comparisons helps distinguish a pattern from a one-off event such as a large sync or an interrupted sleep.
If the Mac is warm after being closed, or the display is visibly active, it likely needs a closer wake or sleep investigation. If it is cool but charge has fallen, do not assume an app is solely responsible until you compare logs and conditions.
Test the dock and display setup
External displays, hubs, storage, network adapters, and input devices are meaningful variables. For a controlled test, disconnect nonessential accessories and use the same location and network. Then compare one lid-closed sleep with the baseline. Reintroduce devices one at a time in later sessions if the result improves.
A MacBook used with an external display may be intended to stay awake in a different operating setup. Check the actual display and power state before deciding that a closed lid represents ordinary portable sleep. The useful question is whether the configured behavior matches what you expect from that session.
Check for apps and wake activity
Before the test, inspect Activity Monitor's Energy pane for apps listed as preventing sleep and for unusually active processes. This is a starting point, not a historical report of the whole closed-lid period. Quit only an app you recognize and can safely close, then recheck one comparable session.
WattGuard shows sleep and wake counts for the selected period alongside charge changes. Compare these records with the times you closed and opened the lid. The reported wake reason is a clue for the next controlled test, not an allocation of battery use to a single component.
Avoid broad power-setting changes
Do not apply generic hibernation or power-management commands copied from a forum as the first response. They can change behavior without proving why the drain occurred. Preserve a simple record of baseline, one change, and recheck. If the issue persists in minimal-accessory tests, use Apple Diagnostics or Apple Support with those observations.