Narrative:

I was conducting initial operating experience with a new first officer and this was my fourth day and tenth leg with this first officer. We were waiting for takeoff near runway 22L at mdw but told our departure route (to ZZZ) was 'not open.' we had been told to park behind another aircraft that was also waiting for takeoff on runway 22L. We kept one engine running; since the information was not indicating how long it might be. After approximately 15 minutes; we were told to expect a runway change to 4R; due to a wind shift. After approximately 5 more minutes; we were told to taxi to runway 4R. I had the first officer enter a request in the ACARS for takeoff data for this runway as it was not included in the original performance data sent. Tower had no information that included any possible takeoff time for us. As such; when we were told to taxi across 30L/C/right runways on Y taxiway and hold short of K taxiway; I figured he was merely repositioning us closer to the new runway; but still without a clue as to our takeoff time. After stopping short of K taxiway; the first officer; who was flying this leg; began to change the information in the FMS for the new runway and brief me. When tower told us to continue taxiing to the runway; I had the first officer stop the briefing and start the second/right engine. As we approached the hold line for runway 4R; we were almost complete with the engine start. I didn't think we had much left to do before we could run the before takeoff checklist; which typically takes approximately 30 seconds. When tower gave us our takeoff instructions; I told the first officer to let tower know we needed approximately one-and-a half minutes before takeoff. We finished the engine start and associated checklist and began the short briefing before the final; before takeoff checklist as tower cleared us for takeoff. Once on the runway; the first officer began reading from the taxi checklist; rather than the before takeoff checklist. It was then I realized there were 'boxed' items (items to be completed when a runway is changed) that we hadn't completed (verified). The first officer completed the short taxi checklist and went through the before takeoff checklist. This was just enough time to cause tower to tell another aircraft on final to go-around. We were powering up as the radio call was made. I am very careful not to make my first officers feel rushed. After flying with this pilot for four days; I felt he was being paced properly. The delay on the runway was my fault. I forgot about the runway-change items on the taxi checklist and purposefully slowed down the operation to make sure we didn't' miss anything else. It wasn't a long time; but it was enough for tower to feel there wasn't enough clearance between our aircraft and the aircraft on final.we should have told tower we needed more time; once I discovered we were not ready for takeoff; rather than delay-without-communicating while on the runway. It was not the way I normally operate.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air carrier Captain reported the crew required more time than expected on the runway before takeoff; which caused an aircraft on final to go around.

Narrative: I was conducting Initial Operating Experience with a new first officer and this was my fourth day and tenth leg with this First Officer. We were waiting for takeoff near runway 22L at MDW but told our departure route (to ZZZ) was 'not open.' We had been told to park behind another aircraft that was also waiting for takeoff on runway 22L. We kept one engine running; since the information was not indicating how long it might be. After approximately 15 minutes; we were told to expect a runway change to 4R; due to a wind shift. After approximately 5 more minutes; we were told to taxi to runway 4R. I had the first officer enter a request in the ACARS for takeoff data for this runway as it was not included in the original performance data sent. Tower had no information that included any possible takeoff time for us. As such; when we were told to taxi across 30L/C/R runways on Y taxiway and hold short of K taxiway; I figured he was merely repositioning us closer to the new runway; but still without a clue as to our takeoff time. After stopping short of K taxiway; the first officer; who was flying this leg; began to change the information in the FMS for the new runway and brief me. When Tower told us to continue taxiing to the runway; I had the first officer stop the briefing and start the second/right engine. As we approached the hold line for runway 4R; we were almost complete with the engine start. I didn't think we had much left to do before we could run the Before Takeoff checklist; which typically takes approximately 30 seconds. When Tower gave us our takeoff instructions; I told the first officer to let Tower know we needed approximately one-and-a half minutes before takeoff. We finished the engine start and associated checklist and began the short briefing before the final; Before Takeoff checklist as Tower cleared us for takeoff. Once on the runway; the first officer began reading from the Taxi checklist; rather than the Before Takeoff checklist. It was then I realized there were 'boxed' items (items to be completed when a runway is changed) that we hadn't completed (verified). The first officer completed the short taxi checklist and went through the Before Takeoff checklist. This was just enough time to cause Tower to tell another aircraft on final to go-around. We were powering up as the radio call was made. I am very careful not to make my first officers feel rushed. After flying with this pilot for four days; I felt he was being paced properly. The delay on the runway was my fault. I forgot about the runway-change items on the Taxi checklist and purposefully slowed down the operation to make sure we didn't' miss anything else. It wasn't a long time; but it was enough for Tower to feel there wasn't enough clearance between our aircraft and the aircraft on final.We should have told Tower we needed more time; once I discovered we were not ready for takeoff; rather than delay-without-communicating while on the runway. It was not the way I normally operate.

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.