# Read an order's history

Send and amend an approved order, then read every recorded change in its history.

Source: https://help.smartfact.ai/purchasing/guides/purchasing-order-history

Audience: Supervisor

Sarah Hughes is signed in with only the Supervisor role and a recent security check. HP-PO-01001 is approved for two hours of machine calibration. She records how it was sent, amends it to one hour and approves the amendment.

## Read an order's history

1. **Open the approved orders**

   Open the approved orders.

   Sarah uses her Supervisor role to record a supplier communication. A recent security check is required.

2. **Check the approved calibration order**

   Check the approved calibration order.

   Open HP-PO-01001 and check the approved revision. It authorises two hours of machine calibration. Downloading or printing its document does not record a send.

3. **Record a communication already made**

   Record a communication already made.

   In this scenario Sarah has entered the approved order in Calder Fixings' supplier portal and retained its acknowledgement. Record that completed communication here; this button does not contact the supplier.

4. **Choose the supplier portal**

   Choose the supplier portal.

   Choose the method actually used to communicate the approved revision.

5. **Keep the destination and reference**

   Keep the destination and reference.

   Retain the supplier portal and acknowledgement reference so another person can check the communication.

6. **Record the communication time**

   Record the communication time.

   Enter the local equivalent of 14 October at 10:00 UTC for this lesson. Help displays and types the value in your browser time zone. In your work, record when the communication actually happened.

7. **Keep the communication evidence**

   Keep the communication evidence.

   Keep a short description of the acknowledgement with the send record. A communication record does not prove supplier acceptance of the order terms.

8. **Save the send record**

   Save the send record.

   Record the completed communication against revision 1. The approved quantity and order identity stay the same.

9. **Prepare a change to the sent order**

   Prepare a change to the sent order.

   The calibration visit now needs one hour instead of two. Open an amendment; the approved revision remains in force until the change is approved.

10. **Reduce the proposed quantity to one hour**

   Reduce the proposed quantity to one hour.

   Enter the revised quantity in hours. Keep the original line identity so the history remains connected.

11. **Propose the revised visit date**

   Propose the revised visit date.

   Request the visit on 22 October. Check the date with the requester before approving the change.

12. **Explain the revised requirement**

   Explain the revised requirement.

   Keep the instruction that the supplier needs with the proposed revision.

13. **Save the amendment draft**

   Save the amendment draft.

   Save revision 2 as a draft. Revision 1 remains in force, including its approved two-hour commitment.

14. **Submit the proposed revision**

   Submit the proposed revision.

   Submit the one-hour amendment for approval. Submission still leaves revision 1 in force.

15. **Approve the reviewed amendment**

   Approve the reviewed amendment.

   This site has a reviewed one-supervisor rule. Sarah can approve revision 2 after checking the quantity, date and note. Approval changes the commitment and creates new documents; it does not communicate the revision.

16. **Read the order history**

   Read the order history.

   The order history keeps every change in order, with its time: the original submission and approval, the recorded send, the amendment and its separate approval. Earlier revisions and their approvals stay on record.

[Watch or practise this chapter](https://help.smartfact.ai/purchasing/demo?guide=purchasing-order-history&chapter=order-history&audience=office)

The order history is a record, not a draft: nothing in it can be edited. Use it to answer who approved what and when, alongside the send history and the recorded rule checks.
