> For the complete documentation index, see [llms.txt](https://guide.mymodone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.mymodone.com/common-features/team-member-portal/log-attendance.md). # Log Attendance modONE provides an easy-to-use Team Member attendance module that takes more than 2-3 minutes to complete. It is a quick and easy way to document attendance and confirm topic comprehension. {% hint style="info" %} modONE Administrators: The attendance module is only available if attendance is enabled at the Organization level (see the [Organization Advanced Settings](/how-do-i.../manage-my-organization/advanced-settings.md) guide) and "Take Attendance" was checked in Content Options when scheduling the content (see the [Content Options](/how-do-i.../schedule-content/content-options.md) guide). {% endhint %} ### Launch Attendance Session Click the Log Attendance icon (

) in the Navigation Ribbon to log attendance. modONE will confirm the following prior to launching the log attendance session: 1. The Team Member is assigned the role of "Employee" 2. Content is active (i.e., the call to action has not expired), the Attendance option is activated, and the Team Member's Location and/or Job are included within the scope of recipients. 3. The Team Member has not already completed an attendance session for this content. ### Log Attendance #### Record Attendance Answer the question, "Did you attend a recent safety meeting?" Click the button that applies: * "Yes, I attended our safety meeting and understood the topic that was discussed" * "No, I did not attend our safety meeting"

If the answer is "Yes", the next step is a question(s) associated with the topic. If the answer is "No," the next step is certification. #### Answer Question(s) If comprehension questions are associated with the content and the option to present the questions when logging attendance was chosen during the scheduling process, the questions will now be presented to the Team Member.

The questions are presented one at a time. When the Team Member answers the question, they are provided immediate feedback on whether their answer is right or wrong. If the answer is wrong, the correct answer is provided. This process is repeated until all questions are answered. If comprehension questions are not associated with the content, the Team Member will be presented with 3 safety topic choices and asked to choose the topic that was reviewed during the safety meeting.

Once the questions are completed, the next step is certification. #### Certify Answers The final step is to certify answers by providing a signature.

The Team Member can draw their signature anywhere in the Signature input box. Click the "Clear" button to clear the Signature input box and start again. If, for some reason, the Team Member is unable to draw their signature, click the "I can't draw my signature..." button to populate the Signature input box with an adopted signature. Click the "Submit" button to complete the process. The Team Member will receive a message indicating that the attendance has been logged. modONE will end the attendance session and load the Team MemberPortal home page. ### Resume Attendance Session In the event that an attendance session is interrupted for some reason (e.g., connection issues, clicking the browser's back button, page refresh), the Team Member should relaunch an attendance session. modONE remembers the last completed step and picks up the attendance logging process from that point. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://guide.mymodone.com/common-features/team-member-portal/log-attendance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.