Difference between revisions of "Inspector’s Daily Work Report (DWR)"

From MediaWiki
Jump to navigation Jump to search
 
(7 intermediate revisions by the same user not shown)
Line 8: Line 8:
  
 
==[[#Inspector's Daily Work Report (DWR)|Inspector's Daily Work Report (DWR)]]==
 
==[[#Inspector's Daily Work Report (DWR)|Inspector's Daily Work Report (DWR)]]==
 +
 +
This information is for AASHTOWare contracts, for FieldManager contracts please see [[FieldManager#Inspector.27s_Daily_Report_.28IDR.29|Inspectors Daily Report (IDR) page]].
  
 
The Inspector’s Daily Work Report (DWR) is a significant piece of documentation that is prepared by the inspector with the objective of summarizing the Contractor’s work and progress. It is necessary that the DWR be prepared correctly, legibly, and thoroughly. At a minimum, a completed DWR will include the information listed below:
 
The Inspector’s Daily Work Report (DWR) is a significant piece of documentation that is prepared by the inspector with the objective of summarizing the Contractor’s work and progress. It is necessary that the DWR be prepared correctly, legibly, and thoroughly. At a minimum, a completed DWR will include the information listed below:
  
* Header information (Pre-Filled)
+
# Header information (Pre-Filled)
* Weather (Also include low and high temperatures)
+
# Weather (Also include low and high temperatures)
* Contractor Workforce (Operator, Laborer, Finisher, etc.)
+
# Contractor Workforce (Operator, Laborer, Finisher, etc.)
* Equipment used (If force account, Form 1101A must be used)
+
# Equipment used (If force account, Form 1101A must be used)
* Number of personnel for each contractor (If force account, Form 1101A must be used)
+
# Number of personnel for each contractor (If force account, Form 1101A must be used)
* Starting and ending Hours for each contractor in the comments section (If force account, Form 1101A must be used.)  
+
# Starting and ending Hours for each contractor in the comments section (If force account, Form 1101A must be used.)  
* Clearly show all computations along with conversion factors and their associated units using the [http://mdotwiki.state.mi.us/construction/index.php/FieldManager#Standard_Rounding_Convention_Guidance Standard Rounding Convention Guidance].
+
# Clearly show all computations along with conversion factors and their associated units using the [http://mdotwiki.state.mi.us/construction/index.php/FieldManager#Standard_Rounding_Convention_Guidance Standard Rounding Convention Guidance].
* Pay item location (Be specific – Plan sheet’s, distance from center line, stationing, etc.)
+
# Pay item location (Be specific – Plan sheet’s, distance from center line, stationing, etc.)
* Quantity Posted with supporting documentation
+
# Checkmarks placed next to verified computations (Only if there is a separate attachment)
* Checkmarks placed next to verified computations (Only if there is a separate attachment)
+
# Proper association of all materials to their corresponding pay items, along with visual inspection, must be documented on DWR’s
* Proper association all materials to pay item along with visual inspection must be documented on DWR’s
+
# Inspectors should complete and submit DWR’s  no later than the first workday after the work was performed. The sooner the information is documented, the more accurate it will be. Additionally, both the personnel submitting and those approving DWRs should consider the timelines required for pay estimate processing.
* Inspectors should complete and submit reports no later than the first workday after the work was performed. The sooner the information is put in writing, the more accurate it will be. Additionally, personnel submitting and approving DWR’s need to consider time frames for pay estimate processing.
+
# The actual date the work was performed must be used when reporting a missed pay item on a DWR.
* The actual work performed date will be used when reporting a missed pay item on a DWR.
+
# Any pay quantities reported on a DWR must have supporting calculations. Calculations included within or directly attached to a DWR in AASHTOWare do not require a check mark, as approval of the DWR implies that the approver has reviewed and verified the accuracy of all calculations.
 
+
# Calculations within any forms or other documents which are not directly attached to a DWR in AASHTOWare must include check marks next to them, along with initials of the reviewer who verified their accuracy. This requirement applies to all calculations stored separately including those housed in ProjectWise.
[[File:Figure 101.04-1 stamp example2.png|thumb|center|800px|Sample DWR Review Stamp]]
+
# It is recommended that DWR attachments in AASHTOWare be generally  limited to quantity calculation sheets and project- related photos (optional). Project- related photos may be stored separately in ProjectWise, if preferred by the Project Office/Engineer.
 
+
# All DWR calculation attachments must be stored in the designated Folder 208 – Miscellaneous in ProjectWise. All MDOT forms must continue to be stored in their respective folders, as described in the Standard Naming Convention found in the Division 1 Supplemental Information section of the MDOT Construction Manual. This applies only to calculation attachments that are saved separately in ProjectWise and not directly attached to the DWR itself..
 
+
# Any other document intended for internal use only should be filed in the appropriate 400 series subfolder(s) in ProjectWise and should not be attached to the DWR.
 +
# The exact nomenclature and pay item code number shown in the proposal must be used when submitting  a pay item. Any inaccuracies  in nomenclature or code can be misleading, as many contracts include pay items with similar descriptions.
 +
# DWR’s will include applicable Subcontractor information, final pay item quantities,and final pay item field measurement. These items should be clearly labeled as final field measured or FFM. The DWR should also document associated pay item test material usage and comments, including remarks on maintaining traffic and traffic control devices. Daily checks of traffic devices must be recorded.
 +
# Comments on the contractor’s attitude and quality of work may also be included. Additional details to document include public complaints and the inspector’s responses, unusual events, daily weather conditions, and any accidents.
 +
# It is the senior technician’s responsibility to (a) review and ensure the accuracy of the DWR with respect to field quantities, work performed, and computations, and then submit it to the office technician, and (b) ensure that DWRs are entered into the system daily. The office technician is responsible for reviewing and approving the DWRs to verify their accuracy prior to final submission.
  
* Any pay quantities reported on a DWR must have supporting calculations.  Any calculations included within, or attached directly to, a DWR in AASHTOWare do not need a check mark next to the calculations.  It is assumed that approval of the DWR means that all calculations were checked by the DWR approver and were verified to be correct.
 
* Calculations within any forms or other documents which are not directly attached to a DWR in AASHTOWare do need check marks next to them along with the initials of the reviewer who verified that the calculations were correct.  This applies to any calculations stored separately including those in ProjectWise. 
 
* It is recommended that DWR attachments in AASHTOWare generally be limited to quantity calculation sheets and project related photos (optional).  Project related photos may be stored separately in ProjectWise, if preferred by the Project Office/Engineer.
 
* Numbered forms and other documents described in the Standard Naming Convention in the Division 1 Supplemental Information section of the MDOT Construction Manual should be filed in the appropriate subfolder in ProjectWise. 
 
* Any other document that is for internal use only should be filed in the 400 series subfolder(s) in Projectwise and should not be attached to the DWR.
 
* The exact nomenclature and pay item code number shown in the proposal must be used when turning in a pay item. Any inaccuracy in nomenclature or code can be misleading, as many contracts contain pay items with similar nomenclature.
 
* DWR’s will include applicable Subcontractor information, final pay item quantities, final pay item field measurement (these items should be clearly labeled as final field measured or FFM), associated pay item test material usage and comments, comments on maintaining traffic and maintenance of traffic devices (traffic device checks must be recorded daily). Comments on attitude and quality of Contractor’s work may also be recorded.  Other details that should be recorded include complaints from the public, along with inspector responses to these complaints, unusual events, daily weather conditions and accidents.
 
* It is always the senior technician’s responsibility to (a) review and ensure accuracy of the DWR with respect to field quantities/work/computations and turn them into the office technician, and (b) ensure that the DWR’s are entered into the system daily. The office technician will approve the DWR’s upon reviewing to ensure  accuracy of the submitted DWR.
 
  
 
Questions regarding this process can be answered by contacting the Helpdesk email: [mailto:MDOT-ConstructionSoftware@michigan.gov MDOT-ConstructionSoftware@michigan.gov].
 
Questions regarding this process can be answered by contacting the Helpdesk email: [mailto:MDOT-ConstructionSoftware@michigan.gov MDOT-ConstructionSoftware@michigan.gov].

Latest revision as of 10:36, 29 July 2025


Email this Page



Inspector's Daily Work Report (DWR)

This information is for AASHTOWare contracts, for FieldManager contracts please see Inspectors Daily Report (IDR) page.

The Inspector’s Daily Work Report (DWR) is a significant piece of documentation that is prepared by the inspector with the objective of summarizing the Contractor’s work and progress. It is necessary that the DWR be prepared correctly, legibly, and thoroughly. At a minimum, a completed DWR will include the information listed below:

  1. Header information (Pre-Filled)
  2. Weather (Also include low and high temperatures)
  3. Contractor Workforce (Operator, Laborer, Finisher, etc.)
  4. Equipment used (If force account, Form 1101A must be used)
  5. Number of personnel for each contractor (If force account, Form 1101A must be used)
  6. Starting and ending Hours for each contractor in the comments section (If force account, Form 1101A must be used.)
  7. Clearly show all computations along with conversion factors and their associated units using the Standard Rounding Convention Guidance.
  8. Pay item location (Be specific – Plan sheet’s, distance from center line, stationing, etc.)
  9. Checkmarks placed next to verified computations (Only if there is a separate attachment)
  10. Proper association of all materials to their corresponding pay items, along with visual inspection, must be documented on DWR’s
  11. Inspectors should complete and submit DWR’s no later than the first workday after the work was performed. The sooner the information is documented, the more accurate it will be. Additionally, both the personnel submitting and those approving DWRs should consider the timelines required for pay estimate processing.
  12. The actual date the work was performed must be used when reporting a missed pay item on a DWR.
  13. Any pay quantities reported on a DWR must have supporting calculations. Calculations included within or directly attached to a DWR in AASHTOWare do not require a check mark, as approval of the DWR implies that the approver has reviewed and verified the accuracy of all calculations.
  14. Calculations within any forms or other documents which are not directly attached to a DWR in AASHTOWare must include check marks next to them, along with initials of the reviewer who verified their accuracy. This requirement applies to all calculations stored separately including those housed in ProjectWise.
  15. It is recommended that DWR attachments in AASHTOWare be generally limited to quantity calculation sheets and project- related photos (optional). Project- related photos may be stored separately in ProjectWise, if preferred by the Project Office/Engineer.
  16. All DWR calculation attachments must be stored in the designated Folder 208 – Miscellaneous in ProjectWise. All MDOT forms must continue to be stored in their respective folders, as described in the Standard Naming Convention found in the Division 1 Supplemental Information section of the MDOT Construction Manual. This applies only to calculation attachments that are saved separately in ProjectWise and not directly attached to the DWR itself..
  17. Any other document intended for internal use only should be filed in the appropriate 400 series subfolder(s) in ProjectWise and should not be attached to the DWR.
  18. The exact nomenclature and pay item code number shown in the proposal must be used when submitting a pay item. Any inaccuracies in nomenclature or code can be misleading, as many contracts include pay items with similar descriptions.
  19. DWR’s will include applicable Subcontractor information, final pay item quantities,and final pay item field measurement. These items should be clearly labeled as final field measured or FFM. The DWR should also document associated pay item test material usage and comments, including remarks on maintaining traffic and traffic control devices. Daily checks of traffic devices must be recorded.
  20. Comments on the contractor’s attitude and quality of work may also be included. Additional details to document include public complaints and the inspector’s responses, unusual events, daily weather conditions, and any accidents.
  21. It is the senior technician’s responsibility to (a) review and ensure the accuracy of the DWR with respect to field quantities, work performed, and computations, and then submit it to the office technician, and (b) ensure that DWRs are entered into the system daily. The office technician is responsible for reviewing and approving the DWRs to verify their accuracy prior to final submission.


Questions regarding this process can be answered by contacting the Helpdesk email: MDOT-ConstructionSoftware@michigan.gov.


A sample 11-Page DWR is shown in Figure 101-1.


[top of page]