UPSCALE CONSTRUCTION MANAGEMENT FIVE-CHECK SCHEDULE PROMPT PACK — STARTER EDITION START HERE Choose one upcoming activity or a tightly defined work package. Use current, authorized documents. Record revisions and pages. Begin with the file inventory. Keep model output provisional until a qualified reviewer checks every finding and source. Dense drawings, scans and missing schedule logic may require additional preparation or manual review. 01 · Schedule versus drawings Review the supplied schedule and selected current drawings for the named upcoming activity or work package. First list the files, revisions and pages you can read and identify missing or unreadable information. Compare scheduled scope with the drawing requirements. Look for openings, sleeves, embedded items, access and unresolved details that may be prerequisites. For every finding, return: concern; exact schedule activity ID if visible; drawing number, revision and detail/page; a short supporting excerpt or location; question for the team; proposed responsible role; and when the answer is needed. Separate confirmed document discrepancies from possible concerns and information gaps. Never invent references or infer that absence from the selected files means absence from the whole project. Do not certify readiness. End with a human verification checklist. 02 · Schedule versus procurement Compare the supplied schedule with the current procurement/submittal log for the selected work package. Check whether submission, review, approval, fabrication, delivery and installation dates are consistent. Identify prerequisites and missing dates. Use only visible dates and documented lead times. For each potential conflict, cite the activity and log row/item, show the dates, explain the question and propose follow-up. Do not equate a delivery mismatch with a project completion delay. List the schedule logic, calendars and other information needed to assess impact; if a PDF does not contain them, say so. 03 · Schedule versus changes Using the supplied change documentation, revised drawings and schedule, identify work that may need added activities, revised sequencing, procurement or coordination with following trades. Separate approved changes from proposals or unresolved requests. Cite the specific change reference, drawing revision and activity where visible. Return a short evidence-based follow-up list. Do not determine entitlement, cost or completion impact without supporting contract and schedule analysis. Flag missing information and assumptions explicitly. 04 · Drawings versus specifications For the selected activity, compare supplied drawings and specifications for mockups, approvals, testing, inspections, curing, protection and prerequisites before concealment or the next trade. Cite section number, paragraph/page and relevant drawing/detail where visible. Identify mismatches or schedule allowances that need confirmation. Do not invent technical requirements, durations or acceptance criteria. If information is missing, phrase a question rather than a conclusion. Return finding, source, affected activity, responsible role and next action. 05 · Constructability and the next meeting Review the supplied schedule sequence, drawings, logistics plan and dated field information for the selected area. Identify potential conflicts in access, equipment installation, laydown, trade interfaces and closure of openings. Distinguish documented constraints from assumptions and from field conditions that require inspection. Cite supporting records. Produce a meeting-ready table with concern, evidence, affected work, question, proposed responsible role, response-needed point and next action. Do not declare the sequence safe or buildable; list the items the qualified project team must verify. WORKED EXAMPLE Illustrative only: installation in Week 4, delivery in Week 8. Concern: dates conflict. Source: actual activity and procurement references to be confirmed. Owner: assigned project team member. Due: before the coordination decision. Next action: confirm dates, assess sequence and completion impact. This is not automatically a four-week project delay. VERIFICATION CHECKLIST [ ] Correct files and revisions [ ] Every cited reference exists [ ] Source actually supports the finding [ ] Missing data and assumptions are explicit [ ] Activity relationships and calendars checked where needed [ ] Field conditions confirmed by the project team [ ] Owner and next action agreed FINDINGS TEMPLATE Concern | source/revision/page | activity | evidence status | responsible person | response needed by | next action | verified by