Auction Data Procedure

Process boundary

This SOP covers an automated auction workflow: setting up one auction row in the Auction House Database, running the Pre-Auction worker to create the working workbook from the catalogue, capturing live auction activity in Chrome with the auction-house capture script, and running the Post-Auction worker to update the same workbook with live bid data and final result evidence. The operating model is:

1. Notion is the control panel.
2. The Notion Worker is the processor.
3. Google Drive is the workbook storage location.
4. The live auction capture still happens in the browser, not inside the worker.
5. Each auction should have one row and one main workbook.

---

Operating workflow

Each auction starts as a single record in our tracking system. We enter the auction house, auction date, catalogue link, and other basic setup details. A few days before the auction, the pre-auction automation reads the catalogue and creates the initial Excel workbook with the lot details, guide prices, links, postcodes, use class, notes/features, and income where available. On auction day, the live capture script runs on the auction page and records bid activity into a CSV and log file. After the auction, the post-auction automation uses the same workbook, the live capture files, and the updated catalogue/results page to add the final result fields: starting bid, final bid, sold price, status, and available-at price.

Workbook specification

Before the auction, the workbook is created with the core lot information:

1. Auction House
2. Lot Number
3. Link
4. Use Class
5. Notes / Features
6. Postcode
7. Guide Price
8. Income per annum, where available After the auction, the same workbook is updated with:
9. Starting Bid Price
10. Final Bid Price
11. Sold Price
12. Status
13. Available At Price The workbook also includes formula columns that calculate automatically for each row:
14. Yield on Guide
15. Yield on Sold
16. Yield on Final
17. Variance on Guide:Sold
18. Variance on Guide:Final