A remote team in Telegram usually lives out one of two scenarios. Either the chat is silent and nobody knows who’s doing what. Or there are 400 messages a day, twenty of them work-related, and assignments drown between memes and “morning, everyone”.
Both extremes have the same cure: a written agreement about how we work. Not a fifteen-page corporate policy — one message, pinned in the chat.
Below is what such an agreement should contain, why those particular items, and a ready text you can copy and adapt.
Why it doesn’t work without one
In an office the space itself sets the rules: the person at the next desk is visible, the 10:00 stand-up is obvious, the day ends when everyone stands up and leaves. Remotely none of that exists — so everyone invents the rules for themselves.
Hence the classic conflicts: one person believes replies should be instant, another that same-day is fine. One writes in DMs, another waits for work in the group chat. One finishes at 18:00, another messages them at 23:40 and takes the silence personally.
An agreement isn’t about control. It’s about everyone holding the same picture.
What belongs in it
1. Chat structure
One general chat for everything is the main source of noise. The minimum workable layout:
- Team-wide chat — announcements, news, non-work. Read once a day.
- Project or discipline chats — actual work discussion. This is where tasks are born.
- Direct messages — personal and urgent only.
The rule: fewer chats is better, but the general chat is not where tasks live. With many projects, three chats where everything is on-topic beat one that nobody reads.
2. Response times
The most important item and the most frequently skipped. Agree explicitly, or everyone decides for themselves:
- Working hours — say 10:00–19:00 in the team’s time. If people are spread across time zones, state the overlap — the “shared hours”.
- Expected response inside working hours — 2 hours. Not “immediately”: demanding instant replies destroys focused work.
- Outside those hours — no reply expected. You may write; the answer comes in the morning.
- Urgent — by phone call only, and only if it genuinely is.
State one thing separately: the right not to reply instantly is part of the agreement, not a violation of it. Otherwise people sit in the chat all day and never work.
3. How to phrase an assignment
The agreement that saves the most time. An assignment in a chat needs four things:
Who · What · By when · Where the result goes
Bad: “Could you have a look, there’s a question hanging on that client.” Good: “Igor, prepare the estimate for the Ivanov project by Wednesday, put it in the project folder.”
The difference isn’t politeness — it’s that a week later, the second version still says what was promised.
4. Tasks don’t live in the chat
The key rule and the hardest one: a chat is for discussion, not storage. Once it’s discussed, the task goes into the tracker. Anything that stays only in the conversation ceases to exist within three days.
In practice this rule is followed badly, because it demands a double action: say it in the chat, then go enter it. Which is exactly why it’s worth automating: the bot recognises assignments in the conversation and offers a task for confirmation instead of forcing manual duplication. More on the mechanism in our breakdown of why tasks get lost in chats.
5. How to report
Not a “progress report”, but a minimum signal:
- Picked up a task — set the status.
- Finished — mark it done and attach the result.
- Stuck — say so immediately, not on the deadline day.
The last point deserves saying out loud: raising a problem early is normal, not an admission of weakness. Otherwise people stay quiet until the end and you learn about the slip after the fact.
6. The rhythm of the week
A remote team needs anchor points. At minimum:
- Monday, 15 minutes — what the week’s priorities are.
- Daily, in writing — a short status in the project chat: did / doing / stuck. Writing beats a call: it doesn’t consume the time of people it doesn’t concern.
- Friday, 15 minutes — what didn’t get done and why.
More calls doesn’t mean better. Every meeting should answer a question that can’t be answered in writing.
7. What must not be in it
- A requirement to be online. A green dot isn’t work.
- Screenshots and activity trackers. Nothing destroys trust faster.
- Mandatory video on every call. Make it optional.
- A rule for every eventuality. Nobody reads an agreement longer than a page.
The ready text: copy and adapt
Pin it in the team chat. It’s deliberately short — a working tool, not a document for a lawyer.
TEAM WORKING AGREEMENT
Chats
• Team-wide — announcements and news, read once a day
• Project chats — actual work discussion
• DMs — personal and urgent only
Time
• Shared working hours: 10:00–19:00
• We reply within 2 hours during working hours
• Outside those hours no reply is expected. Urgent = phone call
Assignments
• Format: who · what · by when · where the result goes
• Discussed in the chat — the task goes into the tracker
• Not in the tracker = it was never assigned
Reporting
• Picked it up — set the status
• Finished — mark done, attach the result
• Stuck — say so immediately, not on the deadline day
Rhythm
• Mon 11:00 — priorities for the week (15 min)
• Daily — a short written status in the project chat
• Fri 17:00 — what closed and what didn't (15 min)
Understandings
• Not being online all the time is fine
• Flagging a problem early is the norm, not weakness
• Rules change in the open: propose in the team chat, we discuss
How to make it stick
1. Discuss it, don’t hand it down. An agreement written by a manager alone lasts exactly one week. Get the team together for 20 minutes and walk the points — especially response times.
2. Start with three rules. Response time, assignment format, “tasks go in the tracker”. Add the rest once those hold.
3. Follow it yourself. If the manager writes at 23:00 and expects an answer, the agreement dies that same day. There’s a simple trick: schedule the message for the morning — Telegram supports it.
4. Revisit quarterly. Some rules will turn out to be unnecessary, others missing. An agreement unchanged for a year is usually one nobody reads.
Bottom line
A remote team’s agreement is one page about four things: where we talk, when we reply, how we phrase assignments, and where tasks live. Everything else is detail.
The key rule of the four: a task exists only if it’s in the tracker. The other three exist to support it.
If assignments in your team are born in conversation, take a look at Gosudarynya: the bot pulls them out of Telegram and MAX chats and chases the deadlines, so the agreement holds without manual duplication. 7 days free, no card.