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, your team reviews hundreds of submittals and logs dozens of RFIs. But without a clear, repeatable method to validate compliance, log questions, and track changes across evolving documents, you're relying on memory, spreadsheets, and tribal knowledge. One missed spec clause can trigger change orders. One untracked drawing revision invalidates your coordination. The work is drowning in PDFs, markups, and email threads. And no one owns the system.
Who this is for
Head of Preconstruction at a mid-sized general contractor or design-build firm. Responsible for ensuring submittals are accurate, RFIs are logged and resolved, and drawing revisions are tracked. Manages a team of coordinators, project engineers, and specifiers. Works across estimating, project management, and field operations. Owns the workflow from bid to handover.
Who this is not for
This is not for project managers who only handle one project at a time. Not for field superintendents focused on daily execution. Not for architects or consultants outside the preconstruction workflow. Not for companies that outsource all submittal management.
What you walk away with
- Diagnose exactly where your submittal review process breaks down
- Build a standardized RFI logging and tracking system
- Map drawing revisions to spec changes systematically
- Reduce rework caused by missed compliance items
- Create accountability across your preconstruction team
How this maps to your situation
- You're manually tracking submittals in spreadsheets
- RFIs are getting lost or taking too long to close
- Drawing revisions are not being tracked systematically
- Your team is repeating the same mistakes across projects
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. Most learners finish in 6-8 weeks.
How this compares to the alternatives
Unlike generic project management courses, this program focuses exclusively on the submittal and RFI lifecycle. Unlike software training, it teaches you how to assess and improve your current workflow—regardless of tools. Unlike consultant-led assessments, it gives you the framework to diagnose and act independently.
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 the submittal lifecycle from bid to closeout
- Identifying all required submittal types by trade
- Mapping submittal deadlines to construction schedule
- Understanding the role of spec sections in submittal prep
- How drawings and specs interact in submittal review
- Common reasons for submittal rejection and delay
- The difference between preliminary and final submittals
- How to track submittal status across multiple projects
- Integrating submittal timelines with estimating workflow
- The impact of delayed submittals on procurement
- Who approves submittals and when they must act
- Documenting submittal feedback for contractor response
- When to issue an RFI versus a submittal clarification
- Structuring an effective RFI with clear questions
- Creating a centralized RFI log with ownership
- Routing RFIs to architects, engineers, and subs
- Setting response time expectations for each party
- Tracking RFI status from issuance to resolution
- How unresolved RFIs delay submittal approval
- Integrating RFI outcomes into drawing updates
- Using RFI trends to improve bid assumptions
- Avoiding duplicate RFIs across project teams
- Documenting verbal clarifications in the RFI log
- Closing out RFIs with formal acknowledgment
- Breaking down spec sections by CSI division
- Identifying mandatory versus optional requirements
- How spec language overrides drawing details
- Using spec checklists for consistent review
- Cross-referencing product data against spec clauses
- Handling ambiguous language in technical sections
- Tracking spec revisions across project phases
- Linking spec requirements to submittal samples
- How to flag conflicts between specs and drawings
- Summarizing key compliance items for contractors
- Using spec notes to guide RFI questions
- Creating a master spec register for reuse
- Verifying drawing scales and sheet organization
- Checking for coordination between disciplines
- Identifying missing details in architectural drawings
- Validating structural notes against design intent
- Reviewing MEP drawings for service clearances
- Using layer visibility to assess drawing accuracy
- Detecting conflicting dimensions across sheets
- How to spot outdated drawing revisions
- Cross-checking detail callouts with master sheets
- Assessing drawing completeness for permitting
- Linking drawing notes to RFI documentation
- Using redline markups to communicate changes
- Understanding revision clouds and change tags
- Tracking revision sequences across drawing sets
- Documenting what changed between issuances
- How to verify all parties received updates
- Maintaining a master revision log for specs
- Using revision dates to validate submittal currency
- Avoiding work based on superseded drawings
- Integrating revision tracking with RFI closure
- Automating revision alerts across project teams
- Handling minor versus major drawing revisions
- Archiving old revisions without losing access
- Auditing revision compliance during QA checks
- Defining minimum content for each submittal type
- Organizing checklist items by spec section
- Including manufacturer certifications as a requirement
- Verifying submittal includes installation details
- Checking for compliance with project standards
- Validating product substitutions against spec
- Ensuring all required samples are included
- Reviewing test reports and performance data
- Flagging proprietary versus non-proprietary items
- Using checklists to train junior reviewers
- Customizing checklists by project complexity
- Integrating checklist results into approval workflow
- Identifying interfaces between mechanical and electrical
- Resolving conflicts in space allocation for ductwork
- Coordinating structural supports with architectural finish
- Aligning finish schedules across interior trades
- Managing lead times for integrated assemblies
- Creating joint review sessions for critical interfaces
- Documenting coordination decisions in meeting minutes
- Using RFI logs to track unresolved trade conflicts
- Assigning responsibility for interface resolution
- Integrating trade coordination into submittal approval
- Avoiding siloed reviews that miss system integration
- Using coordination checklists for recurring projects
- Defining clear approval criteria for each submittal
- Documenting rejection reasons with spec references
- Tracking resubmittal deadlines and expectations
- Using status codes to communicate decision outcomes
- Creating audit trails for client and consultant review
- Managing concurrent approvals across multiple parties
- Handling partial approvals with conditional acceptance
- Linking approval records to procurement decisions
- Using decision logs to improve future estimating
- Avoiding approval bottlenecks with escalation paths
- Storing approval records for project closeout
- Integrating approval history into quality assurance
- Mapping submittal approval to purchase order release
- Identifying long-lead items during preconstruction
- Using approved submittals to lock in pricing
- Coordinating submittal review with bid buyout
- Tracking manufacturer lead times in master schedule
- Avoiding procurement delays due to pending submittals
- Using submittal status to update material delivery dates
- Managing substitutions that impact procurement
- Linking submittal data to purchase order terms
- Creating procurement hold points for critical items
- Updating buyout logs with submittal completion
- Using submittal history to negotiate with vendors
- Creating a pre-submittal internal review checklist
- Assigning QA roles to non-original reviewers
- Using peer review to catch missed spec clauses
- Validating drawing markups before submission
- Checking for consistent formatting and labeling
- Ensuring all required attachments are included
- Reviewing submittal narratives for clarity
- Auditing past submittals for recurring errors
- Using QA findings to update team training
- Measuring QA effectiveness with defect rates
- Integrating QA into project closeout documentation
- Building a QA feedback loop for continuous improvement
- Identifying when field changes require new submittals
- Documenting field modifications with supporting photos
- Issuing RFIs for unanticipated site conditions
- Linking change orders to original scope gaps
- Updating spec references after field adjustments
- Requiring contractor justification for deviations
- Tracking approved modifications in master log
- Using as-built drawings to reflect field changes
- Reconciling field changes with original submittals
- Avoiding undocumented changes that impact warranty
- Integrating change management into closeout package
- Using change history to refine future estimates
- Creating a master submittal log for portfolio tracking
- Standardizing RFI templates across project types
- Developing tiered review processes by project size
- Training regional teams on central workflows
- Using past project data to forecast submittal load
- Building a shared spec and drawing library
- Implementing cross-project QA audits
- Centralizing approval delegation with clear rules
- Managing resource allocation during peak submittal periods
- Using dashboards to monitor team performance
- Documenting lessons learned for future projects
- Creating a continuous improvement cycle for processes
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.