Inter-Club Relationships & Communication Protocols — GoClubPro

Training Module 86 | Working with Opponent Clubs, Rival Clubs, and the Broader Sporting Community

---

What This Guide Covers

Every club exists within a broader competition community — opponent clubs, rival clubs, shared venues, shared umpires, and joint social events. None of this is managed within GoClubPro, but the platform supports the communications and logistics that underpin these relationships. This guide covers the protocols for inter-club communication, conduct toward opponents, and using the platform to manage shared-context situations.

Primary audience: Club Admins, Coaches, Team Managers, Club Secretaries Also useful for: Club Presidents (managing formal inter-club relationships)

---

SECTION 1: TYPES OF INTER-CLUB INTERACTIONS

What You'll Encounter

---

SECTION 2: MATCH-DAY INTER-CLUB COMMUNICATION

Pre-Match Logistics

The Team Manager is typically the point of contact for pre-match coordination with the opposing club. Common coordination topics:

• Confirming venue and start time (especially for away fixtures)
• Colour clash — if both teams wear similar colours, who changes?
• Equipment (who supplies the match ball in your code?)
• Ground access — does the home team have the keys?
• Emergency contact for the day

In GoClubPro: The fixture details (venue, time) are in Schedule. If venue or time changes, update the fixture immediately and broadcast to your members. Do not rely on the opponent club to inform your members.

---

Colour Clash Protocol

Before Round 1 of a new season: Check your fixture list. If you're playing a team in similar colours, reach out early — don't leave it until match day.

Convention in most codes: Away team changes (wears alternate colours or reverses colours). If both clubs don't have alternate kits: the home team defers. Sort it out respectfully and early.

In GoClubPro: No specific setting. Handle externally, then communicate to your squad via the Noticeboard or squad confirmation note field.

---

Post-Match Conduct

How you behave after a match reflects on your club and shapes your relationship with the competition.

Good practice:

• Coaches from both teams shake hands on the field
• Team Manager checks with opposition Team Manager if there are any unresolved issues to note
• If a conduct incident occurred: document internally before discussing with the opposition
• A brief "thanks for the game" message to the opposing Team Manager (text or email)

What not to do:

• Do not post inflammatory comments about the opposing team on your Noticeboard (it will be screenshotted)
• Do not approach the opposing team's coach or admin aggressively on the day
• Do not post match incident details publicly before your own committee has reviewed them

---

SECTION 3: FORMAL INTER-CLUB COMMUNICATION

Club-to-Club Communication Protocol

For formal matters (complaints, transfer negotiations, match incident disputes), the communication hierarchy is:

1. Informal first: Team Manager to Team Manager for minor issues (colour clash, late ball, etc.)
2. Admin to Admin: For issues requiring club-level resolution (travel reimbursement disagreements, code of conduct matters)
3. President to President: For significant disputes, complaints about conduct, or relationship issues
4. Via association: For unresolved disputes, clearance disputes, formal complaints

Never: A player or coach directly contacting the opposing club's administration over a grievance. Route through the appropriate level.

---

Making a Formal Complaint Against Another Club

If your club needs to formally complain about another club (e.g., their player struck one of yours):

1. Document internally: external incident record (Module 76) + Admin Panel notes
2. Committee resolution: confirm the complaint is worth pursuing formally
3. Contact association: most associations have a formal complaint/report process
4. President writes a formal letter/email to the association (cc'ing your club's copy of the incident record)
5. Do NOT contact the opposing club's admin or president about this while an association process is underway

In GoClubPro: No platform action for the complaint itself. If your player was injured: injury recorded in profile. The complaint is handled externally.

---

Responding to a Complaint From Another Club

If you receive a complaint:

1. Acknowledge receipt immediately ("Thank you for raising this. We will investigate and respond within [X] days")
2. Do not admit liability in the acknowledgement
3. Committee reviews the complaint; hears from the people involved; checks your incident records
4. Respond via the same channel the complaint came through (email if email, association portal if via association)
5. Internal action if warranted: discipline process (Module 80)

---

SECTION 4: PRE-SEASON FRIENDLIES AND JOINT EVENTS

Adding a Friendly Match to GoClubPro

Pre-season friendlies can be added to the Schedule so members receive proper RSVP and squad confirmation:

1. Schedule → Add Event (or Add Fixture — non-competition)
2. Type: Friendly / Pre-season match
3. Venue, date, time, opponent name
4. Squad confirmation works normally

The friendly is on your own schedule — the opposing club has no visibility into your GoClubPro. Coordinate start time and venue externally; just enter it into your own platform for your members' benefit.

---

Joint Social Events

For events involving both clubs (end-of-season joint function, combined junior clinic):

Coordination: External (email, phone between the two admins/presidents)

In GoClubPro:

1. Noticeboard post announcing the event (with date, venue, RSVP details)
2. If collecting money (shared function ticket): Payments → or record manually in Accounting
3. If the joint event is a Club event on Schedule: add it as an Event type

Reminder: The opposing club's members will not see your Noticeboard. Communication to your own members happens in the platform; communication to the joint guest list happens externally (email, flyer).

---

SECTION 5: RIVALRY AND SPORTSMANSHIP

Healthy Rivalry Culture on the Noticeboard

Good-natured rivalry between clubs is part of community sport. The Noticeboard can host rivalry content that builds culture without becoming inflammatory:

Good rivalry content:

"The big one this week — we face [Rival Club Name]. After last season's final, we know what's at stake. Let's put the hard work in this week. See you at training Wednesday!"

"Results are in — [Score]. The rivalry continues. See you next year, [Rival Club]."

What to avoid:

• Personal attacks on named players from the opposing team
• Content that's disrespectful about opposing coaches or admins
• Anything that could be screenshotted and shared externally as evidence of poor sportsmanship
• Content that your own players wouldn't be comfortable showing their opposing counterparts

The test: "Would the opposing club's president read this and think less of our club?" If yes: don't post it.

---

Complimenting Opponents Publicly

A brief public acknowledgement of a good game, a strong opposing player's performance, or a well-run event by another club costs nothing and builds enormous goodwill in the competition:

"Tough loss today, but credit to [Club Name] — they were clinical. We'll be back next week."

"Great to play [Club Name] in yesterday's friendly — well run, great atmosphere, looking forward to meeting them in the competition!"

This is the kind of Noticeboard content that gets shared positively within the competition community.

---

VISUAL: Inter-Club Communication Hierarchy

MINOR LOGISTICS (venue, timing, colours)
 → Team Manager ↔ Team Manager (text/phone)
 → Platform: Schedule → fixture notes for own members

CONDUCT INCIDENTS (on-field)
 → Coach/Admin documents internally (Module 76)
 → Admin → Admin if resolution needed at club level
 → Association if unresolved

FORMAL COMPLAINTS
 → President → Association (formal channel)
 → Not directly to opposing club while association process runs

TRANSFER/CLEARANCE
 → Both clubs via association portal (Module 63, 81)

FRIENDLY MATCHES
 → Agree externally → add to own Schedule → squad confirmation as normal

JOINT SOCIAL EVENTS
 → Coordinate externally → Noticeboard for own members

---

TOOLTIPS & HINTS

• Away fixture: confirm venue — don't assume the your league platform draw has the correct venue; confirm with the home club's Team Manager before travel
• Colour clashes: sort early — Round 1 is too late if you need alternate kit; check fixture list at season launch
• Complaint protocol: association first — going directly to the opposing club with a formal complaint often escalates rather than resolves
• Noticeboard rivalry content: apply the screenshot test — if it could embarrass the club externally, don't post it
• Friendly on Schedule — even for non-competition matches, adding to Schedule means your members get proper RSVP and squad confirmation

---

FAQ

Q: An opposing club has posted insulting content about our club on their Facebook page. What do we do? A: Respond once, professionally, publicly if needed ("We were disappointed to see this post. We believe in respectful competition and hope we can continue to represent the sport well together"). Then let it rest. Don't escalate publicly. Raise with the association if it's a pattern or seriously defamatory.

Q: A player wants to trial with another club in the off-season. Is that okay? A: That's an individual decision. If they return to your club next season: they're welcome. If they transfer: clearance process (Module 63). The off-season is typically outside the clearance requirement, but check your association's rules.

Q: The opposing club's coach is spreading rumours about our players. What do we do? A: President contacts the opposing club's president privately first ("We've heard some comments that concern us — I'd like to discuss this directly"). If the issue persists: association. Don't respond via social media or Noticeboard.

Q: We want to organise a joint end-of-season function with our biggest rival. How do we coordinate ticket sales? A: Coordinate externally. For your own members: Noticeboard post + Payments if collecting via the platform (record the income when tickets are sold). For the opposing club's members: they handle it through their own system. Settle costs between the two clubs externally (split by attendance ratio or agreed split).

---

COMMON MISTAKES

---

SHORT ONBOARDING SCRIPT

"Most inter-club communication is handled between Team Managers for day-to-day logistics (venue confirmation, colour clashes, match timing) and between Presidents or Admins for more significant matters. The platform handles your side: update the Schedule for any fixture changes and broadcast to your own members — never rely on the opposing club to tell your people. For conduct incidents, document internally first, then use the association process rather than going directly to the opposing club. On Noticeboard: good-natured rivalry is part of the game, but apply the screenshot test to anything you post about opponents. A brief 'well done to [Club Name]' post after a tough loss does more for your reputation than anything."

---

MICRO-TRAINING QUICK TIPS

• Away venue: Team Manager confirms with home club the day before — don't assume the draw is correct
• Colour clash: check at season launch, not Round 1
• Conduct incident: document internally → association process (not direct club-to-club for formal matters)
• Friendly: add to Schedule → squad confirmation works normally for your own members
• Noticeboard rivals content: screenshot test before posting
• Joint events: coordinate externally → Noticeboard for own members → Payments if collecting
• Complaint from another club: acknowledge → investigate → committee → respond

---

Training Module 86 | See also: 76 Incident Reporting · 59 Match Day Operations · 63 Player Transfers · 40 Communication Playbook · 58 Club Policy & Governance