Skip to main content

How it works

How Tarivra verifies program status

Tarivra reads the work your teams already track in Jira, Azure DevOps, ServiceNow, GitHub and GitLab, checks it against the status they report, and gives leaders a verified portfolio view with the evidence behind every program.

  • JiraEpics, initiatives, stories, sprints and dates
  • Azure DevOpsEpics, features, work items and iterations
  • ServiceNowEpics, themes, releases, stories and changes
  • GitHubLabeled issues and their sub-issues
  • GitLabLabeled issues and their tasks

Tarivra verifies

Any item labeled tarivra-program (Epic, Feature, issue), read every 15 minutes, read-only

  • Progress and blocked work
  • Scope added late
  • Target dates moved
  • Changes and incidents
  • Status reported vs. evidence
  • Integrity scoreReported status checked against the data
  • Executive briefWeekly, cited, by email and chat
  • Decision ledgerWritten back to the team's tool, tracked to done
  1. 01

    Connect your tools, read-only

    Your admin gives Tarivra a read-only account in each tool your teams use: Jira Cloud, Azure DevOps, ServiceNow, GitHub or GitLab, in any mix. Tarivra sees only the projects, repositories and tables you grant, and never reads source code or attachments.

    • Jira and Azure DevOps: a service account limited to the projects in scope
    • ServiceNow: an integration user through OAuth, no shared password
    • GitHub: the Tarivra GitHub App on the repositories you choose
    • GitLab: a project access token on each project you choose
  2. 02

    Label each program once

    A team adds the tarivra-program label to the item its work rolls up to: an Epic, Feature or Initiative in Jira or Azure DevOps, an Epic, Theme or Release in ServiceNow, or an issue in GitHub or GitLab. That item is the program's source of truth for its name, owner and target date. No new forms and no new meetings.

    • One program can draw on more than one tool
    • Teams keep their own boards, statuses and rituals
  3. 03

    Tarivra reads the work every 15 minutes

    Tarivra reads the labeled item and every item under it: status and status history, owners, due dates, estimates, blocked flags, scope added after the start, moved target dates and, in ServiceNow, change requests and the incidents they caused.

    • Each tool's statuses are counted as To do, In progress or Done, starting from the tool's own grouping
    • A status whose name reads differently from its group is flagged for your admin to confirm
  4. 04

    Reported status meets the evidence

    The status the team reports (Team says) is checked against the status the work supports (Data says). Data says comes from seven checks, each Green, Amber or Red, and every check lists the items behind it.

    • Schedule forecast: will the open work finish by the target date at the real pace?
    • Scope growth: how much work was added after the start?
    • Throughput trend: are fewer items finishing than before?
    • Overdue work and blocked work: what share of open items is late or stuck?
    • Stale work in progress: what has not moved in 14 days?
    • Change health: did recent ServiceNow changes fail or cause incidents?
  5. 05

    Every program gets an integrity score

    The integrity score says how well the reported status matches the evidence, from 0 to 100. Reporting a better status than the data supports costs the most points. A check with too little data is left out rather than guessed, and the score says so.

    • 75+
      Matches the evidence
    • 50–74
      Partly matches
    • Under 50
      The status hides risk
  6. 06

    Executives get a cited weekly brief

    Each week the people you choose get a short brief by email with a PDF, or in Slack or Google Chat: what needs attention, in plain sentences, each citing the records it rests on. A sentence the evidence does not support is withheld. Tarivra writes the brief with its own engine, so your program data is not sent to an AI service.

    • Forecast ranges from each team's real pace, with the chance of making the target date
    • Data hygiene: work with no owner, past due or untouched, with a short weekly list to each owner
  7. 07

    Decisions and questions go back to the team

    When leadership decides something, record it in Tarivra with an owner and a due date. Tarivra creates the item in the team's own tool and tracks it until it is done, on time or late. Questions for a program owner work the same way and are answered where the team already works.

    • Written back to Jira, Azure DevOps, ServiceNow, GitHub or GitLab
    • Every decision, question and sign-off is in an audit log nobody can edit

From demo to your first verified brief

It starts with a 30-minute demo on a portfolio like yours. When you are ready, setup is light, and your teams keep working the way they do today.

  1. Day 1Connect read-only accounts and sign in with your company's single sign-on.
  2. Week 1Teams label their programs; your executives get their first verified brief.
  3. Week 4Review integrity scores, decisions followed through and promised dates kept.

See how each tool connects on Integrations, or learn how to verify project status by hand. Want the security details first? Read how Tarivra protects your data, or compare plans and pricing. To see what leaders use it for, from verified status reporting to decision tracking, browse Solutions.

Questions

How do you verify project status?

Compare what the team reports with what the work shows. Tarivra reads the items under each program in Jira, Azure DevOps, ServiceNow, GitHub or GitLab, runs seven checks (schedule, scope, throughput, overdue, blocked, stale and change health) and scores how well the reported status matches.

Does Tarivra change anything in our tools?

No, except the decision and question items your leaders choose to send to the team's tool. Every other connection only reads.

Can one program span Jira and Azure DevOps?

Yes. A program is anchored to one labeled item and can draw on work in more than one tool, so a portfolio that runs on Jira and Azure DevOps is reported in one place.

What if our statuses are custom?

Tarivra starts from each tool's own grouping of statuses and flags any status whose name suggests otherwise. Your admin confirms or changes the mapping, and it applies from the next sync.

How long does setup take?

Usually a day for the connections and labels, and the first verified brief within the first week.