Validation Checklist

Use this checklist before sharing a sponsor-filled Project Information Model workspace with Atlas, reviewers, lenders, regulators, or implementation partners.

Automated Structural Check

Run:

node scripts/validate-template.mjs

For a filled Project Information Model, run:

node scripts/validate-template.mjs --strict

Strict mode reports common placeholder tokens such as REPLACE: so the sponsor can clean final text before formal submission.

Manual Project Information Model Completeness Check

Check	How to Review	Status
Navigation resolves	Open every SUMMARY.md link and confirm the target file exists.	REPLACE: Pending / Complete
Project metadata is current	Review pim.yaml for legal names, site, currency, contacts, and Project Information Model status.	REPLACE: Pending / Complete
Confidentiality is appropriate	Confirm the project repository is private unless publication has been explicitly approved.	REPLACE: Pending / Complete
Information requirements are defined	Confirm required project information is listed with owners, reviewers, evidence locations, and status.	REPLACE: Pending / Complete
Information delivery is planned	Confirm required information is tied to due milestones, decision uses, and accountable parties.	REPLACE: Pending / Complete
Information containers are registered	Confirm major chapters, files, maps, drawings, registers, and evidence packages have stable IDs and review states.	REPLACE: Pending / Complete
Chapter placeholders are filled	Search for REPLACE: and decide whether each remaining token is intentional.	REPLACE: Pending / Complete
Tables are usable	Confirm every editable table has project-specific rows, owners, dates, and evidence links where relevant.	REPLACE: Pending / Complete
Assets are present	Confirm photos, maps, drawings, and diagrams named in chapters are stored under assets/.	REPLACE: Pending / Complete
Evidence is traceable	Confirm appendices/evidence-register.md lists source files for material claims.	REPLACE: Pending / Complete
Acceptance criteria are clear	Confirm decision points have review criteria, reviewers, and acceptance evidence.	REPLACE: Pending / Complete
Financial model is traceable	Confirm data/financial-model.xlsx has assumptions, sources, formulas, and review notes.	REPLACE: Pending / Complete
Risk and clearances trackers are current	Confirm CSV trackers in data/ have owners, dates, and status values.	REPLACE: Pending / Complete
Sensitive files are intentional	Check that contracts, personal data, land records, maps, and correspondence are approved for the repository audience.	REPLACE: Pending / Complete
Safeguards information is complete	Confirm environmental, social, community, and safety obligations are assigned and connected to evidence.	REPLACE: Pending / Complete
Handover is ready	Confirm operating records, owners, update cycles, Atlas destinations, and material-event triggers are documented.	REPLACE: Pending / Complete

Atlas Readiness Check

Atlas Input	File or Folder	Review Notes
Navigation	SUMMARY.md	Chapter order should match the sponsor’s intended viewer order.
Project metadata	pim.yaml	Keep field names stable so Atlas import rules can map them.
Narrative pages	00-project-profile.md through 16-operations-maintenance.md	Markdown should render without broken internal links.
Trackers	data/*.csv	Keep headers intact unless Atlas mapping is updated.
Financial model	data/financial-model.xlsx	Keep workbook tabs named clearly and preserve formulas.
Evidence	appendices/ and assets/	Files should use stable names and avoid duplicates.
Information requirements	information-requirements.md	Requirement IDs should remain stable once shared with reviewers.
Delivery plan	information-delivery-plan.md	Due milestones and reviewer assignments should match the implementation plan.
Container register	information-container-register.md	Container IDs should map to chapters, files, and Atlas destinations.
Handover register	asset-information-handover.md	Operating owners, update cycles, and Atlas destinations should be complete before handover.