Release 1, in effect since November 13, 2026
This is the standard 4 Seasons checks its own jobs against. Each step has a page that lists the photos it needs and when each is taken, the tests and readings with their pass values, the lines that fail the step, who approves it and what sends it back. The pages are read from the same standards the system runs, so a page cannot say something the checks do not do.
Anyone may write their own jobs to it. It is 4 Seasons' own standard, published so both sides of a job can read it before they start.
116 steps across 13 trades
01Taken live in the app
Each photo is taken with the camera inside the 4 Seasons app. A photo picked from the phone's library is marked as picked from the library on the record, where everyone who reviews the step sees it.
02Taken at the address
The phone's location is recorded with the photo. On a 4 Seasons job a photo shows as taken at the house when it is within 150 m of it. On a plan with your own contractor the limit is 200 m from the address plus the phone's own stated accuracy, up to 150 m more. A photo with no location is marked on the record. One taken farther away is marked and the checks send the step to a person.
03Sealed on arrival
A SHA-256 fingerprint of the file is recorded when it reaches us. Anyone holding the file can compute the same fingerprint and see that the photo on the record is the one that was taken. A photo with no fingerprint cannot be shown as unaltered, and the record says so.
04Taken on the job's clock
The time the shutter fired is recorded. A photo taken more than 12 hours before the work started or after it finished is sent to a person as an edge case.
05Not used before
A file that is already on earlier work is marked as reused and the checks fail the step on it. A photo that looks like one from another home goes to a person.
Held to the contractor milestone standard. Contractor milestone
A step or task the system does not recognize is held to one of two general pages.
GET https://www.build4seasons.com/pay-on-proof/standard.jsonOpen
{
"schema": 1,
"release": 1,
"effective": "2026-11-13",
"pages": [
{
"id": "project.waterproof",
"version": 1,
"effective": "2026-11-13",
"title": {
"en": "Backer board and waterproofing",
"es": "Tablero e impermeabilización"
},
"shots": [
{
"id": "walls-banded",
"label": {
"en": "Every wall banded",
"es": "Cada pared sellada"
},
"when": "after",
"required": true
}
],
"readings": [
{
"id": "flood-minutes",
"unit": "min",
"min": 15,
"max": null
}
],
"blocking": [
{
"id": "no-wet",
"text": {
"en": "No wet spots after 15 minutes",
"es": "Sin humedad después de 15 minutos"
}
}
]
}
]
}Each page carries the same fields this site shows, by the same names. rules.json
GET https://www.build4seasons.com/pay-on-proof/standard/spec.json
To check your own sealed photos and machine records before you send them, run the conformance suite in @payonproof/capture/conformance. It runs the checks our API runs, on your machine, with no network calls.
A machine record is a signed summary of a sensor or machine log for one step. It is always labelled machine proof, it counts as evidence, and a person decides on it.
The licence is not chosen yet, and the owner has to confirm it. Until then you can read the standard and check your work against it. Ask us before you republish it.