This construction meeting agenda template carries the question and its related records into an administrative coordination discussion. It keeps a received answer distinct from a reviewed submittal, an authorized change and permission to perform work.
Bring the question and its references together
Use this original fictional packet:
| Record | Administrative subject | Supplied state | Missing evidence |
|---|---|---|---|
| RFI01 | Which supplied finish reference applies to room label R12? | Response missing; open | Response reference and confirmed responsible party |
| S01 | Related submittal linked to RFI01 | Sent for review; awaiting design-representative response | Actual review response and applicable approval record |
| CP01 | Related proposed change linked to RFI01/S01 | Proposed | Confirmed cost/schedule impact and authorization |
R12 is a fictional room label. This packet supplies no finish selection, building detail or installation instruction. The actual source document references, requested dates, responsible parties and approval route are TO CONFIRM from the project's maintained records.
The University of Maryland's general requirements include progress-meeting discussion of submittals, requests for interpretation and pending changes. We use that coordination concept, not the university's contractual meeting frequency, response periods or approval rules. Division 1 — General Requirements
For every agenda item, retain record ID, title, source reference, requested date, response reference, responsible party and next check. An empty response field is an evidence gap, not a technical answer.
Use a 30-minute agenda to produce a traceable record
| Elapsed time | Discussion | Required output |
|---|---|---|
| 0–5 minutes | Previous open items | Confirm what evidence changed; retain unresolved items |
| 5–15 minutes | RFI01 question and source evidence | Exact question, missing response and proposed follow-up |
| 15–23 minutes | S01 and CP01 boundaries | Separate review status, authorization and unknown impacts |
| 23–30 minutes | Record owners and next check | Proposed action, actual route and outstanding confirmations |
The schedule totals 5 + 10 + 8 + 7 = 30 minutes. It is an illustrative agenda, not a required contractual duration.
For RFI01, ask: “Which source reference supports the question, and where would the formal response be recorded?” For S01, ask: “What review evidence is available, beyond the fact that it was sent?” For CP01, ask: “What impact and authorization records remain outstanding?” Leave actual discussion and answers blank until recorded through the project's process.
Show what changes when an answer arrives
In a separate fictional later scenario, A01 is received and recorded as a response reference for RFI01. The technical contents of A01 are not invented here. Its administrative receipt can be recorded without claiming that every related item is approved.
| Record | Effect of the fictional A01 receipt | What it does not establish |
|---|---|---|
| RFI01 | Response reference A01 recorded as received | That the answer was reviewed, fully resolved the question or authorized work |
| S01 | Related response can be located for the actual reviewer | Submittal approval |
| CP01 | Related response can inform the authorized change-review process | Approved cost, schedule change or change order |
Preserve the earlier unanswered snapshot and label the later scenario. Do not let one “received” status propagate as approval across linked records. Actual interpretation, scope and authority still come from qualified project participants and the applicable project records.
Leave unknown impacts unknown
CP01's cost and schedule impact are unknown, not zero. The packet does not provide an amount, delay estimate, completion percentage or review deadline. A meeting agenda cannot create those facts.
Use a blank action record:
Issue/record ID and source reference: ______
Question or missing evidence: ______
Response reference and receipt date, if verified: ______
Review status and supporting record: ______
Authorization status and supporting record: ______
Proposed follow-up: ______
Confirmed responsible party / project route: ______
Next check, once confirmed: ______
Actual discussion or decision: ______
The proposed follow-up for the initial RFI01 is to obtain the missing response through the actual project route. That is a preparation note, not a sent request. Keep the sender, route and next-check date unconfirmed until verified. Maintain the native issue, action and response packet; use only nonconfidential fictional data in a presentation copy.
Copy this prompt for the coordination packet
Prepare an original US-English administrative construction coordination agenda, linked status register and blank action/response record. Do not select materials, give technical building instructions, send requests or invent approval, cost, schedule or work authorization.
Original fictional RFI01 asks which supplied finish reference applies to room label R12. Response missing means open. S01 is related and sent for review, awaiting design-representative response, not approved. CP01 is a related proposed change; cost/schedule impact unknown, not zero, and not an authorized change order. No actual finish or facility details.
Fields per item: ID, title, source reference, requested date, response reference, actual responsible party TO CONFIRM and next check TO CONFIRM. Actual scope and approval route must come from maintained project records. Agenda: 5 minutes previous items, 10 RFI question/evidence, 8 submittal/change boundaries, 7 owners/next check; total 30 minutes, illustrative rather than contractual.
Separate later fictional scenario: A01 response received with its record reference. Record receipt without inventing technical answer. This does not automatically resolve the RFI, approve S01/CP01, alter the cost/schedule baseline or authorize work. Preserve the earlier unanswered snapshot; keep receipt, review, resolution and authorization evidence distinct.
Add blank issue/action/response fields for missing evidence, receipt, review, authorization, proposed follow-up, confirmed party/route, next check and actual discussion/decision. Proposed follow-up is to obtain the missing response via the actual route; no message is sent. No invented deadlines, completion percentage or university contract terms. Native administrative packet and qualified project workflow authoritative. A later sanitized HTML review remains unimplemented; controls, keyboard and width checks pending. No live integration, notifications, persistence or approval service.
Review the linked records without merging their states
The local HTML example places the question, related records and separate response/approval evidence together. NOS supports saving and rendering prepared HTML. Keep the native project records and actual authorization workflow authoritative.
Explore NOS to present the sanitized coordination packet. The meeting record should show which evidence is missing and who must confirm it, while preserving the boundary between an answer received and a change authorized.