SYSTEM // LOADING
BIDQUEST // 2026
GRID // 1280px
BIDQUEST // 2026
Zero manual search • 100% Free
Plan a multi-site GeM order with site-wise quantities, access checks, installation resources, evidence ownership and a realistic cash-flow schedule.

One overall value and one overall delivery date can conceal very different operating conditions. A city office may accept goods during normal hours, while a distant facility needs advance permissions and a separate installation visit.
This article supplies an original planning method. Use current GeM instructions and the actual order for permissible delivery, acceptance and billing steps. Official seller training.

| Site | Qty/scope | Receiver | Access dependency | Delivery/install plan | Evidence owner |
|---|---|---|---|---|---|
| A | Verified allocation | Nominated role | Confirmed readiness | Planned sequence | Named person |
| B | Verified allocation | Nominated role | Open item | Revised action | Named person |
Add the contract milestone and relevant source. Do not create allocations from your own logistics preference if the order provides a different distribution.
If an address or site quantity is missing, ask for the required information early. Avoid transporting equipment based on an informal location forwarded without verification.

For each site, determine whether the obligation ends with receipt or includes testing, installation, training and support activation.
Assign the skills and time needed for those tasks. A delivery driver may obtain a receipt but not be equipped to complete technical commissioning.
Build the schedule around the full required outcome. If installation depends on electrical, network or civil readiness, confirm the dependencies with the relevant role and record what remains open.

Evaluate whether one shipment, several shipments or local support is operationally suitable under the actual terms. Consider packing, unloading, storage, travel, replacement and supervision.
Do not choose only by transport price. A cheaper route that creates extra installation travel or storage risk may cost more overall.
Where subcontractors or local partners are proposed, check permission and responsibility. A local provider's convenience does not establish a permitted contractual arrangement.

A supplier must provide 60 units: 30 at Site A, 20 at Site B and 10 at Site C. Installation is included. The internal estimate originally assumes one truck and one installation team.
Site A is ready, Site B requires access approval and Site C has a different network setup. Operations revises the programme to show the actual sequence, additional technical preparation and any requested formal decision.
Finance adds an extra visit costing an illustrative ₹18,000 and reviews the impact on the expected contribution. The evidence owner tracks receipt and installation separately at each site.
The example shows why allocation and readiness need to be known before quoting or mobilising. It does not establish a right to partial acceptance or separate billing.
Where appropriate, retain serial, asset or batch references, packing lists and site allocation records. Reconcile them at dispatch and receipt.
If a unit changes site or is replaced, record the movement and authorization rather than editing the old sheet silently. The final record should explain what each destination received.
For consumables or bulk materials, use the measurement and quality records the contract requires. The form of evidence should match the product and acceptance method.
Identify the approving role and required proof at each site. That might involve testing, reports, user handover or another specified record.
Assign responsibility for collecting evidence while the team is present. Asking an engineer to recreate installation details several weeks later is less reliable than a contemporaneous record.
Check whether the overall contract treats acceptance collectively or site by site. Use that answer to plan billing and cash flow rather than assuming each delivery produces an immediate receivable.
Clarify whether warranty or service begins per site or under another contractual trigger. Record support contacts, response arrangements and spare capacity where required.
Consider how the business will respond to a problem at the farthest site. Travel and replacement logistics are part of the promised service, not merely a future concern.
Keep the support plan with the order record so customer communications do not rely on whichever salesperson remembers the bid.
Supplier payments, transport and installation outflows can occur before acceptance at every location. Build a site-aware cash calendar and stress case.
If one site slips, ask whether it delays only its own billing or the whole invoice under the terms. Review security, extension and other commercial consequences through the proper process.
Do not treat pending buyer access as an automatically approved date change. Follow notice and formal decision requirements.
At each location, reconcile quantity, configuration, tests, outstanding work and acceptance. Then complete an overall review showing what remains open.
Avoid a single “delivered” status that hides installation at one site and missing evidence at another. Use statuses that correspond to real events.
The order owner should see each site's next action and the person responsible.
Before dispatch or deployment, confirm receiver, access, space, utilities, information and required permissions relevant to the scope. Mark each dependency ready, pending or not applicable.
One central confirmation should not replace site-specific checks when conditions differ. The order owner needs to know which location can receive and which can complete installation.
If readiness is pending, follow the prescribed notice and change process. Do not invent an informal rule that the delivery deadline moves automatically.
Keep the readiness evidence with the site record so a later reviewer can understand the decision to mobilise.
For an illustrative four-site programme, suppose the original plan includes one installation visit per location. Two sites then require additional approved coordination and return visits.
If each extra visit costs an assumed ₹9,000, the simplified additional travel and attendance cost is ₹18,000. Check whether more time, storage or supplier costs also arise.
These are management assumptions, not a reimbursement entitlement. Finance should show how the change affects contribution and funding under the actual terms.
Use the scenario before bidding when incomplete site information makes a single-visit assumption uncertain.
Prepare a programme showing which team, vehicle or equipment serves each site and when. Check for overlap with existing assignments.
If one technical specialist is needed at every location, identify the sequence and realistic travel time. Avoid promising simultaneous completion without the necessary capacity.
Where a local partner is contemplated, establish the permitted arrangement, competence, supervision and evidence responsibilities. A contact near the site is not automatically a committed delivery resource.
Keep the plan linked to the contract milestones rather than an internal preference for convenient travel.
A receiver may request a different room, location, configuration or extra task. Tell the field team which requests it can handle and which require formal approval.
Record the requested change, scope effect and decision. Do not let a series of small informal changes create an unfunded project without management noticing.
If equipment moves between sites, reconcile quantity and identity records. The final allocation should reflect what was authorised and supplied.
Finance should see any effect on price, billing or additional cost through the appropriate process.
For each destination, identify required receipt, testing, installation, training and handover records. Assign who collects them and who reviews completeness.
Use site identity and asset or batch references where appropriate. If the same document template is used everywhere, ensure it does not retain another site's name or quantity.
Keep originals and approved versions in a controlled folder. A central dashboard can summarise status but should link to the actual evidence.
Collect records while the team is at the site where practical, rather than relying on later recollection.
Suppose most of an order is complete but one site's acceptance remains pending. Review whether the actual contract permits billing of the accepted portion or requires another milestone.
Finance should not assume the remaining site has no effect on receipts. Model the applicable process and a plausible timing variation.
At the same time, do not mark the whole contract unpaid indefinitely if the terms and records support separate progress. The cash plan should follow the reviewed billing basis.
This is a reason to resolve acceptance structure before finalising the bid estimate.
Record which team handles each site's warranty or service requirements. Confirm contact routes, escalation and replacement arrangements relevant to the contract.
A multi-site installation can become fragmented if every receiver contacts a different salesperson. Use a clear service owner while preserving the official contractual communication route.
Keep asset and handover records available to the competent support team. They should not have to identify the installed configuration from a vague invoice description.
Include continuing travel and service capacity in the cost model where required.
Complete a site review covering supplied scope, accepted evidence, defects, outstanding tasks and support handover. Then reconcile the whole order's quantity, financial position and contractual obligations.
Do not close the whole project because every shipment arrived, or leave every site open because one minor record remains pending elsewhere.
Use precise statuses and responsibility. The next action should be clear enough that another authorised employee can continue it.
A well-maintained multi-location record supports delivery, billing, security release and future tender estimates with the same underlying facts.
When each destination is complete, reconcile supplied, accepted, replaced and outstanding quantities against the confirmed allocation. Check that the invoice and support register use the same item identity. A site-by-site completion process is useful only if the total contract record also remains accurate. Assign any remaining mismatch to a named owner before closing the order internally.
Give each site receiver the correct order and allocation reference. This reduces handover confusion when similar equipment is delivered to several locations during the same programme.
No. Verify site readiness, scope and evidence separately.
Check the full obligation and the required completion evidence.
Use the actual acceptance and billing provisions; do not assume separate billing is allowed.
Yes, where it is part of meeting the stated service commitment.
Site-wise scope, stage, dependencies, evidence, owner and next action.
Create a site matrix before mobilisation and link it to your cash and evidence plans. Explore BidQuest for discovery; fulfilment remains governed by the official order.
Government e-Marketplace. Accessed 12 Oct 2026.

Prepare a GeM seller registration information checklist covering account ownership, business profile, tax details, authorised signatory and catalogue readiness.
Read the guide
Learn how to compare GeM buyer-added terms, standard platform terms and bid attachments before pricing or submitting an offer.
Read the guide
Cancellation after acceptance depends on the actual order, applicable GeM terms, authority and reason.
Read the guide