Public guides are drafted by practitioners, reviewed against contractual positions by an EPC contract reviewer, and edited for clarity before publication. Use-case guides are reviewed at least every 6 months; corrections are reflected in each page's structured-data dateModified field.
Last reviewed:Contract Copilot editorial team
Editorial Process
This page describes how Contract Copilot creates and maintains the contract correspondence guidance published on this site — what we publish, who reviews it, where the wording comes from, and how often we recheck it.
Who writes and reviews this content
Our editorial work is led by the Contract Copilot editorial team, a small group of practitioners with hands-on EPC and construction contract experience.
Each public guide passes through three roles before it goes live:
- Drafter — assembles the structure (when to use, what to include, common mistakes, sample wording) using project experience and standard-form references.
- Contract reviewer — a practitioner with EPC / construction project background checks the wording against common contractual positions (e.g. notice timing, reservation of rights, scope of variation).
- Editor — checks clarity, neutrality, and that the guide stays a drafting aid rather than legal advice.
We do not publish content drafted solely by an LLM. Models may be used to accelerate first drafts, but every published guide is verified line-by-line by a human reviewer before publication.
Sources we rely on
Our guidance is grounded in:
- Standard-form construction and EPC contracts widely used in international projects (FIDIC Red / Yellow / Silver Book families, NEC, bespoke EPC turnkey forms).
- Publicly available case-law digests and practitioner commentaries on construction contract administration.
- Direct project experience handling correspondence such as delay notices, variation instructions, force-majeure events, and payment-related letters.
We deliberately keep the public guides standard-agnostic — we describe principles (notice timing, evidence required, what not to admit) rather than quoting any single contract verbatim. Any user must reconcile the sample against their actual contract before issuing a letter.
How often we recheck
| Content | Cadence |
|---|---|
| Public use-case guides (/use-cases) | At least every 6 months, plus an out-of-cycle review whenever a major change to a referenced standard form is published. |
| Glossary entries (/glossary) | At least annually, plus when reader feedback flags an inaccuracy. |
| Blog posts (/blog) | Reviewed when material is referenced by another guide; older posts that no longer reflect current practice are either updated or marked as archived. |
| Sample letter wording inside guides | Re-read on every cadence above; flagged tone/positioning issues are resolved before the next publish. |
The "Last reviewed" date shown at the top of each use-case guide reflects the most recent human review — not just an automatic timestamp.
Corrections policy
If you spot an error in a guide:
- Email hi@contractcopilot.app with the URL and the issue.
- We aim to acknowledge within 2 business days and to update or annotate the page within 10 business days for substantive issues.
- Material corrections are reflected in the page's dateModified field (visible in the page's structured data) so search engines and AI engines can detect that the content was revised.
What this site is — and is not
Contract Copilot is a drafting aid. The guidance and sample wording are provided to help users prepare a structured first draft faster.
This site is not:
- A law firm, and we do not provide legal advice.
- A substitute for review by qualified counsel against the user's specific contract and governing law.
- A position paper on any particular dispute.
Every output (whether read on this site or generated through the product) must be reviewed against the actual contract, the governing law, and the project context before it is sent.
Contact
- Editorial questions or correction requests: hi@contractcopilot.app
- General contact: see the About page.