A distributed team's real problem is not tooling, it is that status has to travel without a meeting attached. Redmine's daily digest, saved queries and chat integrations push what changed to people who were asleep when it changed, which is the whole job.
The daily standup exists to answer three questions: what moved, what is blocked, and what is next. Across six time zones there is no hour where asking those questions synchronously is fair to everyone, and the usual fix — moving the meeting to a recorded call or a written thread — keeps the ritual and loses the accuracy, because it is a summary of the system rather than the system. The alternative is to let the tracker answer the three questions directly.
What moved. Redmine's activity stream is a chronological record of everything that changed in a project — issues created, statuses moved, comments added, time logged, files attached — filterable by type and by user. A colleague starting their day scrolls one page and knows what happened while they were offline. No one wrote it, so no one had to.
What is blocked. Blocked by is an issue relation, not a comment convention. A saved query filtered to blocked issues, sorted by age, is the blocker list, and it is accurate because it is derived rather than reported.
What is next. Issues carry assignee, priority, due date and version. A query filtered to a person's open items due this week is their day, and every person's My Page shows it without anyone assembling it. The shift this asks for is real: things that were said in a meeting now have to be written on an issue. Teams that make that shift stop needing the meeting.
Included on every plan, from Startup at $24/mo, the daily digest is the piece that makes the asynchronous loop work without anyone remembering to check anything. Instead of a notification per event — which across time zones means arriving to ninety emails and reading none — the digest delivers one summary of what changed, timed to the recipient. Someone in Manila and someone in Lisbon each get their morning summary in their own morning. Redmine's own notification settings sit underneath: each user chooses whether to be notified about everything in their projects, only things they watch or are involved in, or only things assigned to them. Mentioning someone with @ pulls them into a thread and notifies them directly, which is how you get a specific person's attention without a meeting or a direct message that disappears from the record.
RedminePRO includes Slack on every plan from Startup, and Discord, Rocket.Chat and Mattermost from the Plus plan at $49/mo. The Mattermost and Rocket.Chat options matter for teams that self-host their chat for data-control reasons, a common posture in distributed companies with mixed jurisdictions. The useful configuration is narrow: route a channel's notifications to the issues that channel actually owns, not to everything — a firehose channel gets muted within a week, and a muted channel is worse than no channel because people believe they are covered. Chat is for the interrupt; the issue is the record. When a decision gets made in chat, it goes on the issue, or in three months it did not happen.
Redmine stores a time zone per user in their account settings, and displays timestamps in the viewer's local time. Two people looking at the same issue see “yesterday at 16:40” in their own terms and neither has to do arithmetic. Due dates are dates rather than instants, which avoids the off-by-one that plagues tools treating a deadline as a timestamp. One practical convention worth adopting: when a due date genuinely depends on an hour — a release window, a customer commitment — put the time zone in the issue subject or a custom field.
Distributed teams grow in a specific way: a person here, a contractor there, a support hire in a different country. On per-seat pricing, each is a recurring increment and someone eventually starts asking whether the new person really needs an account. RedminePRO is flat: $24/mo for 25 users, $49/mo for 100, $169/mo for 250, unlimited projects throughout. Adding the contractor costs nothing. Pricing has the detail and the comparison pages have the arithmetic against per-seat vendors at each team size.
Remote teams accumulate tools, because every gap gets filled by whatever someone found that week, and then status lives in five places. A single Redmine instance covers issue tracking, time tracking, a wiki per project, file storage, project forums, a calendar and a Gantt view, with the same permission model across all of them. Documentation next to the work it documents is read; documentation in a separate product is not. And when someone leaves — which happens more visibly on a distributed team — everything they knew is in a system the next person already has access to. If you are consolidating from several tools, the free assessmentcovers what carries over from each, with the migration itself quoted as a one-time professional-services fee afterward. Infrastructure, upgrades, patching and backups are ours, which for a company with no office and no sysadmin is usually the deciding factor: what managed covers.