What supported file handling should look like in estimating software
Estimating software should handle the file types estimators actually work with: PDF drawings, CAD exports, images, spreadsheets, text specifications, and native office files. Unsupported or unreadable file types should be flagged explicitly rather than ignored silently.
Quick answer: what file types should estimating software support?
Estimating software should support the RFQ file types estimators actually receive: PDF drawings, DXF and DWG CAD exports, STEP and IGES models, images, spreadsheets, text specifications, office documents, and compressed RFQ bundles. Just as important, unsupported or unreadable files must stay visible as issues so scope is not missed during pricing.
Visual brief
file format support table showing common RFQ file types and their handling status
The best file-handling workflow does three things: opens common formats in the project workspace, preserves source evidence for every extracted item, and clearly flags anything skipped, unreadable, encrypted, corrupted, or externally reviewed. That protects the estimator from assuming the file set was fully processed when it was not.
For the broader intake workflow around file completeness, see the RFQ intake checklist for fabrication estimating. For file organisation before estimating, see how to organise RFQ files before estimating.
What file types estimators actually work with
Estimators in fabrication and construction-adjacent work handle a mixed file set on every RFQ. PDF drawings are the most common format for scope definition and dimensional references. CAD exports such as DXF, DWG, and STEP files carry geometry that can be measured, counted, or nested.
Images are used for markups, site photos, reference conditions, and quality notes. Spreadsheets hold bills of quantities, material schedules, and commercial summary sheets. Text specifications and native office documents such as Word files contain scope descriptions, coating schedules, and commercial terms.
An estimating platform that supports all these formats inline within the project workspace saves the estimator from switching between separate viewers, import tools, and folder structures. The file handling contract should cover PDF, DXF, DWG, STEP, IGES, common image formats, and office documents.
What happens when file types are not supported
Not every RFQ file fits neatly into supported formats. Proprietary CAD formats, compressed archives, scanned handwritten notes, or encrypted documents may be unreadable by the estimating software. The key requirement is that unsupported or unreadable files are flagged explicitly rather than skipped silently.
If a file is not processed but contains scope information, the estimator needs to know. A skipped file marker in the project workspace tells the estimator to review that file separately before the quote goes out. Unsupported file types that contain pricing or scope data create hidden risks if they are not accounted for.
For each unsupported file, the estimator should have the option to add a manual note, flag it for clarification, or attach it to the project as a reference that was reviewed externally. The project file register should track which files were processed, which were skipped, and why.
Supported file formats for fabrication and industrial estimating
| File type | Common use in RFQs | Support requirement | AI preprocessing capability |
|---|---|---|---|
| Drawings, specifications, schedules, scope notes | View, measure, annotate, extract text and tables | Text and table extraction, revision comparison | |
| DXF / DWG | CAD geometry, part outlines, nesting layouts | View, measure, count parts | Geometry extraction for quantity counts |
| STEP / IGES | 3D models, solid models, assembly references | View, rotate, inspect | Limited; geometry extraction on supported platforms |
| Images (PNG, JPG, TIFF) | Markups, site photos, reference conditions | View, annotate, compare | Raster analysis, OCR for text in images |
| Spreadsheets (XLSX, CSV) | Bills of quantities, material schedules | Import data, link to estimate rows | Table extraction, quantity mapping |
| Office docs (DOCX, TXT) | Specifications, scope descriptions, commercial terms | View, search, extract references | Text extraction for clarification drafting |
| Archives (ZIP, RAR) | Compressed RFQ file bundles | Extract and identify supported file types | Structure identification only |
The specific support level for each format depends on the platform. The core principle is that unsupported or unreadable files are surfaced as issues rather than disappearing into the project folder.
How AI preprocessing handles different file types
AI preprocessing can extract text from PDFs, identify drawing numbers and revision letters, compare document versions, and draft a first-pass clarification list. For images, OCR can read embedded text from scanned drawings or marked-up photographs.
For CAD-derived formats, AI preprocessing is more limited. A DXF file can be processed to identify part geometry and area, but the model cannot interpret fabrication intent, weld symbols, or coating notes in the same way a human can. The AI draft should include a confidence flag for each extraction so the estimator knows which numbers came from direct extraction versus model inference.
The same boundary applies to all formats: AI assists with extraction and grouping, but the estimator reviews every line item against the source document before it reaches the customer quote. For the review model, see why AI estimating should assist, not replace estimators and what local-first estimating software changes for sensitive RFQ data.
The file support contract: why it should live in one place
File type support tends to drift when it is documented in multiple places. The frontend may show a file picker with one filter, the service layer may handle a different set, and the documentation may describe a third. For estimating teams, this creates confusion about what files can be processed and what will be skipped.
The solution is a single file support contract that defines every supported and unsupported format, how each is handled, and what happens when an unsupported file is encountered. That contract lives in the source code and documentation so components, state, and services all reference the same definition.
For a practical RFQ file handling workflow that covers intake through supported file review, see the RFQ intake checklist for fabrication estimating.
Unreadable file escalation workflow
Visual brief
unreadable file escalation workflow showing skipped file, manual review, clarification, assumption, and quote review
When a file is unreadable, the workflow should not stop silently. Mark the file as unsupported, unreadable, encrypted, corrupted, or externally reviewed. Then decide whether it is scope-critical. A corrupted site photo might be low impact. A locked specification or missing CAD assembly can be quote-critical and should trigger clarification before pricing proceeds.
| File issue | Estimator action | Quote impact |
|---|---|---|
| Unsupported format | Open externally or request alternate format | Log as externally reviewed or unresolved |
| Corrupted file | Request replacement | Hold pricing if scope-critical |
| Encrypted document | Ask customer for access or unlocked copy | Do not assume content |
| Poor scan | Use manual review and OCR with caution | Keep confidence low and flag evidence |
| Missing CAD dependency | Check PDF equivalent; request missing part files | Do not rely on incomplete model |
Examples by trade and RFQ package type
Structural steel RFQ: the estimator may receive GA drawings as PDFs, connection details as PDFs, a member schedule in Excel, and model exports in STEP or IFC-adjacent formats. The file-handling workflow should keep the drawing register, member schedule, and model references linked so a changed drawing can be traced to affected quantities.
Sheet metal RFQ: the estimator may receive DXF files for cutting, PDFs for folded part drawings, photos for finish references, and emails describing hardware or packaging. The software should keep geometry files and customer notes together so the estimator does not price parts without finish or hardware context.
Subcontract package: the file set may include specifications, addenda, supplier quotes, marked-up PDFs, and compressed attachments. Unsupported archives or encrypted specs should be visible issues because they can contain scope, compliance, or commercial terms that affect the quote.
Buyer checklist for file-handling capability
Visual brief
estimating software buyer checklist showing supported formats, skipped-file handling, source links, and local data controls
When evaluating estimating software, ask vendors to process a real RFQ pack rather than a clean demo folder. Include a mixed set of PDFs, CAD, spreadsheets, images, office documents, poor scans, duplicate files, and unsupported formats. The goal is to see what the tool does when the file set is messy, because real RFQs are messy.
| Buyer question | Why it matters |
|---|---|
| Which formats are supported natively? | Avoids surprise gaps during intake |
| How are unsupported files shown? | Prevents silent skipped scope |
| Are source links preserved? | Reviewers need proof for each estimate line |
| Can files be reviewed locally? | Sensitive drawings and pricing may need local control |
| Does AI output show confidence? | Low-confidence extraction needs review |
| Can estimators override or annotate file issues? | Human review must stay in the workflow |
| Can the tool handle duplicate revisions? | File handling and revision control are connected |
Strong file handling is a prerequisite for RFQ processing software before pricing. If the system cannot clearly show which files were processed and which were skipped, it is not ready to support automated intake or AI-assisted extraction.
FAQ
What file types should estimating software support?
PDF, DXF, DWG, STEP, images, spreadsheets, text files, and office documents. Unsupported formats should be flagged.
What happens when a file type is not supported?
The file should be marked as unsupported with a clear indicator. The estimator can still add a manual note or attach it as a reference.
Can AI read CAD files for estimating?
AI can extract geometry and quantities from some CAD formats but cannot interpret fabrication intent, weld symbols, or coating notes. Human review is essential.
Why does file format support matter for estimating?
Missing file support means scope information can be hidden in unprocessed files, creating pricing risks that are hard to catch before the quote goes out.
How should unreadable RFQ files be handled?
Classify the issue, decide whether it is scope-critical, request replacement if needed, and keep the file visible in quote review.
How should file handling be documented?
In a single support contract that defines every format, how it is handled, and what happens when a format is not supported.
Ways estimators can keep quote review clear:
- Estimating software should support the file formats estimators actually receive: PDF, DXF, DWG, STEP, images, spreadsheets, and text documents. Missing formats must be flagged explicitly.
- Unsupported or unreadable files should be marked as issues, not ignored. Skipped files that contain scope information create hidden pricing risks.
- AI preprocessing can help extract information from supported formats, but the estimate should still show which source file each line item came from.
- File handling contracts should be documented in one place so components, state, and services stay consistent about what is supported and what is not.
