BuiltBrief and your work
For developers whose team uses BuiltBrief. What it reads, what it never produces, who sees the brief and how to raise a concern.
Your team has connected some repositories to BuiltBrief. This page tells you plainly what that means for you.
BuiltBrief writes a short brief about what got built: what shipped, what's in review, what's blocked, and where risk is building up. It describes the work, and you won't find your name in it.
What it reads
BuiltBrief uses a read-only GitHub App on the repositories your team chose. On a schedule, usually weekly, it reads:
- pull requests: titles, descriptions, comments, reviews and status;
- short, size-limited excerpts of pull request diffs;
- issues and their comments;
- CI results and deployments.
It can't read your repository files directly, and it can't write anything to GitHub.
The text and diff excerpts go to an AI model to write a summary of each pull request. They're then discarded. BuiltBrief doesn't store your code or diffs. It keeps pull request metadata, such as titles, links, status and timestamps, so each claim in the brief can link back to its source. It doesn't store who wrote or reviewed each pull request.
What it never produces
- No per-person scores, ratings or productivity numbers.
- No rankings or leaderboards.
- No commit counts, lines-of-code tallies or "top contributor" lists by person.
- No activity tracking, working-hours analysis or idle time. A quiet week in GitHub is just a quiet week in GitHub.
- No guesses about your mood, effort or attitude.
BuiltBrief is built to decline questions like "who is slowest?". Its terms also forbid your company from using it to evaluate, discipline, pay or fire individual people.
About AI and "agent signals"
Briefs are written by AI and can be wrong. Every claim links to the pull request or issue it's based on, so anyone can check it.
Some briefs note when a pull request carried a coding-agent signal, such as a commit trailer or a bot account. Treat it as a hint: markers can be missing or switched off, and BuiltBrief never labels work as "human". These signals are only reported for the team as a whole.
Who sees the brief
- The person who set up BuiltBrief for your team (the owner).
- Up to 5 other readers the owner adds, usually leaders or stakeholders.
Readers get the brief by email, with a private link.
- Anyone with the team's team link. The owner can share it with the whole engineering team; it opens every brief and doesn't count toward the 5 readers.
You can see it too, and add context
BuiltBrief is meant to be read by the people whose work it describes. Ask the owner for your team's team link. With it you can read every brief, and if a brief gets something wrong or misses why something happened, you can add a short note next to any item. Readers see your note alongside the claim, and the next brief takes it into account as context (never as proof).
How long things are kept
Digests and briefs are kept for up to 13 months, then deleted. If your team uninstalls BuiltBrief, everything is deleted within 30 days.
Raising a concern
- Start with your team. The owner can change which repositories are connected or remove BuiltBrief at any time.
- Ask us. Email hello@builtbrief.com with the subject "Contributor question". We'll answer what we can and, where needed, pass your concern to your team.
- Privacy rights. If you're in the EU, UK or a similar place, you have rights over your personal data. Your employer is responsible for this data; we help them. See our Privacy Policy.
- If something looks like surveillance, tell us. Using BuiltBrief to judge individuals breaks our terms, and we take reports seriously.