What is the Submittals and RFIs for Preconstruction course about?
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.
What does the Submittals and RFIs for Preconstruction cover on the situation this is built for?
Every day, your team reviews hundreds of pages of specifications and drawings. A missed clause in Division 09 means a wrong finish gets approved. An overlooked note on Sheet A-403 triggers an RFI flood. You log RFIs across spreadsheets, PDFs, and emails, but tracking responses and changes is manual and error-prone. When drawings update, you have no system to confirm revised submittals.
Who is the Submittals and RFIs for Preconstruction course for?
Head of Preconstruction at a mid-sized general contractor or specialty trade contractor managing $50M+ in annual volume. You lead a team of estimators, project engineers, and specification reviewers. You report to the COO or Director of Operations. You are accountable for submittal accuracy, RFI resolution speed, and design compliance before construction begins.
Who is the Submittals and RFIs for Preconstruction course not for?
This is not for field superintendents focused on daily build execution, junior document controllers, or software salespeople. It is designed for leaders who own the technical integrity of preconstruction deliverables.
What do you take away from the Submittals and RFIs for Preconstruction course?
Confidently audit submittal review workflows across your team Map every RFI to a specific specification section and drawing Detect missing or conflicting requirements before submission Reduce RFI resolution time through structured tracking Build a defensible record of design compliance.
How does this map to your situation?
Recognizing when specifications conflict with drawings Managing submittal timelines under compressed schedules Coordinating multiple stakeholders in RFI resolution Maintaining accuracy across high-volume submittal cycles.
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.
What does the Submittals and RFIs for Preconstruction cover on delivery and format?
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 at your pace over 8 to 12 weeks.
Closely related courses: Submittals and RFIs in Preconstruction, Construction Submittals and RFIs for Project Leaders.
More answers: what you get with every course, refund policy, all help answers.
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 day, your team reviews hundreds of pages of specifications and drawings. A missed clause in Division 09 means a wrong finish gets approved. An overlooked note on Sheet A-403 triggers an RFI flood. You log RFIs across spreadsheets, PDFs, and emails, but tracking responses and changes is manual and error-prone. When drawings update, you have no system to confirm revised submittals reflect the latest version. The pressure mounts as deadlines approach and stakeholders demand answers. You need a repeatable method to validate, track, and defend every submittal and RFI decision.
Who this is for
Head of Preconstruction at a mid-sized general contractor or specialty trade contractor managing $50M+ in annual volume. You lead a team of estimators, project engineers, and specification reviewers. You report to the COO or Director of Operations. You are accountable for submittal accuracy, RFI resolution speed, and design compliance before construction begins.
Who this is not for
This is not for field superintendents focused on daily build execution, junior document controllers, or software salespeople. It is designed for leaders who own the technical integrity of preconstruction deliverables.
What you walk away with
- Confidently audit submittal review workflows across your team
- Map every RFI to a specific specification section and drawing
- Detect missing or conflicting requirements before submission
- Reduce RFI resolution time through structured tracking
- Build a defensible record of design compliance
How this maps to your situation
- Recognizing when specifications conflict with drawings
- Managing submittal timelines under compressed schedules
- Coordinating multiple stakeholders in RFI resolution
- Maintaining accuracy across high-volume submittal cycles
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 at your pace over 8 to 12 weeks.
How this compares to the alternatives
Unlike generic project management courses, this program focuses exclusively on the technical rigor of submittals and RFIs. It does not teach software use but instead strengthens the judgment, process, and documentation practices that make tools effective.
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.
- Understanding the legal weight of specification language
- Identifying required submittals in Division 01
- How drawing notes trigger submittal requirements
- The difference between shop drawings and product data
- Recognizing when submittals require engineering stamps
- Mapping submittal deadlines to the master schedule
- Defining ownership of submittal preparation in your team
- How specification sections dictate review criteria
- Using submittal logs to track responsibility and status
- The role of the architect in submittal approval
- Common mistakes in interpreting submittal requirements
- Building a checklist for initial submittal screening
- Reading specification sections in three layers
- How to parse technical requirements in Division 09
- Identifying performance vs. prescriptive criteria
- Extracting finish schedules from specification tables
- Tracking referenced standards like ASTM and AISC
- Using section headers to locate critical clauses
- How to handle ambiguous language in specs
- Cross-referencing specifications with drawing callouts
- Validating substitutions against specification intent
- The impact of master specification templates on review
- Documenting interpretation decisions for audit
- Creating a spec highlight library for your team
- Finding submittal notes in sheet legends
- Interpreting clouded revisions for updated requirements
- How detail callouts imply submittal content
- Recognizing when schedules require submittals
- Using elevation drawings to verify finish alignment
- Tracking submittal implications across drawing sets
- How structural notes affect mechanical submittals
- Identifying concealed work requiring pre-installation data
- Validating dimensions against submittal scope
- Using plan notes to confirm assembly methods
- Detecting conflicts between drawing and spec language
- Building a drawing annotation system for review
- Defining roles in the internal review cycle
- Setting review timelines based on submittal type
- Creating a tiered review process for complexity
- How to use redline markup effectively
- Documenting discrepancies between submittal and spec
- Using version control for internal drafts
- Integrating engineering review into the workflow
- Establishing escalation paths for unresolved issues
- Tracking reviewer comments and resolutions
- Validating coordination with other trades
- Preparing internal review summaries for submission
- Archiving completed reviews for future reference
- When to issue an RFI versus making an assumption
- Structuring RFI questions for quick response
- Attaching correct drawing references and spec sections
- Avoiding questions that reveal poor preparation
- Using RFIs to confirm design intent gaps
- How to escalate time-sensitive RFIs
- Maintaining a central RFI register
- Tracking RFI status across multiple projects
- Assigning ownership for RFI follow-up
- Documenting verbal clarifications in writing
- Measuring RFI turnaround time by discipline
- Using RFI patterns to improve future estimates
- Understanding revision cloud conventions
- Comparing drawing sets across issue dates
- Using layer visibility to isolate changes
- Tracking specification updates in transmittals
- How to log changes in a revision tracker
- Validating that submittals reflect latest revisions
- Communicating changes to project stakeholders
- Updating internal checklists after revisions
- Using color coding to highlight revised sections
- Requiring confirmation of change awareness
- Auditing submittal updates after design changes
- Preventing obsolete information from being submitted
- How specification changes impact material costs
- Identifying high-risk items during takeoff
- Using submittal history to refine estimates
- Flagging proprietary products in the bid
- Tracking alternate pricing in submittal review
- Aligning estimate line items with submittal scope
- Documenting assumptions based on spec gaps
- Using RFI outcomes to adjust pricing
- Sharing submittal risks with estimating team
- Updating cost models after submittal feedback
- Building spec compliance into bid validation
- Reducing contingencies through early clarity
- Defining submittal expectations in subcontract agreements
- Reviewing subcontractor submittal schedules
- Validating scope alignment with contract documents
- Tracking subcontractor RFI responsibilities
- Enforcing format standards for submitted documents
- Using subcontractor submittal performance in evaluations
- Managing multiple subcontractor submittals in one log
- Coordinating review cycles with prime submittals
- Handling late or incomplete subcontractor submissions
- Providing feedback without assuming design responsibility
- Clarifying approval versus acceptance
- Documenting follow-up actions for non-compliance
- Organizing submittal packages by specification section
- Including transmittals and cover letters in archives
- Linking submittals to RFI resolution outcomes
- Using timestamps and version numbers consistently
- Storing internal review notes with final submittals
- Creating a master index for easy retrieval
- Meeting legal requirements for document retention
- Preparing for third-party review or mediation
- Using file naming conventions for clarity
- Archiving both approved and rejected submittals
- Ensuring access control and backup protocols
- Demonstrating due diligence in specification review
- Defining clear roles in the review process
- Using assignment matrices to distribute work
- Setting performance metrics for submittal accuracy
- Conducting peer reviews to reduce errors
- Training junior staff on specification language
- Holding weekly submittal status meetings
- Documenting decisions from team discussions
- Using checklists to standardize review steps
- Providing feedback on review quality
- Recognizing consistent performance in reviews
- Addressing recurring mistakes in team settings
- Building a culture of specification ownership
- Choosing file formats that support markup
- Using PDF layers to compare drawing versions
- Organizing digital folders by CSI division
- Maintaining offline backups of critical files
- Using spreadsheet trackers without overcomplication
- Integrating cloud storage with access controls
- Avoiding over-reliance on automated alerts
- Validating software output against source documents
- Using templates to ensure consistency
- Training teams on digital discipline
- Balancing speed with accuracy in digital review
- Auditing digital workflows for gaps
- Conducting post-submission debriefs
- Analyzing rejected submittals for root causes
- Tracking RFI resolution trends by discipline
- Updating checklists based on lessons learned
- Sharing best practices across project teams
- Measuring time spent per submittal type
- Benchmarking performance across projects
- Using lessons from change orders to improve review
- Creating a living submittal playbook
- Incorporating feedback from field teams
- Revising templates at project milestones
- Setting annual goals for process maturity
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.