Onboarding & Teamwork
Create a Team Charter That Resolves Purpose and Boundaries
A complete fictional platform-team charter is tested against three neighboring requests, with accepted capacity, an unresolved ownership gap, and a repaired readback.
A useful team charter explains the problem your team exists to solve, the work it owns, the work it cannot accept, and who can change those boundaries. Write it with team members and the neighboring owners who must confirm its handoffs. Then test it against actual requests before treating agreement on the document as agreement on the work.
This LandOffer.ai guide develops a fictional platform team's charter and applies it to three neighboring teams' requests. The finished examples show acceptance, redirection, and an unresolved ownership gap. They are teaching materials, not records from an employer or evidence that a charter improved delivery.

Start with the problem the team is authorized to own
“Enable engineering excellence” leaves almost any engineering request in scope. A sharper purpose names a user, a problem, and a responsibility: “Maintain shared development-environment templates so product engineers can reproduce the supported local setup.” That still needs an explicit limit. Maintaining the template does not necessarily include debugging every application that uses it.
The Canada School of Public Service's charter guidance, published in 2020 and modified in 2022, covers purpose, roles, operating practices, decision mechanisms, and conflict resolution. It recommends creating the charter together and revisiting it. Those are useful design prompts; they do not give a new team authority over another department.
Before drafting, ask the accountable manager what responsibility has actually been assigned, what capacity is available, and which neighboring owners must confirm the handoffs. Record disagreement as disagreement. A manager can authorize their own team's allocation without silently assigning work to Security or Application Engineering.
Give the charter a clear job alongside your other documents. A project kickoff frames a particular initiative. A decision record explains a particular choice. Working agreements describe everyday collaboration, such as response times. The charter connects enduring purpose, service boundaries, and accountability across those activities. Link to detailed procedures rather than trying to make one document contain every operational rule.
Worked charter: a bounded platform service
Everything in this case, including names, capacity, requests, and review results, is fictional. Harbor is a newly formed three-engineer platform team. Its first responsibility is a shared local development-environment template used by two product teams. It has no production incident mandate.
The original draft says, “Harbor owns developer environments and supports teams as needed.” Product lead Claudia reads that as application troubleshooting. Engineer Imran reads it as template maintenance. Manager Rowan asks the group to replace the sentence with the following version, reviewed on November 2.
| Charter field | Harbor version 1: agreed scope |
|---|---|
| Purpose and users | Give the Atlas and Grove application teams a maintained, documented starting environment for local development. Harbor owns the shared template; product teams own their application-specific setup. |
| Current service | Maintain the template's pinned tool versions, example configuration, supported setup instructions, and a reproducible template-only check. Investigate defects reproduced in that supported template. |
| Explicit exclusions | No production incident response, individual laptop administration, application feature debugging, or approval of security-policy exceptions. A request may expose a shared defect without transferring all related work to Harbor. |
| Team responsibilities | Imran maintains the template and checks; Eliza maintains setup documentation and gathers reader problems; Tomas handles intake and records boundaries. Each has agreed to these responsibilities; Rowan owns staffing and priority conflicts. |
| Capacity this cycle | Thirty engineering days are available after planned leave and existing obligations: eighteen for template maintenance, six for documentation, six for intake and investigation. These are planning allocations, not promised request turnaround times. |
| Intake and acceptance | A requester supplies the supported template version, expected behavior, reproduction steps, and application-specific changes. Tomas classifies the request; an engineer confirms technical scope. Rowan accepts any allocation change. Submission alone creates no delivery commitment. |
| Neighboring responsibilities | Claudia confirms Atlas owns its application configuration. Grove lead Rafael confirms the equivalent for Grove. IT contact Beth confirms the laptop-support route. Security contact Vivian confirms that exception requests go through Security's existing process. |
| Decision boundaries | Harbor engineers choose implementation details within the agreed service and allocation. Rowan decides Harbor priorities. Security retains policy decisions; product leads retain application priorities. New permanent services require the engineering director's remit and staffing decision. |
| Success evidence | Keep a versioned supported-template check record, a reviewed setup guide, and a request log showing accepted work, redirects, and disputed boundaries. Collect time-to-first-local-run reports where participants agree; no baseline or improvement claim exists yet. |
| Review and disagreement | Review on November 30, or earlier if capacity, users, or responsibilities change. Tomas records disputes; Rowan brings cross-team conflicts to the relevant lead. Unresolved ownership stays visible with a next decision and date. |
A requester can now challenge a particular boundary: template ownership, application work, available capacity, or a missing decision. It does not turn every field into a permanent contract. The six investigation days are particularly important: an in-scope problem can still require reprioritization when the available allocation is used.
The team also records its working principle: reproduce a problem before arguing about ownership, and describe a redirect with its reason and next contact. This supports cooperation without making “helpfulness” an unlimited service promise. Detailed coverage hours and communication norms remain in a separate working agreement.
Atlassian's Team Poster template similarly treats team purpose as a living document that can be shared with neighboring teams and revisited at major changes. Harbor uses a shorter first review because its new service boundaries have not yet been tested; that interval is this case's choice, not an Atlassian requirement.
Make neighboring teams part of the boundary review
A list of stakeholders is not evidence that those people accepted responsibilities. Ask each neighboring owner to explain a handoff in their own words. For example: “If a developer's laptop cannot install the required tool, who investigates first, and when would Harbor become involved?”
Atlassian's Network of Teams play maps adjacent teams and assigns relationship owners to maintain communication. That relationship role does not itself authorize someone to decide another team's priorities. Harbor records Tomas as its relationship contact with IT; Beth still controls IT's acceptance of a laptop-support request.
For the fictional review, Tomas sends version 1 to Claudia, Rafael, Beth, and Vivian with three questions: Which responsibility did we accidentally assign to your team? Which handoff is missing? Which request would you expect us to accept that this wording excludes?
Claudia confirms application ownership but asks whether a template regression is Harbor's problem even when Atlas discovers it first. Imran answers yes, if it reproduces in the supported template. Beth confirms the contact route but explicitly declines any guaranteed same-day repair. Vivian confirms the policy boundary and asks Harbor to avoid language that suggests it can preapprove an exception.
Tomas adds these clarifications to the charter's linked intake notes. The resulting record confirms Beth as the IT contact while leaving repair timing unpromised. It also gives a new engineer a concrete way to recognize a shared defect instead of treating every product-team report as outside scope.

Three requests that test the charter
The second completed asset is Harbor's request-decision record. These are fictional discussions and decisions, not actual software tests or delivered fixes. Each entry separates responsibility, accepted capacity, and the requested outcome.
Request 1: Atlas's supported template no longer starts. Claudia supplies the template version and reproduction steps. In the fictional record, Imran reproduces the failure in an unchanged supported template. This is an invented case event, not an executed software test. That places investigation inside Harbor's current service.
Tomas records one investigation day against the six-day intake allocation, which is otherwise unused. Rowan accepts that allocation, and Imran accepts the investigation. Claudia's requested next-day fix is not accepted: the cause and repair effort remain unknown. The response reads, “Harbor owns this template-defect investigation. Imran will provide the reproduction record and a next-step assessment after the allocated investigation day. We have not committed to a fix date.”
The completed decision is ownership plus a bounded next deliverable. It would be misleading to mark the request resolved merely because someone accepted investigation. The log keeps repair and supported-template recheck pending.
Request 2: Grove wants a custom local database migration. Rafael asks Harbor to implement application-specific migration scripts because they run in the development environment. Eliza compares the request with the charter: the shared template starts successfully, while the scripts change Grove's application data model.
Rafael confirms Grove owns that implementation and accepts the redirect. Harbor offers a thirty-minute consultation about the template's documented configuration, charged against intake capacity; Eliza and Rowan accept that limited allocation. The record says, “Grove retains script design, implementation, and validation. Harbor's consultation covers documented template configuration only.” No script delivery date is assigned to Grove by Harbor.
The reply offers limited help while leaving script ownership with Grove. If consultation later reveals a shared-template defect, Tomas will create a separate defect record rather than quietly expanding the original offer.
Request 3: Security wants recurring workstation compliance reports. Vivian asks whether Harbor can operate a weekly collector across developer laptops. The report would concern engineering environments, but it introduces device access, ongoing operations, and a responsibility not covered by the template service.
Beth says IT has not accepted ownership of the collector. Vivian retains the policy question but has not named an operational owner. Rowan therefore does not accept the service or a launch date. He accepts a one-hour scoping conversation, with Tomas participating; Vivian and Beth accept that conversation too. Its purpose is to identify an owner and required approvals, not authorize installation or access.
The log ends, “Operational ownership unresolved. Rowan will bring the ownership and staffing question to engineering director Daria on November 6, with Vivian and Beth supplying their constraints. No collector deployment or recurring report commitment.” Daria has not yet decided. A named escalation is useful precisely because the gap remains open.
These decisions use one charter without producing the same answer three times. One request belongs to the existing service, one stays with a product team with limited help, and one needs an organizational decision. Scope classification, available capacity, and authority are separate checks in every case.
Review what changed without inventing a success story
At the November 9 fictional readback, Eliza asks a new teammate to classify the three records. The teammate correctly identifies Harbor's template investigation and Grove's script ownership but initially describes the Security scoping meeting as accepted reporting work. That misreading exposes a weak phrase in the linked notes: “Harbor will support compliance reporting.”
Tomas replaces it with, “Harbor will attend the ownership-scoping conversation only; operation and deployment remain unassigned.” The teammate then explains the limit correctly. That is a corrected readback in this teaching case, not evidence that every reader will understand the charter or that the organization has solved the ownership problem.
The same review finds a capacity issue. The accepted investigation day, half-hour consultation, and one-hour scoping conversation all consume the intake allocation; none is free work outside the plan. Rowan asks Tomas to record actual effort before accepting further requests. The story does not supply completed effort totals, so it cannot establish remaining capacity or improved response time.
Keep a version note explaining the wording repair, accepted responsibilities, open ownership decision, and next review. If leadership later assigns the reporting service, revise purpose, capacity, permissions, and neighboring handoffs together. Adding “also owns reporting” to a sentence would leave the operational requirements unanswered.
To create your own charter, take one recent ambiguous request to the team and the affected neighboring owner. Agree who owns the problem, what help is accepted, which decision is still missing, and what existing work would move. Save that decision beside the charter; use further workplace guides from LandOffer.ai as needed. Finish with a boundary the affected owners can use, and keep any unresolved assignment visible until its decision owner responds.


