Ask a precise question.
Reference the location, system, drawing revision, observed condition, programme effect, and the decision needed. Attach only information relevant to that question.
Editorial draft / Project delivery
This placeholder field note describes a documentation habit, not a claim about a Kyriarch project, site role, or completed result. Responsibilities always depend on the engagement.
One decision record
Site conditions, supplier information, sequencing, and constructability questions can change how documented intent is delivered. The response is easier to follow when the question, reason, decision, drawing effect, and responsible party stay connected.
A field record can show what was observed and who must decide without stepping beyond the agreed authority. It can also distinguish a clarification from a design change, a proposed alternative, or an instruction.
Reference the location, system, drawing revision, observed condition, programme effect, and the decision needed. Attach only information relevant to that question.
State whether the answer is information, a clarification, a proposed change, a required redesign, or a matter for another responsible party.
Record superseded documents, affected interfaces, approvals still needed, and the current issue that the site team should use.
Plan inspections, concealed-work checks, tests, and witness points around the actual system and contract rather than relying on one generic checklist.
Gather accepted drawings, schedules, test records, operating information, outstanding items, and owners in a form the receiving team can understand.
Draft status
The final article must identify which actions Kyriarch performs under a typical engagement and which remain with the client, contractor, supplier, or another consultant.
No inspection, testing, compliance, programme, or turnover result is claimed here.
Project-specific forms, acceptance criteria, and source documents should be added only after technical and contractual review.