# Project Coordination Controls Evidence Pack

## Classification

**Independent applied case study | Synthetic project data**

This folder contains the inspectable records behind the Construction Project Coordination Controls case study. It demonstrates a complete project-coordination approach without publishing confidential source material or claiming client deployment.

## Start here

1. [`dashboard.html`](dashboard.html) presents the decision-ready weekly coordination view.
2. [`process-map.html`](process-map.html) connects procurement, commitments, meetings, changes, invoices, and closeout.
3. [`project-baseline.md`](project-baseline.md) defines the scenario, scope, authority, milestones, and operating rules.
4. [`rfp-bid-package.html`](rfp-bid-package.html) presents the solicitation and pricing package.
5. [`weekly-meeting-pack.html`](weekly-meeting-pack.html) shows agenda design, minutes, decisions, and action follow-through.
6. [`change-package-control.html`](change-package-control.html) shows the routing gate for a potential change.
7. [`invoice-routing-control.html`](invoice-routing-control.html) shows the routing gate for a pay application.
8. The CSV registers provide the detailed source records behind the visible pages.

## Evidence files

| File | Control demonstrated |
|---|---|
| [`process-map.html`](process-map.html) | Connected lifecycle, responsibility lanes, handoffs, and system-of-record discipline |
| [`rfp-bid-package.html`](rfp-bid-package.html) | Scope, exclusions, schedule, bid instructions, evaluation criteria, and bid form |
| [`bid-submission-checklist.csv`](bid-submission-checklist.csv) | Bid receipt and administrative completeness without transferring award authority |
| [`tender-register.csv`](tender-register.csv) | Solicitation, bidder communication, completeness review, evaluation, and award records |
| [`weekly-meeting-pack.html`](weekly-meeting-pack.html) | Agenda, pre-read, attendance, minutes, decisions, and action ownership |
| [`decision-log.csv`](decision-log.csv) | Decision authority, effective date, related records, boundaries, and follow-up |
| [`change-package-control.html`](change-package-control.html) | Change-package routing gates, authority boundaries, and linked evidence |
| [`change-package-checklist.csv`](change-package-checklist.csv) | Source, scope, cost, time, safety, funding, review, and disposition checks |
| [`change-log.csv`](change-log.csv) | Potential changes, quotations, cost, time, review, status, and commitment linkage |
| [`invoice-routing-control.html`](invoice-routing-control.html) | Commitment reconciliation, missing-document holds, and approval sequence |
| [`invoice-routing-checklist.csv`](invoice-routing-checklist.csv) | Billing, retainage, support, holds, routing, and final record updates |
| [`invoice-tracker.csv`](invoice-tracker.csv) | Commitment, billing, retainage, completeness, approval status, and next action |
| [`action-log.csv`](action-log.csv) | Ownership, due dates, related records, and escalation triggers |
| [`closeout-checklist.csv`](closeout-checklist.csv) | Turnover requirements, readiness, issues, deadlines, and archive location |

## Role boundary

The Project Coordinator may prepare and organize records, verify administrative completeness, route information, track ownership and deadlines, document decisions, and escalate missing information or risks.

The Project Coordinator does not independently approve contracts, technical direction, changes in scope or price, invoices, payments, final acceptance, or closeout.

## Evidence rules

- All names, dates, organizations, vendors, costs, and project records are fictional.
- The records demonstrate current controls and judgment, not client delivery or approval authority.
- No employer, agency, client, contractor, or team source document is published.
- Practical improvements are shown as controls within an established process, not replacement systems.
- System-of-record updates occur only after authorized action.

## Release status

The evidence pack is technically complete and remains on a draft branch pending final visual review and publication approval.