Project Blocker Log Template: Issue, Owner, and Next Follow-Up

A road barrier leads to an owner, a follow-up date and a resolution check mark.

A project blocker log gives every obstacle that stops current work a person responsible for the next action, a follow-up date, and a clear test for resolution. A short log your team checks while it works is more useful than a detailed list nobody owns.

Record a blocker when a specific step cannot proceed. If the client has approved two pages and asked for changes to a third, name which page is blocked and carry on with the other two.

Copy the blocker log

Blocked workWhat is stopping itResolution ownerNext action and follow-upResolved when
Publish pricing pageFinal offer terms await approvalNinaSend the two open questions to the approver on Tue. Check by Wed noonApproved terms are linked and the page can be checked
Confirm event agendaSpeaker confirmation is missingDevAsk for a firm reply by Thu. Confirm the alternate if no reply arrivesOne speaker has accepted and the agenda is updated
[Task or delivery][Observable obstacle][One person][Action and date][Evidence the work can move]

These examples are fictional. Add the date raised and the impact on a commitment when those details help the team decide what to handle first. Keep an old blocker somewhere you can find it after resolution if it explains a deadline change or might recur.

How to run the log

  1. Describe the blocked step. “Pricing page cannot be published until the offer terms are approved” identifies both the work and the missing input.
  2. Give one person the next action. Nina can own getting the answer even if a manager decides the terms. Write both names when the distinction matters.
  3. Set the follow-up. Give the question a date. If the answer will miss the delivery cutoff, decide whether to raise it sooner or adjust the scope.
  4. Record the result on the affected work. Save the approved answer or a reference to it, then confirm the original work can continue.

A project risk register gives potential trouble a trigger and response. When the trigger occurs and work actually stops, record the active issue and the next action here. That separation helps the team keep a current queue small.

Keep the blocker on the task that needs an answer

On a shared SelfManager.ai Team table, keep “Publish pricing page” as the parent task. Add an assigned subtask for Nina called “Confirm offer terms with approver.” Set its follow-up deadline separately from the publishing deadline on the parent. The teammate responsible for publication can keep working on what is ready while the approval question has its own owner.

Enable Comments on tasks in the table settings to keep the questions and replies on the parent task. Use the approved offer reference in a note or comment when it arrives. Subtasks can carry the follow-up and its deadline, with the conversation visible under the parent.

The date of the table represents when you plan to work there. The follow-up deadline represents when you need the next action. Give those dates separately if the follow-up belongs later. If you're dealing with multiple blockers, use a dedicated table for the next review and record the original table link and affected task name.

Close or raise issues deliberately

At each check-in, look first for items that will affect a near deadline. If the approver hasn't replied by noon Wednesday, Nina can report exactly what is missing and ask the team to choose between delaying publication and changing the scope. Close the issue after someone confirms that the team can do the blocked step.

Team AI Review can help summarize the work recorded in shared tables. Ask it to surface outstanding questions and related assignments, then confirm those details with the owners. The person doing the work should be able to tell you whether an obstacle is still real.

Common questions

Is every dependency a blocker?

A dependency is something the work relies on. Treat it as an active blocker when a specific step needs it now and cannot proceed.

How does this differ from a handover?

A project handover gives someone enough context to take over several pieces of work. Use a blocker log to run the short cycle of an individual obstacle, from the first follow-up through resolution.

Take one issue your team is waiting on and give the next action an owner and a deadline in SelfManager.ai Team. Keep the resolution where the person doing the work will see it.

Date-based AI Task Manager

Plan smarter, execute faster, achieve more

AI Summaries & Insights
Date-Centric Planning
Unlimited Collaborators
Real-Time Sync

Create tasks in seconds, generate AI-powered plans, and review progress with intelligent summaries. Perfect for individuals and teams who want to stay organized without complexity.

7 days free trial
$8/mo Individual • $30/mo Team