Use cases and guides / By team
Sands for operations
Operations leads use Sands to see the true state of every project, report on delivery, and keep the team informed.
At a glance
| Job | Try asking | Works with |
|---|---|---|
| Check across projects | How are the website, mobile and data projects doing? | Jira, Linear, Asana |
| Report delivery hours | Hours report for all client projects last month, by person | Jira |
| Chase what is late | What is overdue in OPS, oldest first? | Jira, Linear, Asana |
| Announce a change | Draft a message for #all-hands about the new intake process, don't send it yet | Slack |
Use cases
1. Check across projects
Ask about several projects in one message and get each one's state with its numbers.
Try asking
How are the website, mobile and data projects doing?
2. Report delivery hours
Hours by project and person from Jira worklogs, ready to paste.
Try asking
Hours report for all client projects last month, by person
More: Hours reports
3. Chase what is late
The overdue work across a project, sorted by due date, with owners.
Try asking
What is overdue in OPS, oldest first?
4. Announce a change
Draft a message for review, or send it to one channel right away.
Try asking
Draft a message for #all-hands about the new intake process, don't send it yet
More: Messaging
Recommended setup
- Connect every tool your teams use; Sands can read them all in one chat.
- Use Manually approve if you work on boards you do not own.
Where to go next
Quickstart, Approvals, or the other use case guides.