Inspector’s Daily Work Report (DWR) - Revision history

Clarkj25: /* Inspector's Daily Work Report (DWR) */

2025-07-29T14:36:04Z

Inspector's Daily Work Report (DWR)

Clarkj25: /* Inspector's Daily Work Report (DWR) */

2025-07-28T20:14:55Z

Inspector's Daily Work Report (DWR)

Clarkj25: /* Inspector's Daily Work Report (DWR) */

2025-07-28T20:13:45Z

Inspector's Daily Work Report (DWR)

Clarkj25: /* Inspector's Daily Work Report (DWR) */

2025-07-28T20:12:33Z

Inspector's Daily Work Report (DWR)

Clarkj25 at 20:04, 28 July 2025

2025-07-28T20:04:37Z

Clarkj25 at 22:03, 4 February 2025

2025-02-04T22:03:58Z

Clarkj25: /* Inspector's Daily Work Report (DWR) */

2025-01-22T13:47:31Z

Inspector's Daily Work Report (DWR)

Clarkj25 at 13:46, 22 January 2025

2025-01-22T13:46:29Z

Clarkj25 at 13:40, 22 January 2025

2025-01-22T13:40:37Z

Clarkj25 at 13:37, 22 January 2025

2025-01-22T13:37:08Z

@@ Line 31: / Line 31: @@
 # 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.'''
+# 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."'''
+# 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.

@@ Line 32: / Line 32: @@
 # 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."
+# '''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."'''
-'''# 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
+# 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.

@@ Line 31: / Line 31: @@
 # 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.
+# 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."
+# '''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."
-# 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
+'''# 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

@@ Line 15: / Line 15: @@
 # Header information (Pre-Filled)
 # 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.
-* 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 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.
-* 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 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.
-* 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.
+# 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..
-* 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 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.
-* 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 submitting  a pay item. Any inaccuracies  in nomenclature or code can be misleading, as many contracts include pay items with similar descriptions.
-* 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,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.
-* 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.
+# 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 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.
+# 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: [mailto:MDOT-ConstructionSoftware@michigan.gov MDOT-ConstructionSoftware@michigan.gov].

@@ Line 13: / Line 13: @@
 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.)
 * Equipment used (If force account, Form 1101A must be used)

@@ Line 9: / Line 9: @@
 ==[[#Inspector's Daily Work Report (DWR)|Inspector's Daily Work Report (DWR)]]==
-This information is for AASHTOWare contracts, for FieldManager contracts please see [[https://mdotwiki.state.mi.us/construction/index.php?title=FieldManager#Inspector.27s_Daily_Report_.28IDR.29|Inspectors Daily Report (IDR) page]].
+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:

← Older revision		Revision as of 13:46, 22 January 2025
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 [[https://mdotwiki.state.mi.us/construction/index.php?title=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:

← Older revision		Revision as of 13:40, 22 January 2025
Line 48:		Line 48:

	{{top}}		{{top}}
−
−
−
−
−	~~<div style="text-align: right;">[mailto:Change?body=http://mdotwiki.state.mi.us/construction/index.php/FieldManager Email this Page]</div>~~
−	~~{{top}}~~
−
−	~~==[[#Contractor Read-Only Files\|Contractor Read-Only Files]]==~~
−	Prime contractors are eligible to receive read-only copies of FieldManager files for their awarded contracts. Subcontractors are eligible to receive read-only copies of FieldManager files with approved subcontracts. This applies for all projects let through the Michigan Department of Transportation (MDOT). Managing offices use FieldManager’s read-only distribution function, which automatically sends contractor read-only copies whenever construction pay estimate reports are generated. On rare occasions contractors may also request an additional contractor read-only copy during a time frame that is outside of the normal construction pay estimate report process. These contractor read-only copies can be sent upon mutual agreement of the Engineer.
−
−	~~This policy encourages managing offices and contractors to take advantage of the following contractor read-only benefits:~~
−	*Improved communication between managing offices and contractors.
−	*Reduced time required to gather information for contractors
−	*Reduced volume of questions from contractors
−	*More accurate and timely information from contractors
−	*Earlier identification of errors and concerns
−	*More current material tracking
−	*More efficient discussions concerning item and material status reviews
−	*More efficient review of contract modifications
−	*Timelier responses from MDOT during the busy construction season
−	*Improved quality and timeliness of Inspector Daily Reports (DWRs)
−	*Improved contract finalization process
−	*Elimination of some contractor spreadsheets and hand-generated data
−	*Elimination of difficulties related to viewing information received due to poor quality faxes
−	*Improved managing office/contractor relationships
−
−	~~{{top}}~~
−	~~===[[#Managing Office Information\|Managing Office Information]]===~~
−	The managing office is to add the active FieldNet ID of the prime contractor and any subcontractors to the read-only distribution list in FieldManager. This will provide the read-only files to those contractors who have a valid FieldManager read-only license or a FieldManager contractor license.
−
−	The list of active contractor FieldNet ID’s is maintained in FieldManager. For detailed instructions on how to add FieldNet ID’s to the read-only distribution list in FieldManager, consult the [http://stateofmichigan.sharepoint.com/sites/mdot/Organizational/field_services/construction/Shared%20Documents/ugsup_dot_53a.pdf FieldManager User’s Guide Supplement (For MDOT Offices)].
−
−	~~{{top}}~~
−	~~===[[#Contractor Information\|Contractor Information]]===~~
−	Contractors must obtain a FieldManager license to receive contractor read-only copies. Licenses can be obtained by purchasing a FieldManager read-only license or a FieldManager contractor license from Info Tech, Inc. at 352-381-4400 or [mailto:info@infotechfl.com info@infotechfl.com]. See [http://www.fieldmanager.com www.fieldmanager.com]
−	~~for prices.~~
−
−	MDOT certified Disadvantaged Business Enterprise (DBE) firms performing the types of work that utilize FieldManager may obtain their license through MDOT’s DBE FieldManager Volume Purchase Agreement. Contact MDOT’s Business Development Division at 517-241-4806 for details.
−
−	When installing FieldManager, contractors must configure the software as specified in MDOT’s [http://www.michigan.gov/documents/mdot/ugsup_cnt_53_555649_7.pdf FieldManager User’s Guide Supplement (For Michigan Contractors)].
−
−	Contractors must keep their release of FieldManager current to continue receiving contractor read-only copies. All license types include delivery of new FieldManager releases issued during the license period.
−
−	~~{{top}}~~
−	~~===[[#MDOT Read-Only Files for Consultant Contracts\|MDOT Read-Only Files for Consultant Contracts]]===~~
−	To respond in a timely manner to audit and Federal Highway Administration (FHWA) requests, files must be up-to-date in the MDOT FieldManager system. A manually generated FieldManager read-only file must be submitted to the managing MDOT Transportation Service Center (TSC) office by the consultant hired by MDOT prior to the start of construction operations. An updated read-only file must also be provided with the submission of each bi-weekly pay estimate. The updated read-only file can be automatically sent by using FieldManager’s read-only distribution list. This distribution is required for all MDOT consultant oversight projects
−
−	~~Consultant offices must use FieldManager’s read-only distribution function. MDOT may also request a read-only copy at any time during the life of the contract.~~
−
−	For detailed instructions on how to send manual and automatic updates using the read-only distribution list in FieldManager, consult the FieldManager User’s Guide Supplement (For Michigan Local Agencies and Consultants).
−
−	~~If you have any questions regarding this information, please contact the Helpdesk email [mailto:MDOT-ConstructionSoftware@michigan.gov MDOT-ConstructionSoftware@michigan.gov].~~
−
−	~~<div style="text-align: right;">[mailto:Change?body=http://mdotwiki.state.mi.us/construction/index.php/FieldManager Email this Page]</div>~~
−	~~{{top}}~~
−
−	~~==[[#Bi-Annual FieldManager User Account Verification Process \| Bi-Annual FieldManager User Account Verification Process]]==~~
−
−	Bi-annually, FieldManager administrators for each MDOT office must verify that FieldManager users are assigned appropriate user roles and/or access to the FieldManager system. User roles must be assigned in accordance with the Security Procedures in the latest version of the [https://stateofmichigan.sharepoint.com/sites/mdot/Organizational/field_services/construction/Shared%20Documents/FieldManager/MDOT_FieldManager_User's_Guide_Supplement_for_MDOT_Offices-Release_5.3.c.pdf?csf=1&e=IYVL7c&wdLOR=c2CE6E41F-5E95-4603-92B2-919BD048D53D&cid=ae1549e0-0411-4598-9294-13802c61222c FieldManager User’s Guide Supplement (For MDOT Offices)]. Maintenance of FieldManager user account lists is important for maintaining system security.
−
−	Every year in November and May, the Construction Technology Unit will email FieldManager administrators for each MDOT office. All offices must review their user list and ensure that users are assigned the proper security level. Any users that no longer require access to the system are to be removed. The user list must be documented and approved by the Construction Engineer. Each MDOT office is required to reply by the specified deadline and provide the signed user list. If the office does not provide the documentation by the specified deadline, the Construction Technology Unit will remove all users for that office except for the FieldManager administrator(s).
−
−	~~If your office’s user list is deleted by the Construction Technology Unit, the FieldManager administrator for your office will then need to re-create each appropriate user account.~~
−
−	~~{{top}}~~
−
−	~~==[[#LAP Project Considerations \| LAP Project Considerations]]==~~
−
−	A FieldManager read-only file must be submitted to the managing MDOT Transportation Service Center (TSC) office by the local agency prior to the start of construction operations. An updated read-only file must also be provided with the submission of each bi-weekly pay estimate. MDOT may also request a read-only copy at any time during the life of the contract. Updated read-only files can be automatically sent by using FieldManager’s read-only distribution list.
−
−
−
−
−
−
−
−