Worklog360 Docs

Team Management & Approvals with AI

Use Worklog360 MCP with an AI assistant to review team timesheet status, check required and planned hours, and approve or reject timesheets and individual worklogs. This guide is designed for team leads, delivery managers, project managers, and authorized approvers.

Quick start: Ask “Show my team's timesheet statuses for last week.” You can then review individual submissions before approving or rejecting them.

Worklog360 MCP guides: Overview · Time Tracking · Team Approvals · Automation Examples · Tool Reference

Before you begin: Connect Worklog360 MCP. Connect Atlassian MCP as well when you need actual logged hours, billable time, Jira issue details, or project-level breakdowns. Access depends on your Worklog360 and Jira permissions. See Worklog360 MCP — Overview.

1. Find Your Teams and Their Timesheet Status

Start by asking which Worklog360 teams you manage, then review timesheet statuses for a particular week or month.

What you want to do

Example prompt

See managed teams

“Show the Worklog360 teams I manage and their members.”

Review timesheet status

“Show my team’s timesheet statuses for last week.”

Find unsubmitted timesheets

“Which members of my team have not submitted their timesheets for last week?”

Check one team

“Show timesheet statuses for the Platform team for this month.”

Review required capacity

“Show each team member’s required and planned hours for this week.”

How it works: Worklog360 MCP provides accessible teams, timesheet statuses, required hours, and planned capacity or bookings. It does not treat planned hours as actual logged hours.

2. Check Missing Hours and Timesheet Compliance

Use Worklog360 timesheet context together with Jira worklogs to find employees who may need to complete their time entries.

What you want to know

Example prompt

Find missing logged hours

“Compare the actual logged hours with required hours for everyone on my team last week. Show any differences.”

Spot gaps by day

“Which team members have working days with no logged time this week?”

Check a specific employee

“Show Alex’s required hours, logged hours, and timesheet status for last week.”

Find incomplete submissions

“Which submitted timesheets have fewer logged hours than the required hours?”

Prepare a manager summary

“Summarize missing hours and unsubmitted timesheets for my team, without changing anything.”

Important: These cross-checks are composed workflows rather than a single dedicated compliance tool. Actual logged hours must be retrieved from Jira through an authorized Jira connection such as Atlassian MCP. The assistant should account for time off and nonworking days when that information is available, and state when it is not.

3. Review a Timesheet Before Making a Decision

Review a submission’s status, required hours, approvers, and logged work before approving or rejecting it.

Show Alex’s submitted timesheet for last week. Compare the required and logged hours, highlight missing days, and summarize the main Jira issues worked on. Do not approve it yet.

The assistant can:

  1. Retrieve the employee’s Worklog360 timesheet context and submission status.

  2. Retrieve actual Jira worklogs for the same employee and dates, if authorized.

  3. Compare actual hours to requirements and identify apparent gaps.

  4. Show the summary and request your decision.

Finding and displaying the individual worklogs and top Jira issues requires sufficient Jira worklog access. The assistant must not substitute planned hours for recorded time.

4. Approve or Reject Timesheets

Authorized approvers can approve or reject a complete existing Worklog360 timesheet.

Action

Example prompt

Approve a timesheet

“Approve Alex’s submitted timesheet for last week.”

Review, then decide

“Show Alex’s submitted timesheet, summarize any missing hours, and ask me whether to approve it.”

Reject a timesheet

“Reject Alex’s submitted timesheet for last week with the comment: Please review Wednesday’s missing hours.”

See the result

“Check whether Alex’s timesheet was approved successfully.”

The assistant must identify the correct, existing timesheet record and check that the current user is authorized to review it. Timesheet approval acts on the entire submission, not individual Jira worklogs. If several submissions or periods could match, specify which one should be reviewed.

5. Review Individual Worklogs

Worklog360 MCP also supports actions on selected Jira worklogs: submit, approve, reject, and recall. Use these actions when your workflow requires worklog-level review rather than an entire timesheet decision.

Action

Example prompt

Review a selection

“Find Alex’s worklogs on PROJ-16 for last week and show their status before I review them.”

Approve selected entries

“Approve the three selected worklogs after showing me the issue, date, and hours for each.”

Reject selected entries

“Reject the selected worklog with the comment: Please correct the billable duration.”

Recall selected entries

“Recall the selected worklogs if I have permission to do so.”

Worklog-level review requires exact Jira issue keys and worklog IDs. The assistant should retrieve and verify these identifiers; it should not guess them. Bulk changes should be previewed and confirmed before execution, and failures reported individually.

6. Advanced Manager Workflows

Combine Worklog360 context and Jira worklogs to streamline common weekly management tasks.

Workflow

Natural-language example

Monday compliance review

“Show which team members have not submitted last week’s timesheets and which have fewer logged hours than required.”

Prepare an approval queue

“Find the submitted timesheets for my team, check required versus actual hours, and prepare a review summary. Do not approve anything yet.”

Review multiple submissions

“Show submitted timesheets for Alex and Sam for last week. Review both, then ask which to approve.”

Investigate workload differences

“Compare my team members’ actual logged hours for the past two weeks, grouped by Jira project.”

Report missing time

“Prepare a concise list of missing timesheets and incomplete logged hours for our weekly delivery meeting.”

Review billable work

“Summarize billable versus total logged hours for my team last week, using Jira worklogs and available billing properties.”

These are examples of multi-tool workflows. Some require additional Jira access and orchestration by the AI assistant. Worklog360 MCP does not currently expose a dedicated team analytics or pending-approval queue tool.

7. Automate Weekly Timesheet Checks

On platforms that support scheduled AI tasks with an authorized MCP connection, managers can configure recurring read-only reviews.

Timesheet Watchdog

Every Monday morning, check last week’s timesheet statuses for the teams I manage. Identify who has not submitted, compare actual logged hours with required hours where Jira data is available, and give me a summary. Do not change or approve any timesheets automatically.

Friday Completion Check

Every Friday afternoon, review this week’s timesheet statuses and planned versus actual hours for my team. Highlight members who may need to finish their entries, accounting for nonworking days when available.

Approval Preparation

Every Monday, prepare a summary of submitted timesheets requiring review, highlighting any difference between required hours and recorded Jira hours. Wait for my explicit approval decision.

Scheduling note: Worklog360 MCP itself is not a background scheduler and does not send notifications on its own. Your AI assistant or automation platform must support recurring execution, access to the connected tools, and any notification delivery.

8. Which Tools Are Used?

Worklog360 MCP tool (friendly name)

Purpose

Typical access

get-user-teams

Find accessible teams, managers, and members.

Team members and managers

get-team-timesheets

Read team timesheet statuses, required/planned hours, and daily capacity.

Authorized managers

get-my-timesheet

Read an individual’s timesheet context, status, and approvers.

Employee and authorized viewers

review-timesheet

Approve or reject an existing timesheet.

Assigned approvers and authorized managers

review-worklogs

Submit, approve, reject, or recall selected Jira worklogs.

Users authorized for the requested action

The names above are readable labels for MCP operations; specific names displayed by your assistant may differ. Access is enforced by the underlying Worklog360 and Jira permissions, not by this table.

Frequently Asked Questions

Can a manager approve every employee’s timesheet?

No. The user must have the appropriate rights over the relevant submission. The assistant should verify eligibility before changing approval status.

Is a timesheet approval the same as a worklog approval?

No. A timesheet approval changes an entire submitted timesheet. A worklog approval applies to selected individual Jira worklogs.

Can I find missing hours using Worklog360 MCP alone?

Worklog360 exposes required and planned time information, but to compare these values with actual logged hours, the assistant typically also needs Jira worklogs through Atlassian MCP.

Can the assistant approve timesheets automatically?

An AI platform may support an automated workflow, but approvals still require proper authorization. For safety and auditability, review the relevant submissions and use explicit approval decisions rather than silently approving based on a rough hours threshold.

Tool access and available data depend on each user’s permissions, configured approvals, Jira visibility, and the connected AI assistant.