Communication
How we stay in sync, run meetings, and report bugs.
Good communication is the difference between a smooth project and a stressful one. This page is the single reference for how we talk to each other during your engagement with Calda.
Channels
- Slack (shared channel) — primary channel for day-to-day work, questions, and quick updates. Expect a response within one working day.
- Email — used for contracts, invoices, and anything that needs a permanent paper trail.
- Loom / screen recordings — preferred over long Slack threads for walkthroughs, design reviews, and bug repros.
- Calendar (Google / Cal.com) — all meetings are booked through shared links so no one has to chase scheduling.
Meeting cadence
| Meeting | When | Purpose |
|---|---|---|
| Weekly sync | Every week, 30 min | Review progress, surface blockers, plan ahead |
| Sprint review | Every 2 weeks | Demo the latest build and gather feedback |
| Milestone review | At each pipeline stage | Sign off on Discovery, Design, Build, Publish |
| Ad-hoc | On demand | Anything urgent that can't wait for the sync |
Agendas are posted in Slack the day before; notes and action items are written up the same day the meeting ends.
How to file a bug report
A good bug report saves a round-trip. When something's broken, please share:
- What you did — the steps to reproduce, in order.
- What you expected — what should have happened.
- What actually happened — what you saw instead.
- Where you saw it — device, OS version, app version (visible in Settings).
- Evidence — a screenshot, screen recording, or Sentry link if you have one.
Post bugs in the shared Slack channel using the :bug: emoji so they're
easy to find later, or open a ticket directly if we've set up a tracker
together.
Response-time expectations
- Same business day — anything blocking your team.
- Within 24 hours — questions, decisions, and small requests.
- Within the sprint — feature requests and non-urgent changes.
- Out of hours — we don't expect responses on evenings or weekends from either side, unless a release is actively going out.
If something is urgent and you haven't heard back, tag the project lead directly in Slack.