Pick-up time: what it means
By Soumen Sarkar · October 2026
Pick-up time is how long a handoff waits between being left and someone picking it up to continue the work.
Pick-up time measures how quickly unfinished work starts moving again. A handoff is written when a session stops; pick-up time runs until a person or agent takes it and continues. It is one of the measures a team at agent pace watches, with waiting time and rework.
Two things keep it short. The handoff has to be good enough to act on without asking anyone: done, left, next step, open questions, what to watch out for. And it has to be seen: a handoff nobody notices waits however well it's written.
For example, an engineer's agent stops at 6pm halfway through an export feature and leaves a handoff. A teammate in another time zone sees it at 8am their time, picks it up, and has the next step running ten minutes later. Pick-up time: a few hours, mostly night. If the same handoff sat unseen for two days, the work around it would move on and the handoff would go stale.
A long pick-up time usually means handoffs aren't reaching the right people, or the work isn't anybody's to continue.
Campfyrr shows it in the "What Campfyrr caught for your team this week" card on Activity: handoffs picked up, and how soon after they were written.
The principle behind this: Let the work speak: Our work explains itself, so nobody ever has to come and ask us.
Related: Handoff · Waiting time · Activity
Questions that use it
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).