Team Charter Template and Filled-In Example

Two people on a five-person team both believed they owned the customer schedule. Neither of them was wrong, because nobody had ever said it out loud. It surfaced the way these things always surface: a double-booked Saturday, a short argument in front of a customer, and two weeks of politeness afterwards that were worse than the argument.

A team charter is the ninety minutes that prevents that. It is one to three pages saying why the team exists, what it owns, who is on it, who decides what, and how the group is going to work. Signed by the people it covers, not handed to them.

There are six templates below rather than one, because a standing team, a project with an end date, and a group of people who each keep a separate manager are different problems. One of the six is a complete filled-in example, which is the one most people want first. Five are editable Word files, one is an Excel workbook, and there is no email form in front of any of them.

What a Team Charter Is

A team charter is a short written agreement, made by a team, covering why it exists, what it is responsible for, who decides what, and how the people on it will work together. It is agreed and signed by the members, which is the difference between a charter and a policy.

The reason it earns its ninety minutes is narrow: it converts assumptions into statements. Everyone on a small team carries a private version of who owns what, and those versions overlap in ways nobody notices until two of them collide over a customer. Writing them down is uncomfortable for about twenty minutes and then it is done.

Charters are worth the most in exactly the places small businesses run into trouble: a team that spans functions, a team where somebody has two managers, and a team the owner sits on but does not run. In all three, the reporting line on the org chart answers a question nobody was asking. The question is who decides, and the chart is silent on it.

What Goes In One

Eight elements, sorting into four groups. A charter missing any of these four groups leaks somewhere, and it is almost always the same somewhere: two people acting on a decision they both thought was theirs.

The research on team performance points the same direction. Work drawing on the late J. Richard Hackman's conditions for effective teams holds that what matters most is not personality or chemistry but whether a team has a compelling direction, a strong structure, a supportive context and a shared mindset (Haas and Mortensen, Harvard Business Review, June 2016). A charter is the cheapest way a small company has of putting the first two in writing.

Two sections carry more weight than the rest. The out-of-scope list, because uncontested territory never causes an argument and the boundary always does. And the hours a week column, because a person on four teams for four hours each is on no team at all, and that stays invisible until a deadline is missed.

A Filled-In Example

The clearest way to see what a charter should contain is to read one that has been finished. Template 2 below is a complete charter for the operations team at Ridgeline Home Services, a fictional sixteen-person residential services company with six technicians and a scheduling problem.

Its purpose line is one sentence: every booked job leaves with the right crew and the right parts, and the invoice goes out within two working days. That sentence does real work, because it tells the team that a job which finishes perfectly but goes unbilled for a week is a failure they own.

The scope section puts dispatch, parts, invoicing and collections to 30 days inside the team, and puts pricing over $5,000, hiring, and warranty disputes over $2,000 with the owner. It also leaves one gray area open on purpose, with a date next to it: who answers the after-hours phone in December.

The Decision Rights From the Example

This is the section that stops the arguments, so it is worth seeing filled in rather than blank. Every row has one decider and a limit, which is what makes it usable in the moment rather than a description of good intentions.

Notice what the limits do. The scheduler can move a job without asking, twice, and the third time it becomes somebody else's problem. The office coordinator can settle a small billing complaint on the phone instead of promising to get back to the customer. Those two lines alone remove a dozen interruptions a week from the owner's day.

The example also carries four measures with a starting number and a target: jobs finished on the first visit at 68 percent moving to 80, invoices out within two days at 55 percent moving to 90, jobs moved more than once at nine a month moving under four, and unbilled parts written off at $840 a month moving under $300. Numbers that specific are what make a six-month review a real conversation rather than a feeling.

Which Template Should You Use?

Pick by the kind of team you have. A standing team that exists indefinitely takes the main charter, work that finishes takes the project version, and a group whose members each keep their own manager takes the cross-functional one.

The working agreement is different in kind. It is the behavior half on its own, one page, written by the team rather than for them. It suits a team that already knows what it owns and keeps colliding over meetings, response times and unspoken expectations instead.

6 Free Team Charter Templates

Download all six together as a zip file, or take a single template. Five are editable Word documents and one is an Excel workbook with four tabs. Fill in the brackets, delete what does not apply, and change anything that does not match how your business actually works.

Template 1: Team Charter

The main blank, for a team that exists indefinitely. Purpose, in and out of scope, members with hours and backups, a decision rights table with limits, meeting rhythm and response times, success measures, what the team needs from the rest of the business, and a signature page with a review date.

Template 2: Team Charter Example (Filled In)

The same document completed for a fictional sixteen-person home services company. Real limits, real numbers, and one gray area deliberately left open with a date on it. Read this before you open the blank.

Template 3: Project Team Charter

For work that finishes. The problem stated with a number in it, what done looks like, deliverables with dates, what is explicitly out, the hours each person is released from, escalation, milestones, known risks, and a closing checklist that hands the work to a named owner.

Template 4: Cross-Functional Team Charter

For members who keep their regular manager and take direction here too, which is what a matrix arrangement means in practice. Built around the tie-break, and around getting each home manager to sign the percentage of time before the first meeting rather than after the first missed deadline.

Template 5: Team Working Agreement

One page on behavior alone: meetings, what urgent means with an example, response windows, who decides what, how disagreement is handled, and how the team treats each other.

Template 6: Team Charter Workbook (Spreadsheet)

Four tabs: decision rights with limits and escalation, roles and owners with hours a week, the meeting rhythm with what each meeting produces, and a review log recording every change and the reason for it. Pre-filled with the same worked example, ready to clear.

Writing Decision Rights That Hold

A decision right holds when it names one person and one limit. Everything softer than that gets reinterpreted the first time it is inconvenient, which is usually within two weeks of signing.

Three questions do most of the work, and they are the same ones organizational design guidance asks of a whole company: which decisions get made centrally and which locally, whether a decision belongs to an individual, a team or a committee, and how trade-offs get resolved when two good things conflict (SHRM, organizational design and change management). At fifteen people those questions take an afternoon rather than a consulting engagement.

Two habits keep the table honest. Write the limit as a number rather than a size word, since one person's idea of a small purchase is another person's quarterly budget. And name a tie-breaker who is a person, not a committee, with a number of days attached. A decision with no deadline is a decision that gets made by whoever moves first.

The other thing worth stating explicitly is the default. Anything not listed in the table either belongs to the team or belongs to the sponsor, and you have to say which, or every unlisted case becomes a small negotiation. A RACI matrix is a good companion here when the work involves several teams, because it maps the same responsible and consulted logic across a whole process rather than one group.

Writing It in One 90-Minute Session

Draft it alone, then decide it together in one session of about ninety minutes. A blank document in a room full of people produces an argument about wording rather than a set of decisions, so somebody has to arrive with a rough version and a list of the lines they are unsure about.

The question that earns the session is the direct one: which decisions do you believe you already own? Ask it about the specific recurring calls, not in the abstract. Two people raising a hand on the same row is the moment the charter pays for itself, and it happens in most first sessions.

Keep the discomfort short. If a row cannot be settled in three minutes, write it into the gray areas list with a date and a name, and move on. A charter with two open items and a deadline is a working document. A charter that stalled in minute forty because one row got litigated is a file nobody opens again.

New members get walked through it in their first week, which is the cheapest moment to transfer this knowledge. That is one of the things FirstHR is built to make routine: the charter sits on the team record with the rest of the documents, the walkthrough is a task with a name and a due date instead of a good intention, and the signature comes back e-signed and dated. Applicant tracking is coming soon to FirstHR.

Why Charters Stop Working

Three failures account for nearly all of them, and none is about the writing. A charter fails when it skips the decisions, when it ignores what people's time actually costs, or when nobody opens it again after the day it was signed.

The fix for all three is the same and it is unglamorous: a review date inside the document, a log of what changed and why, and permission for anyone on the team to call for a change between reviews. Six months is about right at a growing company, sooner whenever somebody joins or leaves.

There is a fourth failure worth naming separately. A charter written by the owner and circulated for signature is not a charter, it is a policy in a costume, and teams can tell the difference within a page. The document only creates obligation because the people bound by it argued over the lines first. If you cannot spare the room for that argument, write a shorter document and spare yourself the ceremony.

Charter vs Job Description vs RACI

Four documents get treated as substitutes for each other, and then somebody produces an org chart and calls the question of who decides settled. They answer different questions.

The pairing that covers the most ground at a small company is the charter and the job description. One says what each person is accountable for, the other says who decides when two of those people disagree, and the second question is the one that actually stalls work. A team structure decision sits above both, because it determines which teams exist in the first place.

A charter also does something a job description cannot. It makes the norms discussable, which is a precondition for people raising problems early rather than at the exit interview. That is the practical route into psychological safety: not a values poster, but a written line saying disagreement is said in the room and a decider who ends it.

Sign It, Store It, Review It

Get every member to sign, store it where the team can reach it, and put the next review date inside the document itself. A charter in one person's downloads folder is a charter that expired on the day it was written.

Signing matters more than it looks. It is the difference between a list somebody circulated and a set of commitments people have individually agreed to, and it changes the conversation months later when a line gets ignored. Nobody has to reconstruct what was decided. It is on the page with a date and a name next to it.

Review on a date and on events. Six months on the calendar, plus immediately when someone joins or leaves, when a limit turns out to be wrong, or when the purpose shifts. Log what changed and why in three lines, because the reason is what stops the same argument coming back. The workbook above has a tab for exactly that, and a filled-in log showing what a year of small corrections looks like.

Where a platform earns its place is in the storage and the follow-through rather than the writing. When the charter lives on the team record alongside employee profiles and signed documents, a new joiner gets it as part of onboarding into the team instead of hearing about it in month three, the review lands as a dated task with an owner, and the signatures are captured rather than chased. FirstHR is an HR and onboarding platform, not a law firm, so it stores and routes the document rather than telling you what the document should say. Applicant tracking is coming soon to FirstHR.

Frequently Asked Questions