Date: 202010
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Training / Qualification; Communication Breakdown; Distraction; Confusion
Second reporter function: Captain; Pilot Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors; Procedure
Primary problem: Human Factors

Narrative: The issue was that we departed on a revenue flight without reviewing all required forms.  I was acting as First Officer and non flying pilot in a three pilot crew of Aircraft X ZZZ-ZZZ1. This was my first time working in the First Officer position in two months which was during initial OE training. We were initially setup for a departure on Runway XXR. On the taxiout we were given a last minute runway change to Runway XYR. Performance data for this runway was not provided on the release. This required me to 'manually' acquire the data from the MCDU. This was the first time online or in training for me of obtaining data in this fashion. It requires me to input the current conditions at the airport. When the takeoff data printed out it was in a format that I wasn't accustomed to.  I then inputted the computed speeds and verified the thrust settings were proper; we weighed less than the assumed weight; there was no tailwind; and the temperatures were correct. The Captain and Relief Pilot then reviewed the data and we all agreed we were legal for takeoff. I mistakenly assumed and convoluted the new takeoff date printout with the load closeout and this data superseded and included the load closeout information. Several hours into the flight the Relief Pilot advised myself and the Captain that the actual load closeout in fact printed out a few minutes after rotation. After reviewing the load closeout I determined the takeoff was well within the performance data I imputed. However; that fact remains; we are required to review the load closeout prior to takeoff.Causal factors for me include...1. I am new on this type aircraft. I in fact picked the trip up in order to make sure I obtained enough hours to consolidate.2. I had not worked in the First Officer position in about two months which was when I was receiving line training. 3. This was my first time be it ground training; line training; or on line where is was required to get new runway takeoff data and was not familiar with the outputted format. 4. We were rushed due to a last minute runway change.I would be helpful if in the training environment pilots were required to at least once obtain new runway data to get the experience.


Second narrative: Takeoff without load closeout. Runway change XXR to XYL. First Officer on consolidation after IOE. Received new TPS for XYL. Discussion for 'takeoff data and bugs' for Runway XYL from First Officer included 'weight is right on; T/O power; temp and wind. I responded to checklist item Takeoff Data and bugs with 'checked Runway XYL. Normal first 5 hours of flight. After returning to flight deck from 2nd break I was advised that load close out came up on ACARS at about 1;000 feet. First Officer advised he had used TPS data. I highlighted and showed First Officer header on TPS- 'This does not satisfy requirement for load closeout.' Normal flight.This is a first at XX years; I will not depart again without physical eyes on load closeout.


Synopsis: Air carrier flight crew reported a runway change prior to departure and departing without the correct load closeout.