# Project Controls ### Purpose Project controls ensure that delivery is planned, tracked, and governed. ### Required Controls Each project should maintain: * approved Statement of Work * delivery plan * project initiation document * governance cadence * RAID log * change log * decision log * dependency log * milestone tracker * acceptance register * financial tracker * resourcing plan ### Control Reviews Controls should be reviewed: * at mobilisation * before each milestone * during weekly delivery reviews * before customer governance meetings * when a major risk or change occurs * before acceptance * at closure ### Control Ownership The Delivery Lead owns project controls. The Commercial Lead owns commercial controls. The Technical Lead owns technical controls. The Security Lead owns security controls. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://framework.aic.io/company-operating-manual/delivery-governance/project-controls.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.