Zurück zur Bibliothek

Submittal package review

Checks a construction submittal package against the governing specification, drawings, and register, then produces a cited review record and deviation list. Use for material submittals, equipment data, shop drawings, samples, compliance packages, and approval preparation.

von adlass TemplatesVersion 1Nutzt adlass-ToolsUniversell

Veröffentlicht 21. Aug. 2026 · Aktualisiert 26. Aug. 2026

Hilfreich · 0Rohes SKILL.md ansehen

Voraussetzungen

Add the project specification, drawing index, and review status vocabulary. Define which roles may make technical approval recommendations. Set the citation convention for drawing sheets, details, and specification clauses. Add project-specific turnaround or escalation rules.

Skill-Dokument

Das vollständige SKILL.md, das dein Agent liest und befolgt.

Submittal package review

Purpose

Determine whether a submittal contains the required evidence and conforms to the project requirements before approval.

Scope

Construction material, equipment, product-data, sample, and shop-drawing submittals. Excluded: engineering design certification, approval communication, and physical inspection.

Data basis

  • Submittal package, specification section, drawings, addenda, project requirements, and submittal register.
  • The fixed records, tables, or folders in the skill scope that hold the relevant history or schema.

Result

A review memorandum, deviation sheet, and register update with status recommendation, citations, and unresolved evidence gaps.

Quality criteria

  • Every requirement is marked met, unmet, unclear, or not applicable.
  • Every deviation cites the submittal page and the governing requirement.
  • The recommendation is one of approved, approved with comments, revise and resubmit, or rejected.
  • The review distinguishes missing evidence from technical nonconformance.
  • The register row matches the review memorandum.

Instructions

Start with the requirements applicable to the submitted scope, including referenced standards and required certifications. Compare dimensions, materials, ratings, interfaces, finishes, and installation constraints exactly where stated. Do not invent acceptance criteria. Record conflicts between drawings and specifications as separate issues. Treat an absent required document as a finding, not as compliance.

Adapt before use

Keep the source trail close to every conclusion and preserve the difference between a source fact, a calculated value, an assumption, and a recommendation. Use stable identifiers across the document and sheet so a reviewer can move from a summary statement to the underlying row and source. Prefer a complete, transparent partial result over a confident answer built on missing evidence.

  • Add the project specification, drawing index, and review status vocabulary.
  • Define which roles may make technical approval recommendations.
  • Set the citation convention for drawing sheets, details, and specification clauses.
  • Add project-specific turnaround or escalation rules.

Verwandte Skills

  • 8D problem-solving report

    Builds a traceable 8D problem-solving report from a manufacturing complaint, defect record, and process evidence. Use for customer complaints, recurring production defects, containment records, corrective action reports, and structured root-cause investigations.

  • Capacity resource plan

    Converts demand forecasts, staffing calendars, work hours, absences, and throughput assumptions into a capacity plan with bottleneck dates and quantified staffing options. Use for workforce capacity planning, resource allocation, utilization review, and delivery-load analysis.

  • Construction punch list

    Converts inspection notes, photos, room data, and project requirements into a prioritized construction punch list with trade grouping and verification fields. Use for substantial completion, handover inspections, snagging, closeout walks, and defect follow-up.

  • Construction RFI draft

    Converts a construction field question or document conflict into a precise request for information with evidence, options, and schedule or cost implications. Use for RFIs, design clarifications, plan conflicts, specification gaps, and field coordination questions.