DespiteEven though we always share the weekly report on time, none of the members of the googleGoogle team give a responsemembers have responded to us. Neither they tryThey have not even attempted to exploresearch for any error categories in Pass Files, nor tryhave they tried to exploreexplore the errors mentionmentioned in the segment report. However,This is in spite of the fact that we always share reports on the basis of each error category wisecategory-wise tab, thatwhich makes it easy to detect incorrect marking. Even, even then they are not trying. Is itthat right? May bePerhaps the team has so muchsuch a "busy schedule" that they don'tcan't even havespare an single hour to analyze anya single report. ifIf they wouldn'twon't explore, then how can we couldpossibly reduce all error categories in the coming weeks.weeks? Although we have all the details, we still don't have the exact root causecauses to discuss for any project failure/increased error categories during the quality calls. If they aren't even being proactive for any report analysis or notand don't even try to explore errors in the Fail/Pass file, why we should we share the AB_Weekly Segment report? with them? Most of the time, Charu tells us that we should arbitrate thisX error in thatY project so that error gets reverted. Shouldn't this work be done on our end? We have sufficientenough data by which we canto take preventionboth preventive and cure at the same timecurative measures simultaneously, can'tdon't we? I have always tried to provide every possible detail so that we can reduce error categories, but it can'tcannot be done without the support of the team. So it's my humbleIn light of these observations, I humbly request pleasethat you look into this matter and try to sort out these issues at earliestas soon as possible.