Assess the client-delivery job before handing it over

1. Start with the result you agreed to deliver

Name a specific assignment: a campaign, a research report, a client installation or another piece of agreed work. Avoid starting with an entire role such as “everything a project manager does.”

Write down:

• Agreed result: What does the client expect to receive?
• Source: Where is that agreement recorded, and which revision applies?
• Client contact: Who can answer questions, and who can accept the result? These may be different people.
• Returning responsibility: What do you keep doing personally to get this assignment from agreement to acceptance?

Include the small interventions you would otherwise forget: finding the latest instruction, connecting an answer to the right task or noticing that two contributors are working from different assumptions.

Project coordination includes requirements, schedules, people, problems and deliverables in the US Bureau of Labor Statistics’ description of the work. Your assessment should identify the part of that responsibility your business actually needs to assign.

If you cannot find a shared understanding of the result, start there. Someone else will need that understanding before they can keep the work moving for you.

2. Find the next move and what it depends on

Pick one point where progress is waiting on an answer, contribution or decision. Describe what becomes possible when it arrives.

Record:

• Waiting for: The exact information, contribution or decision needed.
• From: The person responsible for providing it.
• Affects: The work that cannot proceed, or would need an assumption.
• Next move: Who acts when the answer arrives, and what they do with it.
• Follow-through: Who checks the reply, keeps unresolved parts open and gets the usable answer to the person doing the work.
• If it remains blocked: The follow-up or escalation you have agreed, and who decides what happens next.

“A reminder was sent” records an action. The dependency is resolved when the information needed for the next move is available and usable. A partial answer may leave part of the work waiting.

Do not invent a response deadline or follow-up policy while completing the sheet. Where no policy exists, write “needs agreement.” A coordinator can pursue an answer within your rules; they cannot make the client provide it.

3. Separate follow-through from decisions you keep

List the actions another person could own and the choices you want brought back to you. Make the boundary specific enough to use on the next project question.

A design-services coordinator role described by Via Collective separates day-to-day coordination from project leadership’s final decisions. Use that distinction to discuss your own arrangement; the permissions still need to be agreed in your business.

If an AI Worker is one option, assess the context, access and actions it would require. Write unconfirmed access as an open question. A proposed connection to a tool is not proof that the job can be performed reliably there.

4. Keep a changed request attached to the agreement

Choose one real change that arose during the assignment. It might be an extra deliverable, conflicting feedback or a contributor becoming unavailable.

Write down:

• Request or change: What changed, who raised it and where it is recorded.
• Existing commitment affected: Which agreed result, instruction or delivery promise it touches.
• Impact still to establish: What the team needs to learn before making a new promise.
• Decision owner: Who may approve, decline or defer it.
• Decision and follow-through: What was authorized, who needs the answer and which record must be updated.

The Association for Project Management’s change-control guidance distinguishes recording and evaluating a change from authorizing it and updating the plan. You can apply that distinction without building a large approval system.

Until the decision is made, keep the request pending and identify the affected work. If unrelated work may continue, record that too. Preparing an option does not authorize a new price, promise or deliverable.

5. Decide what evidence will mean “finished”

Use the agreement and the people involved to define the finish for this assignment. A sent file, a completed task and an accepted delivery may represent different points in the job.

Record:

• Delivered result: The exact item and version supplied.
• Acceptance or handoff: Who receives it and what response or other agreed evidence is needed.
• Corrections: How feedback stays attached to that version and who follows it through.
• Remaining matters: What is still unresolved, who owns it and whether it prevents closing this assignment.
• Closing record: Where someone can see the evidence and understand the status without reconstructing the conversations.

If the client has not answered, preserve that fact. Do not turn silence into an approval. If your agreement leaves the finish unclear, bring that question to the appropriate people before treating the assignment as complete. This guide does not interpret your contract.

6. Choose the smallest useful change to test

Look at what your assessment reveals before selecting a solution.

Write one next step and who owns it. Include what you will observe: your time coordinating, time checking the new arrangement, corrections, missed commitments and unresolved questions. Use comparable assignments where possible. You do not yet have a savings claim or a reason to assume AI is the best option.

Copy your assessment

Keep this in a document your team can use. Write “unknown — owner to resolve” wherever you cannot yet answer.

CLIENT-DELIVERY ASSESSMENT
Project:
Agreed result / agreement source and revision:
Client information contact / person accepting delivery:
Responsibility that keeps returning to me:

CURRENT DEPENDENCY
Waiting for / from:
Affected work / next move and person responsible:
Who follows through on the reply:
Agreed follow-up or escalation if still blocked:

AUTHORITY
Information and current versions available to the role:
Permitted actions and systems:
Client-message reviewer and sender:
Decisions retained / decision owners:
Pause conditions / escalation contact:

CHANGES
Request or change / source:
Existing commitment affected / impact still to establish:
Authorized decision owner:
Decision, evidence and follow-through:

FINISH
Delivered item and version:
Acceptance or handoff required / evidence location:
Corrections and person following them through:
Unresolved matters / owners / effect on closure:

NEXT ARRANGEMENT TO TEST
Smallest useful change / person responsible:
What we need to verify before trying it:
Owner effort, checking effort and delivery problems to observe:
When and with whom we will review:

Questions that may come up

What if I cannot answer one of the questions?

Keep it open and name who needs to resolve it. Missing agreement, access or authority is useful information. A blank field should not quietly become someone else’s assumption.

Is this a project-management template?

It assesses the responsibility you want to assign. Keep your existing project plan and records. Use the assessment to explain who connects them, handles changes and follows the agreed result through.

Does completing this mean the job is ready for an AI Worker?

No. It gives you a concrete job to investigate. Actual access, permissions, information quality, exceptions, costs and performance still need assessment and testing. A clearer process or a human role may be the better answer.

What if the client never provides the missing answer?

Keep the dependency visible and follow the escalation you have agreed. The appropriate person must decide how to handle the block. Neither a coordinator nor an AI system can supply the client’s decision for them.