if you have an old version of the recruiting home page up, you can still manipulate the points there. i have only heard of this issue happening with changes right around the say 11:03 time (EST - cycle roll time), or after the fact. you can add and remove points from a player who has been signed by someone else, from the recruiting home page, IF the recruiting home page was up from before the guy signed. is it possible you guys had an old version of the recruiting home page up, and didn't realize the guy signed, when you put the points on? perhaps not and its a new way - or perhaps a cycle ran at a weird time, occasionally that happens as well?
anyway, unless you have an old version of the recruiting home page up, where the player in question is not yet showing up as signed, there is no way i could find for a user to fix this themselves, the slow ticket route is probably the only way. you could perhaps change the points on a different recruit, capture the request in transit, and modify the recruit id to get the change to apply to the old recruit, but you'd have to be moderately technically savvy to manage that. i suspect it would work because the server allows such changes on signed recruits with an old UI up, so there appears to only be client-side checking to prevent AP changes on signed recruits (which is dumb and bad, but a fairly common issue). i seriously doubt it, but if either of you guys cares enough to go down that route, burpsuite is what you want for the proxy intercept, set it up to a second browser (download a second browser if need be - i have mostly used it with firefox, i'd start there). i kinda think you could use postman and that postman is a lot simpler, but i'm not really sure about that, and i would be less able to assist with follow up questions... i used burpsuite to test a bunch of WIS recruiting stuff (to make sure it was safe!) at some point, so i know that all works.