Skip to content
Testaroo
md4.7 KB

Pine Property Services: Document set README

Document set README for Pine Property Services. 23 files, 1 of them intentionally invalid, with the reconciliation identities and the exact defect in each broken file named in full.

Preview, first 50 linesmd
# Pine Property Services: progress billing, retainage, change order and lien waiver documents

The payment pack for one construction contract at the second application: the schedule of values, an AIA-style continuation sheet and summary with retainage on both completed work and stored material, the change orders that moved the contract sum, the retainage ledger, the conditional and unconditional lien waivers, the certificate for payment, and the job costing, work order, material, daily log and inspection records underneath them.

All parties, amounts and identifiers are fictional. Fixed snapshot: 2026-09-08. Every record is derived from the shared operating model `trades-property`, so identifiers join across this set and across the business-kit fixtures that use the same model.

## Reconciliation identities this set asserts

- The schedule of values totals 3858.00, the original contract sum.
- Original contract sum plus 255.00 of change orders gives the 4113.00 contract sum to date on line 3.
- The continuation sheet totals 3248.00 completed and stored and 324.80 of retainage, exactly lines 4 and 5 of the summary.
- Retainage is 10 percent of the completed and stored figure to the cent, including the negative retainage on the credit change order.
- Line 6 less line 7 equals the 1582.20 current payment due, which is the amount on the conditional lien waiver and the certificate.
- The two lien waivers total 2923.20, the whole of the earned value less retainage, so nothing certified is unwaived.
- estimate_total minus actual_total is 85.00 on every work order, 1020.00 in total.

## Files

| File | Format | Validity | What it is |
| --- | --- | --- | --- |
| `schedule-of-values.csv` | csv | valid | Schedule of values |
| `application-for-payment-002-continuation.csv` | csv | valid | Application for payment continuation sheet |
| `application-for-payment-002-summary.csv` | csv | valid | Application for payment summary |
| `application-for-payment-002-retainage-rate.csv` | csv | invalid | Application for payment whose retainage was withheld at the wrong rate |
| `schedule-of-values.xlsx` | xlsx | valid | Payment application workbook |
| `change-orders.csv` | csv | valid | Approved change order register |
| `change-order-CO-001.pdf` | pdf | valid | Change order PDF |
| `retainage-ledger.csv` | csv | valid | Retainage ledger |
| `lien-waiver-register.csv` | csv | valid | Lien waiver register |
| `lien-waiver-conditional-LW-2026-002.pdf` | pdf | valid | Conditional lien waiver PDF |
| `certificate-for-payment-002.pdf` | pdf | valid | Certificate for payment PDF |
| `job-cost-report.csv` | csv | valid | Job cost report, estimate against actual |
| `job-cost-report.json` | json | valid | Job cost report JSON |
| `cost-code-summary.csv` | csv | valid | Cost code budget against actual |
| `work-order-export.csv` | csv | valid | Work order export |
| `work-order-export.json` | json | valid | Work order export JSON |
| `material-purchases.csv` | csv | valid | Material purchase register |
| `daily-log.csv` | csv | valid | Site daily log |
| `inspection-register.csv` | csv | valid | Completion inspection register |
| `properties-export.csv` | csv | valid | Property register with job costs |
| `maintenance-schedule.csv` | csv | valid | Planned maintenance schedule |
| `construction-reconciliation.json` | json | reference | Construction reconciliation assertions |

## Deliberate defects

These files are broken on purpose. Each one is a single named mutation of a correct file in the same directory, so a parser under test can be checked against both.

- **`application-for-payment-002-retainage-rate.csv`** Line 5a states 10 percent of 3108.00, which is 310.80, but carries 155.40. Line 8 is therefore 162.40 overstated. Every other line still adds up, so line-by-line arithmetic checks pass and only a check against the stated rate catches it; the contractor is paid 162.40 of money the contract says is retained.

## Notes and limits
… 57 lines total: download for the full file.

Specifications

Document Set
construction
Industry
trades-property
Source Kit
trades-property
Synthetic
true
As Of
2026-09-08
Documented Files
23
Documented Defects
1

Testing contract

Reference control
Scenario
Read the README before using the set, then check that every filename it lists exists in the same directory and that the defect list matches the files marked invalid.
Expected result
The file table lists 23 entries including this README, and the deliberate-defect section names 1 file(s). The reconciliation section states the arithmetic identities the valid files satisfy exactly.

What is a .md file?

Markdown (MD) is a lightweight plain-text markup language that uses simple punctuation conventions to denote headings, lists, links, emphasis, and code. It is designed to be readable as-is and to convert cleanly to HTML. It is widely used for documentation, READMEs, and content authoring.

How to use this file

Use an example Markdown file to test parsers and renderers, verify GitHub-Flavored Markdown extensions like tables and fenced code, and exercise HTML-conversion pipelines.

How to use this file for testing

“Pine Property Services: Document set README” is a deterministic Testaroo fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: MD · 4,836 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Document fixtures list their internal structure (pages, fields, tracked changes, embedded objects) in the spec table. Test extractors, converters, and OCR against that known structure, and compare searchable↔scanned or format-twin companions when present.

Code examples

import markdown  # pip install markdown

html = markdown.markdown(open("README.md").read())
print(html[:200])

Generated by generation/industry_documents.py. Free for any use, no attribution required, license.