Guides
A library you can browse by problem
Practical document-control guides for contractors in any state — current-set rules, miss stories, Drive and Dropbox setups, templates, and when to bring in a pro.
These are practical guides for contractors who want a current set, honest logs, and a closeout folder they can hand over, without an enterprise software contract.
Browse by problem or by hub. The flagship articles are the longer starting points, and the templates are ready to copy in the Job File Kit. Nothing here replaces your contract, and the miss stories are typical cases, not specific jobs.
Browse by problem
RFIs or submittals are slipping, or answers are not reaching the field.
The job file is a mess, or we are about to start a new one.
Closeout or retention is already a problem, or will be.
A pay app is stalling over missing paper.
I want to know if we can run this ourselves, or should bring someone in.
I want to understand Procore's process, then run it with Drive or a spreadsheet.
I need Arizona-specific filing habits (notices, heat-season dailies, inspections).
A new superintendent is about to inherit the file.
I have a general question, or I want a definition.
Why Document Control Matters
What the big GCs know, and what you can borrow.
- H1-01
What the Big GCs Know About Paperwork That Saves Them Money Flagship
You already know how to build.
- H1-02
What Document Control Actually Means on a Job Without a Full-Time Controller
Document control is the system that keeps the field, the office, and the design team on the same facts — not a full-time desk job you have to hire before…
- H1-03
Why Big Contractors Insist on One Current Set of Drawings
A single source of truth for the sheets that govern today's work is the cheapest insurance against building last week's design.
- H1-04
RFI and Submittal Tracking: The Habit That Pays for Itself
A good log shows what is open, who has the ball, and whether the field has seen the answer — which is how questions stop turning into rework.
- H1-05
The Audit Trail: How a Clean File Ends Arguments Before They Start
Dates, transmittals, and distribution records are what you reach for when someone says they never got the bulletin.
- H1-06
Closeout Is Won in Week One, Not the Last Month
Warranties, as-builts, and O&M manuals are easier to collect while the people who produced them are still on the job.
- H1-07
You Don't Need Enterprise Software to Borrow Enterprise Habits
The value is the rule and the cadence, not the logo on the login screen; folders and a spreadsheet can carry the same habits.
- H1-08
Why Owners, Lenders, and Inspectors Care About Your Paper Trail
Other people on the job are already judging the quality of your record, even if you think of it as "just paperwork."
- H1-09
Looking for the File Is a Job Cost, Even If It Never Hits a Line Item
Time spent hunting through email for the right PDF is still time, and a simple job file makes that hunt shorter.
- H1-10
Arizona Schedule Pressure: Heat, Monsoon, and Notice Deadlines
Early pours, weather delays, and payment or notice clocks only stay manageable if the daily report and the current set are in a place you can find.
- H1-11
Document Control Is Risk Management, Not Clerical Work
Logs and current-set rules are how you reduce rip-outs, disputes, and held retention — the same risk a large GC staffs a person to watch.
Common Misses and What They Cost
Miss stories that show how these problems typically play out, unless a page says otherwise.
- H2-01
The Missed RFI: How One Unanswered Question Turns Into a Rip-Out Flagship
On a large job, an RFI is not a casual email.
- H2-02
Built Off Last Week's Sheet
A revised drawing was issued, but the set in the truck was yesterday's, and the install followed the old dimensions.
- H2-03
The ASI That Never Left the Inbox
An architect's supplemental instruction changed the work, then sat in email until after the area was closed up.
- H2-04
Approved as Noted — and Nobody Read the Notes
A submittal came back approved with comments, the comments never reached the installer, and the product or layout was wrong.
- H2-05
The Handshake Change That Never Got a Paper Trail
A field decision everyone agreed on, with nothing in writing, turns into a fight when the cost shows up on a pay application.
- H2-06
Photos That Can't Prove What You Think They Prove
A camera roll of unmarked, undated, or unfindable photos is not a record when you need to show what was in the wall.
- H2-07
The Pay App Held Up Over Missing Lien Waivers
A complete work month still sits unpaid when the waiver packet, backup, or dates are incomplete or cannot be found.
- H2-08
Closeout Delayed by a Missing O&M or Warranty
Retention and final payment wait on documents that were easy to collect at submittal time and painful to chase after demobilization.
- H2-09
The RFI Answer That Reached the Office but Not the Field
Closing the log in the office is not the same as putting the answer in the hands of the person doing the work.
- H2-10
Two "Current" Sets on the Same Job
When the trailer, a phone, and a sub each have a different "latest" set, somebody will build the wrong one.
- H2-11
A Daily Report Gap During a Weather Delay
A monsoon day or a heat shutdown is hard to explain later if the daily reports skip the dates that matter.
- H2-12
The Transmittal That Would Have Ended the Argument
"I never got that bulletin" is a short conversation when you can show what was sent, to whom, and when.
Basic Controls for Contractors Without Staff
RFIs, submittals, the current set, changes, dailies, photos, transmittals, and closeout.
- H3-01
How to Run an RFI Log Without Enterprise Software
A visible spreadsheet log — number, dates, subject, ball-in-court, due date, closed date, and who in the field received the answer — is enough if someone…
- H3-02
A Submittal Log a Superintendent Can Keep Up With
Track what was sent, what came back, whether it was approved as noted, and whether those notes reached the installer.
- H3-03
Current-Set Control: One Place, One Date, One Rule
If it is not in the current-set folder, do not build from it; yesterday’s sheets go in a superseded folder, not in the truck.
- H3-04
A Naming Convention That Survives a Busy Week
Dates first, then project, type, number, and revision, so the newest file sorts to a place a tired person can trust.
- H3-05
Distribution: Who Gets the Update, and How You Prove It
When something changes, a short, consistent notice to the people who need it — with a record that it was sent — beats a forwarded email with no trail.
- H3-06
Simple Sign-Offs That Close the Loop
A column in the log or a one-line reply from the superintendent, “got it, posted to the current set,” is often all the acknowledgment you need.
- H3-07
Change Orders: Paper First, Then the Work
A verbal field agreement still needs a written change record before the extra work is treated as approved and billable.
- H3-08
Daily Reports That Protect the Schedule Story
Dated, consistent dailies — weather, manpower, areas of work, delays, and visitors — are the backbone of later delay and extra-work conversations.
- H3-09
Job Photos You Can Find Six Months Later
Name, date, and locate photos by area and issue so they can prove a condition, not just fill a camera roll.
- H3-10
Transmittals in Plain English
A transmittal is a short record of what you sent, to whom, and why — not a legal essay — and it is what you reach for in a dispute.
- H3-11
Closeout Starts at Mobilization
Build the closeout folder on day one and drop warranties, O&Ms, as-builts, and extra-stock records in as they appear.
- H3-12
Lien Waivers and Pay Apps: A Clean Package Every Month
A repeatable monthly packet — application, backup, waivers, and dates — keeps payment from stalling over missing paper.
- H3-13
Meeting Minutes and a Decision Log
Decisions made in the weekly meeting need a date, an owner, and a home in the job file, or they evaporate by Friday.
- H3-14
After Bid Day: Specs, Addenda, and What Actually Governs
The contract set is the bid set plus every addendum and accepted alternate; if those are not in one place, the job will be built to the wrong documents.
- H3-15
Shop Drawings, Product Data, and Samples — Keep Them Straight
Different submittal types have different risks; a log that treats them as one pile is how an unreviewed shop drawing reaches the field.
- H3-16
ASI, RFI, and CCD: The Alphabet Without the Confusion
A short, practical guide to which document changes the work, which asks a question, and where each one belongs in the file.
- H3-17
Before-You-Cover-It Photos
Photos taken before a pour, a cover-up, or a ceiling close are only useful if they are dated, named, and filed the same day — not left in a personal camera…
- H3-18
Photos That Support a Delay or Extra Work Claim
Photos used later to explain a delay or extra work have to be dated, specific, and tied to a daily or a ticket — this is a filing habit, not legal advice.
- H3-19
Time-and-Material Tickets and the Change Order They Become
A T&M ticket is backup, not a change order. Write it the same day, get a signature if you can, file it, and land it in the change log.
- H3-20
Backcharges: The Paper Trail You Wish You Started Earlier
A backcharge needs the same same-day habit as a change: photos, a notice, hours or costs, and a folder — started when the condition is visible, not at the…
- H3-21
Assembling O&M Manuals Without a Last-Month Scramble
Operations and maintenance manuals are easy to collect as approved submittals come back, and painful to rebuild after the trades have left.
- H3-22
Warranties, Attic Stock, and the Handoff to the Owner
Warranties, extra-stock records, and training or handoff notes are easy to collect while the sub is on site, and they belong in a tracker, not in a…
Simple Tool Setups
Google Drive, Dropbox, spreadsheets, a phone, and careful use of AI.
- H4-01
A Procore-Level Job File With Google Drive (or Dropbox) and a Spreadsheet Flagship
You do not need Procore to have a controlled job file.
- H4-02
Google Drive for a GC: A Practical Setup
Shared drives, a current-set folder, phone access, and a few permission settings that stop someone from overwriting today’s drawings.
- H4-03
Dropbox If That’s Already Where Your Team Lives
The same job-file rules in Dropbox, for teams that should not be asked to move platforms just to get organized.
- H4-04
The Spreadsheet Logs That Replace a Software Module
The exact columns a small RFI or submittal log needs, and the status habits that keep the sheet from going stale.
- H4-05
Shared Drives, Permissions, and Who Can Overwrite the Current Set
Most people should be able to view and download the current set; only a short list should be able to replace it.
- H4-06
Making the Current Set Obvious on a Phone
If the superintendent cannot open today’s sheets on a phone in the sun, the “current set” still lives in the truck.
- H4-07
Phone Photos Without Creating a Junk Drawer
How to get jobsite photos out of a personal camera roll and into dated, named folders in the job file.
- H4-08
Where AI Helps: Summaries, Draft Transmittals, and Searching a Folder
Used as a clerk, AI can summarize a long RFI, draft a short transmittal, or help you search a project folder — and a person still checks the source PDF.
- H4-09
Where AI Should Not Be Trusted
AI cannot tell you which drawing is current, should not “approve” submittals, and should not be the last word on contract or notice language.
- H4-10
A Naming Convention You Can Paste Into a New Job
A one-page naming rule, with examples, that you can drop into the root of every new job folder.
- H4-11
The Job Folder Structure, Explained Folder by Folder
What belongs in each folder of the recommended structure, and what should never be dumped into “Misc.”
- H4-12
Handing a Clean Job File to a New Super Mid-Project
How to turn over drawings, logs, open RFIs, and access so a mid-job staff change does not reset the record to zero.
- H4-13
Drafting RFIs and Meeting Notes With AI — and What You Still Have to Check
AI can turn field notes into a draft RFI or a first pass at meeting minutes. A person still has to check every drawing reference, date, and commitment…
- H4-14
Building a Closeout Package With AI — and What It Will Miss
AI can draft a first closeout checklist from a spec section. It will miss items, invent others, and cannot chase a warranty. A person still owns the list.
- H4-15
Using AI to Search Specs, Caption Photos, and Draft Dailies — Honest Limits
AI can help you search a spec book, draft a daily from notes, or suggest a photo caption. It can also retrieve the wrong paragraph or write a day that did…
- H4-16
A First-Week Document-Control Checklist for a New Superintendent
A new superintendent should be able to find the current set, the open RFIs, the logins, and the closeout folder in the first week — and a departing super…
When to Bring In a Pro
When a simple setup will hold, and when it will not.
- H6-01
What Document Control as a Service Looks Like
Someone else keeps the current set, the logs, the distribution, and the closeout folder — and the files stay yours.
- H6-02
When DIY Is Enough, and When It Isn’t
A clean file and a twice-weekly log review will hold a lot of jobs; fast revisions or a closeout already behind are signs to get help with your own file.
- H6-03
Job File Setup: Starting the Next Project Clean
A one-time setup of folders, naming, logs, and access, so the superintendent is not inventing the system in week three.
- H6-04
Retainer Document Control During Construction
Ongoing log, current-set, and distribution support while the field stays focused on the work.
- H6-05
Closeout Prep Before the Scramble
Collecting closeout documents along the way, then packaging them before the last-month hunt for warranties and as-builts.
- H6-06
A First Conversation: What to Bring to a Short Call
A recent RFI thread, a look at where your drawings live, and one pain point are enough to tell whether a simple setup will hold.
Templates and Checklists
Practical starting points you can copy. Get the full Job File Kit by email.
- H7-01
RFI Log Template (Google Sheets)
A ready-to-copy log with the columns that matter, plus a short note on how to run it each week.
- H7-02
Submittal Log Template
A companion sheet for submittals, including “approved as noted” and field-distribution columns.
- H7-03
Job Folder Template for Google Drive or Dropbox
An empty, pre-labeled folder tree you can duplicate at the start of a job, with a one-page readme in the root.
- H7-04
Closeout Checklist
A practical closeout list — O&Ms, warranties, as-builts, extra stock, tests, punch, and training records — to start on day one.
- H7-05
Current-Set Cover Sheet and Transmittal
A simple cover sheet and transmittal form so each issuance has a date, a list of sheets, and a recipient record.
- H7-06
Arizona Pay App and Lien Waiver Packet Checklist
A monthly checklist for a clean payment package, including a reminder to track preliminary notices and waiver forms, clearly marked as not legal advice.
- H7-07
Change Order Log Template
A ready-to-copy log for potential and executed changes, including T&M tickets, with a short note on how to run it.
- H7-08
Daily Report Template
A short same-day daily report you can copy into a Doc or a form, with manpower, work, delays, inspections, and a pointer to photos.
- H7-09
Photo Log Template
A simple log for the photo sets that would hurt you if they were missing — before cover-up, conditions, punch, and extra work — plus a same-day filing rule.
- H7-10
Meeting Minutes Template
A simple minutes form that separates decisions from discussion, plus a rule to issue them promptly and file a send-record.
- H7-11
Warranty Tracker Template
A closeout tracker for warranties and a companion attic-stock list, started from the specs, with a rule to request documents while the sub is still on site.
- H7-12
Document Transmittal Log Template
A simple log of what was sent, to whom, and when, so “I never got that bulletin” has a date and a recipient list behind it.
Procore Processes, Simpler Tools
What the enterprise platforms enforce for RFIs, submittals, drawings, dailies, punch, closeout, and changes, run in Drive, Dropbox, and a spreadsheet.
- H10-01
How Procore Handles RFIs — and How to Do the Same With a Spreadsheet
Procore’s RFIs tool facilitates a numbered question, an assignee, a due date, and an official response. A visible spreadsheet, a filed PDF, and a short note…
- H10-02
How Procore Handles Submittals — and How to Do the Same With a Simple Log
Procore’s Submittals tool facilitates a register, a review workflow, and a status you can filter. A spreadsheet log and a clearly named folder can do the…
- H10-03
How Procore Handles Drawings — and How to Do the Same With a Current-Set Folder
Procore’s Drawings tool is built to keep a current set and archive revisions. A clearly named Current folder and a Superseded folder can do the same job if…
- H10-04
How Procore Handles Daily Logs — and How to Do the Same With a Simple Daily Report
Procore’s daily log facilitates a dated record of manpower, work, visitors, and conditions. A short daily report, filed the same day in Drive or Dropbox,…
- H10-05
How Procore Handles Punch Lists — and How to Do the Same With a Simple List
Procore’s punch-list tools facilitate dated items, assignees, photos, and a closed record. A spreadsheet and a photo folder can do the same job if the list…
- H10-06
How Procore Handles Closeout — and How to Do the Same With a Folder and a Checklist
Procore can facilitate a closeout checklist and a place to upload the package. A dated closeout folder, a checklist, and a warranty tracker can do the same…
- H10-07
How Procore Handles Change Events — and How to Do the Same With a Change Log
Procore’s change-event and change-order tools facilitate a dated record from a potential change to an executed document. A change log, T&M tickets, and a…
Arizona Context
Filing habits for notices, heat-season dailies, and inspection records under Arizona rules. Other states differ. Not legal advice.
- H11-01
Arizona ROC Paperwork You Should Keep With the Job File
A practical filing habit for license, bond, and job records that often matter if an Arizona ROC issue comes up — not a guide to licensing, and not legal advice.
- H11-02
Preliminary Notices: A Document Control Habit, Not a Legal Seminar
Arizona’s preliminary twenty-day notice is a dated document with a statutory clock. Track it in the job file like any other deadline — and get legal advice…
- H11-03
Heat-Season Daily Logs in Arizona
Summer heat and monsoon afternoons change the workday. The daily report is where that story has to live, written the same day, in language specific enough…
- H11-04
City and County Inspection Records: What to Keep and Where
Passed and failed inspections, correction notices, and final sign-offs belong in the job file, named and dated — requirements vary by jurisdiction, and this…
Working With Owners
Owner file requests, walkthroughs, and the paper that follows.
- H12-01
Looking Organized When the Owner or Lender Asks for the File
A current set, honest logs, and a closeout folder you can share on short notice are how a contractor looks reliable to a sophisticated owner or a lender —…
- H12-03
Owner Walkthroughs, Punch, and the Paper That Follows
A walk is only as useful as the list it produces. One official punch list, same-day photos, and a closeout path keep an owner walk from becoming three…
About Built On Record, services, the FAQ, the Services FAQ, and the glossary live on their own pages. If you want to talk, start at Contact. Bring a recent RFI thread and show me where the drawings live.