Narrative:

New automated point-out procedures are excessively cumbersome and unsafe not allowing to have safe and efficient flow of traffic. I was unable to adhere to the new automated point-out procedures nor did I have time to call to coordinate thus I reverted to the old point-out procedure policy to safely maneuver my traffic. Aircraft X was forced to remain at 7;000 feet thus keeping him in the tracy sector to expedite to flight to his destination. Had I allowed him to climb to his requested cruise altitude he would've tangled up with my oak arrivals. I was unable to call or update my data block in accordance with the new point out procedures because of lack to time and I could not keep my eyes off radar scope long enough to update data block either. Thus I resorted to the previous auto point-out procedures to accomplish coordination. Aircraft Y was an arrival from the south. He was vectored for sequence forcing him into fairfield sector's airspace. I did not have time to call to coordinate with affected sector nor did I have time to update data block accordingly to adhere to the new auto point-out procedures. Thus I resorted to the previous auto point-out procedures to accomplish coordination. [Multiple aircraft] all had to be delayed due to a aircraft Z on the arrival route (14;000 feet over eca). Aircraft moved too fast not allowing me time to coordinate via new automated point-out procedures. Thus I resorted to the previous auto point-out procedures to accomplish coordination. The auto point-out procedures are too cumbersome and unsafe! It needs to be changed back to the way it was as soon as possible![recommend to] go back to old auto point-out procedure.

Related reports:

Google
 

Original NASA ASRS Text

Title: NCT TRACON Controller reported being too busy to comply with newly implemented facility coordination procedures. The Controller accomplished the coordination using the previous procedure.

Narrative: New automated point-out procedures are excessively cumbersome and unsafe not allowing to have safe and efficient flow of traffic. I was unable to adhere to the new automated point-out procedures nor did I have time to call to coordinate thus I reverted to the old point-out procedure policy to safely maneuver my traffic. Aircraft X was forced to remain at 7;000 feet thus keeping him in the Tracy sector to expedite to flight to his destination. Had I allowed him to climb to his requested cruise altitude he would've tangled up with my OAK arrivals. I was unable to call or update my data block in accordance with the new Point Out procedures because of lack to time and I could not keep my eyes off radar scope long enough to update data block either. Thus I resorted to the previous auto point-out procedures to accomplish coordination. Aircraft Y was an arrival from the south. He was vectored for sequence forcing him into Fairfield Sector's airspace. I did not have time to call to coordinate with affected sector nor did I have time to update data block accordingly to adhere to the new auto point-out procedures. Thus I resorted to the previous auto point-out procedures to accomplish coordination. [Multiple aircraft] all had to be delayed due to a Aircraft Z on the arrival route (14;000 feet over ECA). Aircraft moved too fast not allowing me time to coordinate via new automated point-out procedures. Thus I resorted to the previous auto point-out procedures to accomplish coordination. The auto point-out procedures are too cumbersome and unsafe! It needs to be changed back to the way it was ASAP![Recommend to] go back to old auto point-out procedure.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.