Contracts in present-tense fact form
Commercial and private contract authors adopt QPSG when they want agreements to read as mutual facts both parties affirm now — not as a wall of “whereas” recitals and “shall” obligations floating in future time. The processor does not rewrite your deal terms; it helps language match QPSG discipline.
Contract issues QPSG targets
- Shall/will stacking — every clause “shall” when present-tense mutual facts would suffice.
- Passive obligations — “payment shall be made” vs. who pays whom, when, in what amount.
- Defined-term sprawl — “Contractor,” “Client,” “Party” without consistent naming.
- Boilerplate bloat — severability and notice clauses copied from unrelated forms.
Processor workflow for contracts
- Paste or load from CONTRACTS template category.
- Run analyze — focus on tense and phrase rows first.
- Preview corrections — verify numbers, dates, and party names unchanged.
- Export copy for your signing workflow (wet ink, notary, or record as you choose).
Related: Contracts landing page