The arithmetic of a project manager's day
Take a PM running two or three active jobs. Call volume of 30 to 50 a day is ordinary. Say each call carries two things that matter — something you owe someone, or something someone owes you.
That's 60 to 100 open obligations generated per day. Some resolve immediately. Many don't. And the mechanism for capturing them is, for most PMs, memory plus whatever got scrawled on the back of a submittal.
Nobody's memory holds that. The question isn't whether things fall through — it's which things, and what they cost when they do.
Where commitments actually leak
Between the call ending and the next one starting
This is the biggest one. The call ends, you have four things to do, and the phone rings again before you've written any of them down. Two of the four survive to lunch.
The ones that belong to someone else
Your own to-dos have a fighting chance because they nag at you. The sub who said he'd send the updated manpower plan by Friday has no such mechanism. Friday passes. Nobody notices until Tuesday, when it's now a schedule problem.
Commitments with no deadline attached
"I'll get you pricing on that" with no date is not a commitment, it's a sentiment. It never becomes overdue because it was never due.
Things you heard but didn't register as commitments
The owner mentions in passing that their tenant's lease starts November 15. That's not a task, so it doesn't go on a list — but it's the fact that makes the TCO date immovable, and you'll wish you'd captured it when the schedule slips.
The Friday afternoon cliff
Anything agreed after about 2pm Friday has a materially worse survival rate than the same thing agreed on a Tuesday morning. The weekend clears working memory.
What it costs
The dropped callback itself is usually cheap. The second-order effects are not.
| What gets dropped | What it turns into |
|---|---|
| A callback to a supplier | A material lead time you find out about too late to absorb |
| A sub's promise you didn't track | Manpower doesn't show; two days of float gone |
| A price agreed but not confirmed | A dispute at closeout you'll probably split |
| An owner question left unanswered | Erosion of confidence that shows up in the next negotiation |
| A schedule constraint you heard once | A delay claim you can't defend because nobody documented the constraint |
And there's a cost that doesn't show up on any job cost report: the nights and weekends spent reconstructing what you were supposed to be doing. That's the one PMs actually feel.
Three systems that close the gap
1. Capture at the moment, not at the end of the day
The single highest-leverage change. Commitments captured within a minute of the call survive at a rate that isn't comparable to anything captured later.
"I'll write it up tonight" fails for a structural reason, not a character one: by tonight you've had eleven more calls, and the details have blurred together. You'll capture the gist and lose the specifics — and the specifics are the part that mattered.
What works is whatever you can do in the thirty seconds after hanging up, before the next call. For most people that's talking, not typing. A voice note in the truck beats a note-taking app you have to open, focus, and thumb-type into.
2. One list, not six
Most PMs have commitments spread across a notebook, their email flags, three text threads, a whiteboard in the trailer, and the project management software the office makes them use. Six partial lists is functionally zero lists, because no single one can be trusted and checking all six is nobody's morning routine.
One list you actually look at beats a better-designed system you don't.
3. Track what you're waiting on, separately
Most task systems only track what you owe. Half the risk on a construction job is what other people owe you — the sub's manpower plan, the owner's signed change order, the supplier's confirmation.
Those need their own list with dates attached, reviewed on a fixed rhythm. Monday morning, one pass: what did I ask for that hasn't arrived? That single habit catches most of what would otherwise become a schedule problem three weeks later.
Why "just be more organized" doesn't work
Every PM has already tried discipline. They've tried the notebook, the app, the inbox-zero routine. It works for a week, then a bad Tuesday arrives — a flood, a failed inspection, a no-show crew — and the system is the first thing dropped, exactly when it's needed most.
Systems that depend on you being organized on your worst day will fail on your worst day. The ones that hold are the ones that don't require you to do anything extra at the moment you have the least capacity to do it.
That's the real test for any tool or habit in this category: does it still work on the day everything goes wrong? If it needs you to remember to use it, it won't.
Common questions
Why do project managers forget follow-ups?
Volume and structure, not carelessness. A PM on active jobs takes 30 to 50 calls a day, each generating a couple of obligations, with no gap between calls to record anything. That's 60 to 100 open items a day against a capture system that is usually just memory.
What's the best way to track commitments from phone calls?
Capture within a minute of the call ending, keep a single list rather than several partial ones, and track what other people owe you separately from what you owe them, with dates attached and a fixed weekly review.
How much does a dropped follow-up cost a construction project?
The dropped item itself is usually minor. The second-order cost is what hurts: material lead times discovered too late, lost schedule float when a sub doesn't show, disputes at closeout over prices that were never confirmed, and time spent on nights and weekends reconstructing what was owed.
Should I track what other people owe me, or just my own tasks?
Both, and separately. Most task systems only capture your own to-dos, but roughly half the schedule risk on a construction job sits in what subs, suppliers and owners owe you. Those items need their own list with due dates and a regular review.
Why do note-taking systems fail for project managers?
Because they require effort at exactly the moment there's no capacity for it — right after a call, before the next one. Any system that depends on discipline gets abandoned on a bad day, which is the day it matters most.
Stop losing the details between calls.
Iron Notes records your work calls and voice notes and sends you a plain recap — what was said, who owes what, and what's next. Free for 30 days.
See how it works