1. CLAIMS AND DOCUMENTATION

2. WHAT IS A CLAIM? A demand or request for something considered one's due.

3. WHY IS THERE A CLAIM? The contractor feels deprived of something—usually time or money or both. The contractor believes it is someone’s fault, usually the Department, but it may be an outside entity (utility or railroad). A contract stipulation has been violated.

4. How could a contractor have a basis for a claim? We have the following: Standard Specifications Supplement Specifications Standard Drawings Plans Proposal Questions and Answers

5. Error in the contract documents

6. Project is unable to proceed due to utilities in the way

7. Communication

8. Interpretation

10. Getting started on the right track Communication (from the start of the project.) Clear, and if not, ask questions Document—email or letter Follow up if no response

11. Getting started on the right track Schedule. Must be checked and verified before work commences. Updates must be made if something changes.

12. But if things don’t go well… Standard Specification 105.13. Must file the Notice of Changed Condition/Disagreement. Must be done within 10 days that the contractor knew or should have known of the events causing the claim. IMPORTANT—Notice and Acceptance of the Notice does not: Validate the claim. Cause the work to stop. The contractor must complete the work.

13. Typical Claim Costs Direct cost Indirect cost (OH & Profit) Overhead cost

14. Documentation No such thing as too much. Examples Weather on the site Equipment-types, models, working or idle Personnel-work performed Type of work conducted daily on the project Document why a decision was made Pictures are great

15. Every project delay is different; There is no standard delay Very hard to standardize the process. Must review all the facts and make a decision that is in the best interest of the Department. Obviously, the best solution is to wait until the projects are clear and ready to be constructed. Is this going to happen? Not likely.

16. Questions?