Tolmete Patterns

Find Process Gaps Across Your Projects

Tolmete checks your connected tools for missing reviews, unassigned work, and gaps in project planning. After the first sync, your team can see existing issues and suggested fixes.

Explore Patterns

* No manual rule setup. Clear fixes. Internal to your team.

Connect GitHub, Bitbucket, Jira, and Asana.
Available checks depend on the connected tool and accessible data.

Project Planning
Medium

An estimate with no description

A ticket has an estimate, but no written description of the work.

Alex CooperFront-End Engineer
15 Sep, 2026
Task OwnershipNew
High

Work in progress with no owner

A ticket is in progress, but its assignee field is empty.

Yevhen SyniiPM & Product Owner
15 Sep, 2026
Code Review
Low

Merged with no review

Code was merged without an approving review.

Jane MillerUX/UI Designer
15 Sep, 2026

Do All Your Repositories Require Code Review?

A written rule does not tell you which repositories actually enforce it. Tolmete shows where review requirements are missing across your connected repositories, so you know which settings to change.

Use the findings to check your process before answering a client's security questionnaire.

Code Review Across Your Repositories

12 of 14 repositories require an approving review before merge.

  • GithubPavloGithub
    Review Not Required
  • @design_leadAsana
    Review Required
  • alex.devGithub
    Review Not Required

Connect Your Tools. See What Needs to Change

Setup takes one connection. From there, Tolmete reads the process context in your data and surfaces the gaps in three steps.

  1. 01.

    Connect the Tools Your Team Already Uses

    Connect a supported integration. Tolmete works out the process context from the data without a rule setup form.

  2. 02.

    Review the Gaps Already in Your Data

    See existing process gaps after the first sync. Each Pattern explains what happened, how often it occurred, and where it appeared.

  3. 03.

    Make the Change That Addresses the Gap

    Follow the suggested fix in your repository, tracker, or project setup. Your team makes the change.

Day-one value

You do not need to wait for a new incident to uncover an existing gap. Initial findings depend on the settings and history available from your connected tools.

See the Finding, the Evidence, And the Fix

Each Pattern connects a process gap to the projects it affects and a practical change. This example shows a missing review step and the setting that addresses it.

Pattern found: 3 pull requests merged with no review. Rule: code should be reviewed by someone other than its author. Fix: turn on branch protection with required reviews on main.

Find the Gaps Behind Everyday Delivery Problems

Tolmete runs 21 checks covering code review, task ownership, estimates, and project records. Browse the checks below by the process question they answer.

  • Review not requiredThe main branch does not require an approving review before merge
    Available
  • Branch protection offThe main branch has no protection rule
    Available
  • Pull request checks missingAutomated checks do not report on pull requests
    Available
  • Merged with no reviewCode was merged without an approving review
    Available
  • Approved too fastApproval arrived unusually quickly, suggesting the review may need a closer look
    Available
  • No reviewer requestedA pull request is open, but no reviewer has been requested
    Available
  • Merged with open commentsCode was merged while review comments were still unresolved
    Available
  • Large change with no descriptionA large code change was merged without a description
    Available
  • Force-push or direct commitShared history was rewritten, or code was pushed directly past the pull request process
    Available
  • Stale branchA branch holds commits without a pull request for an extended period
    Available
  • Work in progress with no ownerA ticket is in progress, but its assignee field is empty
    Available
  • Stale in progressStale in progress
    Available
  • Repeatedly reopenedThe same work keeps returning after it was considered complete
    Available
  • Tracker behind codeThe code was merged, but the linked ticket status was not updated
    Available
  • Status behind realityTime was logged against a ticket that never left To Do
    Available
  • Estimate coverageToo few tickets have estimates to support a project forecast
    Available
  • An estimate with no descriptionA ticket has an estimate, but no written description of the work
    Available
  • Project plan with dates missingThe project does not have a plan with dates
    Available
  • No contract dataThe project lacks the hours ceiling and rates needed for financial calculations
    Available
  • A pull request with no ticket numberThe main branch has no protection rule
    Available
  • Unmatched commit accountsCommits come from accounts that are not linked to a known team member
    Available

Clear Findings. Less Admin Work

Your managers get a clear finding and a suggested fix, without configuring rules or maintaining reports.

  • One Message Across Projects

    When the same process gap appears in several projects, Tolmete groups the findings into one message. It lists the affected projects and the number of occurrences in each, with access to individual project details.

  • A Clear Limit On Interruptions

    Each person receives at most 3 Pattern messages per week, with no more than 1 per day. No Pattern messages are sent on weekends.

  • Your Managers Stay In Control

    A Project Admin or Super Admin can switch off a Pattern for that project. There is currently no Undo.

  • Internal to Your Team

    Patterns do not name people, rank developers, or assign personal scores. They are not shown in the Client Portal and cannot be shared with clients.

1 process gap found across 5 of your projects: pull request titles have no ticket number. This happened 24 times in the last 7 days across Northwind Retail, ARQ Decisions, Beacon Health, Halden Group, and Vantage Labs.
Patterns summary: consistent work style, Tuesday peak day, and 92% logging discipline.

Understand Process Gaps With Patterns And Project Risks With Signals

Patterns and Signals run on the same connected data but answer different questions. One keeps your process clean, the other protects the margin on a specific project.

Patterns
Main question
Where does the project process need attention?
Scope
Process gaps within and across projects
What you see
The finding, its frequency, and a suggested fix
Signal
Internal team only
Audience
Code was merged without an approving review
Signals
Main question
Which project problems could lead to financial losses?
Scope
Risks affecting an individual project
What you see
The risk, supporting evidence, project context, and severity
Signal
Can be shared with the client
Audience
Unplanned work puts a fixed-price project's margin at risk
Explore Evidence-Based Signals

See What Needs to Change Across Your Projects

See how Tolmete finds process gaps, shows where they repeat, and explains the next step. Book a demo to explore Patterns in practice.

FAQ

Frequently Asked Questions

Patterns are findings that show gaps in how work is planned, assigned, tracked, or reviewed. Each finding identifies the issue, the affected projects, and a suggested fix. For example, a ticket may be in progress with no assignee, or a pull request may have been merged without approval. Supporting examples let your team check what happened before making a change.
Yes, if the first sync provides the data a check needs. Tolmete can identify existing problems without waiting for them to happen again. A missing review requirement can be read from repository settings, while finding past merges without approval requires review and merge history. What appears first depends on the data available through the connected source and its permissions.
No manual rule setup is required. Tolmete identifies the process context from your connected tools. You do not need to enter a list of branches or describe your workflow in a configuration form. Your team reviews the suggested fixes and decides whether they fit the project's requirements.
Tolmete Patterns works with GitHub, Bitbucket, Jira, and Asana. Available checks depend on the integration and the data Tolmete can access. Repository checks use branch settings and pull request activity, while tracker checks examine ticket status, assignees, and estimates. Some checks draw on several of these sources.
Patterns highlight process gaps and suggest fixes. Signals flag project issues that could lead to financial losses. A Pattern might identify missing estimates or skipped reviews without assigning a loss in hours or money, while a Signal uses project context to explain a potential financial risk.
No. Patterns report process gaps without naming people, ranking reviewers, or assigning individual performance scores. Repository checks use settings and activity metadata, such as pull request status and review timing. Tolmete does not read source code for either Patterns or Signals.
Each person receives at most three Pattern messages per week, and no more than one per day. No Pattern messages are sent on weekends. If the same gap appears in several projects, Tolmete groups the findings into one message.
Yes. Got It! acknowledges and hides a message. Don't Show Again turns off that type of Pattern for a specific project. This affects only the selected project, and there is currently no Undo option.
No. Tolmete suggests a fix, and your team applies it in the relevant tool or project settings. For example, you can enable required reviews when a branch allows merges without approval.