Contractual Notice Tracking Construct Ai Primary

---
name: contractual-notice-tracking-construct-ai-primary
title: Contractual Notice Tracking
description: Track all contractual notices, time bars, and conditions precedent to preserve rights
author: Construct-AI-primary
author_url: https://github.com/Construct-AI-primary/agent-companies-paperclip/tree/main/doc/companies.bak/construct-ai/00435_contracts-post-award/contractual-notice-tracking
license: MIT
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: contracts
language: en
---

# Contractual Notice Tracking

## Overview
Track all contractual notices, time bars, and conditions precedent to preserve rights

**Announce at start:** "I'm using the contractual-notice-tracking skill for Contracts Post-Award operations."

## When to Use This Skill
**Trigger Conditions:** Track all contractual notices, time bars, and conditions precedent to preserve rights task required, discipline-specific task or request received
**Prerequisites:**
- Domain knowledge available (Contracts Post-Award domain knowledge)
- Appropriate authority and permissions granted
- Relevant inputs and reference documents accessible
- Required coordination with related disciplines confirmed

## Step-by-Step Procedure

### Step 1: Initiation and Scoping
1. Identify the specific contracts post-award task triggering this skill
2. Verify the requestor has appropriate authority
3. Gather all required input documents, drawings, specifications, and supporting data
4. Confirm scope clearly matches this skill's purpose; escalate if out of scope

### Step 2: Analysis and Assessment
1. Review relevant domain knowledge sections for this discipline
2. Identify applicable standards, codes, specifications, and regulatory requirements
3. Assess dependencies on other disciplines, agents, or data sources
4. Document any gaps, ambiguities, or conflicting requirements

### Step 3: Execution
1. Apply discipline-specific methods and tools for track all contractual notices, time bars, and conditions precedent to preserve rights
2. Generate required outputs using approved templates, formats, and systems
3. Maintain full audit trail of all actions, calculations, decisions, and outputs
4. Cross-reference with related contracts, policies, standards, and specifications

### Step 4: Quality Review
1. Validate all outputs against domain knowledge requirements and applicable standards
2. Verify compliance with regulatory requirements and project specifications
3. Ensure required documentation is complete, accurate, and properly formatted
4. Identify any exceptions, deviations, or non-standard items for specialist review

### Step 5: Approval and Routing
1. Route outputs through appropriate approval workflow based on value/complexity
2. Verify approval authority matches delegated authority limits
3. Incorporate any required revisions from reviewers
4. Obtain final approval and sign-off from authorized personnel

### Step 6: Close-Out and Filing
1. File all outputs in appropriate registers and repositories (EDMS, project registers)
2. Update relevant tracking systems and databases
3. Archive working documents per project retention policy
4. Update contracts post-award records, logs, and registers

## Success Criteria
- [ ] Task scope clearly defined and authorized
- [ ] All required inputs gathered and validated
- [ ] Contractual Notice Tracking output generated per requirements
- [ ] Compliance with applicable standards and codes verified
- [ ] Quality review completed and documented
- [ ] Approval obtained through proper workflow
- [ ] Outputs filed in appropriate registers
- [ ] Audit trail complete and accurate
- [ ] Contractual Notice Tracking completed successfully

## Common Pitfalls
1. **Incomplete Inputs** — Attempting execution without all required documents or data. Always verify completeness before starting.
2. **Outdated References** — Using superseded specifications, codes, or drawing revisions. Always check for current versions in EDMS.
3. **Missing Authority** — Acting beyond delegated authority limits. Always verify approver authority before routing.
4. **Inadequate Documentation** — Failing to maintain audit trail or file outputs properly. Every action requires documentation.
5. **Non-Compliant Outputs** — Generating outputs that don't meet applicable standards. Always validate against requirements before approval.
6. **Inter-Discipline Gaps** — Not coordinating with affected disciplines. Always identify and communicate interface impacts.

## Cross-References

### Related Skills
- Additional contracts post-award skills for related functions
- Skills from interfacing disciplines for cross-functional tasks

### Related Agents
- **Primary:** Contracts Engineer — Main execution
- **Supporting:** Contracts Post-Award Administrator — Document and data management
- **Oversight:** Contracts Post-Award Manager — Review, approval, and escalation

### Related Domain Knowledge
- Contracts Post-Award Domain Knowledge for role responsibilities and frameworks
- Contracts Post-Award Glossary for terminology, definitions, and abbreviations