Rushed Into Service
A new ship, vehicle, or technology is sent into action untested because it's needed right now.
Already have? Motion To Discard

(permanent link) added: 2014-01-21 17:11:59 sponsor: Tallens (last reply: 2014-01-23 05:15:02)

Add Tag:
JARVIS: Sir, the Mark VII hasn't finished testing yet.
Tony: Then skip the spinning wheels, we're on the clock.

When something is brand-new, fresh off the assembly line, there is typically a period of testing and shakedown to work out all the bugs and make sure everything's working the way it should and ensure a smooth entry into service. The larger and more complex it is, the more tests it needs, but in this case, that important step is skipped and it's put directly into service.

Why? Because it's needed, right now!

This is common in military settings, where one side finds itself lacking in resources or up against something its current assets can't handle and so starts deploying things that really aren't ready yet. Ships that have just barely finished being built, and still have the paint drying, if that, tanks that were just designed suddenly being fielded, or at times computer systems that are compiled and implemented.

This can cause more problems, as parts of it will not be up to standards or even active at all. Field installations will then be required to get finished in days or less what might take weeks at a dedicated facility. Rushed programs will have many undetected bugs, and be unstable.

Compare Obvious Beta for when this happens in the gaming industry, though the consequences are generally less severe there, except possibly for the developers. Compare Super Prototype.


  • Star Trek V: The Final Frontier has the Enterprise-A being sent into action despite being barely operational to investigate a Hostage Situation.
  • Star Trek: Generations begins with the Enterprise-B being forced to undertake a rescue mission despite being on a shakedown cruise and not having most of her main systems installed, which was supposed to happen on Tuesday.
  • In The Avengers, Tony's Mark VI armor is barely holding together, so he demands his AI butler JARVIS deploy his new Mark VII even though it hasn't finished testing yet. JARVIS manages to deliver it just as Loki throws Tony out a window.
  • The Mark I Jaegers in Pacific Rim were thrown together in 14 months. Unfortunately, this meant that certain features were skimped, including radiation shielding for the pilots. As a result, Marshall Pentecost (the Big Good, a former Mk. I pilot) is Secretly Dying of radiation poisoning.

  • In the Vorkosigan Saga book The Vor Game, the Prince Xav, the brand-new flagship of the Barrayaran fleet, launches for battle with construction crews still aboard putting in the finishing touches. Fortunately, getting there with big enough guns mostly ends the actual battle

Live-Action TV
  • Stargate SG-1:
    • The Asgard ship O'Neill was barely out of drydock before it was used to draw a Replicator fleet away from the Asgard homeworld and blown up.
    • The Russian BC-304, Korolev, was rushed into service to help fight the Ori invasion at the Supergate, and was destroyed in the battle.
  • Stargate Atlantis: In an Alternate Timeline the newest BC-304, the Pheonix, was sent to the Pegasus Galaxy to help curb Michael's forces. It was so new that more than half it's systems were not operable yet and Carter and Mc Kay had to finish the work themselves.

replies: 16

TV Tropes by TV Tropes Foundation, LLC is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
Permissions beyond the scope of this license may be available from
Privacy Policy