Cross-Team Collaboration Brief for Logistics

# Cross-Team Collaboration Brief - Logistics

## Purpose
Create at the start of any initiative involving multiple teams to prevent miscommunication and establish clear ownership.

## When to Use
A collaboration brief for cross-functional projects defining shared objectives, each team's responsibilities, communication channels, and escalation paths.

## Instructions
1. Review the template below and familiarise yourself with the structure
2. Replace all [bracketed placeholders] with your logistics business details
3. Customise the tone and formatting to match your brand
4. Save in your preferred tool (Notion or Slack)

---

# Cross-Team Collaboration Brief

**Initiative:** [Project/Initiative Name]
**Date Created:** [Date]
**Created by:** [Name]
**Status:** [Planning / Active / Complete]

---

## 1. Shared Objective

[Two to three sentences describing the goal that requires cross-team collaboration. For example: "We are launching a new client onboarding experience that requires coordinated effort from Sales, Operations, and Technology. The objective is to reduce onboarding time from 14 days to 5 days while improving the client satisfaction score from 7.2 to 8.5 out of 10. This initiative is a strategic priority for Q[X] and has executive sponsorship from [Name]."]

**Success looks like:**
- [Measurable outcome 1]
- [Measurable outcome 2]
- [Measurable outcome 3]

**Target completion date:** [Date]

---

## 2. Teams Involved

### [Team 1 Name, e.g. "Sales"]
- **Team Lead:** [Name]
- **Team Members:** [Names]
- **Responsibilities:**
  - [Responsibility 1]
  - [Responsibility 2]
  - [Responsibility 3]

### [Team 2 Name, e.g. "Operations"]
- **Team Lead:** [Name]
- **Team Members:** [Names]
- **Responsibilities:**
  - [Responsibility 1]
  - [Responsibility 2]
  - [Responsibility 3]

### [Team 3 Name, e.g. "Technology"]
- **Team Lead:** [Name]
- **Team Members:** [Names]
- **Responsibilities:**
  - [Responsibility 1]
  - [Responsibility 2]
  - [Responsibility 3]

---

## 3. Shared Timeline

| Phase | Dates | Lead Team | Deliverables | Dependencies |
|-------|-------|-----------|-------------|-------------|
| [Phase 1, e.g. "Discovery"] | [Date range] | [Team] | [What gets delivered] | None |
| [Phase 2, e.g. "Design"] | [Date range] | [Team] | [What gets delivered] | Phase 1 complete |
| [Phase 3, e.g. "Build"] | [Date range] | [Team] | [What gets delivered] | Phase 2 sign-off |
| [Phase 4, e.g. "Test and Launch"] | [Date range] | [All teams] | [What gets delivered] | Phase 3 complete |

---

## 4. Communication Plan

**Primary channel:** [e.g. Slack #project-onboarding-v2]
**Project tracker:** [e.g. Asana board - Link]
**Shared documents:** [e.g. Notion workspace - Link]

**Regular meetings:**
- Cross-team sync: [Day] at [Time], [Duration] - [Meeting Link]
- Async updates: Each team posts progress in [Channel] by [Day/Time]

**Update format:**
Each team lead posts a weekly update covering:
1. What was completed this week
2. What is planned for next week
3. Any blockers or dependencies on other teams
4. Decisions needed

---

## 5. Decision-Making Framework

**Day-to-day decisions** within a team's domain: Team lead decides
**Decisions affecting multiple teams:** Raised at cross-team sync, resolved by consensus
**Escalation (if no consensus):** [Escalation Contact Name and Title] makes the final call
**Budget decisions over $[Amount]:** Require approval from [Name/Role]

---

## 6. Escalation Path

| Issue Type | First Contact | Escalation | Final Authority |
|-----------|--------------|------------|----------------|
| Technical blocker | [Team Lead] | [Department Head] | [CTO/Director] |
| Resource conflict | [Team Lead] | [Operations Manager] | [COO/Director] |
| Scope disagreement | [Project Lead] | [Executive Sponsor] | [Executive Sponsor] |
| Timeline risk | [Project Lead] | [Department Heads] | [Executive Sponsor] |

---

## 7. Ground Rules

To keep this collaboration productive, we agree to:
- Respond to cross-team requests within [timeframe, e.g. "4 business hours"]
- Flag blockers immediately rather than waiting for the next sync
- Keep the shared project tracker updated at all times
- Respect each team's domain expertise and decision authority
- Raise concerns directly with the relevant team lead before escalating

---

**Agreed by:**
- [Team 1 Lead Name] - [Date]
- [Team 2 Lead Name] - [Date]
- [Team 3 Lead Name] - [Date]

---

**Complexity:** intermediate | **Setup time:** 15 minutes | **Tools:** Notion, Slack, Asana

Note: This template has been tailored for logistics businesses in Australia. Adjust terminology and compliance references to match your specific context.