ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Schlieffen Plan

Updated on July 23, 2019
Kaili Bisson profile image

Kaili is a student of history and of WWI. She has researched BEF and Canadian battles and has visited WWI battle sites, including Gallipoli.

As the two sides began squaring off in the very early days of World War I, Germany put its Schlieffen Plan to work. But, the Germans had a major stumbling block to overcome in order to see their plan through. Luxembourg and Belgium, two countries that were neutral – so far at least – lay in between Germany and France. As history has shown, that didn’t stop Germany.

Count Alfred von Schlieffen


What was the Schlieffen Plan?

The Schlieffen Plan, or von Schlieffen Plan, was originally developed in 1905. Ever since handing the French a resounding slap by defeating them in the Franco-Prussian War of 1870-71 and grabbing Alsace and Lorraine, Germany had been preparing for the next war with France.

The Germans weren't the only country that had been busy drawing up plans for war. Other countries too were drawing up, or had already drawn up, plans to defend what was rightfully theirs against ambitious neighbors, recapture what had been taken from them in the past, or simply settle old scores. The French had their own plan called Plan XVII.

The architect of Germany’s plan was Count Alfred von Schlieffen, a Prussian Field Marshall and Chief of General Staff of the German military forces. The plan was devised based on three different scenarios, each of which had at its heart a Franco-German war. The scenarios differed only in what other countries might also be involved and what that meant in terms of possible support from allies like Austria and the number of troops deployed to specific defensive or offensive positions.

German Advance Through Belgium


The Schlieffen Plan in WWI

The scenario applied in WWI was one in which the war would be fought on two distinct fronts – against France in the west and Russia in the east, with Austria lending its support to Germany. Germany also realized that Britain could become involved because of alliances it had in place with both France and Russia.

Besides the different scenarios, there were also many assumptions on which the Schlieffen Plan was based. One of these assumptions was that the Russians, ill-equipped as they were and lacking transportation infrastructure for troop and armament movement, would need a minimum of six weeks to mobilize their army in the event of war. The Schlieffen Plan, as it was implemented in WWI, called for Germany to rout France in that short period of time, focusing the bulk of the German troops on the western front with France, flanking them, and once they had defeated France, turning their troops back east to meet the Russians who would only just be arriving on the eastern front scene by that point.

Once the plan was put into play in 1914, it was modified somewhat. One of these modifications was to leave a larger portion of the German army along the eastern front. In order to get at France, the Germans had to move their army across Luxembourg and Belgium. Germany occupied sovereign and neutral Luxembourg on August 2nd, 1914, only a day before it formally declared war on France. The plan was to hit France hard using a flanking movement.

Schlieffen Plan 1914 and Possible French Response


WWI Timeline

July 28th, 1914 - Austria declares war on Serbia.

August 1st, 1914 - Germany declares war on Russia. Russia defies Germany’s warning to halt mobilization of its troops, replying that the mobilization is only against Austria.

On August 1st, France enters the fray when it orders its army to mobilize to come to the aid of its ally Russia.

August 3rd, 1914 - France declares war on Germany and Germany declares war on France.

August 4th, 1914 – Germany’s invasion of Belgium causes Britain to formally declare war on Germany.

Failure of the Schlieffen Plan

The first ever implementation of the Schlieffen Plan almost succeeded and the Germans came very close to marching into Paris in the timeframe that von Schlieffen had foreseen – give or take about six weeks.

A number of things led to the failure of the Schlieffen Plan. One of these was a problem with troop and armament movement on the German side. Though the plan had anticipated these challenges on the Russian side, it was thought that with their superior equipment, leadership and better transportation infrastructure in Western Europe, that troop movement would not be a problem for the Germans.

The fact that central command was so far removed from the troops also led to some poor tactical decisions by the Germans. They had assumed that France would be on the defensive and would not be able to mount a successful offensive campaign. They were wrong.

The French mounted a great offensive attack during the first Battle of Marne in September 1914. Supported by the British Expeditionary Forces who had by that time joined the fighting, the combined Franco-British forces pushed the Germans back in a north-easterly direction toward Belgium. This Race to the Sea, as it is called, was what ultimately led to the trench warfare that marked so much of WWI.

The Failure of the Schlieffen Plan 1914


  • Anon. (1923) Source Records of the Great War, Volume I. Canada: National Alumni, The Great War Veterans Association of Canada
  • Anon. (1914-1921) History of the War, Volume I. London UK: The Times

© 2014 Kaili Bisson


This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

Show Details
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)