Schedule a crew on a new job in ClockShark

1. Create the job first, because SCHEDULES only offers the jobs in its list on the left side to drag onto an employee.
2. Drag the job onto an employee date block. ClockShark creates an all-day shift with no start or end time, so each one needs the pencil icon, All Day switched off and times set.
3. For several people at once, click Add Shift, pick start and end dates and times, Employees, Job, Task and Notes, then click Publish, or Save Draft to hold it back.
4. Draft shifts show with a dotted border, and the Publish button at the top right counts the drafts in the date range before publishing them in bulk.
5. Toggle the schedule between the job and employee views to check that every job has people on it. It is all done again for every new job, and the scheduling articles we read describe no warning when someone is already booked elsewhere.

Create a job for 42 Oak Street and put Ana and Luis on it Monday to Wednesday, 7:00 to 15:30. Check nobody is booked elsewhere and show me the drafts before you publish.

1. 01

   Reuse the job if it exists

   The agent searches list_jobs by address or number before calling create_job, so a job the office already entered is not duplicated. A new job gets the budget hours from the quote when you give them.

2. 02

   Check who is free

   list_shifts for the dates shows every crew member's existing shifts, drafts included, and list_time_off_requests shows pending and approved time off. A person booked on another job or off that day is reported with an alternative, never double booked.

3. 03

   Draft one day at a time

   Each create_shift call covers one start and end, so the agent drafts one call per working day with the same crew, task and notes. Weekends are skipped unless you ask for them.

4. 04

   Show the drafts, then publish only those

   You see the drafted week as a short list before anything reaches the crew. publish_shifts waits for your OK and gets only the shift IDs just created, so other drafts in that week stay hidden.

5. 05

   Stop when Simpro owns the schedule

   If the account syncs schedules from Simpro, the agent stops and says so, because shifts made in ClockShark never reach Simpro and the next sync overwrites edits to imported ones.

Job created: 2041 42 Oak Street, Harlow Homes, 320 budget hours
Drafted 6 shifts, Mon 13 to Wed 15 Oct, 7:00 to 15:30, task Framing
Ana Silva: 3 shifts. Luis Ortega: 3 shifts
Clash check: no other shifts or time off for Ana or Luis on those days
Published 6 shifts after your OK, visible in the crew app now

• Dragging a job onto the ClockShark schedule makes an all-day shift with no start or end time until someone edits it.
• ClockShark draft shifts stay hidden from the crew until published, and a published shift can be turned back into a draft with Unpublish.
• A published ClockShark shift appears in the employee's mobile app right away, and later changes to time, job or notes sync to the app on their own.
• ClockShark does not write schedule changes to the Audit Log, unlike timesheet edits.
• With Simpro schedule sync on (ClockShark Pro plan), Simpro is the source of truth: most changes arrive within about an hour, and shifts whose job or employee is not synced yet are skipped.

publish_shifts asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.

Sources: ClockShark: Scheduling employees, web and mobile · ClockShark: Draft schedules · ClockShark: Sync your Simpro schedule into ClockShark · ClockShark: Audit Log FAQ

curl https://cotlet.dev/api/v1/clockshark/create_shift \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"employee_ids":["e_48213","e_48219"],"job_id":"j_3307","start":"2026-10-13T07:00:00-05:00","end":"2026-10-13T15:30:00-05:00"}'

{
  "shifts": [
    {
      "shift_id": "s_77201",
      "employee_id": "e_48213",
      "job_id": "j_3307",
      "start": "2026-10-12T07:00:00-05:00",
      "end": "2026-10-12T15:30:00-05:00",
      "status": "draft"
    },
    {
      "shift_id": "s_77202",
      "employee_id": "e_48219",
      "job_id": "j_3307",
      "start": "2026-10-12T07:00:00-05:00",
      "end": "2026-10-12T15:30:00-05:00",
      "status": "draft"
    }
  ]
}

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

• Approve ClockShark timesheets before payroll
• Fix missed clock outs in ClockShark every morning
• Approve ClockShark time off requests against the schedule
• ClockShark API and MCP server: every tool
• All use cases