Conference Tracker: How do I get rid of any Invalid Logs?

Conference Tracker: How do I get rid of any Invalid Logs?

Introduction

Invalid logs are inconsistencies in an attendee's sign-in record, such as:
  1. Multiple consecutive sign-ins.
  2. Multiple consecutive sign-outs.
  3. A sign-out without a preceding sign-in.
Primary Cause: These errors typically occur when an operator allows attendees to swipe their badges multiple times or forgets to reset the system's "In/Out" toggle between sessions. This is a common issue during high-traffic periods at busy conferences.

Solutions: The following methods can be used to identify and correct these invalid records.

Step-by-Step

To get started, go to the Fix Attendance Logs page from the navigation menu: Attendance → View Attendance. At the top of the page, click More, then select Fix Swipes.

STEP 1: Check for Multiple Sign-ins


1.     In the Use this tool to fix invalid attendance logs in bulk section, check the boxes for these options:
    1. Remove swipes before the session started,
    2. Create a swipe at the beginning of the session, and
    3. Change all swipes near the start to sign-ins (within a 10-minute window).
2.      Next, in the Select Logs to Fix section, enter the session where the multiple sign-ins occurred in the Session field.

Info
Note: You can leave this blank to fix all such logs at once.

3.      Now, choose the current Status of the logs you want to update. In this case, all these attendees have an Invalid status, so select Invalid from the drop-down menu.

4.      Finally, review the Before and After diagrams to ensure that this change will be applied as planned, and click the Apply Changes button to complete the fix to this set of attendance logs.

STEP 2: Check for Multiple Sign-outs


1. In the Use this tool to fix invalid attendance logs in bulk section, check the boxes for these options: 
  1. Remove swipes after the session ended, 
  2. Create a swipe at the end of the session, and
  3.  Change all swipes close to the end to be sign-outs (within a 10-minute frame).


2.       Next, in the Select Logs to Fix section, enter the session where the multiple sign-ins occurred in the Session field.
Info
   Note: You can leave this blank to fix all such logs at once.


3. Now, choose the current Status of the logs you want to update. In this case, all these attendees have an Invalid status, so select Invalid from the drop-down menu.

 4. Finally, review the Before and After diagrams to ensure that this change will be applied as planned, and click the Apply Changes button to complete the fix to this set of attendance logs.

STEP 3: Check for a Sign-out before Sign-In


1.      In the Use this tool to fix invalid attendance logs in bulk section, check the boxes for these options: 
  1. Change all swipes close to the start to be sign-ins (within a 10-minute frame) 
  2. Change all swipes close to the end to be sign-outs (within a 10-minute frame).
2.      Next, in the Select Logs to Apply section, enter the session where the sign-out before sign-in happened in the Session field.
Info
Note: You can leave this blank to resolve all logs like this at once.
3.      Now, choose the current Status of the logs you want to update. In this case, all these attendees have an Invalid status, so select Invalid from the drop-down menu.
4.      Finally, review the Before and After diagrams to ensure that this change will be applied as planned, and click the Apply Changes button to complete the fix to this set of attendance logs.

STEP 4: Verify there are no other issues in the Attendance Logs.

Before leaving the Attendance Logs, be sure to check for any other error statuses. Check out these tips to resolve them:

  1. Not Signed-In: This error occurs if there is a sign-in swipe for an attendee but no sign-in swipe. Click here to learn how to fix these types of logs.

  2. Not Signed-Out: This error occurs if there is a sign-out swipe for an attendee but no sign-in swipe.  Click here to learn how to fix these types of logs.

  3. Stayed Less Than Required: This simply means that the attendee did not stay in the session long enough to get credit. Click here to learn how to fix these types of logs.

Conclusion

Once you have reviewed all error statuses, made the necessary corrections, and verified that the Attendance Logs are accurate within the Conference Tracker software, you are ready to export the data.



    • Related Articles

    • Conference Tracker - How do I create Attendance Logs?

      Introduction In Conference Tracker, administrators can manually create Attendance Logs. This is useful if participants forgot to scan their badges or if you need to correct information that was entered incorrectly. Step-By-Step 1-Go to Attendance > ...

    • Conference Tracker: How do I add a new Attendance Log?

      Introduction Following this guide, you'll be able to create a new attendance log for an attendee. If done correctly, they will receive credit for the session, which will be added to their existing credits. This is only needed if they never signed in ...

    • Conference Tracker - How do I create attendance logs?

      Introduction Once your conference begins and operators start scanning attendees into sessions, the Attendance section will start collecting this data. In this article, you’ll learn how to add manual attendance logs and manual swipes if needed. ...

    • Conference Tracker - How do I manage attendance logs that have already been generated?

      Introduction Manage Attendance - In this section, you will be able to see every single scan performed by your Operators. You can also see full attendance logs, create any logs or scans missing from an attendee, and fix any issues that have appeared ...

    • Conference Tracker: How do I filter the Attendance Logs?

      Introduction Following this guide, you'll be able to create a new Attendance Log for one of your Attendees.   If done correctly they will receive credit for the session and it will be added to their existing credits.  This is only necessary if they ...