Sleuth Documentation
HomeBlogSupportSign up
  • Getting started
  • Navigating Sleuth
  • DORA metrics
    • Deploy frequency
    • Change lead time
    • Change failure rate
    • MTTR
    • Interpreting Metrics in Sleuth
  • Deployment tracking
    • Organization
      • Labels
      • Trends
      • Compare
      • Search
      • Status
    • Projects
      • Issue trackers
    • Environments
    • Code deployments
      • Creating a deployment
      • How to register a deploy
      • Rollbacks
      • Automatic tagging
      • Deployment locking
      • Environment drift
      • Move code deployments
      • Search everything
    • Feature flags
    • Manual changes
    • Deploys
    • Teams
  • Work in Progress
  • Goals
  • Sleuth Automations
    • Automations Marketplace
      • Installing Automations
        • Installing PR "Update" Automations
      • Editing and uninstalling Automations
      • Smart suggestions
      • Understanding efficacy
    • Custom Automations
      • Automations Cookbook
      • Webhook Actions
      • Trigger Build Actions
        • Bitbucket Pipelines
        • CircleCI
        • Github Actions
        • Jenkins
  • Slack & Email Notifications
  • Auto-verify deploys
    • Anomaly detection
    • Error impact
    • Metric impact
  • Ignoring pull requests
  • Slack mission control
    • Approvals
    • Project notifications
    • Personal notifications
    • Search Sleuth in Slack
    • Project/Deployment history
    • Developer standup
  • Sleuth API
    • Deploy Registration
    • Deploy import
    • Manual Change
    • Custom Incident Impact Registration
    • Custom Metric Impact Registration
    • Deprecation information
    • GraphQL Queries
    • GraphQL Mutations
    • Query batching
  • Integrations
    • About Integrations...
    • Code integrations (read-only)
      • Azure DevOps
      • Bitbucket
      • GitHub
      • GitLab
      • Custom Git
      • Terraform Cloud
    • Code integrations (write)
    • Feature flag integrations
      • LaunchDarkly
    • Impact integrations
      • Error trackers
        • Bugsnag
        • Honeybadger
        • Rollbar
        • Sentry
      • Metric trackers
        • AppDynamics
        • AWS CloudWatch
        • Custom
        • Datadog
        • Jira metrics (Cloud / Data Center)
        • NewRelic
        • SignalFx
      • Incident tracker integrations
        • Blameless
        • PagerDuty
        • Datadog Monitors
        • Statuspage
        • Opsgenie
        • Jira (Cloud/Data Center)
        • FireHydrant
        • Rootly
        • ServiceNow
        • Custom
          • Grafana OnCall
      • CI/CD builds
        • Azure Pipelines
        • Bitbucket Pipelines
        • Buildkite
        • CircleCI
        • GitHub Actions
        • GitLab CI/CD Pipelines
        • Jenkins
    • Sleuth DORA App for Slack
    • Microsoft Teams integration
    • CI/CD integrations
      • Azure Pipelines
      • Bitbucket Pipelines
      • Buildkite
      • CircleCI
      • Github Actions
      • GitLab CI/CD Pipelines
      • Jenkins
    • Issue tracker integrations
      • Jira Cloud
      • Jira Data Center
      • Linear
      • Shortcut
    • Fixing broken integrations
  • Pulse
    • Welcome to Pulse docs
    • Quick Start setup guide
    • Beginner tutorials
      • 1. How to create a Teamspace
      • 2. How to create a Review
      • 3. How to create a Survey
  • Features
    • Reviews
      • Review workflow
      • Review templates
      • Widgets and Sections
        • Widget type
      • Review settings
    • Surveys
      • Survey Workflow
    • Teamspaces
    • Inbox
    • AI assistant
    • General settings
      • Users and Teams
      • Investment mix
  • Settings
    • Organization settings
      • Details
      • Authentication
        • SAML 2.0 Setup
          • Okta Configuration
          • Azure AD Configuration
          • PingIdentity Configuration
      • Access Tokens
      • Members
      • Team Settings
      • Billing
    • Project settings
      • Details
      • Slack settings
      • Environment settings
      • Code deployment settings
      • Feature flag settings
      • Impact settings
    • Account settings
      • Account settings
      • Notifications settings
      • Identities settings
    • Role Based Access Control
  • Resources
    • FAQ
    • Sleuth TV
    • Purchasing
    • About Sleuth...
Powered by GitBook
On this page
  • Review cycles
  • Review roles
  • Review states
  • Sharing Reviews

Was this helpful?

  1. Features
  2. Reviews

Review workflow

PreviousReviewsNextReview templates

Last updated 1 month ago

Was this helpful?

Sleuth Reviews follow a common workflow to help users:

  • Review automated metrics

  • Provide manual data (e.g. quantitative metrics, text, images)

  • Add comments (as they collaborate on preparing the review)

  • Add action items (to be reviewed in the next Review cycle)

  • Add summary narratives and scores (manually or using Sleuth's AI assistant)

  • Share their completed reviews with stakeholders

Review cycles

Engineering organizations have recurring Review cycles at all levels. Teams might perform daily stand-ups, weekly planning syncs, biweekly sprint reviews, or monthly retros. Managers report up to senior leaders who in turn report out to go-to-market teams, the board, or at all-hands.

Sleuth's Review workflow aligns to cycles, guiding users to repeat activities on a predictable schedule.

Review roles

Reviews always have one Review owner and might also have assigned Section owners. See more on these roles below.

Review states

All Sleuth reviews move through the following three states:

  • Draft: This first state is where the Review owner sets up by arranging its Widget and Sections or assigning section owners in Review settings. When ready, the Review owner moves the Review to the next state by clicking the Start review button.

  • In progress: Most of the activity in a Review happens during the this state. If Section owners have been assigned, Sleuth sends them notifications to let them know them to complete their sections. Once the Review owner is satisfied that all Sections are complete, they Publish the Review to move it to the final state.

  • Published: Sleuth "freezes" Reviews once they're published in order to preserve their history. Automated Widgets stop refreshing their data, and users are no longer able to edit the content of the Review. If needed, Review owners and admins can manually revert Reviews to In progress from Review settings.

Sharing Reviews

Once published, Review owners and section owners can share reviews by sending them as a link, downloading them as a PDF, or using Presentation mode to show them as a slide presentation from right within Sleuth. Users can also use the Share button to send a link to the presentation view with anyone, even if aren't Sleuth Users.


Related feature guides:

Review templates
Widgets and Sections
AI assistant
Review settings