| S.No. | Checkpoint | IS Requirement | Status |
|---|---|---|---|
| A. Document List - Details of Documents Being Transmitted | |||
| A1 | Prepare a table with columns: S.No (1,2,3...), Document No (e.g., QC-CON-CHK-001), Title (e.g., Concrete Cube Strength Test Report, Structural Steel Inspection Report), Revision (e.g., 00, 01, 02), No. of Copies (number of physical/digital copies), Purpose (select: For Approval / For Information / For Review / As Requested) Acceptance: All columns must be filled; each row represents one document; total count of documents must be accurately reflected | Mandatory | OK NC NA HOLD |
| A2 | Document No - Record the unique document identifier. Use project code + document type code (e.g., INF-CON-TST-001 means Infralens project, Concrete material test, serial 001) Acceptance: Document number must follow project numbering convention and be traceable in project records | Mandatory | OK NC NA HOLD |
| A3 | Title - Provide clear, descriptive title that identifies the document content (e.g., "Test Report - Compressive Strength of M30 Concrete Mix Design Validation") Acceptance: Title must be specific enough that recipient immediately understands the document purpose | Mandatory | OK NC NA HOLD |
| A4 | Revision Number - State the revision level (00 for first issue, 01 for first revision, etc.). Ensure that the revision transmitted matches the latest approved version Acceptance: Revision number must match the document header; outdated revisions must not be transmitted without explicit reason | Mandatory | OK NC NA HOLD |
| A5 | Number of Copies - State how many hard/soft copies are being transmitted (e.g., 2 printed sets, 1 digital copy via email) Acceptance: Number of copies must match actual transmittal; if multiple recipients, each row may have different copy counts | Mandatory | OK NC NA HOLD |
| A6 | Purpose - Select one: (1) For Approval - recipient must approve before work proceeds, (2) For Information - FYI only, no response required, (3) For Review - recipient must review and comment, (4) As Requested - per specific request from recipient Acceptance: Purpose must be clearly selected; this drives response tracking requirements | Mandatory | OK NC NA HOLD |
| B. Action Required from Recipient | |||
| B1 | Select action required: Review & Approve (return approved copy with signature), Review & Comment (provide comments/feedback), For Information (no action required - FYI), For Record (file without action) Acceptance: One action type must be clearly selected for entire transmittal or per document if varying actions apply | Mandatory | OK NC NA HOLD |
| C. Response Tracking | |||
| C1 | Response Due Date - State the date by which recipient must respond (if applicable). Leave blank if no response required (For Information documents) Acceptance: Due date must allow reasonable time for review; must be at least 3-5 working days unless otherwise agreed | Conditional | OK NC NA HOLD |
| C2 | Response Received Date - Record the actual date when response is received (approval, comments, or confirmation of receipt) Acceptance: If response was due, this field must be completed; if response is overdue, escalate per project procedures | Conditional | OK NC NA HOLD |
| C3 | Response Status - State: Received & Approved, Received & Under Review, Received With Comments, Not Yet Received (overdue), Acknowledged Acceptance: Status must be updated as responses are received; overdue items must trigger follow-up | Conditional | OK NC NA HOLD |