USACE RMS Software: Records Management System for Military Construction Projects

The Records Management System is a web-based or server-based platform that provides centralized storage and organization of all project documents. RMS replaces the traditional practice of maintaining physical file cabinets or decentralized digital folders by providing a structured environment where all documents are organized according to standardized naming conventions and coding systems that allow rapid location and retrieval of specific documents. The system maintains an audit trail of all documents including creation date, upload date, revision history, and access logs that show who has viewed or modified documents. RMS integrates various project management functions including management of submittals, tracking of requests for information, organization of correspondence, maintenance of schedules, progress payments tracking, contract modifications, pay activities management, and storage of quality documentation such as test reports and inspection records. Every project participant must have access to the RMS system and must understand the organizational structure used on that specific project. USACE projects typically establish RMS at the pre-construction conference where the contractor is briefed on the specific RMS requirements for the project, including the organizational structure for document storage, access credentials, user roles and permissions, and the procedures for uploading and managing different document types.

Every USACE military construction project designates a Quality Control Manager (also called Quality Manager or Quality Assurance Manager depending on project terminology) who bears responsibility for oversight of the quality documentation program and management of quality records within RMS. The Quality Control Manager must have specific qualifications and experience and must perform defined responsibilities throughout the project duration.

Quality Control Manager Qualifications:

Quality Control Managers typically must have a Bachelor's degree in engineering, construction management, or a related technical field, though some projects may accept candidates with extensive related experience in lieu of formal education. The Quality Control Manager must have at least five to ten years of experience in construction or quality management, with specific experience on military or federal projects being highly valued. Many USACE projects require Quality Control Managers to hold professional certifications such as Certified Quality Engineer (CQE), Certified Professional Inspector (API), or other quality-related certifications. The Quality Control Manager must be present full-time on the project site during all work activities and must maintain daily communication with the contractor's project management team and USACE representatives. The Quality Control Manager reports directly to the contractor's Project Manager and has responsibility for all quality-related functions on the project.

Quality Control Manager Responsibilities:

The Quality Control Manager develops and implements a Quality Control Plan that describes how the contractor will manage quality throughout the project. This plan includes identification of quality checkpoints for different work activities, procedures for inspections and testing, procedures for documentation of quality activities, and procedures for corrective action when quality issues are identified. The Quality Control Manager oversees and documents all inspections of work performed by the contractor, including daily inspections of ongoing work and detailed inspections at critical quality checkpoints such as concrete placement, structural steel connections, or mechanical equipment installation. The Quality Control Manager ensures that all required testing is performed in accordance with project specifications, that testing is conducted by qualified laboratories or testing personnel, that test results are properly documented, and that test data is uploaded to RMS in a timely manner. The Quality Control Manager maintains daily quality records including inspection logs, testing results, corrective action documentation, and quality correspondence. The Quality Control Manager organizes and uploads all quality documentation to RMS in accordance with the project's document coding and naming conventions. The Quality Control Manager participates in quality-related meetings with USACE representatives and the design professional to discuss quality issues, review test results, and resolve quality disputes. The Quality Control Manager serves as the point of contact for quality-related questions and ensures that all project personnel understand quality requirements and procedures.

Professional correspondence on USACE projects must follow specific formatting requirements and must include appropriate document coding to ensure proper organization within RMS. All project correspondence—whether internal communication between contractor personnel or external communication with USACE or the design professional—must be prepared using company letterhead with official business information including company name, address, phone number, and appropriate contact personnel identification.

Correspondence Formatting Requirements:

All correspondence must include specific header information that facilitates document organization and retrieval. The document header must include the project name exactly as specified in the contract documents, the project code or number assigned by USACE, the date the letter is written. The correspondence must clearly identify the sender with name, title, company, and contact information, and must clearly identify the recipient including specific name and title of the intended recipient. The subject line must clearly and concisely describe the purpose and content of the correspondence in a format that facilitates document searching and retrieval. For example, instead of "Project Update," a subject line might read "Submittal of Concrete Compressive Test Results—Structural Slab 2A."

Correspondence Content Organization:

The body of the letter must be organized in a clear, logical format using numbered paragraphs for ease of reference. The opening paragraph must clearly state the purpose of the correspondence, the specific document or action being referenced, and the specific request or information being provided. Subsequent paragraphs must provide supporting details, background information, technical explanation, or documentation references necessary for understanding the subject matter. Attachments must be clearly referenced within the correspondence body and must be listed in an attachments section at the end of the letter. The correspondence must include appropriate signature authority—typically the Project Manager or other designated project representative—with typed name, title, and company. All correspondence must be dated and must be maintained as a scanned PDF file for upload to RMS.

Document Coding for Correspondence:

When correspondence is uploaded to RMS, it must be assigned appropriate coding that places it in the correct organizational category. Correspondence related to design clarifications or technical questions should be coded as RFI correspondence and organized within the RFI section of RMS. Correspondence related to quality issues, test results, or inspection activities should be coded as Quality Documentation and organized within the quality section. Correspondence related to schedule changes, project delays, or progress updates should be coded as Project Correspondence and organized in the administrative correspondence section. Correspondence related to payment applications, contract changes, or other contract administration matters should be coded as Contract Correspondence. The specific coding used depends on the project's RMS structure and the nature of the correspondence being submitted.

Successful RMS management depends on consistent, accurate uploading of documents according to standardized procedures. Every project establishes specific procedures for document submission, review, and approval within RMS that must be understood and followed by all project personnel.

Document Preparation Before Upload:

Before uploading any document to RMS, the document must be properly formatted, scanned if physical copies exist, named according to project naming conventions, and organized in a logical file structure on the contractor's local network or servers. Documents should be scanned at high enough resolution to ensure that content is readable and searchable, typically at least 300 dpi for text documents. Documents should be converted to PDF format to ensure consistent display across different computers and software versions. Multi-page documents should be organized into a single PDF file rather than multiple separate files. The document must be named using the exact naming convention established for the project, with all required elements in the correct sequence. If the document is a revision to a previously submitted document, the revision level must be incremented and the previous version must remain in RMS with clear indication that it has been superseded.

Upload Process and Approval Workflow:

Most USACE projects require that documents be uploaded to RMS through a formal submission process that includes initial upload by the contractor, review by appropriate project team members, approval by designated approval authority, and final release to project participants. The typical workflow involves the contractor uploading the document to a holding or review area within RMS, selecting appropriate reviewers based on the document type and content, and notifying reviewers that a document is available for review. Reviewers examine the document for completeness, accuracy, compliance with specifications, and proper formatting and coding. Reviewers may approve the document, request changes or clarifications, or reject the document and request resubmission. Once all required approvals are obtained, the document is released to the "current version" status within RMS, where all project participants can access the approved version. Previous versions remain in RMS in archived status for historical reference and record-keeping. The document upload date, approval date, and revision history are automatically recorded by the RMS system.

Best Practices for Document Organization:

Documents should be uploaded promptly after they are ready for project team review, without unnecessary delays that might cause downstream scheduling impacts. Documents should be organized into logical document folders within RMS that match the project's coding system, allowing documents to be easily found through folder browsing or document searches. Documents should include comprehensive descriptions or abstracts in the RMS system to facilitate searching and to provide context for other project participants who may encounter the document. Documents should be regularly archived once they are superseded by newer versions, removing clutter from active document lists while maintaining historical records. The Quality Control Manager should regularly review the RMS system to ensure that all required quality documentation has been uploaded in a timely manner and that documentation is properly organized and coded.

Requests for Information represent a critical communication channel between the contractor, USACE, and the design professional when clarification of contract documents or specifications is required. RFI management within RMS provides a structured process for submitting requests, tracking responses, and maintaining a record of all clarifications provided during the project.

RFI Initiation and Submission:

A Request for Information is initiated when the contractor encounters a condition in the contract documents that is ambiguous, conflicting, or requires clarification. Common reasons for RFI submission include conflicting dimensions or specifications in different drawings, specification requirements that appear impossible to meet given site conditions, or lack of clarity regarding how specific requirements should be interpreted or implemented. The contractor prepares an RFI document that clearly describes the ambiguity or question, provides relevant references to specific contract document pages or sections, includes sketches or marked-up drawings that illustrate the issue, and specifically states the question being posed to the design professional. The RFI is submitted through RMS where it is assigned an RFI number and organized within the RFI section according to the project's coding system. The RFI status is automatically set to "Pending" upon submission, indicating that it awaits response from the design professional.

RFI Review and Response Process:

RFIs are typically routed to the design professional for review and response. The design professional has a specific timeframe—usually five to seven business days—to review the RFI and provide a response. The response may provide the requested clarification, may request additional information from the contractor to better understand the question, or may provide direction on how the work should proceed pending full clarification. Once the design professional provides a response, the RFI status changes to "Responded" within RMS. The contractor reviews the response to ensure that it adequately addresses the question and allows work to proceed. If the response is unclear or incomplete, the contractor may submit a follow-up RFI or request further clarification. The RFI status is then changed to "Closed" once the contractor confirms that the response is adequate and work can proceed accordingly.

RFI Organization and Documentation:

All RFIs and responses are maintained within RMS and organized by RFI number and subject matter. The RMS system maintains a searchable index of all RFIs allowing project personnel to review previous RFIs and determine whether similar questions have been posed and answered. This functionality prevents duplicate RFI submissions and allows the contractor to learn from previous clarifications. The RFI record includes the original question, all responses, dates of submission and response, responsible parties, and status. RFIs become part of the permanent project record and may be referenced in post-project reviews, claim documentation, or dispute resolution if schedule impacts or cost impacts result from design changes or clarifications.

Submittals represent documentation of specific products, materials, or work methods proposed by the contractor for use on the project. Submittals are required by specifications to verify that proposed products meet specified requirements and that work methods comply with contract requirements before the work is performed or materials are installed.

Types of Submittals and Submittal Requirements:

Submittals typically fall into several categories depending on the nature of the item being submitted. Product submittals are submitted for manufactured materials or equipment such as concrete admixtures, reinforcing steel, mechanical equipment, electrical components, specialty materials and coatings, or prefabricated components. For product submittals, the contractor must provide complete manufacturer's technical data, published performance specifications, test reports and certifications, material safety data sheets (MSDS), warranties, and comprehensive documentation that verifies the product meets all specification requirements. Shop drawing submittals are submitted for items that are custom-fabricated or specifically designed for the project, such as reinforced concrete details, structural steel connection details, mechanical system layout drawings, electrical routing and conduit plans, plumbing system details, specialty fabrications, or any item requiring engineering design. Shop drawings must be prepared by qualified designers or professional engineers and must clearly show all dimensions, details, connections, and specifications that demonstrate how the specific item will be constructed, fabricated, or installed to meet contract requirements and accommodate site conditions. Method and procedure submittals are submitted to document specific work methods, construction procedures, quality assurance procedures, safety procedures, testing and inspection protocols, equipment operation procedures, or sequencing plans that will be used to perform the work. These submittals should describe procedures for concrete placement and finishing, reinforcement placement and splicing, welding and connection procedures, material testing and inspection protocol, equipment operation and maintenance, specialized installation methods, or coordination of work activities. Warranty and certification submittals are submitted to provide evidence that manufacturers will provide written warranties covering their products and that installers, fabricators, or workers hold appropriate licenses, certifications, qualifications, or insurance required for the work. Quality management submittals document the contractor's quality control procedures, inspection points, testing schedules, and corrective action procedures for different work activities.

USACE Submittal Codes and Approval Status:

RMS uses specific submittal codes to track the status of each submittal throughout its lifecycle. Understanding these codes is essential for effective submittal management and contract administration. The primary submittal codes used in RMS are:

SUBMITTED (S): The submittal has been uploaded to RMS by the contractor and is available for review by the quality control manager or design professional. The submittal has been formally transmitted and assigned a submittal tracking number. This is the initial status when a new submittal is first uploaded to RMS.

APPROVED (A): The submittal has been reviewed by the quality control manager or design professional and has been found to meet all specification requirements without exception. No changes or corrections are required. The contractor is approved to proceed with procurement, fabrication, or installation of the item or implementation of the proposed method.

APPROVED AS NOTED (AN): The submittal has been reviewed and is acceptable for use, but there are minor comments, clarifications, notations, or observations that do not require resubmission. The contractor should carefully note these comments and incorporate them during fabrication or installation but does not need to submit a revised submittal unless specifically requested.

APPROVED WITH RECOMMENDATIONS (AW): The submittal has been reviewed and is acceptable for use and approved, but the design professional or quality manager has included recommendations for optimization, improved performance, efficiency improvements, or best practices. These recommendations are not mandatory requirements but are suggested for consideration by the contractor to achieve superior results.

REJECTED (R): The submittal has been reviewed and has been found to be unacceptable. The submittal does not meet specification requirements, contains inadequate or incomplete technical information, proposes non-compliant products or methods, or is otherwise unacceptable for use. The contractor must revise and resubmit the submittal with complete corrections addressing all identified deficiencies before proceeding with the work.

REVISE AND RESUBMIT (RR): The submittal requires revision or substantial additional information before approval can be granted. This status is less severe than outright rejection and indicates that the submittal has potential but requires corrections, additional clarifications, supplemental data, or technical justification before it can be approved.

NO SUBMITTAL REQUIRED (NSR): The item or activity does not require submittal documentation. This status is used for items that are purchased over-the-counter without customization, when standard products are used that clearly meet specifications, or when certain activities do not require pre-work approval.

Submittal Organization and Tracking:

All submittals must be properly organized within RMS with sequential submittal numbers assigned in order of submission. Submittal numbers are typically formatted as S-001, S-002, S-003, or similar sequences, providing unique identification for each submittal within the project. Each submittal must include a comprehensive cover page or submittal transmittal form with the project name, submittal number, detailed submittal description, date submitted, contractor name and contact information, specification section reference, and identification of the material or method being submitted. Supporting technical documentation must be clearly organized, labeled, and cross-referenced. When a submittal receives Revise and Resubmit status, the revised submittal should reference the original submittal number and note that it is a revision (e.g., S-001 Rev A or S-001.1). Approval dates, reviewer names, and approval comments must be recorded within RMS. All submittal transmittals, approvals, rejections, and correspondence related to submittals must be documented and tracked within RMS and must be readily accessible to all project team members throughout the project duration.

Submittal Preparation and Quality Review:

Submittals must be prepared in a professional format that clearly communicates the required information and provides complete technical justification for the proposed product, method, or procedure. Product submittals should include complete manufacturer technical data sheets with full specifications, published performance data and ratings, all applicable test reports and certifications (such as mill certs, lab test reports, third-party certifications), product comparison information showing how the proposed product meets each specification requirement, warranty and guarantee documentation, and any required quality documentation. Shop drawing submittals should be prepared by qualified professionals using professional-grade drawing software with appropriate title blocks, legend, detailed notes, dimensions, and material specifications. Method submittals should be organized in logical sequence describing the proposed work method, identifying all equipment and materials to be used, describing quality control procedures and inspection points, identifying testing and inspection requirements, and referencing applicable standards or specifications. All submittals must be transmitted as PDF files that are clearly organized, easy to navigate, and contain all necessary supporting documentation. RMS provides a formal approval workflow where submittals are reviewed by project team members based on their expertise and role. adequate documentation to allow proper review. Submittals should be organized with a cover sheet identifying the project, the submittal number, the item being submitted, the specification reference, and the intended use or application. Manufacturer data sheets should include full technical specifications, performance ratings, test data, quality certifications, and warranty information. Shop drawings should include all necessary dimensions, connection details, construction details, and notes describing how the item will be constructed and installed. Submittals should be organized into a single PDF document with all pages properly numbered and titled. The submittal must be named according to the project's naming convention with appropriate coding that identifies it as a submittal for easy organization within RMS.

Submittal Review Process and Approvals:

Once a submittal is uploaded to RMS, it is routed for review to appropriate team members including the design professional, specialty consultants if required, and USACE representatives if USACE approval is required for specific items. The reviewing parties examine the submittal to verify that the proposed item meets specifications, that shop drawings are correct and complete, and that methods and procedures are appropriate. Submittals are typically marked as "Approved," "Approved as Noted," "Revise and Resubmit," or "Rejected" based on the review results. "Approved" indicates that the item fully complies with specifications and work can proceed. "Approved as Noted" indicates that the item is acceptable but minor revisions or clarifications are noted. "Revise and Resubmit" indicates that corrections or additional information is required before approval. "Rejected" indicates that the item does not comply with specifications and must be replaced with a different product or method. Submittals marked as "Revise and Resubmit" must be corrected by the contractor and resubmitted for additional review. Once final approval is obtained, the submittal status changes to "Approved" and the item is cleared for use or installation on the project.

Project schedules represent a critical component of project management and USACE requires that contractors maintain and regularly update project schedules, with all schedule revisions documented and tracked within RMS.

Schedule Development and Baseline Establishment:

The contractor develops a detailed project schedule during the pre-construction phase that shows the planned sequence and timing of all major work activities throughout the project duration. The baseline schedule is typically submitted for USACE review and approval within the first weeks after project start. The baseline schedule identifies major milestones such as start date, completion of design phase, start of construction, completion of major work phases, and final project completion date. The schedule identifies critical path activities that directly impact project completion date and non-critical activities that have float or schedule flexibility. The schedule is typically prepared in critical path method format using standard project scheduling software and is submitted to RMS for documentation and historical reference.

Schedule Updates and Revisions:

The contractor must regularly update the project schedule to reflect actual progress and to adjust future planned activities based on current conditions. Monthly schedule updates are typical, where the contractor reviews actual progress during the previous month, updates the percentage completion of ongoing activities, updates future activity durations if schedule changes have been identified, and rebalances the schedule to reflect current status. Each schedule update should show the current status of all activities, identify any schedule delays or accelerations that have occurred, project completion date based on current progress, and identify any activities that have become critical if they were not previously critical. Schedule revisions must be submitted to RMS with appropriate coding and version control that clearly identifies each revision and maintains historical versions for reference. USACE reviews monthly schedule updates to monitor project progress and to identify schedule risks or delays that might require corrective action.

Schedule Change Documentation:

Any significant changes to the project schedule—such as delays caused by design changes, acceleration of activities to make up for previous delays, or rescheduling of activities due to changed site conditions—must be documented and submitted to RMS. Schedule change documentation should explain the reason for the change, identify specific activities affected, quantify the schedule impact, and show the revised planned completion date. If schedule changes result in delay to project completion, documentation of the cause and responsibility for the delay becomes important for potential claim purposes. Schedule change documentation is maintained in RMS alongside schedule updates to create a complete record of how the project schedule evolved throughout the project duration and the reasons for any changes.

Effective RMS management requires appropriate system administration, access control procedures, and security measures to ensure that only authorized personnel can access sensitive project information and that documents are protected from unauthorized modification or deletion.

User Access and Credentials:

Each project participant is assigned access credentials that allow them to log into the RMS system and view documents appropriate for their role on the project. Access levels are typically defined based on organizational role and project responsibilities. The contractor's project team members have full access to all contractor-generated documents and broad access to project documents. USACE representatives have access to all project documents including contractor documents, design documents, and quality records. The design professional has access to all design-related documents and contractor submittals but may have restricted access to internal contractor quality records. Subcontractors and specialty consultants may have limited access to only documents relevant to their specific work areas. Each user is assigned a unique username and password that creates an audit trail of user activity within the RMS system.

Document Version Control and Change Management:

RMS maintains version control of all documents, automatically tracking revision history and maintaining archived copies of previous versions. When a document is revised and resubmitted, the system automatically increments the version number or revision letter, archives the previous version, and establishes the new version as current. The system records the date of submission, the user who uploaded the revision, and any revision notes or change descriptions provided by the uploader. Users can view revision history of any document and can access previous versions if needed for reference or comparison. This version control prevents confusion about which document version is current and provides complete history of document evolution throughout the project.

Security and Data Protection:

RMS systems are typically hosted on secure servers with encryption protecting data transmission and storage. Access is controlled through authentication procedures ensuring that only authorized users can access the system. Backup procedures ensure that project data is regularly backed up and can be recovered if system failure occurs. Access logs record all user activities including login times, documents accessed, and modifications made, creating an audit trail for security and compliance purposes. Projects should establish security policies addressing handling of sensitive information, restrictions on external sharing of documents, and procedures for protecting confidential project information.

USACE projects require strict compliance with RMS requirements and establish specific procedures for project close-out and final documentation.

Compliance Monitoring and Enforcement:

USACE project representatives regularly review RMS to verify that the contractor is uploading required documentation in a timely manner, that documents are properly named and coded, and that quality documentation is current and complete. USACE may issue corrective action requests if RMS management is inadequate or if required documentation is not being submitted. Failure to maintain proper RMS documentation may result in withholding of payment applications or other enforcement actions. Regular communication between the contractor's Quality Control Manager and USACE representatives regarding RMS status helps ensure that compliance issues are identified and corrected promptly.

Project Close-out and Final Records:

As the project nears completion, the contractor prepares a final project record consisting of all RMS documents organized in a comprehensive archive. The final record includes all design documents, specifications, construction documents, quality records, inspection reports, test data, RFIs and responses, submittals and approvals, schedules, and correspondence. All documents should be verified for completeness, properly named and coded, and organized in logical categories within RMS. Final payment applications typically cannot be approved until USACE confirms that all required project documentation has been properly uploaded to RMS and is complete and accurate. Upon project completion, RMS remains accessible for the required retention period established by contract, typically seven years or longer for military projects, allowing access to project documentation for warranty periods, potential claim resolution, or reference for future similar projects.