# Delivery quantities and received condition for fragile items

Example: A venue received all ten lamps, but two arrived with damage. The supplier gives a satisfactory state for the complete delivery.

By Righthand Team · 2026-10-23

Source: https://www.righthand.ai/blog/delivery-quantities-and-received-condition-for-fragile-items

Use quantities for completeness. Use condition evidence for suitability, and keep acceptance with the responsible owner.

This article is from Righthand. The story and result are illustrative.

## Two records with different meanings

A delivery quantity counts items at receipt.

Received condition records observed damage or other item state.

## The customer's situation

A venue received all ten lamps, but two arrived with damage. The supplier gives a satisfactory state for the complete delivery.

The owner gives the Righthand the identified source material and relevant contacts. A Righthand is an assistant with email, text, phone, and Slack communication. [Introduction](https://docs.righthand.ai/introduction).

## The request to the Righthand

> Read the supplied count and condition notes.
>
> Send damaged items independently from quantity.
>
> Contact the supplier about the approved remedy question.
>
> Send the owner the result in this conversation.
>
> Get approval before you change an accepted commitment.

The assistant reads the sources for their different meanings. It compares the relevant facts and sends the difference to the owner.

If the request permits contact, the assistant sends the identified question to the supplied recipient. Send the reply to the person responsible for the decision.

## An illustrative result

> Ten lamps arrived. Two have reported damage. The quantity count does not establish whether the lamps are satisfactory.

The owner gives a decision about a remedy after examining condition evidence.

## Set access and authority for the actual task

Supplied source material can be sufficient for the first procedure. For direct account access, a connection with the applicable operation and Righthand access is necessary. [Connections](https://docs.righthand.ai/guides/adding-your-first-connection).

For an external action, identify the recipient and task. **Ask** uses an explicit instruction or approval. Connection tool permissions are another required control. [Communications Policy](https://docs.righthand.ai/security/external-communications).

## Try the difference with one case

1. Give the assistant one example of each source.
2. Include a difference that affects the task.
3. Compare the returned difference with both sources.
4. Make sure that the test recipient receives a permitted message.
5. Examine the work in [Activity](https://docs.righthand.ai/guides/working-with-your-righthand).

A satisfactory result must keep the difference and identify the next owner decision. It must not silently replace one source with the other.

## When another approach is sufficient

A direct record or a human review can be sufficient when it gives the answer and no further conversation is necessary. A Righthand is an alternative when you want responsibility for the next information request and decision handoff.

[Compare plans](https://www.righthand.ai/pricing). [Get a Righthand](https://teams.righthand.ai).