Mastering NCH LogIt!: Tips to Improve Time Tracking Accuracy

How to Automate Reports with NCH LogIt! — Step-by-Step

Overview

Automating reports in NCH LogIt! saves time by exporting scheduled summaries of tracked time and tasks. Below is a prescriptive, step-by-step guide assuming Windows desktop LogIt! (common setup). If your interface differs, the steps map to similar menu items (Preferences, Reports, Export, Scheduler).

1. Prepare your data

  1. Open LogIt! and confirm all time entries are complete for the period you want reported.
  2. Organize entries by project/client and add notes or tags consistently so reports group accurately.

2. Create the report template

  1. Go to Reports (or File > Reports) and choose the report type you want (Summary, Detailed, By Project).
  2. Set the date range, grouping (by day/project/client), and columns to include (duration, rate, total, notes).
  3. Preview the report and adjust layout (sorting, filters).
  4. Save the configuration as a template or preset if available (look for Save Template or Save Preset).

3. Configure export settings

  1. In the report preview, choose Export and pick a format (CSV, PDF, XLS).
  2. Set export options (include headers, delimiters for CSV, page orientation for PDF).
  3. Choose a default output folder on your machine or a synced folder (e.g., OneDrive, Dropbox) for easy access.

4. Set up scheduling (automation)

  1. Open Scheduler or Automation within LogIt! If LogIt! lacks a built-in scheduler, use Windows Task Scheduler (steps below).
  2. In LogIt! scheduler:
    • Create a new scheduled task.
    • Select the saved report template.
    • Choose frequency (daily, weekly, monthly) and time.
    • Set destination file name pattern (include date token if available, e.g., ReportYYYYMMDD.pdf).
    • Enable email delivery if supported and enter recipient(s).
  3. Using Windows Task Scheduler (if LogIt! has a command-line export or can open with command-line switches):
    • Create a task -> Trigger (set frequency/time) -> Action: Start a program.
    • Program/script: path to LogIt! executable or a small script (.bat or PowerShell).
    • Arguments: include command-line switches to load template and export (consult LogIt! docs).
    • Configure task to run whether user is logged on and store password if needed.

5. Automate emailing (if not built-in)

  1. If LogIt! can send email, enable SMTP settings and add recipients in the scheduler.
  2. If not, create a script (PowerShell example) that:
    • Attaches the exported report file.
    • Sends via SMTP (use an app password for security).
  3. Call that script from Task Scheduler after the export action (add a second action with a short delay).

Example PowerShell email snippet:

powershell

\(smtp</span><span> = </span><span class="token" style="color: rgb(163, 21, 21);">"smtp.example.com"</span><span> </span><span></span><span class="token" style="color: rgb(54, 172, 170);">\)port = 587 \(user</span><span> = </span><span class="token" style="color: rgb(163, 21, 21);">"[email protected]"</span><span> </span><span></span><span class="token" style="color: rgb(54, 172, 170);">\)pass = “app-password” \(msg</span><span> = </span><span class="token" style="color: rgb(57, 58, 52);">New-Object</span><span> System</span><span class="token" style="color: rgb(57, 58, 52);">.</span><span>Net</span><span class="token" style="color: rgb(57, 58, 52);">.</span><span>Mail</span><span class="token" style="color: rgb(57, 58, 52);">.</span><span>MailMessage</span><span class="token" style="color: rgb(57, 58, 52);">(</span><span class="token" style="color: rgb(163, 21, 21);">"[email protected]"</span><span class="token" style="color: rgb(57, 58, 52);">,</span><span class="token" style="color: rgb(163, 21, 21);">"[email protected]"</span><span class="token" style="color: rgb(57, 58, 52);">,</span><span class="token" style="color: rgb(163, 21, 21);">"Weekly LogIt Report"</span><span class="token" style="color: rgb(57, 58, 52);">,</span><span class="token" style="color: rgb(163, 21, 21);">"See attached"</span><span class="token" style="color: rgb(57, 58, 52);">)</span><span> </span><span></span><span class="token" style="color: rgb(54, 172, 170);">\)msg.Attachments.Add(“C:\Reports\LogIt_Report_20260207.pdf”) \(smtpClient</span><span> = </span><span class="token" style="color: rgb(57, 58, 52);">New-Object</span><span> Net</span><span class="token" style="color: rgb(57, 58, 52);">.</span><span>Mail</span><span class="token" style="color: rgb(57, 58, 52);">.</span><span>SmtpClient</span><span class="token" style="color: rgb(57, 58, 52);">(</span><span class="token" style="color: rgb(54, 172, 170);">\)smtp,\(port</span><span class="token" style="color: rgb(57, 58, 52);">)</span><span> </span><span></span><span class="token" style="color: rgb(54, 172, 170);">\)smtpClient.EnableSsl = \(true</span><span> </span><span></span><span class="token" style="color: rgb(54, 172, 170);">\)smtpClient.Credentials = New-Object System.Net.NetworkCredential(\(user</span><span class="token" style="color: rgb(57, 58, 52);">,</span><span class="token" style="color: rgb(54, 172, 170);">\)pass) \(smtpClient</span><span class="token" style="color: rgb(57, 58, 52);">.</span><span>Send</span><span class="token" style="color: rgb(57, 58, 52);">(</span><span class="token" style="color: rgb(54, 172, 170);">\)msg)

6. Test the full flow

  1. Run the scheduled task manually or trigger the LogIt! export to verify output formatting and file naming.
  2. Confirm email delivery and attachments open correctly.
  3. Adjust timing, retries, or file overwrite behavior as needed.

7. Maintain and secure

  • Rotate or protect any credentials used in scripts (use app passwords or secure vault).
  • Periodically verify scheduled runs and update templates when reporting needs change.
  • Archive older reports automatically (e.g., move to an Archive folder via a scheduled script).

If you want, I can:

  • Provide a tailored Windows Task Scheduler .xml or PowerShell script for your exact report filename and schedule.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *