problem
The rendered file is the version listeners and platforms actually receive.
Offline export, sample-rate conversion, dithering, normalization, and codec preparation can all change the final file. Small changes are enough to affect true peak, file loudness, or clipped samples.
Metering only inside the session can miss problems that appear in the rendered audio.
Open the exported WAV or final delivery file and measure integrated loudness, true peak, channel balance, and any obvious overs. Listen from the beginning and end so fades, count-ins, and tails are not missed.
If you create multiple formats, check each important version rather than assuming the first bounce represents all of them.
A post-export check should be quick but non-negotiable for masters, podcasts, and release files. It catches problems while the session is still open and easy to fix.
Meter Core can be used as the final check before delivery so the rendered file matches the intended loudness and peak behavior.