Your agreement, assembled by rules — not by memory.
Intake form in, signature-ready contract out. Exhibits, signing authority, and conditional clauses are driven by a rulepack you control, on your own templates — with an audit record of every value from birth.
Request early accessThe problem: copy-paste is a contract risk
Most owner organizations assemble agreements the same way: find the last similar contract, save-as, and start swapping values. The failure modes are familiar — a stale exhibit grid, a retention percentage from the wrong deal, a time-and-materials clause left in a lump-sum agreement, a signature block below the signer’s actual authority. Each one is invisible until it matters.
How it works
- Tag your templates once
Your existing agreements become fill-ready templates. The language stays exactly as your counsel approved it.
- Fill the intake
Project, parties, contract value, compensation type, schedule, insurance limits. The rulepack validates as you go — a T&M contract without a not-to-exceed, or retention above your cap, is refused before a document ever exists.
- Generate
A signature-ready contract with the right exhibits attached, the right conditional clauses in or out, and the right signatory tier computed from contract value — plus an audit JSON recording every value and rule that produced it.
The audit record is the point
That audit JSON is a machine-readable index of the contract you just signed — its caps, notice windows, and markup limits. The Change Orders module consumes it directly: the contract you generated defends itself for the rest of the project.
Who it’s for
Owners and owner’s reps who issue their own agreements — construction contracts, consultant agreements, service agreements — and want every one of them produced the same disciplined way, whoever filled in the form.
Frequently asked questions
- Does it use its own contract templates?
- No — it assembles yours. Your attorney-approved templates are tagged once; from then on, every agreement is generated from them with project-specific values filled in and validated. Your paper, your clauses, consistently applied.
- Is this practicing law?
- No. ProjectOpsIQ Contracts is document assembly on templates your counsel has already approved. It enforces the rules you configure — it doesn't write legal language or advise on terms.
- What is a rulepack?
- A per-organization configuration file: which intake fields exist, what values are valid, which exhibits attach under which conditions, who has signing authority at which contract value, and which clauses switch in or out. Change the rulepack, and every future contract follows the new rules.
Early access
The platform is in active development. We're lining up a small first group of owners, owner's representatives, and A/E teams to shape it against real projects. A sign-up form is coming to this page shortly — check back, or watch this site.