Use cases and guides / By industry
Sands for financial services
Teams in regulated environments use Sands for planned, reviewable change: every change is shown before it runs if you choose, and every run keeps a record of what was read and changed.
At a glance
| Job | Try asking | Works with |
|---|---|---|
| Plan remediation work | Create a remediation plan from these audit findings: attached | Files, Jira, Linear, Asana |
| Status with evidence | Status of the compliance remediation project, with what is overdue | Jira, Linear, Asana |
| Effort reporting from the source | Hours logged against the audit project this quarter | Jira |
Use cases
1. Plan remediation work
Turn a findings list into tickets with owners and due dates, reviewed before anything is created.
Try asking
Create a remediation plan from these audit findings: attached
More: Plans
2. Status with evidence
Health reads cite the numbers they found, and the run shows where each came from.
Try asking
Status of the compliance remediation project, with what is overdue
3. Effort reporting from the source
Hours computed from worklogs, never typed by a model.
Try asking
Hours logged against the audit project this quarter
More: Hours reports
Recommended setup
- Use Manually approve so every change waits for review.
- Keep each run's record: expand a reply to see what was read and changed.
- See Security and data for how credentials and data are handled.
Where to go next
Quickstart, Approvals, or the other use case guides.