Blog / Other resources

Why is it important to trace finished work to pull requests and tickets?

A unit of finished work that links to its pull request and ticket can be checked by the client, the provider and the manager. See why it matters.

What does traceability give you?

Without traceability With traceability
A number in a report A number with the work behind it
Disputes about what was delivered One shared record
Hours as the only proof The shipped change as the proof
Agent work is not visible Agent work links to its pull request too

Where does it matter most?

  • Pricing per unit of work: a client pays for delivered work only if it can check the work.
  • Contract renewals: delivery evidence from the code supports the new price.
  • AI agents: an agent session that ends in a merged pull request is delivered work. A session with no pull request is cost only.

How does Pensero do it?

  1. It reads pull requests, reviews, tickets and docs read-only.
  2. It scores each piece of finished work after it ships, by magnitude × complexity.
  3. It links each delivery point to its pull request and ticket.

How Pensero helps

Frequently asked questions

Why not use hours as proof?

Hours show effort, not the result. A pull request shows the change that shipped.

Does this work for AI agents?

Yes. Agent work links to its pull request and ticket, the same as human work.

Can a client see the evidence?

Yes. Each delivery point links to the pull request and the ticket behind it.

What do I do with the evidence?

Use it to agree on what was delivered and what to improve next. Then measure delivery, cost per delivery point and quality again.