Set up the subcontract — parse the PDF into the fields the job runs on

Forty-one pages. I used to read two. The executed subcontract is the document the whole job runs on — the value, the retainage, the payment terms, the notice period that decides whether a change gets paid — and most of it lives on pages nobody opens after signing. STrOp keeps the PDF once, reads it for you, and puts the terms where the modules that need them can see them. You still review every field. You just don't retype them.

Register the document

1. Open the job → Records → Documents. + Upload, or drop the file on the page.
2. In the staging row set the type to Contract and give it the title you'll search for later — Creekside's is SC-2026-0412. Upload.
3. That's the only time you touch the PDF. From here it's a record with a viewer, a revision, and a status (Current, Superseded, Void).

Fill the contract fields

1. Setup → Contract. The Contract Details card holds the fields the job runs on: Awarded GC, Contract #, Contract Value, Retainage %, Contract Date, NTP Date, Subst. Completion, Final Completion — and the three clause numbers the Compliance tab dates from: Claim Notice (days), Insurance Expires, Warranty (months). The award seeded the value and dates; this is where they get corrected against the signed paper, and where the three numbers get typed if you skip the parse.
2. Parse Contract. Select document to parse — contract-typed documents sit at the top of the list — then Parse Contract again. A forty-page subcontract takes a minute or two.
3. Review. The modal opens with What Claude read, a plain-English digest, then Contract Fields (parties, contract numbers, type, prevailing wage, value, retainage, dates, then the notice days, insurance expiry, and warranty months as numbers — blank when the contract doesn't state one), any SOV table it found, and milestones. Every value cites the page it came from; a Medium or Low confidence banner means read all of them. Uncheck any section you don't want written.
4. Apply to Contract. The fields land on the card. Below it, the Contract Analysis card keeps the clauses that aren't fields — Payment Terms, Notice Requirements, Insurance, Liquidated Damages, Warranty, Bonds Required — each with a link to the page in the PDF where the language lives.

Flag what the contract makes due

1. Setup → Compliance. Creekside is public works, so Prevailing-wage contract is on — that switches on DIR registration, certified payroll, and break tracking.
2. Record the DIR Project ID, PWC-100 Number, and PWC-100 Registration Date. The live status rolls up under Billing → Compliance, where the weekly CPR is tracked from here on.
3. Below it, the Obligations card turns the clauses into dates. Five lines, sorted by what's due first: Pay app payment due (the latest period end plus the project's Net terms), Insurance certificate expires (the date you entered — Due soon inside thirty days, Past after), Warranty ends (substantial completion plus the warranty months — the issued SC date once Closeout has one, the planned date until then), Retention release eligible (the Closeout clock: 35 days from the notice of completion, or from SC until the notice records), and Claim / change notice, which is a window rather than a day — written notice within N days from the event — so it shows as a rule. A line that's missing its number reads Not set and says what to enter, with a link to the tab that holds it.
4. The billing-side dates — the conditional waiver with each pay app, the unconditional after the check clears, the preliminary-notice clock — still run per project on the lien deadlines and waiver rules. The clause text itself stays in the Contract Analysis card with its page link; the Obligations card is the number the text boils down to.

Common mistakes

• Applying without reading. The parse is a draft, not a signature. Retainage, the notice period on changes, and the insurance limits are the three that cost real money when they're wrong — check each against its cited page before Apply to Contract. The notice days and warranty months are the parser's reading of prose ("one (1) year", "within seven days") — if the clause is conditional, the number is the simple case.
• Leaving the award's numbers in place. Award recorded the deal as you understood it; the executed subcontract is the deal. If buyout moved the value or the retainage in the paper isn't what you assumed, the signed page wins.
• Uploading the contract as Other. Parse still finds it, lower in the list, but the next person who filters Documents by type finds nothing.

See also

• E8 · Awarded
• E10 · Week one
• California lien deadlines
• Lien waivers — the four California forms