Here's an idea.
When a citizen gets robbed, have the citizen store a report:
public class report{
Thief offender;
Time timeOfOccurrence;
Citizen victim;
Vector3 location;
Item[] stolenItems;
}
After the citizen gets robbed, have the citizen run around looking for a guardguard. It could be random running until the citizen finds a guardguard via Physics.OverlapSphere or any other similar method if you're not using Unity (to simulate the effect of not knowing where the guardguard is) or they could run to the nearest Guard Post where guards area guard is usually standing.
When the citizencitizen finds a guardguard, it tags them and the guardguard and citizencitizen move toward each other. Once within range, the citizencitizen gives it's report to the guardguard. The guardguard then paths to report.location and looks around until it finds report.offender.
If the guardguard doesn't find report.offender within x amount of time after report.timeOfOccurrence, the guardguard gives up and goes back to his post. The report remains, but the guard no longer actively searches for report.offender.
When the guardguard finds report.offender, they chase him down and get back report.stolenItems, incarcerate report.offender based on the value of report.stolenItems, and go back to report.victim and give them back report.stolenItems. The report is then disposed of.
This of course is a very old-fashioned representation of law enforcement. In a more modern setting, citizensa citizen could call in a report to a dispatch center who would then relay the report to a nearby lguardsguard.
In summary, I like to create classes that store information and exchange those class instances between scripts. Think of how packets of data are sent through the internet. The machines that send them might be different, but they can understand the data inside the packets, so communication is possible.