Automated Timesheet Chasing for ProjectManager
Every Monday, WebRun opens ProjectManager.com, reads last week's timesheets, works out who has not submitted and how many hours are missing per project, opens a Trello card for each person still outstanding, and posts your ops channel a Teams summary of the gap so invoicing is not held up by a handful of unsubmitted sheets.
How do I chase unsubmitted timesheets before invoicing?
WebRun chases timesheets every Monday. It reads last week's ProjectManager.com timesheets, works out who has not submitted and how many hours are missing per project, opens a Trello card per person, and posts a Teams summary of the unbilled total, so invoicing goes out on time.
- Missing timesheets are named on Monday, not at invoice time
- The unbilled hours at risk are quantified every week
- Billable work stops getting written off because hours went in late
Built for project managers · agency operations · consultancies · finance and billing teams
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.projectmanager.comin a real browser with your saved login - no setup, no API keys. -
1
ProjectManager.com - read last week's timesheets
WebRun opens ProjectManager.com to read last week's timesheets. - Sign in to ProjectManager.com and open the timesheets for the week just finished
- Capture every team member with their submitted status, hours logged, and the projects those hours sit against
- Compare hours logged against each person's expected hours and note the shortfall, plus any timesheet submitted but still awaiting approval
Done when Every team member has a submitted status and a figure for missing hours.
-
2
Trello - open a card per person outstanding
WebRun opens Trello to open a card per person outstanding. - Open a card on your ops board for each person who has not submitted, titled with their name and the missing hours
- Use separate lists for not submitted and awaiting approval, since one needs the person and the other needs a manager
- Archive the card as soon as the timesheet lands, so the board shows only what is still holding up the billing run
Done when The board matches exactly who is still outstanding this week.
-
3
Microsoft Teams - post the missing hours
WebRun opens Microsoft Teams to post the missing hours. - Post the ops channel a short summary: how many timesheets are in, how many are missing, and the total unbilled hours at stake
- List the outstanding people with their missing hours and the projects affected, so the billable impact is obvious
- Leave the personal nudge to a manager. WebRun posts an internal summary and never messages an individual directly
Done when The ops channel knows who is outstanding and how many hours are at risk.
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 timesheets for people?
No. WebRun reports who is missing and how many hours. Submitting hours and approving them stay with the person and their manager, because a timesheet is a billing record.
Does it message people directly about their hours?
No. It posts an internal Teams summary and opens Trello cards for your ops lead. Any personal nudge comes from a manager who has read the list.
How does it know what hours are missing?
It compares hours logged against each person's expected hours for the week and reports the shortfall per project, so partial timesheets show as well as absent ones.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.