CONCORD has a standard response time really , an interval in a system based on its security status . For Uedama and other 0 . 5 s , it ' s roughly 17 seconds . That means when you go GCC , after 17 seconds , CONCORD appears , jams you out , kills you seconds later . If an instance of CONCORD already exists in a system , it takes an extra 6 seconds for that instance to respond . I believe this accounts for them ' warping ' from one point in the system to you . In the case of Uedama , we ' re now at 23 seconds . Here ' s an exampleBoney goes to Uedama immediately after downtime . Find a mackinaw . Shoots mackinaw . ~ 17 seconds later , CONCORD shows up and kills Boney . Afterward , Boney reships to a catalyst . Boney goes and finds a hulk . Boney shoots hulk , 23 seconds later , CONCORD arrives , kill Boney . Later , Boney and Andy want to kill a mackinaw . They both land on the mackinaw and shoot . Because Boney shot first , the existing CONCORD spawn is coming for him . It will arrive in 23 seconds . There is not a CONCORD spawn for Andy , however , so a new CONCORD instance spawns and will arrive in 17 seconds . After shooting for 17 seconds , the CONCORD arrives and kills Andy . 6 seconds after that 23 seconds after Boney shoots , CONCORD arrives and kills Boney . So ' prepping ' a system refers to having 1 CONCORD spawned for each member in the fleet this is often done during GCC timer , or at least as many CONCORD spawned as it will take people to kill the target may be less than fleet size . I really don ' t give a fuck about your opinion of my blackbox spreadsheet , because you are opining against an expert , and expertise trumps opinions every single fucking time . Go look at my killboard or something , jfc .