Drawing Notes & General Conditions

A drawing set speaks in several registers of note. General notes apply across the whole project: they state the codes and standards the work complies with, dimensioning conventions, what governs when documents conflict, and standing instructions like "do not scale from drawings; figured dimensions govern". Discipline and sheet notes are narrower - structural notes, plumbing notes, notes specific to one plan. An abbreviations legend and symbol key let anyone read the set. And in the contract, the general conditions set out the rights, obligations and procedures of the parties - the legal frame around the technical work.

All of this is standing text, and standing text drifts. It is copied from the last job because rewriting it each time would be madness, and in the copying it silently ages. A general note may cite a superseded edition of a code; a note may promise a detail the current set no longer contains; a note on one sheet may contradict a note on another or the specification; an abbreviation may appear on drawings but not in the legend. None of this is dramatic on any single day - and then a contractor prices a contradiction, or a claim turns on a note nobody had read in years.

The work, therefore, is not really writing - it is completeness, consistency and currency. Are all the notes that should be there present? Do they agree with each other, with the spec, and with the drawings? Are the codes and editions they cite current? Doing this by hand across a large set is exactly the sort of patient, tireless cross-checking humans do worst late in a submission and Claude does tirelessly.

So the pattern from the earlier lessons holds. Claude is superb at drafting a complete, well-ordered note set from your intent and at reconciling an existing one for gaps and clashes. You are the one who confirms that a cited code is the current edition, that a legal clause is appropriate and lawful, and that the notes match the design as actually drawn. Speed and completeness from Claude; correctness and currency from you.

To draft, give Claude the job and the categories, and let it produce an ordered, complete set you edit down - it is easier to cut an over-complete list than to remember a missing note at 11pm before a submission. A useful prompt:

Draft the general notes for a residential building drawing set in India.
Group them: (1) codes and standards complied with, (2) dimensioning and
scaling conventions, (3) precedence when documents conflict, (4) materials
and workmanship general clauses, (5) site and setting-out. For any specific
code number or edition, write [VERIFY: current edition] rather than stating
one. Keep each note short and imperative.

Again the [VERIFY] habit is doing the heavy lifting: you get a complete note structure without a single confidently-stated-but-unchecked code edition baked in. Claude gives you the shape and the wording; you fill and confirm the facts.

The same works for an abbreviations legend and symbol key. Paste your drawings' text or your abbreviation list and ask Claude to build a clean, alphabetised legend and to flag any abbreviation that appears in the notes but is missing from the legend, or vice versa. This tiny completeness check catches the omissions that make a set look unprofessional and, occasionally, ambiguous.

For general conditions, be more cautious. Claude can draft plain, well-organised conditions and explain what a standard clause does - which is genuinely useful for understanding and for a first draft. But general conditions are a legal instrument. In many jurisdictions and on public work you will use a recognised standard form of contract, and the conditions must suit the procurement route and the law. Claude can help you read, structure and question conditions; it is not your lawyer, and bespoke conditions or amendments to a standard form should be settled with one. Draft and understand with Claude; commit with professional advice. Keep your verified note library and your standard conditions in a Project so every set starts from your best, current version rather than last job's stale copy.

The higher-value use is reconciliation. Because Claude holds a large context at once, you can give it the notes plus the specification plus a schedule and ask it to find where they disagree. "Here are my general notes, my specification and my finishes schedule. List every place a note contradicts the spec, every code cited in the notes but not the spec or vice versa, every note that refers to something not present in the set, and any two notes that conflict." A human doing this flicks between documents and misses things; Claude scans the lot and returns a candidate list in seconds.

Typical catches: a general note says "all glazing toughened" while the window schedule specifies laminated in wet areas; a note references a fire strategy drawing that was removed; a note cites IS such-and-such while the spec cites a different edition; a "do not scale" note sits beside a schedule that depends on scaled dimensions. Each is a small thing that grows expensive when a contractor prices the ambiguity or a dispute mines the contradiction.

The limits are the same as before, and worth repeating because they are where people get burned. Claude raises candidate contradictions; you confirm which are real, because some apparent conflicts are deliberate and correct. Claude only checks what you paste in, so feed it the live revisions - a contradiction against last week's superseded drawing is noise. And Claude cannot tell you a cited code edition is out of date unless you ask it to flag the reference and you then check the issuing body; its training cutoff means it may not know a standard changed.

Used as a reconciliation engine you drive, Claude turns the thankless final-check pass - the one that gets rushed before every issue - into a fast, structured review. You still make every call, but you make them on a list Claude assembled rather than on problems you hoped you had not left in. For boilerplate, where attention naturally flags, that assist is worth a great deal.

The loop. One: build a verified library. Keep your standard general notes, discipline notes, abbreviations legend and standard conditions in a Project, each already confirmed - your best current version, not last job's copy. Two: draft for the job. Have Claude tailor the library to this project, using [VERIFY] for any specific code or edition, and produce a complete, ordered set. Three: fill and confirm facts. Replace every [VERIFY] with a checked value, confirming code editions against the issuing body and any legal clause with professional advice. Four: reconcile. Give Claude the notes, spec and schedules and have it flag contradictions, orphan references and missing abbreviations. Five: adjudicate. Confirm each flag, correct the set, and read the standing text as the professional who issues it. Six: fold back. Save improvements to the library so it compounds over projects.

A note on stakes. Most drawing notes are low-drama boilerplate where consistency is the main risk, and Claude's help is nearly free. But two categories deserve harder scrutiny: code and standard references, because a stale or wrong one is a compliance risk, and general conditions and any legal wording, because they allocate rights and liabilities and are a lawyer's domain, not a drafter's. Scale your checking accordingly - light on the truly routine, ruthless on anything that carries a code or a legal consequence.

The honest summary: drawing notes and general conditions are where documentation is quietly won or lost, because they are boilerplate and boilerplate is where attention dies. Claude is a near-ideal partner for exactly this - it never gets bored, it keeps a long set consistent, and it reconciles the standing text against the rest of the documents faster and more completely than a tired human before a deadline. What it cannot do is guarantee a code is current or a clause is lawful. Let it make your notes complete and consistent; you make them correct, current and yours.