Project Management Support in Afghanistan

Provide the objective, location, current project stage, deliverables and intended timeframe. Explain stakeholders, open decisions and which coordination responsibilities you need support with.

Yes. Share current progress, committed suppliers, existing plans and outstanding activities. Identify the coordination gap so the discussion focuses on the work that remains.

Describe the outputs the assignment must produce and who will review them. Include acceptance criteria and supporting records so completion can be assessed against the agreed scope.

A milestone represents a reviewable point in the project, with its required inputs and responsible parties identified. Explain dependencies and distinguish target dates from dates confirmed by the responsible parties.

Only when explicitly agreed with the appropriate qualified party. Coordination support does not automatically include specialist design, certification or approval authority.

Identify the person coordinating client decisions and the people authorised to approve scope, cost, dates and acceptance. Their roles should be visible to suppliers and the support team.

Yes. Explain the interfaces, deliverables and handovers between them. The scope should state which coordination activities are assigned and where decision authority remains.

Record the proposed change, its reason and its effect on deliverables, cost, responsibilities and dates. Obtain the required approval before treating it as part of the agreed work.

Agree status against deliverables and milestones, key issues, decisions needed and outstanding actions. Define recipients and frequency so the report supports decisions rather than repeating an unverified schedule.

List each location and explain the work and stakeholders at each. Travel, access, reporting and interfaces between sites need to be assessed in the specific proposal.

Identify activities retained by your organisation or another provider, specialist tasks outside the engagement and assumptions that the plan depends on. Review these boundaries before confirming the scope.

Mark unknowns and name the people who can resolve them. An initial discussion can organise the questions, but dates, costs and delivery commitments need a sufficiently clear agreed basis.

Yes. Include product or material needs, supplier status and required delivery milestones. Agree purchasing approvals and transport interfaces alongside the project coordination responsibilities.

Describe the dependency or uncertainty, its possible effect and the person responsible for the next action. The appropriate technical or commercial decision owner should review issues within their authority.

Raise the cause, affected dependencies and decisions required. The impact on scope, costs or other dates should be assessed and any revised commitments confirmed by the authorised parties.

Project stage, duration, locations, deliverables, supplier interfaces and reporting needs shape the scope. Distinguish coordination support from specialist services or physical execution.

Describe the specific workstream, milestone or interface you need help with. A bounded assignment can be discussed without assuming responsibility for the whole project.

Review the agreed deliverables, completion evidence, unresolved items and acceptance responsibilities. Keep a clear record of what is accepted and what remains outstanding.

Explain the sector, scope, operating conditions and evidence your evaluation requires. Project descriptions and third-party reference information depend on availability and disclosure permissions.

Select Project management on the quotation form and share the project stage, objective and support needed. Use the project scope guide to organise deliverables and responsibilities first.