Fix missed clock outs in ClockShark every morning

1. An administrator turns the alert on once: Admin > Alerts and Reminders, tick Missing Out on the Timesheet Alerts page, click Save.
2. Each morning, open Time > View, set the date at the top left and use the filter icon for a department, location or employee to find the red exceptions.
3. Ask the employee or look at the schedule for the real end time; ClockShark only knows the clock in.
4. Click the timesheet, click the pencil icon next to the shift, tick the box under Alerts to ignore it, change the end time under Shift and click Save.
5. If the day was already approved, unapprove it first, edit, then approve again. The hunt repeats every working day, and one missed shift becomes a 23-hour day on a paycheck.

Every morning, find yesterday's ClockShark shifts with a Missing Out alert, end them at the scheduled time and ask me about anyone with no schedule.

1. 01

   Find yesterday's open shifts

   Each morning the agent asks list_time_entries for the previous day with with_alerts_only and keeps the shifts whose alerts include Missing Out. A night shift whose scheduled end has not passed yet is left alone.

2. 02

   Pick an end time it can defend

   The agent looks up that person's shift for the day with list_shifts and proposes the scheduled end. With no schedule it uses the time you gave, or asks. It never invents an end from the clock in alone.

3. 03

   Check approval before editing

   An approved day cannot be changed. If the shift is already approved, the agent says so and, only after your OK, unapproves that employee for that single day with approve_timesheets, edits, then approves the day again.

4. 04

   Clear only the alert it fixed

   edit_time_entry sets the end and ignores the alerts only when Missing Out was the sole alert on the shift. A shift that also carries Out of Bounds or Location Tampering keeps its alert for you.

5. 05

   Leave a reason in the record

   The agent writes a timesheet note such as "End set to schedule, confirmed by text" in the same edit, so the Audit Log entry with the old and new value also says why.

Missing Out yesterday, Thu 9 Oct: 3 shifts
Mike Torres, 42 Oak Street: end set to 16:30 from the schedule, alert ignored
Ana Silva, Elm Ave remodel: end set to 15:00 as you said, alert ignored
Jen Park, Maple Court: end set to 16:00, Out of Bounds alert kept for you
Carlos Ruiz: no shift scheduled, left open. What time did he leave?

• ClockShark ends a shift automatically after 23+ hours when an employee forgets to clock out, so an unfixed shift shows close to a full day.
• The ClockShark Missing Out alert exists only if an administrator ticked it on the Timesheet Alerts page; managers cannot turn timesheet alerts on or off.
• ClockShark clock out reminders set by an admin are only defaults: each employee has to enable them in the mobile app under My Account > Time Clock Reminders.
• A ClockShark manager needs Add and Edit under Manager Settings > Timesheets to change a shift, and every time card edit stays in the Audit Log with the old and new value.

edit_time_entry and approve_timesheets change only your own ClockShark data and reach no one else, so they run without asking first.

Sources: ClockShark: Reviewing and editing timesheets · ClockShark: Using alerts, notifications and reminders · ClockShark: Audit Log FAQ · ClockShark: Roles and manager permissions

curl https://cotlet.dev/api/v1/clockshark/edit_time_entry \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"entry_id":"te_90412","fields":{"end":"2026-10-09T16:30:00-05:00","notes":"End set to schedule, confirmed by text"},"ignore_alerts":true}'

{
  "entry_id": "te_90412",
  "start": "2026-10-09T07:00:00-05:00",
  "end": "2026-10-09T16:30:00-05:00",
  "alerts": [],
  "approved": false
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is clockshark_edit_time_entry. Example data.

• Approve ClockShark timesheets before payroll
• Schedule a crew on a new job in ClockShark
• Approve ClockShark time off requests against the schedule
• ClockShark API and MCP server: every tool
• All use cases