Skip to main content

S_00008 — Reviewed document takeoff into structured opportunities

This solution addresses P_00009; the problem owns the forward reference in its ordered solutionsIds array.

kind: solution_catalog
schema_version: 1
solutions:
  - id: S_00008
    proofIds: []
    priority: 60
    name: 'Reviewed document takeoff into structured opportunities'
    status: approved
    mechanism: >-
      Import project listings from a connected project source, retain the
      associated plans and specifications on the commercial record, and apply
      customer-configured document extraction and matching rules to identify the
      relevant material, quantity, unit of measure, specification, and location.
      Present the extracted information for staff review and correction before
      saving confirmed values as structured lead or Opportunity data. Use the
      confirmed relevant quantity, rather than total project value, as the basis
      for sizing and comparing opportunities.
    capabilities:
      - name: 'Import project leads from ConstructConnect into the sales pipeline'
        classification: integrated
        conditions:
          - "Requires authorized access to the customer's ConstructConnect feed."
          - 'The source must provide an FTP file compatible with the implemented import path.'
          - 'The observed hook documentation states that it parses the feed and identifies leads; its production coverage was not verified.'
          - 'Integration availability, licensing, source-file coverage, and implementation effort must be confirmed before recommendation.'
        evidence_ids: []
      - name: 'Attach project plans, specifications, scopes, and drawings to lead and Opportunity records'
        classification: native
        conditions:
          - 'The source documents must be available for upload or retrieval.'
          - 'Attaching a document retains it on the record but does not itself interpret or validate it.'
          - 'The ConstructConnect import was not verified to retrieve every required source document.'
        evidence_ids: []
      - name: 'Extract and match relevant material, quantity, unit, specification, and location from project documents'
        classification: configured
        conditions:
          - 'The customer must define which material is commercially relevant and how its applicable quantity is calculated.'
          - 'Representative documents and manually verified takeoffs are required to configure and test extraction.'
          - 'Terminology and units must be mapped to maintained product, variant, packaging, and unit-of-measure records.'
          - 'Missing, ambiguous, conflicting, or low-confidence values must be routed to staff review.'
          - 'A configured project-document extraction hook and field mappings are required.'
          - 'An analogous PDF/image OCR and matching hook was observed, but no dedicated plan-or-specification-to-Opportunity implementation was verified.'
          - 'Configuration and testing effort cannot be sized before the document population and takeoff rules are inspected.'
        evidence_ids: []
      - name: 'Review and correct generated notes and structured opportunity information'
        classification: native
        conditions:
          - 'A staff member must compare extracted values with the source documents before treating them as confirmed.'
          - 'The source documents must remain attached or otherwise traceable from the reviewed record.'
          - 'The observed interface supports editable AI-generated lead notes and editable Opportunity fields; no dedicated confidence-scored takeoff review interface was verified.'
        evidence_ids: []
      - name: 'Store reviewed material quantity, unit of measure, location, source, and attachments on an Opportunity'
        classification: native
        conditions:
          - 'The reviewed material must resolve to maintained product and unit-of-measure data where structured matching is required.'
          - 'Specification details that do not map to existing product, variant, packaging, or address fields require configured fields or must remain in notes and attachments.'
          - 'Only reviewed values should be used for commercial sizing or comparison.'
        evidence_ids: []
    expected_outcome_hypotheses:
      - 'A representative project can enter the commercial record with a reviewed relevant material quantity rather than only a headline project value.'
      - 'Opportunities with reviewed quantities can be filtered and aggregated using relevant product demand rather than total project value.'
      - 'The source documents and the reviewed quantity can remain traceable from the same lead or Opportunity workflow.'
      - 'Missing, ambiguous, or conflicting document information can be identified for review instead of being silently accepted.'
      - 'Geographic and specification analysis can begin when the required location and specification fields have been reviewed and structured.'
    limitations:
      - 'No dedicated project-plan-or-specification-to-Opportunity takeoff workflow was verified in MCP server d8189168.'
      - 'The observed OCR and AI extraction implementation parses vendor price lists; it does not establish reliable plan takeoff.'
      - 'Scaled drawing measurement, geometry interpretation, detail-reference traversal, and reconciliation across document revisions were not verified.'
      - 'The ConstructConnect import was not verified to retrieve every plan, specification, scope, or drawing required for takeoff.'
      - 'No dedicated specification or specifier field was verified on the Opportunity; additional field configuration may be required.'
      - 'Opportunity AI search and retrieval-augmented generation are disabled in the observed document configuration.'
      - 'Extraction accuracy, coverage, review effort, source integration effort, and the proportion of projects that can be sized are not established.'
      - 'Documents that omit dimensions, contain poor scans, conflict across revisions, or require specialist interpretation may not support a reliable automated takeoff.'
      - 'Human verification remains necessary before extracted quantities are used commercially.'
    prohibited_claims:
      - 'That every plan, specification, scope, or drawing can be interpreted automatically.'
      - 'That project-document takeoff into Opportunities is a verified native capability.'
      - 'That the ConstructConnect integration supplies every document needed for takeoff.'
      - 'That extracted quantities, specifications, or locations are accurate without comparison to verified takeoffs.'
      - 'That scaled drawing measurement or geometry-based takeoff has been verified.'
      - 'That this mechanism removes human review or specialist takeoff judgment.'
      - 'That total project value predicts the relevant product opportunity.'
      - 'That geographic or specifier analysis is automatic without the required reviewed fields.'
      - 'Any quantified revenue, coverage, accuracy, throughput, or labor improvement.'

Outstanding​

  1. proofIds is empty. Run W7 after at least one eligible evidence record exists.
  2. Every capability has evidence_ids: []. The implementation checks from MCP server d8189168 are deployment-specific observations, not canonical evidence records. Route formal product evidence through W9.
  3. Product implementation verification is partial. A dedicated project-document takeoff flow into Opportunity records was not verified.
  4. Configured effort is unknown. Inspect representative project documents, manually verified takeoffs, and the customer's product and unit data before estimating extraction and matching work.
  5. Priority 60 is approved for this draft only. Revisit it when the related problem has an approved priority and the solution catalog is ordered against current sales priorities.