# Pine Property Services

Six fictional properties with estimates, scheduled/completed work orders, maintenance checks and reconciled job costs.

All entities and transactions are fictional. Snapshot: 2026-09-08.

## Start with the linked model

1. Open operations.xlsx and review the Summary sheet. Source tables contain stable primary keys and declared references.
2. Change source values in the workbook to explore the calculated totals and editable chart.
3. Compare output values with expected-results.json. The JSON Schema checks types; primary-key uniqueness and joins also require the listed semantic checks.
4. Use invalid-records.json only in a local validation harness. Its three cases exercise duplicate keys, wrong types and an orphan reference.

## Included tables

| Table | Records | Primary key |
| --- | ---: | --- |
| properties | 6 | property_id |
| work_orders | 12 | work_order_id |
| job_costs | 12 | cost_id |
| estimates | 12 | estimate_id |
| inspections | 9 | inspection_id |
| maintenance | 6 | maintenance_id |

## Expected totals

- Estimated work: 3,858.00 USD. Sum estimates.estimate_total over the included records.
- Recorded job costs: 2,838.00 USD. Sum job_costs.total over the included records.
- Work orders: 12.00 records. Count unique work_order_id values in work_orders.

## Platform mapping

primary-records.csv is a generic example table. It is not a native platform export. Where this kit includes a named profile, use that profile’s separate CSV and schema and review its compatibility level before uploading.

## Scope and assumptions

- Scheduled work-order costs are planned commitments; completed work-order costs are actuals in this fictional register. Inspection records are operational examples, not statutory certificates.