How detailed should my issue report be for a campaign problem?

An issue report should be detailed enough to clearly explain what happened, where it happened, and how it affected the assignment. The goal is to provide enough useful information that the campaign team can understand the problem without needing to guess at the missing details.

A strong report usually includes the type of issue, the location or route area involved, when it happened, and what part of the assignment was affected. If the issue prevented work from being completed or changed how the task had to be handled, that should be explained clearly as well. More detail generally makes review easier, as long as the report stays clear and relevant.

Vague reports can make it harder to investigate the problem or determine what needs to happen next. Workers do not need to write excessively long explanations, but they should include enough context that someone reviewing the campaign can understand the situation accurately.

Overall, issue reports should be clear, specific, and detailed enough to show what happened and why it mattered to the assignment. That helps the campaign record stay accurate and makes follow-up more effective.