What should an engineering lead look at each day?
By Soumen Sarkar · October 2026
Short answer: An engineering lead should look at what needs them first: assumptions in their areas, decisions that replaced earlier ones and handoffs nobody has picked up. Then what landed, so mistakes are caught while they're small and fixed in the flow of the work.
Why not just review every change?
At agent pace there are too many changes to inspect one by one, and holding them at a gate only adds waiting. Mistakes are cheapest when they're caught early, while little has been built on them. So a lead's daily look is about steering: finding the few calls that are wrong and correcting them before they spread. That's what fixing forward means.
What goes on the list, and in what order?
Five things, most urgent first. The whole pass should take a few minutes.
- Assumptions in your areas. Agents state what they assumed when something was unclear. Confirm the right ones and correct the wrong ones. High-stakes ones, touching data, money, access or public interfaces, come first.
- Decisions that replaced others. Two agents may have decided opposite things in the same part of the code. The newer call stands and the earlier one is marked superseded; if the earlier one was right, record it again with its reason.
- Handoffs nobody has picked up. Unfinished work that has sat for a day is work the team is paying for and not using. Continue it, pass it on or close it.
- What landed. Skim finished work against its plan. Where it turned out differently from what was promised, check that whatever was built on it still holds.
- What's in progress. Glance at goals and plans to spot two efforts heading at the same ground before they collide.
Notice what isn't on the list: a status meeting, a queue of approvals or reading transcripts. The work should already explain itself.
What does a correction look like?
Say an agent working in Accounts · lib/accounts assumed overnight that deleting an account should also delete that user's invoices. The lead sees it at the top of the morning's list, marked high stakes. Invoices have to be kept for accounting, so the correction is one sentence: "Keep invoices; detach them from the account instead." The agent picks it up at its next turn and changes course. Only the work built on that assumption is redone, and it's caught before anyone else builds on it. That is rework kept small.
How does the lead see all this in one place?
In Campfyrr, each project's Activity page is that list: one feed of decisions, actions and status updates, which you can filter by type, person, area or "since your last visit". Open assumptions show with an "Answer it" link to a page where you confirm or correct them in one click, and a correction reaches the agent at its next turn. When two decisions clash, the newer call stands on its own and the feed shows which one it replaced.
Without a tool, the same habit works as practice: ask agents to write their assumptions, decisions and handoffs in one shared place, and read that place first each morning.
How does the daily look change the team over time?
Correcting the course every day keeps each fix small, and each correction becomes part of the record the next agent reads. The questions the team answered once stop coming back. The playbook on measuring at agent pace shows how to tell whether it's working.
Words used here
- Activity: Activity is Campfyrr's one page per project: a read-only feed of the team's decisions, actions and status updates, each written as what happened and why it matters.
- Assumption: An assumption is the best available answer to an unknown, stated and acted on, kept visible so anyone can correct it.
- Decision: A decision is a call made in the work, recorded with its reason at the moment it is made, so it travels to everyone who touches the same ground.
- Rework: Rework is work done again because it was built on something wrong: a mistaken assumption, a clashing decision, or a plan that changed without anyone hearing.
The principle behind this: Fix forward: We don't guard the gate. We correct the course.
Move as one at agent speed. Nobody waits. Add Campfyrr to Claude: it briefs every agent before it touches the code, keeps assumptions and handoffs where the team can see them, and never takes your code (what it keeps).