The Contract Says 300 Beds — So Why Does the Site Report Say 286?

A hospital project orders 300 beds.

The purchase order clearly shows 300 units.

The supplier completes production.

Several shipments arrive at the hospital.

The installation team begins work.

Then the project manager asks a simple question:

How many hospital beds have actually been completed?

One spreadsheet says 300.

The shipping documents show another operational number.

The receiving team has recorded 296 units received.

The installation team reports 289 beds installed.

Several beds are waiting for accessories.

Some are installed but have open issues.

A few have been moved to different rooms.

The final acceptance team has signed off only part of the project.

Which number is correct?

Potentially, several of them are correct because they describe different project statuses.

This is why large hospital bed projects need quantity reconciliation rather than one generic column called “quantity.”

A practical project sequence is:

Contract Quantity → Production Quantity → Shipped Quantity → Received Quantity → Installed Quantity → Pending Quantity → Accepted Quantity → Final Reconciliation.

One Project Can Have Several Correct Quantities at the Same Time

The Purchase Order Quantity Answers One Question

How many beds did the buyer order?

It does not automatically tell you how many are physically at the hospital today

The Shipped Quantity Answers Another Question

How many beds have left the supplier under the relevant shipment record?

It does not automatically equal the installed quantity

The Installed Quantity Answers Yet Another Question

How many beds have reached the defined installed status?

It does not automatically equal final acceptance

The First Rule: Stop Using One Number to Describe the Whole Project

“We Have Completed 280 Beds” Is Too Ambiguous

What does completed mean?

Produced?

Shipped?

Received?

Assembled?

Installed?

Functionally checked?

Accepted?

Every Status Needs a Clear Definition

Otherwise two teams can report different numbers while both believe they are correct.

Define status before counting

Start With the Contract Quantity

The Contract Quantity Is the Commercial Baseline

This is the quantity the supplier is expected to provide according to the applicable purchase agreement.

It should be broken down by model where multiple bed configurations are included

Do Not Record Only the Grand Total

A 300-bed project may contain several different models.

The total can balance while individual models remain incorrect

For Example, a Project Could Include

• Electric multi-function hospital beds
• Manual hospital beds
• ICU beds
• Pediatric beds
• Other agreed project configurations

Reconcile each required configuration separately before reconciling the total

A Correct Grand Total Can Hide a Model-Level Shortage

For example, one model may be over-supplied while another is short.

Total quantity alone cannot detect this

Contract Quantity and Current Requirement Are Not Always the Same Forever

Projects Can Change After the Initial Order

Approved additions or reductions may occur.

The current authorized quantity should therefore be distinguishable from the original contract quantity where applicable

Do Not Silently Edit the Original Number

Keep the original commercial baseline and the approved revision history.

This preserves project traceability

Build an Approved Quantity Baseline

A Practical Quantity Record Can Separate

• Original ordered quantity
• Approved additions
• Approved reductions
• Current authorized quantity

The exact structure depends on the contract and project

This Prevents Change Orders From Becoming Invisible

Project teams can see why the current quantity differs from the original order.

Do not overwrite project history

Next, Record the Production Quantity

Production Status Is Different From Shipment Status

A bed may be manufactured but still remain at the factory.

Produced does not mean shipped

A Bed May Also Be Partially Complete

Depending on the project definition, it may still require accessories, packaging, labeling or other agreed work.

Define what “production complete” means

Do Not Count Partially Finished Beds as Fully Complete Without a Defined Rule

Project Reporting Should Reflect Actual Status

If a bed frame is finished but required components are not complete, the reporting method should make that visible.

Avoid optimistic counting

Use Consistent Completion Criteria

The factory and project team should understand the same definition.

Consistency makes later reconciliation easier

Then Record the Shipped Quantity

Shipment Quantity Should Be Linked to Actual Shipping Records

Do not rely only on an informal message saying that the goods have left the factory.

Use the relevant shipment documentation

For Multi-Shipment Projects, Keep Each Shipment Separate

Shipment 1.

Shipment 2.

Shipment 3.

Then calculate the cumulative shipped quantity

Cumulative Quantity Is Important

A Project Manager Needs to Know Both

How many beds are in this shipment?

And how many have been shipped in total?

Do Not Replace Shipment-Level Data With Only a Running Total

You may need to investigate a discrepancy later.

Preserve the underlying shipment records

Shipped Quantity Should Be Reconciled by Model

A Container Can Carry More Than One Hospital Bed Model

The total number of packages or beds does not automatically prove that the model mix is correct.

Check configuration-level quantity

This Becomes More Important When Several Departments Require Different Beds

An ICU bed cannot simply replace a different ordered configuration in the project record without an approved change.

Quantity and configuration belong together

What About Beds Packed in Multiple Packages?

Package Quantity and Bed Quantity Are Not Always the Same

One complete bed may be divided into several packages.

Do not count cartons as beds

Accessories May Also Be Packed Separately

Mattresses, IV poles or other agreed items may travel separately from the main bed package.

Define the unit being counted

A Project Can Have the Correct Number of Packages but Still Have an Incomplete Bed Quantity

For Example, a Required Component May Be Missing

The main bed frame may be present while another required part has not arrived.

Completeness needs its own check

Do Not Confuse Physical Package Count With Complete Supply Scope

These are related but different controls.

Count what the project actually requires

Next Comes Received Quantity

Received Quantity Means the Destination Has Physically Recorded Receipt

This is different from the supplier reporting shipment.

The two records should eventually reconcile

But They May Not Match Immediately

Some goods may still be in transit.

Some shipments may arrive on different dates

Receiving Teams Need a Clear Counting Method

Do Not Record Only “Container Received”

A container arrival is a logistics event.

It does not by itself confirm every required bed and accessory

Reconcile the Actual Received Quantity

Use the appropriate packing and receiving records.

Document discrepancies promptly

What If a Package Is Damaged?

Received and Usable Are Different Statuses

A package can physically arrive while the product inside requires inspection or corrective action.

Do not erase it from the received quantity

Instead, Add an Appropriate Condition Status

Received.

Received with visible issue.

Pending inspection.

Other project-defined status.

Keep quantity and condition separate

This Prevents a Common Accounting Problem

If Damaged Goods Are Removed From the Received Count

The records may falsely suggest that the shipment never arrived.

Record physical receipt and condition independently

One Asset Can Have More Than One Attribute

Location status.

Condition status.

Installation status.

Do not force every fact into one column

Then Comes Staging Quantity

Some Beds May Be Received but Not Yet Released to the Ward

They may remain in a temporary staging area.

This is normal in many large projects

Staging Should Be Visible in the Project Record

Otherwise received beds can appear to have disappeared between unloading and installation.

Use an intermediate status where useful

Do Not Automatically Treat Staging as Installation Delay

The Project May Intentionally Sequence Deployment

Different wards may become ready at different times.

Project context matters

But Long-Unresolved Staging Should Be Visible

The project team should know which beds remain there and why.

Status visibility supports project control

Installed Quantity Needs a Definition Too

When Is a Hospital Bed Considered Installed?

When it enters the room?

When packaging is removed?

When assembly is complete?

When accessories are attached?

When electrical functions are checked?

When the room is ready for use?

The Project Should Define the Installation Gate

Without a definition, different installers may count differently.

One status needs one rule

Room Placement Alone May Not Equal Installation Completion

A Bed Can Be Physically Inside the Ward but Still Be Incomplete

Accessories may be missing.

Assembly may be unfinished.

A function may still require verification.

Location is not the same as completion

Use Separate Status Fields Where Necessary

Location.

Assembly.

Functional check.

Then define which combination qualifies as installed

Installed Quantity and Accepted Quantity Are Not the Same

This Is One of the Most Important Distinctions in Hospital Projects

A bed can be installed before formal acceptance is complete.

Installation is an execution status

Acceptance Is a Project or Commercial Status

The exact acceptance process depends on the contract, tender requirements and hospital procedures.

Do not automatically merge the two

Why Might an Installed Bed Remain Unaccepted?

There Can Be an Open Issue

A missing accessory.

A documentation issue.

A cosmetic issue requiring agreed correction.

A functional issue.

An identification issue.

The exact reason should be recorded

Do Not Simply Reduce the Installed Quantity

The bed is still physically installed.

Instead, show its acceptance status separately

Create a Pending-Issue Quantity

This Helps Explain the Gap Between Installed and Accepted

Suppose 290 beds are installed.

Eight remain pending agreed corrective actions.

Then the acceptance count may be lower than the installed count.

The gap becomes explainable

Without a Pending Status, the Difference Looks Like a Missing Quantity

That creates unnecessary confusion.

Every gap should have a reason

Do Not Use One Generic “Pending” Category for Everything

Pending Can Mean Many Things

Waiting for delivery.

Waiting for room readiness.

Waiting for installation.

Waiting for accessory completion.

Waiting for corrective action.

Waiting for acceptance.

Different reasons require different next actions

Use Reason Codes or Clear Descriptions

The system can remain simple.

Clarity matters more than complexity

What About Beds Moved After Installation?

Hospital Projects Can Change Room Allocation

A bed originally installed in one ward may later be reassigned.

This should not change the total installed quantity if the bed remains installed

But the Location Record Should Change

Otherwise the quantity may be correct while the room-level record is wrong.

Quantity accuracy and location accuracy are separate controls

Do Not Count a Reallocated Bed Twice

This Is a Common Spreadsheet Risk

The bed appears once under the original ward and again under the new ward.

The total suddenly increases even though no new bed arrived

Use Persistent Bed or Package References Where Appropriate

This makes movement easier to track.

One physical bed should remain one project unit

What About Replacement Beds?

A Replacement Can Easily Create Double Counting

An original bed has an issue.

A replacement bed arrives.

The original bed remains temporarily on site.

Now two physical beds may exist for one contractual requirement

Do Not Automatically Increase the Project Completion Quantity

The replacement may substitute for an existing project unit rather than increase the contractual quantity.

Track replacement relationships clearly

Record the Original and Replacement Separately

The Original Bed May Have a Status Such As Removed or Pending Return

The replacement can then take over the required project position.

This preserves physical traceability without inflating commercial quantity

Replacement Logic Should Follow the Project Agreement

Do not create an informal counting rule during the project.

Use consistent records

What About Spare Beds Included in the Project?

Reserve or Spare Units Should Be Identified Separately If the Contract Requires Them

They may not be assigned to a normal patient room immediately.

That does not mean they are missing

Do Not Force Spare Units Into Ward Installation Counts

Their project role is different.

Keep their status visible

A Spare Unit Can Be Delivered and Accepted Without Being Installed in a Patient Room

This Is Why One Universal Completion Definition Can Fail

Different supply categories may require different acceptance paths.

Define them before final reconciliation

Separate Operational Deployment From Contract Fulfillment

The two can overlap without being identical.

Project design determines the correct record

What About Mattresses and Accessories?

Do Not Let the Bed Count Hide Accessory Shortages

Three hundred bed frames do not automatically mean three hundred complete bed sets.

Reconcile required accessories separately

For Example, the Project May Need to Track

• Mattresses
• IV poles
• Other ordered accessories
• Model-specific components

Use the actual project scope

Create a Complete-Set Status Where Useful

A Bed Can Be Physically Installed but Still Await an Agreed Accessory

This explains why bed-frame installation and project acceptance can differ.

Supply completeness matters

Do Not Solve the Problem by Reducing the Installed Bed Count

Record the missing accessory as a separate open item.

Preserve accurate status information

Why Do Spreadsheet Totals Often Become Wrong?

Manual Copying Creates Duplicate Records

A bed may be copied from the staging sheet to the installation sheet without being removed or status-updated in the original record.

Now the same physical unit appears twice

Different Teams May Maintain Independent Files

Factory.

Logistics team.

Receiving team.

Installation team.

Project management team.

Each file can become a different version of reality

The Solution Is Not Necessarily More Spreadsheets

The Project Needs a Controlled Master Record

Other operational sheets can feed into it.

But one source should define the current consolidated status

Assign Responsibility for Updating It

Otherwise everyone assumes someone else is maintaining the data.

Ownership matters

Build a Quantity Reconciliation Equation

The Exact Formula Depends on the Project

But the principle is straightforward.

Every authorized project unit should eventually have an explainable status

For Example, Current Authorized Quantity Should Be Accounted for Across Relevant Statuses

Not yet produced.

Produced but not shipped.

In transit.

Received and staging.

Installed but pending acceptance.

Accepted.

Other defined project status.

No quantity should disappear between stages

Avoid Double Counting Across Statuses

This Depends on How the Dashboard Is Designed

If statuses are mutually exclusive, each bed should occupy one current status.

If milestone columns are cumulative, the same bed can legitimately appear as received and installed

Do Not Mix These Two Reporting Models

A current-status dashboard and a milestone dashboard use different counting logic.

Choose one logic for each report

Current Status and Milestone Status Are Different

Current Status Asks

Where is this unit in the workflow right now?

One current status is usually easier to reconcile

Milestone Status Asks

Has this unit ever reached a particular stage?

Several milestone fields may all be true

For Example, an Accepted Bed Has Also Been Received and Installed

That Is Normal in a Milestone Model

Do not add received, installed and accepted quantities together.

They are cumulative stages, not separate physical beds

This Simple Distinction Prevents Major Reporting Errors

Project dashboards should explain which model they use.

Make the counting logic visible

Use a Model-Level Reconciliation Sheet

Each Model Can Have Its Own Quantity Line

This allows the team to compare:

• Authorized quantity
• Produced quantity
• Shipped quantity
• Received quantity
• Installed quantity
• Accepted quantity
• Open quantity

Keep the definitions consistent

Add Project-Specific Columns Only When They Help Decisions

Do not create unnecessary complexity.

A useful dashboard should answer operational questions quickly

Then Reconcile by Department or Ward Where Required

The Project Total Can Be Correct While Department Allocation Is Wrong

This is why a second level of reconciliation may be necessary.

Project total and destination total should agree

Do Not Create a New Commercial Quantity When a Bed Moves Between Wards

Only its allocation changes.

Separate quantity from location

How Often Should Quantity Reconciliation Be Updated?

There Is No Universal Interval for Every Project

The appropriate frequency depends on shipment volume, installation activity and project complexity.

Fast-moving phases may need more frequent updates

The Important Point Is That Reconciliation Happens Before Errors Accumulate

Waiting until final acceptance can make investigation much harder.

Reconcile throughout execution

Useful Reconciliation Gates Can Include

Before Shipment

Compare authorized quantity with production and planned shipment quantity.

Detect factory-side gaps

After Receiving

Compare shipped quantity with physically received quantity.

Detect logistics discrepancies

After Installation

Compare received quantity with installed, staging and pending quantities.

Detect site-side gaps

Before Final Acceptance

Compare the full authorized scope with accepted and unresolved quantities.

Close the project systematically

What If the Shipped Quantity Is Lower Than the Ordered Quantity?

First Determine Whether the Project Is Still in Partial Shipment

The difference may be planned.

Do not label every difference a shortage

Check the Remaining Production or Shipment Plan

Identify the outstanding quantity by model.

Make the gap explainable

What If the Received Quantity Is Lower Than the Shipped Quantity?

Check Shipment Status and Receiving Records

Some goods may still be in transit or pending unloading and verification.

Use actual evidence

If a True Discrepancy Exists

Record it promptly and follow the agreed project procedure.

Do not hide the gap by adjusting unrelated numbers

What If Installed Quantity Is Lower Than Received Quantity?

This Is Not Automatically a Problem

Some beds may still be in staging.

Some rooms may not yet be ready.

Some units may require assembly or agreed corrective work.

Explain the status of the difference

The Key Question Is Where the Remaining Beds Are

Every unit should have an identifiable project status.

Unexplained quantity is the real warning sign

What If Accepted Quantity Is Lower Than Installed Quantity?

Check the Open-Issue Register

Some installed beds may still require correction, documentation or formal acceptance activity.

Link the quantity gap to actual open items

Do Not Mark Everything as “Not Accepted” Without a Reason

The project team needs actionable information.

Reason codes improve follow-up

What If Accepted Quantity Is Higher Than Installed Quantity?

First Check the Definitions

Some project items may be accepted without normal ward installation, such as agreed spare units.

The project scope determines whether this is legitimate

If the Definitions Do Not Explain It

The records may contain duplication or incorrect status updates.

Investigate before closing the report

Do Not Force the Numbers to Match by Editing Them Manually

Reconciliation Is About Explaining Differences

It is not about making every column display the same total.

Different stages naturally have different numbers during execution

The Objective Is Logical Continuity

Every difference should have an understandable reason.

Trace the gap rather than hiding it

Use Exception Records for Unexplained Differences

Examples Can Include

• Missing unit
• Extra unit
• Wrong model
• Incomplete accessory set
• Damaged unit
• Duplicate record
• Unidentified package
• Incorrect ward allocation
• Replacement pending reconciliation

Use project-specific terminology

Assign an Owner to Each Exception

A problem without an owner can remain open indefinitely.

Responsibility supports closure

Every Exception Should Have a Next Action

For Example

Verify receiving record.

Locate the package.

Correct the model entry.

Supply the missing accessory.

Replace the affected unit.

Correct the duplicate record.

Turn discrepancies into actionable tasks

Then Record Closure

Do not simply delete the original issue.

Preserve the reconciliation history

Use Dates Carefully

A Quantity Without a Reporting Date Can Be Misleading

The project changes over time.

State when the number was valid

For Example, Installed Quantity on Monday May Differ From Friday

Both reports can be correct.

Time is part of project status

A Dashboard Should Show Its Data Cut-Off

This Prevents Teams From Comparing Numbers From Different Dates

A shipping report from yesterday and installation report from last week should not be treated as simultaneous snapshots.

Synchronize reporting periods where practical

Use the Latest Verified Update

Do not assume the most recently emailed spreadsheet contains the most current underlying data.

Control versions

Do Not Let Percentage Complete Replace Actual Quantity

Project Teams Often Like Progress Indicators

But a progress indicator should be supported by actual counts.

Keep the source quantity visible

Different Teams May Define “Complete” Differently

Production completion.

Delivery completion.

Installation completion.

Acceptance completion.

Specify which milestone is being reported

A Project Can Be Fully Shipped but Not Fully Installed

That Is Not a Contradiction

It simply means the project has reached one milestone but not another.

Use precise language

Likewise, Installation Can Be Complete While Final Acceptance Remains Open

The project may still have unresolved acceptance items.

Keep milestone status separate

Who Should Own the Master Quantity Record?

The Exact Role Depends on the Project Organization

It may be maintained by project management, logistics coordination or another designated function.

The important point is explicit ownership

Multiple Teams Can Supply Data

Factory team.

Freight team.

Receiving team.

Installation team.

Acceptance team.

But consolidated control needs a defined owner

Do Not Allow Every Team to Change the Master Data Without Control

Uncontrolled Editing Can Destroy the Reconciliation Trail

Use an appropriate update process.

Simple controls can be enough

Keep Previous Versions Where the Project Requires Them

This helps investigate when and why a discrepancy appeared.

History supports accountability

What Should a Hospital Bed Quantity Dashboard Show?

A Practical Dashboard Can Include

• Project reference
• Bed model
• Current authorized quantity
• Produced quantity
• Shipped quantity
• Received quantity
• Installed quantity
• Accepted quantity
• Outstanding quantity
• Open-issue quantity
• Last update date
• Responsible team or owner where useful

Adapt the dashboard to the actual project

Avoid Adding Fields That Nobody Maintains

A complicated dashboard with outdated information is less useful than a simple accurate one.

Design for real project use

What Is an Outstanding Quantity?

The Definition Must Be Explicit

Outstanding against production?

Outstanding against shipment?

Outstanding against installation?

Outstanding against acceptance?

Each produces a different number

Do Not Use “Outstanding” Without Naming the Milestone

For example, “outstanding for shipment” is much clearer than simply “outstanding.”

Precise labels improve decisions

How Should a Project Handle Quantity Changes?

Use Approved Changes

If the project quantity officially changes, update the authorized baseline through the appropriate project process.

Do not let informal requests rewrite the master quantity

Keep the Original Quantity Visible

This helps explain why the current authorized total changed.

Preserve the history

Quantity Changes Should Flow Through Downstream Plans

A Change Can Affect

Production.

Shipment.

Accessories.

Installation.

Ward allocation.

Acceptance.

Update all affected records

Do Not Change One Spreadsheet and Forget the Others

That is how project totals diverge.

Synchronize controlled records

What About Partial Acceptance?

Some Projects May Accept Equipment in Stages

The exact process depends on contractual and project requirements.

Do not assume one universal acceptance method

If Partial Acceptance Is Used

Record the accepted quantity and the remaining quantity clearly.

Link each accepted batch to the appropriate project record

Do Not Mark the Entire Project Accepted Because One Batch Was Signed Off

Batch-Level and Project-Level Status Are Different

A project may have several completed sections while others remain open.

Keep status granularity appropriate

Likewise, One Open Batch Does Not Necessarily Mean Nothing Has Been Accepted

Report actual status rather than an all-or-nothing summary.

Precision improves communication

Why Quantity Reconciliation Matters Before Final Acceptance

Final Acceptance Is Too Late to Discover Basic Quantity Confusion

By then packaging may be gone.

Teams may have left the site.

Beds may have moved between wards.

Early reconciliation preserves evidence

The Final Stage Should Confirm a Controlled Record

Not reconstruct the entire project from memory.

Build the record throughout execution

Why Quantity Reconciliation Matters to the Supplier

The Supplier Needs to Demonstrate What Was Produced and Supplied

Clear records reduce disputes about missing quantities.

Shipment evidence alone may not explain site-side status

The Supplier Should Also Understand Open Exceptions

This helps distinguish true supply shortages from installation or allocation issues.

Use evidence rather than assumptions

Why Quantity Reconciliation Matters to the Buyer

The Buyer Needs to Know Whether the Contracted Scope Has Actually Been Fulfilled

Not merely whether containers arrived.

Commercial completion depends on the agreed project requirements

The Buyer Also Needs Visibility Into Remaining Work

How many beds remain?

Where are they?

Why are they pending?

Who is responsible?

A good reconciliation system answers these questions

Why Quantity Reconciliation Matters to the Installation Team

Installers Need a Clear Scope

They should know how many beds of each model are expected in each relevant area.

This reduces accidental duplication or omission

Installation Progress Should Feed Back Into the Master Record

Otherwise project management sees outdated information.

Field activity and project data should stay connected

Why Quantity Reconciliation Matters to Hospital Management

The Hospital Needs a Clear Picture of What Is Actually Ready

Ordered quantity alone does not answer that question.

Operational readiness depends on actual project status

A Reliable Status Report Should Distinguish What Is Present From What Is Ready

This supports more accurate internal planning.

Use project-defined readiness criteria

15 Questions to Ask During Hospital Bed Quantity Reconciliation

• 1. What is the original ordered quantity?
• 2. Have any approved quantity changes occurred?
• 3. What is the current authorized quantity?
• 4. How many beds are production-complete?
• 5. How many beds have been shipped?
• 6. How many beds have been physically received?
• 7. How many remain in staging?
• 8. How many meet the project's installed definition?
• 9. How many have been accepted?
• 10. How many have open issues?
• 11. Are all model-level quantities correct?
• 12. Are mattresses and accessories complete?
• 13. Are any replacement units being double-counted?
• 14. Are any beds recorded in more than one location?
• 15. Can every remaining quantity gap be explained?

The exact checklist should follow the project structure

Common Mistake 1: Using the Purchase Order Quantity as the Current Site Quantity

The Purchase Order Is the Commercial Baseline

It does not describe every later project stage.

Track operational quantities separately

Common Mistake 2: Counting Packages as Beds

One Bed May Use Multiple Packages

Accessories may also be packed separately.

Define the counting unit

Common Mistake 3: Treating Received as Installed

Goods Can Remain in Staging

Physical arrival does not equal installation.

Keep milestones separate

Common Mistake 4: Treating Installed as Accepted

Open Issues May Still Exist

Formal acceptance can follow a different process.

Do not collapse the statuses

Common Mistake 5: Deleting Damaged Beds From the Received Quantity

They Were Still Physically Received

Condition should be recorded separately.

Preserve accurate receipt records

Common Mistake 6: Double-Counting Replacement Beds

A Replacement Does Not Automatically Increase the Contract Scope

Track its relationship to the original unit.

Separate physical asset count from contractual requirement

Common Mistake 7: Counting Reallocated Beds Twice

Moving From Ward A to Ward B Does Not Create Another Bed

Update location rather than duplicating the record.

One physical unit remains one unit

Common Mistake 8: Tracking Only the Total, Not the Model Mix

The Total Can Balance While Configurations Are Wrong

Reconcile each model.

Configuration matters

Common Mistake 9: Ignoring Accessories

A Bed Frame Is Not Always the Complete Ordered Set

Track the agreed supply scope.

Completeness matters

Common Mistake 10: Using Several Uncontrolled Master Spreadsheets

Multiple Sources of Truth Create Conflicting Totals

Establish a controlled consolidated record.

Assign ownership

Common Mistake 11: Hiding Quantity Gaps by Editing Totals

A Difference Should Be Investigated

Not erased.

Reconciliation explains discrepancies

Common Mistake 12: Waiting Until Final Acceptance

Quantity Errors Become Harder to Investigate With Time

Reconcile during the project.

Do not postpone basic control

A Practical Quantity-Control Workflow

Step 1: Establish the Authorized Quantity Baseline

Confirm the current project requirement by model.

Use controlled commercial documents

Step 2: Record Production Completion

Apply a defined completion rule.

Do not count partial work inconsistently

Step 3: Record Each Shipment

Keep shipment-level and cumulative quantity.

Preserve the source records

Step 4: Reconcile Physical Receipt

Compare shipped and received quantities.

Record exceptions

Step 5: Record Staging Status

Keep received-but-not-installed units visible.

Prevent site-side disappearance

Step 6: Record Installation

Use the project's agreed installation definition.

Separate location from completion

Step 7: Record Open Issues

Identify why installed units remain pending.

Assign responsibility

Step 8: Record Acceptance

Follow contractual and hospital acceptance requirements.

Keep acceptance separate from installation

Step 9: Reconcile Model, Accessory and Location Data

Do not rely on the grand total alone.

Check the complete scope

Step 10: Close Every Unexplained Quantity Gap

Every remaining unit should have a clear status.

Finish with evidence, not assumptions

The Better Question Is Not “How Many Beds Did We Order?”

That is only the beginning of project quantity control.

A stronger question is:

How many beds are currently at each defined stage, and can every difference between those stages be explained?

For a bulk hospital bed project, the quantity chain can be understood as:

Authorized Quantity → Produced → Shipped → Received → Staged → Installed → Pending Issue → Accepted → Reconciled.

The numbers do not need to be identical during project execution.

In fact, they often should not be identical while different shipments and installation activities are still in progress.

What matters is that the differences are controlled and explainable.

A bed should not disappear between shipment and receiving.

A received bed should not disappear between staging and installation.

A replacement bed should not accidentally become an extra contractual unit.

A bed moved between wards should not be counted twice.

An installed bed with an open issue should not be confused with a missing bed.

And the final accepted quantity should be reconcilable with the authorized project scope according to the applicable contract and acceptance process.

For hospital project managers, quantity reconciliation is therefore not simply counting beds.

It is maintaining a consistent relationship between commercial scope, physical equipment and project status from production through final completion.

Hebei Heyuan Medical Equipment Co., Ltd. manufactures electric hospital beds, manual hospital beds, ICU beds, pediatric beds and related medical equipment for international distributors, importers and hospital projects.

Buyers can review our hospital bed range for different hospital departments, project configurations and bulk procurement requirements.

For hospital project specifications, model configurations, OEM or ODM requirements and bulk quotations, please contact Heyuan Medical with your required models, quantities and destination market.