Automated Celoxis Timesheet Chasing
Every Monday, WebRun opens Celoxis, checks last week's timesheets resource by resource, works out who has not submitted and which submitted sheets a manager has not approved, puts the closing deadline on the team calendar, and posts Microsoft Teams two short lists: one per person and one per approver.
How do I chase unsubmitted and unapproved timesheets each week?
WebRun opens Celoxis every Monday, checks last week's timesheets resource by resource, and separates who has not submitted from which submitted sheets an approver still holds. It puts the closing deadline on Google Calendar and posts both chase lists to Microsoft Teams, so billing is never built on missing hours.
- Unsubmitted and unapproved hours are named separately every Monday
- Approvers see only the sheets they personally hold up
- The closing deadline and the outstanding count sit on the shared calendar
Built for PMO teams · project managers · professional services firms · consultancies
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.celoxis.comin a real browser with your saved login - no setup, no API keys. -
1
Celoxis - check submissions and approvals
WebRun opens Celoxis to check submissions and approvals. - Open Celoxis and go to last week's timesheet period
- List every resource expected to submit and mark who has and who has not
- For submitted sheets, read the approval status and note which approver is holding each one
- Capture the projects each person booked time entries against, and flag anyone with a suspiciously empty week
- Note how many days remain before the period closes
Done when Every resource has a submission status and every submitted sheet has an approval status.
-
2
Google Calendar - put the deadline on the calendar
WebRun opens Google Calendar to put the deadline on the calendar. - Put the timesheet closing deadline on the shared team calendar for this period
- Title it with the days remaining and the count of sheets still outstanding
- List the names still to submit in the event description
- Update the existing event rather than creating a second one for the same period
Done when The closing deadline and the outstanding count are on the team calendar.
-
3
Microsoft Teams - post both chase lists
WebRun opens Microsoft Teams to post both chase lists. - Post the PMO channel a list of resources whose timesheet is still unsubmitted, longest outstanding first
- Post a second list grouped by approver showing the submitted sheets each one still has to sign off
- Show the days left before the period closes at the top of both lists
- Keep it to the internal channel. WebRun does not email or message anyone individually
Done when The PMO has both chase lists in Microsoft Teams with the deadline attached.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it submit or approve a timesheet for anyone?
No. WebRun only reads submission and approval status in Celoxis. Submitting hours and signing them off stay human actions. It also never emails or direct-messages a person about their sheet.
Where does the chase list go?
Into your own Microsoft Teams channel, as two internal posts: one listing people who have not submitted, one grouped by approver. Nothing leaves your workspace.
Does it catch someone who submitted an empty week?
Yes. A sheet submitted with little or no time booked against any project is flagged separately, so a technically complete submission that carries no hours does not pass as done.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.