Whose problem is it? Handing a problem back to the person who owns it, with a date
The project manager's personal list says chase drywall delivery. The trade foreman has the supplier contact and purchasing responsibility, but the project manager keeps making the calls. Meanwhile, nobody has confirmed what the delayed delivery means for the shared loading arrangement or the next work area.
Separate a problem into the contributions it actually needs. The person who can obtain a delivery answer may differ from the person who assesses the project sequence or authorizes a change. Clarifying those roles can stop you adopting every task while preserving your real obligations. A trade's contract responsibility alone does not erase the project's coordination, technical or safety responsibilities.
Receive the contribution without abandoning the problem
- Describe the unresolved result. State the actual location, consequence and needed answer, with the current source information. Identify any immediate route before ordinary follow-up. Avoid a vague label such as delivery problem: obtaining a supplier commitment, assessing an affected work area and changing an agreed booking may involve different people and different receiving times.
- Identify who can contribute and decide. Check actual responsibilities, access to information, competence and authority. Ask what part the other person can own and what support is missing. Separate fact gathering from authorization. Retain your own required contribution and joint interfaces. The person who made a purchase may obtain a supplier answer without being authorized to move another trade's booking.
- Agree the handover and needed timing. Name the specific result, receiver and feasible return point, including any earlier exception. Provide the reference, introduction or other help you have agreed to supply. Confirm that the person has received and can undertake the task. A sentence handing it back is incomplete when the recipient lacks capacity or the answer would arrive after affected work needs it.
- Track your remaining interface and the return. Update your personal actions and the appropriate project record without deleting the unresolved issue. Check the promised contribution at a suitable point and act sooner if the consequence changes. If the task cannot proceed, obtain the appropriate next arrangement. Do not quietly resume every supplier call or treat assignment as proof that delivery and coordination are resolved.
Common mistakes
- Assigning a vague problem instead of a specific contribution.
- Assuming contract responsibility transfers every related duty.
- Setting a return date after the affected work needs the answer.
- Deleting an unresolved project issue when a task is handed over.
Checklist
A useful problem handover includes
- The unresolved result and actual consequence.
- Specific information, decision and interface roles.
- A capable recipient and the support agreed.
- The needed return, receiver and earlier exception route.
- Your remaining actions and the linked project status.
Check your understanding
The trade foreman accepts the supplier call. Can you remove the whole delivery issue from your project coordination record?
