Date: 201510
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Checklists
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure; Workload; Distraction; Situational Awareness; Fatigue
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: Other Takeoff Roll
Result: Flight Crew Rejected Takeoff; Flight Crew Took Evasive Action; Flight Crew Became Reoriented; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Company Policy; Procedure; Aircraft; Chart Or Publication
Primary problem: Company Policy

Narrative: Upon starting takeoff roll; and thrust levers increased to takeoff power; we received an alert message for improper takeoff configuration. We aborted the takeoff roll at approximately 15-20 KTS and continued off the runway. We reset the trim and continued the flight with no further issues. The trim appeared to be just outside of the range for takeoff. I'm not sure if it was bumped after the trim was set during the appropriate checklist; or if it was something that was missed during the performance check.A few threats I can think of was both the captain and I had commented on how tired we were; we were delayed leaving the gate due to a maintenance swap; and we were trying to get back on schedule. As well; the way the new checklist procedures are written is; simply put; ridiculous. As far as I know; we are the only airline that has 'above the line/below the line.' The checklist is over complicated; and was designed to eliminate heads down activity. But what it has done is put the FO; 'heads down' at a critical time; as we are taking the runway; making a radio call; and some of the time being transferred controls. There is simply no reason that I can come up with to need to be heads down as we take the runway. The only items that should wait; and can be completely eliminated from checklist; and be a procedure are runway heading verification; and lights. Everything else can be done holding short of the runway when you have time to verify that things are properly set. I also feel that the 'takeoff configuration okay' status message should be part of the 'before takeoff' checklist before the line if we feel it is so necessary to have an above/below the line checklist setup.The company should eliminate the above/below the line use in checklists. It is a set up for errors like this. I end up jump seating to and from work on a regular basis [with many other companies.] None of them have the above/below the line nonsense. When we take the runway for departure; all check lists should be completed; and we should be ready for flight. The way the training video is set up; if I remember correctly; specifically instructs the FO to run the 'below the line' checklist as we line up. It's a set up for task saturation everywhere except the sim; where the checklist was designed.




Synopsis: A CRJ-700 Captain rejected that takeoff for the TAKEOFF CONFIG alert because of a miss set trim. The First Officer complained the new Takeoff Checklist forces heads down; task saturation operation before takeoff.