Widebody Transport
Flight Crew Last 90 Days 250; Flight Crew Total 5000; Flight Crew Type 2200
Time Pressure; Confusion; Workload
ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Human Factors; Airport; Chart Or Publication; Environment - Non Weather Related; Procedure
Note: SFO recently changed some departure and arrival routings and names.ATC clearance was GNNRR1 departure. Tower cleared us to hold short RW 28L (we were anticipating takeoff on 28L - FMC was loaded for that runway). Tower switched runways on us at last second and gave us 28R. The FMC was changed to reflect 28R while Takeoff Data was pulled up and reviewed. All new data was loaded and we were cleared for takeoff 28R. LNAV/VNAV was engaged and we were flying the assigned SID (GNNRR1). Passing approximately FL200; ATC asked if we were flying to STINS (the GNNRR1 routing consists of GNNRR-STINS-AMAKR etc.). Shortly after ATC's call they gave us direct REDWD; which we complied with. After we reviewed the SID and discussed ATC questioning us; we realized that we may have unintentionally left STINS out of our clearance when Tower gave us the new runway. Apparently when the runway was changed from 28L to 28R in the FMC; it created a discontinuity. Due to being rushed with the last second runway change; the discontinuity was closed (the correct procedure); but inadvertently deleted STINS. There was limited time to cross check FMC work prior to takeoff. We think the FMC had us flying GNNRR-AMAKR instead of GNNRR-STINS-AMAKR.Recommended actions to avert the problem - SFO recently changed some departure/arrival plates. They are new to all crews and are not as familiar to us as the old plates. Tower changed the runway on us at the last second. We needed to slow down and carefully check/cross check data input to the FMC. This would have delayed our departure and possibly created spacing issues for ATC; but would have been the prudent thing to do.
[Report narrative contained no additional information].
Just prior to departure; SFO changed the departure Runway to 28R so the crew reloaded the new FMS data and GNNRR 1 RNAV routing except for STINS. During climb; ZOA detected the error.