Set Up a Project Management Binder or Digital Job File

A. Finished-Project Specification

Deliverable: one secure, indexed, version-controlled project-management job file, physical or digital, containing controlled sections for every required document category, a document register, a revision log, a naming convention and status terms, loaded Project 01 and Book 23–25 source documents, field-record and log templates, tested document recovery, a confirmed backup, and an issued procedure acknowledged by the project team.

B. Job File Section Schedule

Section	Content	Source	Purpose
Project information	Address, client, contacts, contract number, permit numbers, emergency information	Agreement, permit application	Establishes the identifying record for the project
Contract and scope	Contract, scope statement, insurance, bonds, licenses, notices	Executed agreement, Project 01 scope statement	Preserves the controlling contractual and scope baseline
Design documents	Architectural, structural, civil, landscape, plumbing, electrical, HVAC, energy, specialty drawings	Book 23 drawing package	Stores the physical design the project must match
Specifications and submittals	Specifications, addenda, bulletins, sketches, calculations, submittals, product data, samples, shop drawings	Book 23–24 documents	Stores the technical basis for materials and installation
Permits and inspections	Permits, inspections, test reports, correction notices, approvals, certificates	Book 25 compliance package	Tracks regulated scope and authority approvals
Schedule and procurement	WBS, schedule, lookaheads, procurement, deliveries, equipment, logistics	Later Projects 03, 05–07	Reserves the structure future scheduling and procurement records will use
Commercial records	Subcontracts, purchase orders, supplier quotes, invoices, payment applications, lien releases, job-cost reports	Book 24 estimate, later Project 15	Organizes the financial and contractual trade records
Meetings and changes	Meetings, RFIs, clarifications, decisions, changes, allowances, alternates, claims-related notices	Later Projects 09–11	Reserves the structure future coordination records will use
Safety and quality	Safety plans, orientations, inspections, incidents; quality plans, checklists, mockups, deficiency logs, punch lists	Later Projects 12–14	Reserves the structure future safety and quality records will use, according to access rules
Daily field records	Daily reports, manpower, weather, visitors, deliveries, equipment, delays, field notes	Field team	Captures day-to-day project activity as it occurs
Communication	Owner, trade, supplier, design communication, formal notices	Later Project 17	Preserves decisions, notices, commitments, and approvals
Closeout	Warranties, manuals, training, spare materials, keys, as-built notes, final photographs, approvals, owner handoff	Later Projects 18–19	Reserves the structure closeout documents will use as they are collected

C. Information and Document Takeoff

• Source records: the approved Project 01 scope statement, executed agreement, Book 23 drawing package, Book 24 estimate, and Book 25 permit-and-inspection compliance package, sufficient to populate every section of the section schedule above without inventing missing information.
• Access record: the confirmed access level for owner, management, field staff, accounting, subcontractors, suppliers, designer, and consultants, obtained before the structure is built.
• Policy record: the company's confidentiality, cybersecurity, backup, and retention policy, obtained before confidentiality rules are drafted.
• Recovery test record: the results of retrieving one current drawing, one contract document, one inspection record, one photograph, and one pending RFI, and the results of confirming a superseded document is clearly separated from the active set.

D. Acceptance Standards

Check	Standard
Access levels	Every stakeholder role has a defined and confirmed access level before documents are loaded
Folder structure	Every section in the section schedule exists and is correctly populated with the assigned document category
Naming convention	Every filed document follows the established date, type, discipline, subject, revision, and status convention
Document register	Every controlled document has an identifier, title, originator, date, revision, status, distribution, and location entry
Active / archive separation	No superseded document appears in a location a field user would search as the active set
Recovery test	Every representative document listed in Step 32 is retrieved successfully, and the superseded-document separation test in Step 33 passes
Backup	A backup is confirmed and a sample file restoration is tested successfully

E. Preparation — Select the Platform and Set Access Rules

1. Select the approved file platform, physical binder, cloud system, project-management application, or coordinated hybrid system. Confirm the selection matches company policy before proceeding.
2. Identify access levels for owner, management, field staff, accounting, subcontractors, suppliers, designer, and consultants. Record each role's permitted access individually.
3. Create confidentiality, cybersecurity, backup, retention, and document-release rules. Base each rule on the company's confirmed policy, not an informal assumption.
4. Create the project root folder using the approved project number and name. Confirm the number and name match the executed agreement and permit application exactly.
5. Create a project-information index with address, client, contacts, contract number, permit numbers, and emergency information. Verify each entry against the source document it comes from.

F. Build the Controlled Section Structure

6. Create controlled sections for contract, scope, estimate, budget, insurance, bonds, licenses, and notices. Follow the section schedule in Section B above.
7. Create sections for architectural, structural, civil, landscape, plumbing, electrical, HVAC, energy, and specialty drawings. Match section names to the disciplines present in the Book 23 drawing package.
8. Create sections for specifications, addenda, bulletins, sketches, calculations, submittals, product data, samples, and shop drawings. Keep each document type in its own labeled subsection.
9. Create sections for permits, inspections, test reports, correction notices, approvals, and certificates. Match section names to the Book 25 permit-and-inspection categories.
10. Create sections for WBS, schedule, lookaheads, procurement, deliveries, equipment, and logistics. Reserve these sections for Projects 03 and 05–07 without populating them yet.
11. Create sections for subcontracts, purchase orders, supplier quotes, invoices, payment applications, lien releases, and job-cost reports. Reserve these sections for later commercial records.
12. Create sections for meetings, RFIs, clarifications, decisions, changes, allowances, alternates, and claims-related notices. Reserve these sections for Projects 09–11.
13. Create sections for safety plans, orientations, inspections, incidents, competent-person records, and emergency procedures according to access rules. Apply the confidentiality rules from Step 3 to this section specifically.
14. Create sections for quality plans, checklists, mockups, deficiency logs, photographs, punch lists, and acceptance records. Reserve these sections for Projects 13–14.
15. Create sections for daily reports, manpower, weather, visitors, deliveries, equipment, delays, and field notes. Confirm the field team can access this section from the jobsite.
16. Create sections for owner communication, trade communication, supplier communication, design communication, and formal notices. Reserve these sections for Project 17.
17. Create closeout sections for warranties, manuals, training, spare materials, keys, as-built notes, final photographs, approvals, and owner handoff. Reserve these sections for Projects 18–19.

G. Naming, Registers, and Loading Source Documents

18. Establish a file-naming convention using date, document type, discipline, subject, revision, and status. Record the convention in writing before any document is named under it.
19. Establish status terms such as draft, submitted, under review, approved, approved as noted, rejected, superseded, record, and closed. Use only these defined terms in the document register.
20. Create a document register with identifier, title, originator, date, revision, status, distribution, and current-file location. Begin the register before any document is loaded.
21. Create a revision log showing what changed, why, by whom, and when it became effective. Link each revision-log entry to its document register identifier.
22. Create a transmittal system for controlled document distribution. Confirm the transmittal record captures date, recipient, and document identifier.
23. Create separate active and archive locations so superseded documents cannot be mistaken for current documents. Confirm the separation is structural, not merely a label.
24. Upload or file the approved scope, contract, Book 23 drawing package, Book 24 estimate, and Book 25 compliance package. Assign a register identifier to each document before filing it.
25. Verify that drawing and specification indexes match the files received. Record any missing or unindexed document as an open item.
26. Create a photograph protocol with date, location, direction, subject, phase, and related issue identifier. Confirm the protocol matches the field-note form created in the next step.
27. Create a field-note form that distinguishes observation, conversation, decision, direction, and follow-up. Confirm the form's categories match the definitions in the Reference Conventions table.
28. Create logs for RFIs, submittals, procurement, deliveries, changes, allowances, inspections, deficiencies, punch items, and closeout. Create each log as an empty, correctly structured template for the projects that will populate it.
29. Create a required-document matrix showing who creates, reviews, approves, distributes, and archives each record. Assign one responsible role to each function per document category.

H. Verify, Test, and Issue the Job File

30. Establish daily, weekly, monthly, milestone, and closeout filing responsibilities. Assign each responsibility to a named role, not a general team.
31. Create an offline or field-access method for current plans and emergency information. Confirm the method functions without a live connection where required.
32. Test recovery of one current drawing, one contract document, one inspection record, one photograph, and one pending RFI. Record the time and result of each retrieval attempt.
33. Test that a superseded document is clearly separated from the active set. Confirm a test user cannot mistake the superseded document for the current version.
34. Correct broken links, duplicate files, ambiguous names, missing permissions, and inaccessible records. Re-run the affected recovery test after each correction.
35. Back up the system and test restoration of a sample file. Record the backup method, frequency, and the result of the restoration test.
36. Issue the job-file procedure to the project team and record acknowledgment. Confirm every stakeholder identified in Step 2 has received and acknowledged the procedure.