George Washington Appointed Commander-in-Chief
June 15, 1775 George Washington Appointed Commander-in-Chief
On June 15, 1775, you can trace the moment the Second Continental Congress unanimously voted to appoint George Washington as Commander-in-Chief of the Continental Army. Congress chose him for his French and Indian War experience, his Virginia roots, and his reputation for unshakeable character. He accepted the role humbly, refused a salary, and pledged full obedience to civilian authority. There's much more to this story than a single vote.
Key Takeaways
- Congress voted on June 14, 1775, to establish the Continental Army before appointing Washington commander-in-chief on June 15, 1775.
- John Adams nominated Washington, believing Virginia's involvement would unify the colonies behind the revolutionary cause.
- Washington was chosen for his French and Indian War experience, Virginia roots, and strong personal character.
- On June 16, 1775, Washington accepted the command, refusing salary and pledging full obedience to civilian authority.
- Washington arrived in Cambridge on July 3, 1775, immediately working to discipline and organize the poorly structured army.
Why Congress Had to Create an Army Before Naming a Commander
Before Washington could lead anything, Congress had to figure out what he'd actually be leading. On June 14, 1775, Congress voted to raise the Continental Army from soldiers in Pennsylvania, Maryland, and Virginia. That decision wasn't symbolic — it addressed the need for logistics, legal authority, and supply procurement before placing anyone in command.
Without formal legal authority, Washington would've commanded nothing but scattered militias with no binding obligation to follow him. Recruitment challenges meant Congress couldn't simply draft men; it had to structure enlistments, define terms, and secure funding.
Supply procurement required establishing chains of responsibility before a commander could even request resources. Canada faced a similar challenge in 1914, when Prime Minister Borden's Cabinet passed the War Measures Act to establish the legal framework needed before mobilizing 25,000 troops.
You can't appoint a general to lead an army that doesn't legally exist. Congress understood that sequence mattered.
Why Congress Unanimously Chose Washington as Commander in Chief
With the Continental Army now a legal entity, Congress needed someone to lead it. They turned to George Washington, and their choice wasn't accidental. Washington brought proven military experience from the French and Indian War, giving Congress confidence he could face British regulars. But experience alone didn't seal it.
Regional unity mattered enormously. The revolution risked appearing like a New England problem. Washington, a Virginian, signaled that all colonies stood together. John Adams nominated him specifically to bridge that divide and draw the wealthiest, most populous colony into full commitment.
Personal character sealed the decision. Washington projected integrity, patriotism, and determination. Congress trusted he wouldn't abuse military power or threaten civilian authority. At 43, he was vigorous enough for a long war—exactly what they needed. This concern for keeping military power subordinate to civilian oversight echoed the same principle of responsible government that constitutional framers across the British world were embedding into their governing structures during this era.
Who Else Was Considered for Commander in Chief?
Washington's appointment may seem inevitable in hindsight, but Congress seriously weighed other candidates before casting its unanimous vote. John Hancock wanted the position badly and expected it, given his role as Congress's president. His lack of battlefield experience, however, worked heavily against him.
Charles Lee was another serious contender. He'd served as a British officer and carried impressive military credentials, but his foreign birth raised concerns about his loyalties and his ability to unite the colonies behind a common cause.
Henry Knox, though deeply respected, was still proving himself and hadn't yet earned the broader confidence Congress needed in a commander.
Ultimately, Washington's combination of actual combat experience, Virginia roots, and unimpeachable character made him the candidate no one could reasonably argue against. Similarly, when Canada formed its first federal Cabinet in 1867, Macdonald carefully balanced regional representation and loyalty rather than relying solely on partisan consistency to secure support for the new government.
What Washington Actually Said When He Accepted the Command
Standing before Congress on June 16, 1775, Washington didn't deliver the confident, triumphant speech you might expect from a man handed command of a revolution. Instead, you'd have heard a humble admission of self-doubt. He openly stated he felt distress because his abilities and military experience mightn't match the enormous responsibility Congress placed on him.
He also made a point of obedient civics, firmly pledging loyalty to civilian authority rather than positioning himself as an independent military power. That reassurance mattered deeply to a Congress wary of military dictatorship.
He refused a salary, asking only for expense reimbursement. Yet despite his reservations, he committed fully, telling Congress that since they desired it, he'd enter upon this momentous duty without hesitation.
No Salary, No Ego: Washington's Terms of Service
When Washington declined his salary, he made it clear this wasn't a gesture of false modesty—he meant it. He asked Congress to cover only his expenses, nothing more. That act of voluntary modesty sent an immediate message: this wasn't about personal gain.
Think about what that decision signaled to a Congress already nervous about handing military power to one man. Washington's symbolic sacrifice put those fears to rest before they could take root. He wasn't positioning himself for wealth or influence—he was showing up to serve.
He also pledged full obedience to civilian authority, reinforcing that Congress remained in charge. You don't make those commitments unless you understand exactly what's at stake. Washington did, and he acted accordingly from day one. Similarly, meaningful acts of public recognition—like Canada's designation of National Ribbon Skirt Day—show how symbolic gestures rooted in principle can reshape cultural respect on a national scale.
From Philadelphia to Cambridge in Two Weeks
You can imagine the weight he carried — a new army awaiting leadership, British regulars holding Boston, and an entire revolution depending on his success.
He arrived in Cambridge, Massachusetts, on July 3, 1775, and assumed command that same day. In under two weeks, Washington had transformed from a congressman's appointee into the Continental Army's active commanding general.
What Washington Found When He Took Command in Cambridge
The scene Washington encountered at Cambridge was far from what any general would want. You'd have seen thousands of men with little discipline, scarce ammunition, and almost no organizational structure holding them together.
Logistical disarray defined the camp—units lacked clear chains of command, record-keeping was poor, and coordination between colonial militias was nearly nonexistent.
Supply shortages compounded every problem. Gunpowder reserves were dangerously low, weapons were unreliable, and basic provisions ran thin.
The men surrounding Boston were passionate but untrained, more resembling an armed crowd than a professional fighting force.
Washington didn't flinch. He immediately pushed for structure, accountability, and discipline. He knew transforming this ragged force into something capable of challenging British regulars wouldn't happen overnight—but he started that work on day one.