Don't do it if you can avoid, especially if company culture is to treat rough estimation as a promised deadline.
If you can't avoid giving estimation, try to pad it as much as possible, add every single uncertainty to the task list, and estimate very conservative. Add enough time for testing, communication, work on change requests.
And even after the original estimate is approved / published be sure to communicate updates to the estimation after every single change request, question, bug, new insight.
And if something by chance take less time than estimated, make sure not to decrease estimation, but to use it as a buffer.
If you can't avoid giving estimation, try to pad it as much as possible, add every single uncertainty to the task list, and estimate very conservative. Add enough time for testing, communication, work on change requests.
And even after the original estimate is approved / published be sure to communicate updates to the estimation after every single change request, question, bug, new insight.
And if something by chance take less time than estimated, make sure not to decrease estimation, but to use it as a buffer.