Load the manuals for the equipment you actually service into a ChatGPT or Claude project, or a Gemini Notebook (formerly NotebookLM), and ask questions that demand the exact quote, section heading and page number. Open that page in the PDF before you act on it. Use the tool to find things faster, never to decide anything safety-related.
Most failures are quiet ones: an answer for the wrong model suffix, a table read down the wrong column, a manual one revision out of date, or a reply that came from the AI's general knowledge instead of your file. The routine below is built to expose each of them.
Which documents to load, and which to leave out
A manufacturer's paperwork for one unit is several documents, and each answers different questions. Loading the right ones, labelled clearly, is most of the work.
| Document | Good for | Where it goes wrong |
|---|---|---|
| Installation manual | Mounting, clearances, wiring, start-up steps | One manual often covers a whole family of capacity suffixes, so a table row can belong to a different model |
| Service or technical manual | Fault codes, test procedures, sequence of operation | Older revisions stay in circulation |
| Wiring diagram | Terminal labels, control circuit | An image, and usually the part of a file that an AI reads least reliably |
| Spec or data sheet | Capacity, airflow, electrical data, dimensions, sound level | Figures are rated at stated test conditions, and the footnotes carry the conditions |
| Parts list | Part numbers, exploded views | Parts get superseded; confirm with the distributor before ordering |
| Service bulletin | Field fixes and corrections, often by serial-number range | Easy to forget and easy to bury under older files |
Leave out customer files, quotes, invoices, dealer price lists and manuals for equipment you do not service. Do not put two revisions of the same manual in one project unless the file names make the revision obvious. Name each file by brand, model family, document type, revision and date, for example ExampleCo_F96_Service_RevD_2025-03.pdf. Then match the revision to the unit in front of you: the nameplate gives the model and serial number, and the manual's cover or back page usually shows its revision or date.
ChatGPT project, Claude project or Gemini Notebook: what each takes
All three can hold a library of PDFs and answer from it. The differences that matter for manuals are file limits, how PDFs are read and who can share the project. These are the limits as of October 2026; check each vendor's page before you build around them.
| Tool | What it takes | PDFs | Sharing and cost notes |
|---|---|---|---|
| Claude project | Project files up to 30 MB each, with no fixed file count, but on the free plan everything must fit in the context window. Paid plans switch to retrieval for large knowledge, which Anthropic says can expand capacity by up to 10 times. | Text and visual elements for PDFs up to 100 pages; text only from 101 to 1,000 pages | Projects exist on every plan, with up to five on Free. Sharing is for Team and Enterprise only. |
| ChatGPT project | Files per project: 5 on Free, 25 on Go and Plus, 40 on Pro, Business, Enterprise and Edu. Per-file limits are generous: up to 512 MB, and roughly 2 million tokens of text. | Reads text-based PDFs; test a scanned, image-only page before you rely on it | Project sharing is available on every plan. |
| Gemini Notebook | Each source up to 500,000 words or 200 MB; a free account can hold up to 50 sources in a notebook | PDF is a supported type; Google's page does not mention scanned PDFs | Free to start; paid Google plans raise the limits |
My rule of thumb: if the manuals are mostly text and tables, any of the three will do and you should pick the one your team already has an account for. If wiring diagrams matter, a Claude project with diagram pages split into a PDF under 100 pages gives you the best chance of the diagram being read as an image. Either way, test a diagram page in your own project before you rely on it. Gemini Notebook compared with ChatGPT and Claude projects covers the document-handling differences in more detail.
Preparing a manual so the answers can be checked
- Split big manuals. Cut by function (installation, troubleshooting, parts) or by chapter, and keep each file under 100 pages so a tool that analyses visuals can do so. Put the page range in the file name.
- Pull the wiring diagrams into their own PDF. A short file of diagram pages is more likely to have its images analysed than a 250-page manual.
- Check the text layer. Open the PDF, try to select a sentence and copy it. If you cannot, it is a scan, and it needs OCR before an AI can work with it reliably.
- Add a one-page index note. A short text file in the project lists the model families covered, what each suffix means, the revision and date of each manual, and the units used (metric or imperial). Tell the assistant to read it first.
- One project per equipment family. "Gas furnaces, Brand A" and "Heat pumps, Brand B" are separate projects. Mixed families are how an answer for one unit ends up on another.
Page numbers deserve a warning of their own. A manual's printed page numbers are often chapter-based (such as 3-12) and often differ from the page index in the PDF viewer, because of covers, contents pages and inserts. Always ask for both, and make checking them the first test you run, because every later answer depends on it.
The instruction that forces a citation
Put this in the project's instructions so every answer has the same shape:
You answer questions about HVAC equipment using ONLY the files in this
project. For every answer give:
1. The answer in one or two sentences.
2. The exact words from the manual, in quotation marks.
3. The file name, the section heading, the printed page number and the PDF
page number.
4. The model or capacity suffix the answer applies to, copied from the row
or heading you used.
If the files do not say, reply "Not stated in the files" and stop. Do not
use general knowledge. If two files disagree, show both and do not choose.
Never give a go or no-go on safety. Point to the page and say that a
qualified person decides.The exact words are what make the check quick. Open the PDF at the page given, press Ctrl+F (or Cmd+F) and paste a few words of the quote. If they highlight, the answer rests on the page. If nothing highlights, you have caught a paraphrase or an invention, and the answer is a guess. A typical exchange looks like this, using an invented manual:
Question: Fault code 33: what does it mean, and what does the manual tell me to check?
Answer: Code 33 is a limit circuit open condition. "Limit switch circuit is open." File: F96_Service_RevD.pdf, section "Diagnostic codes", printed page 41, PDF page 47. Applies to all models in this manual. The manual's checks are listed as steps 1 to 4 under the code table. Not stated in the files: replacement part numbers (see the parts list).
Searching the PDF for "limit switch circuit is open" lands on PDF page 48, one page later than the answer said. That is a typical slip: the quote is right and the page reference is off by one. It is why the instruction asks for both page numbers and why the quote, not the page number, is what you trust.
Compare that with a loose question such as "What clearance does this furnace need?" Without a quote requirement, the usual reply is a confident general answer with a round figure, no file name and no page. It may match your manual or it may describe furnaces in general, and nothing on the screen tells you which. Questions that name the file, the model suffix and the table are the ones that produce answers you can check in 30 seconds.
Six jobs worth doing, with the question to ask
Fault codes and diagnostic steps
The exchange above is the model: one code, one quote, one page. Ask for the manual's own step list rather than a paraphrase, and have the tool stop at the end of the manual's list. A parallel from another trade, with the same limits, is covered in AI for mechanic diagnosis: fault codes, manuals and limits.
Clearances and service space
This is the question that comes up on every survey. Ask: "From the installation manual, give the clearance table row for the -048 suffix. Quote the row, name the table and say which clearances are for service and which are to combustible materials." The reply should quote the row with its values, for example "service clearance, front: [x] mm". The value is left blank here on purpose, because the number you rely on has to come from the printed page and not from a tutorial. The risk is a table read across the wrong row, so open the table, put a finger on the right suffix and photograph the page into the job file.
Electrical data for sizing the supply
Ask for a table of the electrical figures the manual lists for the three models you quote most, with a page reference per row. Then confirm each figure against the nameplate of the unit that is actually being fitted, because the nameplate is the figure of record. A model-suffix mix-up shows up here as a figure that is plausible for the wrong capacity.
Commissioning checklist as a job sheet
Turn the "Start-up and adjustments" section of the installation manual into
a one-page checklist with a tick box for each step. Keep the manual's order
and step numbers. Add the page number after each step. Do not add steps
that are not in the manual. At the end, state how many numbered steps the
manual has and how many your checklist has.The last line is the check. If the manual has 14 numbered steps and the checklist has 15, find the extra one and delete it. A tidy checklist with an invented step is worse than no checklist.
Comparing two spec sheets for a substitution
When a distributor offers an alternative unit, ask for a table of capacity, airflow, sound level, electrical data, dimensions and weight, one column per unit, a quote and page reference in every cell, and "not stated" where a sheet is silent. Then read the footnotes yourself. Ratings are given at stated test conditions, and two sheets can quote different conditions. A like-for-like comparison needs the same conditions, and an assistant will happily compare two numbers that were measured differently.
The instruction "if two files disagree, show both and do not choose" earns its place here. Here is the awkward case: the data sheet gives one airflow figure and the installation manual a lower one, each at a different external static pressure. With the instruction, the project returns both, each with a quote and a page, and the technician reads the conditions before deciding which applies. Without it, an assistant may quietly pick the larger number and say nothing about the other.
Parts lookup and supersession
Use the parts list to find the part number and the exploded-view page, and treat the result as a starting point. Parts get replaced by newer numbers, so confirm the number with your distributor against the model and serial number before ordering. The assistant is a fast index here, not the authority. It also helps to log the page you used in the warranty file, which is where HVAC warranty claims and failed-part evidence picks up.
Safety decisions stay with a qualified person
The tool can speed up finding a page. It does not make the call. A simple three-level rule keeps that straight:
| Level | Examples | What you do |
|---|---|---|
| Find a page | Fault code meaning, part numbers, which section covers start-up | Use the answer, then open the page for anything you will act on |
| Check a table | Clearances, electrical data, charge or pressure figures | Read the table row yourself and compare with the nameplate |
| Decide something safety-critical | Gas pressure and combustion settings, venting and flue arrangements, carbon monoxide readings, refrigerant handling limits, isolation and lock-out, pressure-test limits | Read the manual page, call the manufacturer's technical support if in doubt, and follow your training. The assistant is not part of the decision. |
The vendors say the same. Anthropic's own vision guide says to review and verify image interpretations carefully, especially for high-stakes uses, and not to rely on Claude for tasks needing perfect precision without human oversight. OpenAI's image-input guide says plainly that vision models can make mistakes, and its terms tell users not to treat output as a sole source of truth. Some equipment, such as units that use mildly flammable refrigerants, carries additional installation requirements in its instructions, and the page itself is what you follow, not a summary. The same rule is argued from the electrician's side in can ChatGPT answer code questions safely?
A ten-question test before you trust a project
Before a project goes to the team, run ten questions whose answers you already know from a manual you have used. Mix the types: fault codes, a clearance row, an electrical figure, a diagram, a part number, a commissioning step, a footnote. Record the page the tool gave and whether the quote was on the page.
| Question type | Expected page | Tool's page | Result |
|---|---|---|---|
| Fault code lookup | 41 | 41 | Right |
| Blower motor part number | 77 | 77 | Right |
| Clearance, left side, -048 | 12 | 12 | Right |
| Electrical data, -036 | 9 | 9 | Right |
| Start-up step 6 | 28 | 28 | Right |
| Control board terminal labels | 63 | None given | Wrong: diagram not read |
| Condensate drain requirement | 15 | 15 | Right |
| Electrical data, -060 | 9 | 9, but the -048 row | Wrong: neighbouring row |
| Footnote on rated conditions | 3 | 3 | Right |
| Question the manual does not answer | None | "Not stated in the files" | Right |
Eight out of ten. My reading of the result, and these thresholds are my own suggestion rather than a standard: nine or ten, use it for finding pages and still open them. Seven or eight, use it but fix the causes first. Six or fewer, stop and fix the files or change the tool. Here the two failures have clear causes. The diagram was in a PDF of more than 100 pages, so only its text was read, and the -060 mix-up came from an index note that never said which row belonged to which suffix. Split the diagrams out, add the suffix map to the index note, and re-run the test.
The last row is the negative test, and it matters most. Ask something the manual does not say, such as the recommended condensate trap height when the manual gives none. A good project answers "Not stated in the files". If it answers with a number, your instruction is not holding. Remember that "not stated" only means the tool did not find it. For anything that matters, search the PDF yourself before you conclude the manual is silent.
Mistakes that showed up, and what they looked like
These five are illustrations of the usual ways a manual project goes wrong, not reports of particular jobs.
- The wrong suffix. The manual covered units from -036 to -060, and the tool quoted a table row for -048 on a -036 job. The answer had no suffix in it. The instruction now requires the suffix copied from the row, and the technician checks it against the nameplate.
- General knowledge dressed as the manual. Asked about condensate trap height, the tool gave a figure "typical for this type of equipment" without saying the manual was silent. The "not stated" rule and the quote requirement fixed it. If there is no quote, there is no answer.
- Swapped units. A clearance came back in millimetres on a table printed in inches. The instruction now asks for the units as printed, and the index note states which system each manual uses.
- The superseded manual. Revision B was still in the project after revision D was published, and the answer cited revision B. Retire old revisions from the project, and put the revision in the file name.
- The page offset. The printed page and the PDF page differ by six. The technician typed the printed number into the PDF viewer and landed on the wrong page. Both numbers are in every answer now.
Setting it up in an afternoon, and what it saves
For a firm that services five or six equipment families, the first project takes about three hours and a bit more for each further family.
| Step | Time | Result |
|---|---|---|
| Download the manuals and bulletins for your five most-serviced families | 60 minutes | A folder of PDFs |
| Rename, split and pull the diagrams into their own files | 60 minutes | Files under 100 pages, with revisions in the names |
| Write the index note | 20 minutes | One text file |
| Create the project and paste the instruction block | 15 minutes | A working project |
| Run the ten-question test and fix the causes | 45 minutes | A scored test and a short fix list |
| Total | 200 minutes | About 3 hours 20 minutes |
On the savings side, take an illustrative six-technician firm in which each technician looks something up in a manual about five times a week. Finding the right PDF and the right page by hand takes about eight minutes. With the project it takes about three, including opening the page to check. That is 6 x 5 x (8 - 3) = 150 minutes a week, or 2 hours 30 minutes, which you can multiply by your own loaded labour cost. The cost side is about $20 a month for a personal plan, or $40 to $50 a month at the two-seat minimum of a team plan if you want sharing. Time your own technicians for a week before you believe my numbers.
Sharing with the team and keeping the project current
If several technicians will use the project, share one rather than letting everyone build their own. ChatGPT shares projects on every plan, and Claude shares only on Team and Enterprise (a Team plan starts at two seats). Use the same instruction block and the same files for everyone, and keep a short log with columns for date, question, page checked and who checked it. After a month the log tells you which questions are asked most, and those are the ones to turn into one-page cheat sheets.
Keep the library current. When a manufacturer publishes a bulletin or a revised manual, replace the old file the same day and note the change in the index. Once a quarter, re-run the ten-question test, because a changed file or a changed tool can quietly change the results. The routine is short, and it is the thing that turns "the AI told me" into "page 41 says". For the paperwork that follows the work, turning technician notes into an HVAC service report is the natural next step, and how accurate is Gemini Notebook? runs a similar citation check on Google's tool.
Questions HVAC contractors ask about AI and manuals
Is it all right to upload manufacturer manuals to an AI tool?
Most installation and service manuals are published for installers, but the terms differ. Read the download page, your dealer agreement and any confidentiality note on bulletins. Keep restricted documents out of shared workspaces unless the terms allow it, and never upload customer names, addresses or job records alongside manuals.
Will AI read a wiring diagram correctly?
Treat it as navigation, not as the answer. Anthropic's help page says Claude analyses visual elements in PDFs of up to 100 pages and reads text only in longer ones, and dense diagrams are exactly where image reading slips. Ask the tool which page the diagram is on, then read the diagram yourself.
What if the manual is a scan and I cannot select the text?
Run it through an OCR tool first, then check that you can select and search the text. Google's sources page does not mention scanned PDFs, and I would not assume any of the three tools reads one well, so test it: ask for a sentence you can see on a scanned page and see whether the tool finds it.
How do I keep answers consistent between technicians?
Use one shared project with the same instruction block and the same files, and keep a short log of questions with the page checked. ChatGPT shares projects on every plan, while Claude shares projects only on Team and Enterprise. If you cannot share, give each technician the same instruction text and file list.
Further reads
- Can AI Build a Gym Equipment Maintenance Checklist From Manuals? — The same manual-to-checklist method on other equipment.
- AI Estimating Software for HVAC: Replacement Quotes and Duct Takeoffs — Duct takeoff tools and replacement quote builders do different jobs. See what each does, what it misses, and how to test one on a finished duct job.
- HVAC Companies AI: What Warranty Paperwork Automation Costs — A monthly cost table for four ways to automate warranty registration and claims, with serial-number capture, a deadline tracker and claim wording.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Anthropic's help pages on uploading files and on Projects; Anthropic's vision guide; Google's Gemini Notebook help page on sources; OpenAI's help-centre pages on projects and file uploads, its image-input guide and its terms of use; ChatGPT and Claude pricing pages (October 2026). Manual excerpts and figures in the examples are invented for illustration and are not from any manufacturer.