Project File · Standard v1 · 17 August 2026

The field manifest.

A Project File is what a credit union receives instead of a lead: the bid and its amount, the contractor's licence and certificate of insurance, permit status, the cancellation date, a signed consent record — and, after the work, a dual-signed completion attestation. This page is every field in it, and whether that field exists in running code this morning.

What it is

One object, three tiers

DuckWater is a technology and attestation company. It sells a Project File, not a lead, and it never makes the decision that follows one.

Tier 1 is in every file. Tier 2 is there only because the person put it there, one item at a time. Tier 3 is the tier that never exists — the fields DuckWater refuses to hold, listed so that "we do not do that" is checkable rather than reassuring.

The file is built to land in the institution's own systems and be underwritten there. DuckWater does not lend, insure, decide, price, hold funds or keys, or charge the contractor a fee — see the rules we publish, where each of those is tied to the test or the clause that keeps it true.

How to read the Today column

Every row says what exists now, because a field list with no such column is a wish list.

  • CollectedThe intake or the document store writes this field today.
  • PartialSomething is collected, but not yet in the shape this spec names. The row says which part is missing.
  • SpecifiedWritten down here, not built. No page on this site describes it in the present tense.

Tier 1 — in every file

FieldWhere it comes fromToday
Bid and scopethe contractor's own document, attached as signedUpload · required of the homeownerCollected
Amountthe figure on that bidIntakePartiala band today (under 15k / 15–40 / 40–75 / 75+), not an exact figure
Contractor identitylegal entity, trade, service areaBuilder Partner recordCollected
Contractor licencenumber and issuing stateContractor signup · required, photo or PDFCollectedthe file and the number are on the partner record at signup; the issuing state is the state they work in
Certificate of insurancecarrier, lines, limitsContractor signup · required, carries an expiryPartialthe file, the carrier and the expiry date are on the partner record at signup; lines and limits are not yet parsed fields
Permit statusfiled, issued, or not required — with the authority namedDocument · optionalPartialthe permit document is collected; the status is not yet a field
Cancellation windowa date, not a durationComputed at signatureSpecified
Consent recordthe disclosure text exactly as the person saw itConsent store · verbatim, versioned, timestampedCollected
Completion attestationdual-signed by contractor and homeowner, after the workPost-completionSpecified

Tier 2 — only if the person adds it

Consumer-permissioned, one item at a time. Nothing here is required to get an answer, and refusing any of it does not change what an institution is shown.

FieldWhere it comes fromToday
Photosbefore, during, afterHomeowner uploadPartialthe document store takes homeowner uploads today — photo ID, income, the bid, the contract, the permit. Project photos are not one of its kinds yet
Lien waiverwhen the job reaches the stage that produces oneUploadSpecified
Permit close-outthe authority's document, not our summaryUploadSpecified
Change orderssigned, or they are not in the fileUploadSpecified

Tier 3 — the row that never exists

Not "we do not currently". These are absent by construction: there is no column for them, and adding one would be a schema change with a reviewer on it.

  • A DuckWater credit score, band, tier or rating of the homeowner.
  • A DuckWater ranking, grade, star rating or league table of contractors.
  • Credit-bureau data. DuckWater performs no credit inquiry of any kind, so there is nothing to hold.
  • SSN, date of birth, income or assets held for DuckWater's own use. The institution collects what its own programme requires, in its own flow.
  • Anything sold, rented or syndicated to a third party. There is no list, and there is no buyer.

The completion attestation

Deliberately narrow, because the wide version would be a claim DuckWater is not licensed to make. The attestation is a record that the contractor and the homeowner both signed to say the work described in the bid was done — corroborated by the photos, the lien waiver and the permit close-out attached to the same file.

It is a record, not an inspection. DuckWater does not visit the site, does not verify workmanship, and does not certify that anything was built to code. Two parties said so, in writing, on a date. That is the whole claim.

Delivery

Four integration shapes are modelled today — a link, a hosted redirect, an embedded widget and an API hand-off — and a file is never handed anywhere without a matching consent record, which is enforced by a test rather than by a convention.

No institution is connected. No Project File has been delivered to anyone. When the first integration goes live this page will name the date it did, and the shape it used.