The Executive Diagnostic and Governance Toolkit
Mastering Submittals and RFIs for Preconstruction Leaders
Score your own function red, amber or green, find out which part is weakest, and walk into the next budget round able to defend what you want to fix. Built for leaders reviewing reading specifications and drawings to check submittals, logging RFIs, tracking changes across PDFs.
Each order is checked and updated against the latest insights before delivery. That is why access takes up to 24 hours rather than being instant.
| 1 |
You stop guessing where you stand. You finish with a score, not an opinion: every part of your function rated red, amber or green, with the weakest ranked first. Evidence: a Quick Scan for the shape of it, then seven domain assessments of 30 scored questions each, 210 in all, rolled into one scorecard, plus a maturity radar and a current-versus-target gap analysis. |
| 2 |
You can defend the decision. You walk into the budget round with the gap named, the owner named and done defined, instead of a case built on instinct. Evidence: project charter, scope statement, RACI, requirements traceability and work breakdown structure, pre-filled in your domain's language. |
| 3 |
The work actually moves. The month after the decision is already built, so nothing stalls waiting for someone to design a form. Evidence: more than 60 project templates across all five PMBOK process groups, plus runbooks, SOPs, a KPI framework, audit checklists and a risk matrix. 55 to 65 files in total. |
| 4 |
You use it the day it lands. No blank templates to interpret. Every workbook opens with what it is, who uses it, when, how, a 1 to 5 scoring guide, what good looks like, and a worked example you delete and type over. |
The situation this is built for
Every project cycle, you face the same pattern. Specifications are updated but not flagged. Drawings evolve across versions with no change tracking. Submittals arrive with incomplete data, and your team spends hours cross-checking instead of validating. RFIs go unanswered for days, delaying schedules. You’re expected to guarantee compliance, yet the tools at hand make traceability manual and error-prone. The cost isn’t just time—it’s risk accepted silently, change orders missed, and credibility eroded when issues surface downstream.
Who this is for
Head of Preconstruction at a mid to large-sized general contractor or design-build firm, managing multiple concurrent projects and overseeing teams responsible for submittal review, specification compliance, and RFI generation. You report to executive leadership and are measured on bid accuracy, preconstruction timelines, and risk mitigation.
Who this is not for
This is not for project coordinators doing data entry, field superintendents managing daily logs, or subcontractors submitting documents. It is not for executives seeking high-level strategy without operational depth.
What you walk away with
- Audit your current submittal review process with precision
- Map RFI workflows to eliminate response delays
- Track specification changes across project phases
- Integrate drawing revisions into compliance checks
- Build a repeatable framework for preconstruction validation
How this maps to your situation
- You inherit inconsistent submittal practices across projects
- Your team spends more time chasing documents than reviewing them
- Specifications and drawings evolve without synchronized tracking
- Leadership demands visibility into preconstruction risk
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 3 hours per module, designed to be completed alongside active project work. Total investment: 36 hours over 12 weeks with flexible pacing.
How this compares to the alternatives
Unlike generic project management courses, this program focuses exclusively on the technical workflows of submittals and RFIs. It does not teach software tools but instead strengthens the underlying processes that any tool must support. Compared to on-the-job learning, it provides a structured, auditable method to elevate team performance systematically.
Also included: the full course, for when you want the reasoning behind a finding (12 modules, 144 chapters)
Depth reference. The diagnostic and the templates stand on their own; this is what to read when you want the reasoning behind a finding.
- Defining submittals in the context of preconstruction
- Mapping the journey from request to approval
- Identifying key stakeholders in submittal review
- Differentiating between shop drawings and product data
- Recognizing the role of specifications in submittal validation
- Understanding when submittals trigger RFIs
- Classifying submittal types by trade and complexity
- Reviewing submittal timelines in the master schedule
- Establishing thresholds for internal pre-review
- Documenting submittal transmittal requirements
- Linking submittals to procurement milestones
- Assessing common gaps in submittal completeness
- Navigating specification divisions and sections
- Extracting performance criteria from technical specs
- Identifying required submittals in Section 01
- Tracking manufacturer and model number requirements
- Highlighting compliance language like 'shall' and 'must'
- Cross-referencing specs with master specification libraries
- Validating third-party certifications in submittals
- Checking for required test reports and warranties
- Using checklists to ensure spec completeness
- Flagging deviations from specified products
- Documenting spec interpretation decisions
- Maintaining a spec deviation log for audit trails
- Understanding drawing revision clouds and legends
- Matching submittal details to sheet-specific notes
- Tracking drawing issue dates across transmittals
- Verifying scale and dimension compliance
- Checking for coordination between disciplines
- Identifying conflicts between drawings and specs
- Using layer visibility to assess drawing completeness
- Validating structural and MEP interfaces
- Confirming architectural alignment with shop drawings
- Documenting drawing discrepancies in review logs
- Integrating drawing markups into team workflows
- Creating a centralized drawing revision tracker
- Determining when to issue an RFI versus a submittal
- Crafting clear and concise RFI descriptions
- Identifying responsible parties for RFI responses
- Setting internal deadlines for RFI generation
- Prioritizing RFIs by schedule impact
- Including supporting drawings and spec excerpts
- Avoiding duplicate RFIs through log management
- Using RFI templates to standardize formatting
- Tracking RFI status across multiple projects
- Managing client and consultant response timelines
- Integrating RFI outcomes into submittal updates
- Archiving resolved RFIs for future reference
- Designing a master submittal log template
- Including fields for spec section and drawing reference
- Assigning responsibility by trade and project phase
- Setting internal review deadlines ahead of due dates
- Tracking submittal status with color-coded indicators
- Linking submittals to RFI resolution status
- Updating logs for resubmittals and revisions
- Generating weekly submittal status reports
- Integrating submittal logs with scheduling tools
- Auditing log accuracy during project milestones
- Using filters to isolate high-risk submittals
- Exporting log data for executive summaries
- Identifying change sources in design development
- Monitoring addenda and revision transmittals
- Assessing impact of drawing changes on submittals
- Evaluating specification updates for compliance
- Documenting change decisions in meeting minutes
- Notifying trade partners of required resubmittals
- Updating submittal logs to reflect change orders
- Linking change notices to RFI responses
- Maintaining a change impact register
- Validating that revised submittals address changes
- Archiving obsolete submittal versions securely
- Reporting change-driven delays to leadership
- Scheduling coordination meetings with trade partners
- Sharing submittal review timelines across teams
- Resolving conflicts between mechanical and architectural drawings
- Facilitating joint review of integrated systems
- Using RFI responses to align cross-trade assumptions
- Coordinating specification interpretations
- Managing interface requirements between vendors
- Documenting coordination decisions in writing
- Tracking action items from interdisciplinary meetings
- Integrating coordination outcomes into submittals
- Escalating unresolved coordination issues
- Measuring coordination effectiveness over time
- Defining roles in the internal review process
- Setting up review cycles by discipline
- Using digital markup tools consistently
- Creating standardized comment codes
- Consolidating feedback from multiple reviewers
- Holding internal pre-review meetings
- Documenting resolution of internal comments
- Setting escalation paths for unresolved issues
- Timing internal reviews to meet external deadlines
- Integrating legal and risk review into submittals
- Training junior staff on review expectations
- Auditing internal review quality monthly
- Cross-walking submittals against spec checklists
- Validating product data sheets for completeness
- Checking for required third-party listings
- Confirming code compliance by jurisdiction
- Reviewing fire rating documentation
- Verifying sustainability certifications
- Assessing accessibility requirements in details
- Evaluating material safety data sheets
- Confirming local code amendments are addressed
- Using checklists to close compliance gaps
- Documenting compliance exceptions formally
- Preparing compliance summaries for clients
- Assessing current reliance on manual PDF reviews
- Identifying pain points in file version control
- Evaluating cloud-based document sharing options
- Using metadata to organize submittal packages
- Implementing consistent file naming conventions
- Leveraging search functions for spec clauses
- Integrating drawing viewers with comment tracking
- Adopting structured data fields for submittals
- Connecting submittal logs to project management tools
- Ensuring mobile access for field coordination
- Training teams on digital review protocols
- Measuring time saved after tool adoption
- Defining lead time for submittal review cycles
- Tracking RFI response turnaround times
- Measuring percentage of complete initial submittals
- Calculating rework rates due to non-compliance
- Monitoring on-time submittal delivery rates
- Analyzing RFI volume by trade and cause
- Benchmarking against project schedule milestones
- Creating dashboards for leadership reporting
- Using data to identify training needs
- Auditing log accuracy quarterly
- Correlating submittal delays with cost impacts
- Reporting process improvements over time
- Documenting standard operating procedures
- Creating a master template library
- Onboarding new team members systematically
- Conducting post-project process reviews
- Updating playbooks based on lessons learned
- Scaling workflows across multiple projects
- Integrating feedback from project teams
- Aligning submittal practices with estimating
- Ensuring continuity across project phases
- Maintaining institutional knowledge in databases
- Standardizing training for consistency
- Evolving the system with new project types
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.
Thousands of organisations have bought from The Art of Service since 2000.