New Verified Business Manager products are now available – Explore the latest BM deals today.
When you buy verified BM, the order may include several deliverables: an agreed access arrangement, configuration assistance, documentation, training, or follow-up support.
Receiving one part does not necessarily mean the entire order is complete.
If something appears to be missing, start by comparing the delivery with the accepted scope. Identify what you received, what you checked, and what remains unresolved.
This guide explains how to organize that review and request a practical completion plan from the supplier.
Find the quotation, order confirmation, and any changes both sides approved.
Use the latest agreed version as your reference. An early sales message may describe a different package from the one you eventually accepted.
Collect the relevant records:
The itemized scope.
Delivery milestones.
Inspection arrangements.
Agreed changes.
Payment records.
Handover documents already received.
Messages explaining any delay or dependency.
Keep these together under the order reference. This gives both sides a clear basis for discussing the gap.
An item may be unfinished, or the supplier may have completed it without providing enough information for your team to inspect it.
Describe the distinction carefully.
| Delivery status | What it means | Next question |
|---|---|---|
| Received and checked | Your team inspected the agreed result | Can this item be recorded as complete? |
| Reported complete | The supplier says the work is finished | What evidence or demonstration is available? |
| Partially delivered | Some parts of the item are available | Which parts remain outstanding? |
| Not delivered | The agreed item has not been supplied | What is the completion plan? |
| Blocked | A prerequisite prevents progress | Who must provide the missing input? |
| Disputed scope | The parties disagree about inclusion | Which accepted record addresses the item? |
Avoid describing the entire order as complete or incomplete when individual items have different statuses.
Replace general messages such as “nothing works” with a short, factual description of each issue.
Include the agreed requirement, what your team observed, and what you need next.
For example:
The accepted scope includes a written operating guide. We received the configuration summary, but it does not include the agreed instructions for routine checks. Please provide those sections or identify where they appear in the delivered material.
For a functional issue, record the relevant environment, action attempted, observed result, and expected behavior.
Use screenshots or recordings only when they help explain the problem. Remove unrelated personal information and avoid including credentials.
Precise reporting helps the supplier investigate without first having to reconstruct the issue.
Ask the supplier to explain the reason for each outstanding item.
Possible explanations include missing buyer information, unfinished supplier work, an unsuccessful test, or an external decision still pending.
Keep these categories separate.
If your team has not supplied a required input, identify the person responsible and the expected availability. If the supplier has unfinished work, request its next action and proposed date.
For an external review, ask what preparation or submission work has been completed and what remains outside the supplier’s control.
Do not classify an external decision as a missing supplier deliverable unless the agreement and actual circumstances support that conclusion.
Ask for a written plan covering each unresolved item.
A useful plan includes:
| Field | Information to record |
|---|---|
| Outstanding item | The specific requirement still open |
| Current condition | What has been delivered or attempted |
| Next action | The work needed to move forward |
| Responsible person | Supplier, buyer, or another named participant |
| Target date | A proposed milestone with dependencies identified |
| Completion evidence | What your team will inspect |
| Next update | When progress will be reported |
A message such as “we will handle it soon” leaves the practical questions unanswered.
If a final completion date cannot yet be estimated, agree on the next investigation step and update time instead.
During inspection, your team may discover an additional requirement that was not part of the order.
Record it separately from missing agreed work.
For example, an omitted handover document and a newly requested training session are different issues. The first should be assessed against the accepted scope. The second may need its own quotation.
If the supplier labels an item as additional work, ask which part of the scope supports that interpretation. If your team misunderstood an ambiguous phrase, clarify the intended outcome and discuss a written resolution.
Avoid combining corrections, optional improvements, and new services into one unexplained additional charge.
Review how the agreement connects delivery milestones with acceptance and payment.
Do not assume that receiving part of the order settles every remaining condition. Equally, do not assume that an unresolved item automatically changes payment obligations.
Ask the supplier to reconcile the delivery status with the agreed milestones and document any adjustment both sides accept.
Also clarify when support begins. If the order is delivered in stages, ask whether coverage starts for each completed component or follows another agreed arrangement.
These dates matter because your team needs to know which assistance remains available while the outstanding work is being completed.
When the supplier reports that the missing work is complete, inspect it against the original requirement.
Focus the follow-up check on the affected item and any related functions that the change could influence.
Update the record with:
What was supplied or corrected.
The evidence reviewed.
The result of the check.
Any remaining limitation.
The person who reviewed it.
The final status of the item.
If an issue remains unresolved, explain why it is still open and request the next step through the agreed support or escalation channel.
Keep the completion record with the order documents.
Consider a hypothetical order containing three deliverables: a configuration review, a written asset inventory, and a handover session.
The supplier completes the review and supplies the inventory, but the session has not taken place.
The buyer records the first two items as inspected and the session as outstanding. Both sides agree on an appointment, required attendees, and the topics to demonstrate.
This preserves an accurate record of completed work while keeping the remaining commitment visible.
Hello, regarding order [reference], we reviewed the delivery against the accepted scope dated [date]. We have received and checked [completed items]. The following items remain unresolved: [specific gaps]. Please confirm the status of each item, any input required from our team, the responsible person, proposed next action, target date, and evidence we can review. Please also clarify how the outstanding work relates to the agreed acceptance, payment, and support milestones.
Check the scope. Documentation, configuration, testing, or training may be separate deliverables.
Compare the accepted quotation and approved changes. Identify the wording both sides relied on and request a written clarification.
First document the issue and ask what can be completed or corrected. Assess any replacement proposal against the actual agreement and its consequences.
It can leave an outcome pending. Record supplier-controlled work and the external decision separately so the status is clear.
Use the established escalation contact, keep your records together, and send a concise summary of the unresolved items and requested response. Further options depend on the agreement and the circumstances.
Before ordering, define the deliverables, inspection process, dependencies, and method for addressing outstanding work.
If you need assistance reviewing your situation, visit BMXMDN to discuss your business verification and setup requirements.
Request a proposal through BMXMDN covering itemized deliverables, completion evidence, delivery milestones, support dates, and a clear process for resolving missing items.
