# Student: Project Check-Ins For long-running or open-ended projects, students check-in weekly on their progress. This provides some implicit structure, and lets students dynamically rescope their projects as they learn more about what is involved in their execution. **Project Check-In** Each week of your project, please submit as a single PDF: * a description of the work you have done in the last week, including: * what you intended to do for the task * what you were able to accomplish * how much time you spent on each task * who worked on each task * documentation from your design journal that illustrates your progress * a brief reflection on what you have learned through the week's project work * a brief reflection on how your tasks this week (and success/failure in achieving them) relate to the overall goals for your project * a description of how, if at all, you plan to re-scope your project given your experience thus far * a description of the tasks you intend to perform for next week * a list of questions you have for instructional staff, on how we can best support your project work --- # 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://codingcrafter.gitbook.io/toolkit-reflective-and-equitable-ungrading-for-pbl/conversational-reflection-for-assessment/student-project-check-ins.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.