# Pipeline hygiene workflow

> How Koshra's revops_desk sets stage rules and required fields, then runs a scheduled scan that proposes CRM fixes in small batches without merging or deleting.

Canonical: https://koshra.com/workflows/pipeline_hygiene
Last updated: 2026-11-02

Stage rules and required fields, then a scheduled scan that proposes fixes in small batches. Bots never merge or delete.

Owner: [revops_desk](https://koshra.com/roles/revops_desk)

## How it runs

1. revops_desk writes the stage rules and required fields with you.
2. routines_desk writes the scan as a checklist with an owner and a stop condition.
3. You approve the schedule, and the scan runs on the server.
4. Each run flags the rows that break a rule and proposes fixes in small batches.
5. You approve writebacks. Deletes and merges are blocked.

## What waits for you

- The schedule
- Every CRM writeback, and any bulk change

## Roles involved

- [revops_desk](https://koshra.com/roles/revops_desk)
- [pipeline_desk](https://koshra.com/roles/pipeline_desk)
- [routines_desk](https://koshra.com/roles/routines_desk)

## Apps it can use

- [HubSpot](https://koshra.com/integrations/hubspot)
- [Twenty CRM](https://koshra.com/integrations/twenty)
- [Google Sheets](https://koshra.com/integrations/google_sheets)

The steps show how the roles in our template divide the work. Your setup is agreed with you. Pricing: talk to us.