Scheduling Progress Update and Schedule Monitoring
Overview
Update schedules with actual progress, analyze variance from baseline, forecast completion
Announce at start: "I'm using the sched-progress-update-monitoring skill for Scheduling operations."
When to Use This Skill
Trigger Conditions: Update schedules with actual progress, analyze variance from baseline, forecast completion task required, discipline-specific task or request received
Prerequisites:
- Domain knowledge available (Scheduling 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
- Identify the specific scheduling task triggering this skill
- Verify the requestor has appropriate authority
- Gather all required input documents, drawings, specifications, and supporting data
- Confirm scope clearly matches this skill's purpose; escalate if out of scope
Step 2: Analysis and Assessment
- Review relevant domain knowledge sections for this discipline
- Identify applicable standards, codes, specifications, and regulatory requirements
- Assess dependencies on other disciplines, agents, or data sources
- Document any gaps, ambiguities, or conflicting requirements
Step 3: Execution
- Apply discipline-specific methods and tools for update schedules with actual progress, analyze variance from baseline, forecast completion
- Generate required outputs using approved templates, formats, and systems
- Maintain full audit trail of all actions, calculations, decisions, and outputs
- Cross-reference with related contracts, policies, standards, and specifications
Step 4: Quality Review
- Validate all outputs against domain knowledge requirements and applicable standards
- Verify compliance with regulatory requirements and project specifications
- Ensure required documentation is complete, accurate, and properly formatted
- Identify any exceptions, deviations, or non-standard items for specialist review
Step 5: Approval and Routing
- Route outputs through appropriate approval workflow based on value/complexity
- Verify approval authority matches delegated authority limits
- Incorporate any required revisions from reviewers
- Obtain final approval and sign-off from authorized personnel
Step 6: Close-Out and Filing
- File all outputs in appropriate registers and repositories (EDMS, project registers)
- Update relevant tracking systems and databases
- Archive working documents per project retention policy
- Update scheduling records, logs, and registers
Success Criteria
Common Pitfalls
- Incomplete Inputs — Attempting execution without all required documents or data. Always verify completeness before starting.
- Outdated References — Using superseded specifications, codes, or drawing revisions. Always check for current versions in EDMS.
- Missing Authority — Acting beyond delegated authority limits. Always verify approver authority before routing.
- Inadequate Documentation — Failing to maintain audit trail or file outputs properly. Every action requires documentation.
- Non-Compliant Outputs — Generating outputs that don't meet applicable standards. Always validate against requirements before approval.
- Inter-Discipline Gaps — Not coordinating with affected disciplines. Always identify and communicate interface impacts.
Cross-References
Related Skills
- Additional scheduling skills for related functions
- Skills from interfacing disciplines for cross-functional tasks
Related Agents
- Primary: Scheduler — Main execution
- Supporting: Scheduling Administrator — Document and data management
- Oversight: Scheduling Manager — Review, approval, and escalation
Related Domain Knowledge
- Scheduling Domain Knowledge for role responsibilities and frameworks
- Scheduling Glossary for terminology, definitions, and abbreviations
1---2name: sched-progress-update-monitoring3title: Scheduling Progress Update and Schedule Monitoring4description: Update schedules with actual progress, analyze variance from baseline, forecast completion5version: 1.06frequency_percent: 60.07success_rate_percent: 87.08memory_layer: durable_knowledge9para_section: docs_construct_ai/skills/domainforge_ai/02035_scheduling/sched-progress-update-monitoring10gigabrain_tags: disciplines, 02035_scheduling, sched-progress-update-monitoring, scheduling11openstinger_context: 02035_scheduling_operations, skill-execution12last_updated: 2026-04-0213related_docs:14 - docs_construct_ai/disciplines/02035_scheduling/agent-data/domain-knowledge/02035_DOMAIN-KNOWLEDGE.MD15---1617# Scheduling Progress Update and Schedule Monitoring1819## Overview20Update schedules with actual progress, analyze variance from baseline, forecast completion2122**Announce at start:** "I'm using the sched-progress-update-monitoring skill for Scheduling operations."2324## When to Use This Skill25**Trigger Conditions:** Update schedules with actual progress, analyze variance from baseline, forecast completion task required, discipline-specific task or request received26**Prerequisites:**27- Domain knowledge available (Scheduling domain knowledge)28- Appropriate authority and permissions granted29- Relevant inputs and reference documents accessible30- Required coordination with related disciplines confirmed3132## Step-by-Step Procedure3334### Step 1: Initiation and Scoping351. Identify the specific scheduling task triggering this skill362. Verify the requestor has appropriate authority373. Gather all required input documents, drawings, specifications, and supporting data384. Confirm scope clearly matches this skill's purpose; escalate if out of scope3940### Step 2: Analysis and Assessment411. Review relevant domain knowledge sections for this discipline422. Identify applicable standards, codes, specifications, and regulatory requirements433. Assess dependencies on other disciplines, agents, or data sources444. Document any gaps, ambiguities, or conflicting requirements4546### Step 3: Execution471. Apply discipline-specific methods and tools for update schedules with actual progress, analyze variance from baseline, forecast completion482. Generate required outputs using approved templates, formats, and systems493. Maintain full audit trail of all actions, calculations, decisions, and outputs504. Cross-reference with related contracts, policies, standards, and specifications5152### Step 4: Quality Review531. Validate all outputs against domain knowledge requirements and applicable standards542. Verify compliance with regulatory requirements and project specifications553. Ensure required documentation is complete, accurate, and properly formatted564. Identify any exceptions, deviations, or non-standard items for specialist review5758### Step 5: Approval and Routing591. Route outputs through appropriate approval workflow based on value/complexity602. Verify approval authority matches delegated authority limits613. Incorporate any required revisions from reviewers624. Obtain final approval and sign-off from authorized personnel6364### Step 6: Close-Out and Filing651. File all outputs in appropriate registers and repositories (EDMS, project registers)662. Update relevant tracking systems and databases673. Archive working documents per project retention policy684. Update scheduling records, logs, and registers6970## Success Criteria71- [ ] Task scope clearly defined and authorized72- [ ] All required inputs gathered and validated73- [ ] Scheduling Progress Update and Schedule Monitoring output generated per requirements74- [ ] Compliance with applicable standards and codes verified75- [ ] Quality review completed and documented76- [ ] Approval obtained through proper workflow77- [ ] Outputs filed in appropriate registers78- [ ] Audit trail complete and accurate79- [ ] Scheduling Progress Update and Schedule Monitoring completed successfully8081## Common Pitfalls821. **Incomplete Inputs** — Attempting execution without all required documents or data. Always verify completeness before starting.832. **Outdated References** — Using superseded specifications, codes, or drawing revisions. Always check for current versions in EDMS.843. **Missing Authority** — Acting beyond delegated authority limits. Always verify approver authority before routing.854. **Inadequate Documentation** — Failing to maintain audit trail or file outputs properly. Every action requires documentation.865. **Non-Compliant Outputs** — Generating outputs that don't meet applicable standards. Always validate against requirements before approval.876. **Inter-Discipline Gaps** — Not coordinating with affected disciplines. Always identify and communicate interface impacts.8889## Cross-References9091### Related Skills92- Additional scheduling skills for related functions93- Skills from interfacing disciplines for cross-functional tasks9495### Related Agents96- **Primary:** Scheduler — Main execution97- **Supporting:** Scheduling Administrator — Document and data management98- **Oversight:** Scheduling Manager — Review, approval, and escalation99100### Related Domain Knowledge101- Scheduling Domain Knowledge for role responsibilities and frameworks102- Scheduling Glossary for terminology, definitions, and abbreviations