Project Management
Teamwork.com
Connect your AI to Teamwork.com
Agency owners, project managers, and account leads run client work in Teamwork.com, but knowing which projects are over budget, whose time is unbilled, and what is slipping means checking projects, tasks, and timesheets one by one. AI can bring that together in seconds, but only if it respects client and project permissions and keeps billable time accurate.
Why it matters
Capabilities that matter most for Teamwork.com
01
Nearly 30 ready-made API endpoints
Install Teamwork.com endpoints from the app store for projects, tasks, time and milestones, ready to use straight away.
02
Projects beside billing
Join Teamwork.com time and projects with accounting lists to see what was delivered next to what was invoiced.
03
Governed AI for client work
AI tools answer within per-user and per-team security, and change tasks only through approved actions.
Use cases
Example AI Use Cases for Teamwork.com
scenario
-
Client people who join your calls often need to be in Teamwork.com so the delivery team can work with them, but adding them by hand means checking each email and typing details in. Add someone the wrong way and they may get an invite they should never see.
What popdock provides
--
Name the client and how far back to look. It finds the client's company in Teamwork.com, then gathers the outside people from its Chorus calls, leaving out colleagues by email domain, and drops anyone Teamwork.com already has. You see each missing person with their title and number of calls, and confirm, edit or drop them before anything is written. They are added as contacts under the client company, never as administrators and without sending an invite, and names that do not split cleanly are shown to you first.
Business outcome
---
Client contacts from your calls are set up in Teamwork.com under the right company, with no invites sent.
scenario
-
A client whose projects are slipping in Teamwork.com and who has not heard from anyone in weeks is an escalation waiting to happen. Spotting them means checking health scores and late milestones, then searching Chorus for recent contact with each client.
What popdock provides
--
Set the health score that counts as unhealthy and how many quiet days to allow. It finds Teamwork.com projects at or below the threshold or with late milestones, groups them by client, and checks Chorus for recent calls or emails with each. Clients with no recent contact are listed most troubled first, with lowest health score, late milestones, last contact and who it was with. Names too generic to search are reported as unchecked rather than guessed, and nothing is changed.
Business outcome
---
Troubled clients get a call from your team before frustration turns into an escalation.
scenario
-
Before speaking to a client you want to know how their projects are really going in Teamwork.com and what they said on recent calls. Putting delivery and conversation side by side means opening every project and rereading Chorus summaries.
What popdock provides
--
Name the client and how many days of history to cover. It finds the company in Teamwork.com, asking which one if several match, and reads each open project's health score, late milestones and latest update. It then reads the client's Chorus calls and emails, saying when the two systems spell the name differently. The brief gives a one-line headline, a delivery table, the conversations, and anything the client raised that relates to a late milestone or poor health rating, quoted from the summary. Nothing is changed.
Business outcome
---
You speak to every client knowing both their delivery status and what they told your team last time.
scenario
-
Commitments made on a client call often live only in the Chorus summary. Getting them into the right Teamwork.com task list means rereading it, finding the project and checking nothing is already there, so some promises never become work.
What popdock provides
--
Give the Chorus conversation and, optionally, the task list. It reads the summary and pulls out only concrete commitments, with who made them and any dates, and stops if there is no summary. It finds the client's open Teamwork.com project and task list, asks when several match, and drops actions that already have an open task. You see each proposed task with the owner named in its description and confirm, edit or drop them before anything is created. It never invents actions or guesses the project.
Business outcome
---
Client commitments become Teamwork.com tasks in the right list the same day, without duplicating existing work.
scenario
-
Client calls take real time, but they often never make it onto a timesheet in Teamwork.com. Finding the gaps means comparing a person's Chorus call history with their time entries, day by day and project by project.
What popdock provides
--
Give the person's email and a date range. It confirms the person in Chorus and Teamwork.com, reads their client calls with durations in minutes, and reads their logged time for the same dates. A call is covered when a same-day entry sits on the client's project or mentions the call, and one entry can cover several calls if its minutes are enough. You get the uncovered calls with their likely project and the total uncovered minutes. Internal calls are counted but not listed, and nothing is written.
Business outcome
---
Unrecorded client time is caught before invoices go out, with the minutes and likely project for each call.
scenario
-
Logging time for client calls means checking your calendar, working out durations, finding the right Teamwork.com project and making sure you did not log it already. At the end of a busy week, much of that time never gets recorded.
What popdock provides
--
Give the person's email and a date range, and whether time is billable. It reads their Chorus client calls, rounds each up to the nearest 15 minutes, and finds the matching open Teamwork.com project, asking when several match and marking calls with no project as unplaceable. Calls already covered by a same-day entry on that project are skipped. You see every proposed entry and confirm, edit or drop them before anything is written; time is never logged on a project you have not seen, and failures are reported, not retried.
Business outcome
---
Client call time reaches Teamwork.com accurately and once, without rebuilding your week from memory.
scenario
-
What a client says on a sales or account call rarely reaches the delivery team working on their project. Writing it up in Teamwork.com means rereading the summary, finding the project and checking nobody posted it already.
What popdock provides
--
Give the Chorus conversation, and say whether the message should be private, which is the default. It reads the call summary and attendees, finds the client's open Teamwork.com project, and stops if a message for this call was already posted. You see a drafted message with who attended, a summary, decisions and follow-ups taken only from the summary, and approve or edit it before it is posted. Pricing, contract terms and anything marked confidential are kept out and listed for you, and notifications stay off unless you ask.
Business outcome
---
The delivery team hears what the client said on the call, in one clear project message, posted once.
scenario
-
People often record time twice: on a Dynamics 365 Business Central timesheet for costing and in Teamwork.com for the project. When the two disagree, billing and payroll are both at risk, yet comparing them means lining up a resource with a Teamwork.com user and checking every day by hand.
What popdock provides
--
Name the person and a period, and it finds them in Teamwork.com, asking if several match, then matches them to a Dynamics 365 Business Central resource by name or employee email, stopping if there is none. It compares hours day by day, flags days that differ by more than a quarter hour or appear on only one side, and lists timesheet lines still open or unapproved. Entries are compared by day, not one to one. Neither timesheets nor time logs are edited.
Business outcome
---
Time discrepancies are caught before billing or payroll, one day at a time.
scenario
-
Billable hours logged in Teamwork.com should turn into invoices in Dynamics 365 Business Central, but some projects never get billed. Spotting under-billing means totalling time per project, finding the client's invoices and working out which lines were time.
What popdock provides
--
Name the client and a period, and it totals billable Teamwork.com time and value per project, noting whether hours are verified, then finds the client in Dynamics 365 Business Central and the invoices posted in the same period. It shows the gap between billable value and time billed, calls the client under-billed, over-billed or square within two percent, and lists projects with no invoice line. It notes when timing may explain a gap and skips the gap if currencies differ. No invoice is raised by this check.
Business outcome
---
You catch unbilled project work before it is written off, project by project.
scenario
-
When a job is set up in Dynamics 365 Business Central, delivery still needs a matching project in Teamwork.com. Creating it by hand means checking one does not already exist, finding the right client company and owner, and copying dates, and duplicates appear when someone does it twice.
What popdock provides
--
Give a job number, and it reads the Dynamics 365 Business Central job, stopping if it is completed or blocked. It searches Teamwork.com for a project by job number, then by description, and stops or asks if one may already exist. It matches the client company and owner without creating a company, shows the project it would create with name, dates and description, and creates nothing until you confirm. The new project is read back, and nothing in Business Central is changed.
Business outcome
---
Every Business Central job gets one Teamwork.com project, with the right client and dates and no duplicates.
scenario
-
Before a client meeting, you need two answers: do they owe money in Dynamics 365 Business Central, and how is their work going in Teamwork.com. Getting both means pulling invoices from one system and project health and budgets from the other, then working out for yourself whether the two stories conflict.
What popdock provides
--
Name the client, and it finds them in Dynamics 365 Business Central, asking if several match, and lists balance, credit limit, block status and open invoices with overdue ones first. It then finds the client company in Teamwork.com and shows each active project's status, end date, health score and budget used. An attention list flags issues such as an overdue balance on active work or a project over budget. Amounts and budgets are never added together, and nothing is changed.
Business outcome
---
Account leads see money owed and delivery health side by side before every client conversation.
scenario
-
Turning logged project time into an invoice means totalling billable hours per project in Teamwork.com, checking nothing has already been billed in Dynamics 365 Business Central, and keying lines by hand. Mistakes here mean either double billing a client or leaving hours unbilled.
What popdock provides
--
Name the client and a start date, and it totals billable Teamwork.com time per project, then finds the customer in Dynamics 365 Business Central, stopping if none matches or the account is blocked. Existing invoices mentioning the projects are shown before going further. You review a draft with one line per project, hours and rate, and nothing is created until you confirm. The invoice is created unposted and its total is checked against what you approved. A rejected line stops the run rather than guessing.
Business outcome
---
Billable time becomes a reviewed draft invoice in minutes, without double billing.
scenario
-
Jobs in Dynamics 365 Business Central and projects in Teamwork.com should line up one to one, but over time some jobs have no project, some projects have no job to post costs to, and statuses and end dates drift apart. Matching the two lists by hand means guessing which project belongs to which job.
What popdock provides
--
Optionally name a customer, and it reads Dynamics 365 Business Central jobs and Teamwork.com projects and matches them by job number in the project name or description, or by name and client, marking name-only matches as possible. You get matched pairs with status and end date mismatches over seven days, jobs with no project, and projects with no job. Dates are compared by calendar day. It reads only and points to a separate job for creating missing projects.
Business outcome
---
Delivery and finance agree on which work exists, so no project runs without a job to cost against.
scenario
-
When a client falls behind on payment in Dynamics 365 Business Central, the project team in Teamwork.com usually keeps working without knowing. Telling them means checking which invoices are overdue, finding the client's active projects and posting a careful note on each.
What popdock provides
--
Name the client and how many days overdue counts, and it finds overdue invoices in Dynamics 365 Business Central, stopping without posting if there are none. It matches the client's Teamwork.com company, stopping rather than messaging the wrong client, and finds active projects. You see the invoices, projects and exact message, which leaves out credit terms, and nothing is posted until you confirm. It posts at most one message per project and reports any failures.
Business outcome
---
Project teams learn about overdue clients while it still matters, through one approved message per project.
scenario
-
Teamwork.com client companies and Dynamics 365 Business Central customers share no common ID, so clients doing project work with no customer to bill, or blocked customers with active projects, go unnoticed until invoicing time. Comparing names by hand is thrown off by punctuation and suffixes like Inc or Ltd.
What popdock provides
--
Optionally narrow by name, and it matches Teamwork.com companies to Dynamics 365 Business Central customers by name, ignoring case, punctuation and legal suffixes, using city and country to break ties and never picking between true ties. You get matched rows with blocked customers who still have projects flagged, clients only in Teamwork.com, and customers only in Business Central with a balance. Near matches are shown as possible with a reason. No customer or company is created or edited.
Business outcome
---
Every client doing project work has a customer to bill, and blocked accounts with live projects are flagged.
scenario
-
People log their hours in Teamwork.com as they work, then fill in Sage Intacct timesheets separately for billing and payroll. Checking that one person's two records agree means exporting both, converting minutes to hours and lining projects and days up by hand.
What popdock provides
--
Name the person and a date range, and it finds them in Teamwork.com and Sage Intacct, stopping if either name matches more than one person. It totals their time by project and by day on both sides, treating gaps under a quarter of an hour as matching, and lists days where only one system has time. It also shows whether the Intacct entries are still draft, submitted or approved, and notes when a gap may close once drafts are submitted. Nothing is changed in either system.
Business outcome
---
You can confirm one person's billable time is fully on their timesheet before it is approved or invoiced.
scenario
-
Delivery teams track a project's health, milestones and budget in Teamwork.com while finance tracks its contract, costs and invoices in Sage Intacct. When the two tell different stories, nobody notices until the project is over budget or the client is far behind on payment.
What popdock provides
--
Name the project, and it reads the Teamwork.com health score, budget used, late milestones and open risks, then the Sage Intacct contract amount, actual cost, percent complete and the customer's open invoices. It compares budget used with cost against contract, and milestone progress with Intacct percent complete, calling out any gap over 15 points. It notes that open invoices cover the whole customer, skips percentages when the contract value is missing, and closes with a short note on what needs attention. Nothing is changed.
Business outcome
---
Delivery and finance see the same project picture, so overruns and billing gaps are raised while they can still be fixed.
scenario
-
Before a project can be set up for a new client in Teamwork.com, someone has to create the client company, usually by retyping details from Sage Intacct. Without a check first, it is easy to create a second company for a client that is already there under a slightly different name.
What popdock provides
--
Name the customer, and it reads their details from Sage Intacct, stopping if the name matches more than one. It checks Teamwork.com for a company with the same or a very similar name and stops rather than creating a duplicate. You see the company to be created, with the country code only filled in when it can be converted with certainty, and nothing is written until you confirm. Any missing email or address details are named in the result.
Business outcome
---
New clients appear in Teamwork.com once, ready for projects, without duplicate companies to tidy up.
scenario
-
Project teams keep doing billable work for clients who are months behind on their invoices, because overdue balances sit in Sage Intacct and the teams live in Teamwork.com. By the time someone raises it, more unbilled work has piled up.
What popdock provides
--
Name the client and an overdue threshold, and it checks Sage Intacct for invoices past due, totalling the amount and noting the oldest due date. It finds the client's active Teamwork.com projects and skips any that already carry an open risk about overdue invoices. You see the risk text and the projects it will go on, and nothing is added until you confirm, then each new risk is read back. The risk mentions only the overdue total, never invoice numbers, since project members may not have finance access.
Business outcome
---
Project teams know when a client is behind on payment before committing more billable work.
scenario
-
Projects get created in Teamwork.com for delivery and in Sage Intacct for billing, and over time the two lists drift. A project missing from Intacct means time that never gets billed, and spotting it means comparing two long lists with different naming habits.
What popdock provides
--
Optionally name a client, and it reads active Teamwork.com projects and open Sage Intacct projects and matches them by name, ignoring case, punctuation and leading project codes. Names that only partly match with the same client are listed as probable matches for you to judge, not counted as matched. You get projects in Teamwork.com only, in Intacct only, and the count of exact matches. It is read-only and stops rather than listing everything when one side returns nothing.
Business outcome
---
Both systems track the same projects, so delivery work does not go unbilled because a project was never set up.
scenario
-
Before billing a project, someone has to check that every hour logged in Teamwork.com made it onto a Sage Intacct timesheet. Comparing person by person across two systems, with names spelt differently and minutes on one side and hours on the other, takes most of an afternoon.
What popdock provides
--
Name the project and a date range, and it totals each person's hours and billable hours on both sides, matching Teamwork.com users to Sage Intacct employees by name without pairing people on a shared first name. You get a table sorted by the largest difference, with gaps under a quarter of an hour treated as matching, and lists of people found in only one system. It says which side is higher rather than calling either wrong, and changes nothing.
Business outcome
---
You bill projects knowing every logged hour is on a timesheet, with the people who need chasing already named.
scenario
-
Account managers talking to a client want to know what work is under way and whether the client is paying. That means checking active projects and hours in Teamwork.com and the balance and aging in Sage Intacct, which rarely happens before a quick call.
What popdock provides
--
Name the client, and it finds them in both systems, carrying on with whichever side has them if the other does not. It lists active Teamwork.com projects with owners, end dates and billable hours in the last 30 days, then the Sage Intacct balance, credit limit and percentage used, and open invoices aged by due date. A one-line flag warns when billable work continues with invoices over 60 days overdue or the balance is over the limit. Nothing is changed.
Business outcome
---
Account managers go into client conversations knowing both the work in flight and the money owed.
scenario
-
When a project starts in Teamwork.com, finance still has to create a matching project in Sage Intacct before time and costs can be billed. Retyping names, dates and the client by hand invites duplicates and projects attached to the wrong customer.
What popdock provides
--
Name the Teamwork.com project and an Intacct category, and it reads the project and checks Sage Intacct for one with the same or a very similar name, stopping rather than creating a duplicate. It finds the matching Intacct customer, asks you to pick when there are several, and never creates a customer. You see the name, category, customer, dates and description, and nothing is created until you confirm. The new project is then looked up and its ID reported.
Business outcome
---
Billing projects exist in your ledger as soon as delivery starts, attached to the right customer and never duplicated.
scenario
-
What a client signed for lives in Rillet, while what the team plans and burns lives in Teamwork.com project budgets. Comparing the two means lining up contract terms with budget dates by hand, and a project quietly planned beyond what was sold, or still running after the contract ended, goes unnoticed until the margin is gone.
What popdock provides
--
Name the client and it reads their contracts and contract items in Rillet, then finds the matching Teamwork.com company, by name or by email domain, and reads the budget on each project. Each budget is paired with the contract whose term overlaps it, and hour budgets are converted only when a default rate is set, with a note saying so. It flags budgets above contract value, usage beyond what the client pays for, contracts or budgets with no partner, ended contracts on active projects and term dates more than 30 days apart. Currencies are never converted, and nothing is changed in either system.
Business outcome
---
You see where delivery plans have drifted past the contract before the overrun lands on an invoice nobody can send.
scenario
-
When finance adds customers in Rillet, the delivery team still has to recreate each one as a client company in Teamwork.com before work can be tracked. Doing it by hand means checking every name first, and a slightly different spelling or a missing legal suffix produces a second company for the same client.
What popdock provides
--
Optionally give part of a customer name, and it reads your Rillet customers with their location and billing email, then checks Teamwork.com for each one by name, ignoring case, punctuation and legal suffixes, and then by contact email. Anything that matches, even loosely, is left alone, and anything matching more than one company is listed as ambiguous rather than created. You see the companies to be created, can remove rows, and nothing is written until you confirm. Each new Teamwork.com company id is reported, and a create rejected for an existing name is called out as a missed match.
Business outcome
---
Every Rillet customer has a Teamwork.com client to track work against, with duplicates treated as worse than a gap.
scenario
-
A client can be months behind on Rillet invoices while your team keeps logging hours on their Teamwork.com projects. Finance and delivery rarely look at the same screen, so nobody notices until the unpaid balance has grown by another month of work.
What popdock provides
--
Optionally set a minimum overdue amount and a lookback window, and it totals each customer's overdue Rillet invoices with the oldest due date, then finds their Teamwork.com company and the time logged on its projects in that window. You get one row per customer still receiving work, sorted by what they owe, with hours, billable value and the people involved, plus a short list of overdue customers with no recent time. Clients it cannot match are marked as not found rather than idle. It posts nothing in Teamwork.com and changes nothing in Rillet; you decide who to talk to.
Business outcome
---
You catch clients who are not paying but still getting work, before another month of unbilled effort piles onto the balance.
scenario
-
Billing a project means exporting Teamwork.com time, grouping it by rate, finding the matching Rillet customer and product, and typing the invoice lines in. It is slow, and it is easy to bill the same period twice or miss a rate that was never set.
What popdock provides
--
Name the project, the period and optionally the product, and it reads the billable Teamwork.com time grouped by rate, then matches the client to a Rillet customer by name or company email domain and says which rule matched. Before drafting, it looks for existing Rillet invoice lines that overlap the period or name the project and asks whether to continue. You see the draft lines beside the Teamwork.com total, zero-rate time is set aside for you, and the invoice is created in Rillet only after you confirm. It never creates customers or products, and an error is shown rather than retried with changed values.
Business outcome
---
Project time becomes a correct Rillet invoice in one pass, with a double billing check before anything is created.
scenario
-
Renewal conversations go badly when nobody checked how delivery is going first. The contract end date is in Rillet, but late milestones, open risks and unhappy project updates are scattered across Teamwork.com, so a renewal at risk looks safe until the client says no.
What popdock provides
--
Set how many days ahead to look, and it lists the active Rillet contracts ending in that window with each customer's overdue balance. For each client it finds the active Teamwork.com projects and reads their health score, latest update, late milestones and open risks. Each renewal is rated High, Medium or Low by stated rules, such as any late milestone or overdue invoice making it High, and every High row gets one sentence of reasoning. Clients not tracked in Teamwork.com are rated on the Rillet side alone, and nothing is changed in either system.
Business outcome
---
Account teams walk into renewals knowing which ones are at risk and why, with time left to fix delivery first.
scenario
-
Client lists drift apart when delivery adds companies in Teamwork.com and finance adds customers in Rillet. A client with active projects but no Rillet customer may never be invoiced, and checking the two lists against each other by eye misses near matches and different spellings.
What popdock provides
--
Optionally narrow by part of a company name, and it reads the Teamwork.com companies and the Rillet customers with their emails. Names are matched ignoring case, punctuation and legal suffixes, then unmatched companies are tried by contact email or shared company domain, never a public mail domain and never on city alone. You get four sections, matched with any address differences, Teamwork.com only with project-holding companies first, Rillet only, and ambiguous, plus counts. Your own site company is left out and noted, and nothing is changed.
Business outcome
---
You find clients that are being served but never billed, and fix the gaps before month end.
scenario
-
Knowing whether a client is worth keeping means setting invoiced revenue in Rillet against the cost of the hours logged in Teamwork.com. Pulling both, matching the client and netting out credits takes an afternoon, and people with no cost rate quietly make the margin look better than it is.
What popdock provides
--
Name the client and a period, and it reads every Teamwork.com project's hours, cost and billable value, then matches the client to a Rillet customer by name or company email domain and totals invoice lines in the period, less credit memos. The report shows margin and margin percent, revenue per hour and billable value not yet invoiced. It names anyone with hours but no cost rate and says the margin is overstated by their time. Revenue is stated as invoiced, not recognized, currencies are never converted and nothing is changed.
Business outcome
---
You get an honest margin for each client, with its blind spots named, before deciding on rates or renewals.
scenario
-
Billable hours logged in Teamwork.com do not always make it onto a Rillet invoice. There is no link between a time entry and an invoice line, so checking means adding up time per project, adding up invoiced amounts for the same period, and guessing where the gap came from.
What popdock provides
--
Name the client and a period, and it totals billable Teamwork.com time per project, noting unverified entries, then finds the Rillet customer by name or company email domain and totals the invoice lines for that period net of credits. If time exceeds invoicing by more than 5 percent it calls out probable unbilled time and lists the ten largest entries. If Rillet is higher it checks for a fixed-fee or retainer contract. It says plainly that the comparison is by amount and period only, flags time with missing billable rates and changes nothing.
Business outcome
---
Unbilled work is found and sized while it can still go on an invoice, not written off at year end.
scenario
-
A Teamwork.com budget can look fine in total while being spent far faster than the project's timeline allows. Working out used versus elapsed share for each budget, and the recent pace, takes a calculator and several screens.
What popdock provides
--
Name the project, and it finds it in Teamwork.com, listing candidates if the name is ambiguous, and reads every budget on it. Each budget's used share is set against the share of its time that has passed and rated over, burning fast, underused or on pace, with repeating budgets marked as approximate. It adds the last four weeks of logged hours, and projects a run-out date only when the units plainly match. It is read-only and keeps money and hours in the units the budget returns.
Business outcome
---
Project managers spot budgets burning too fast while there is still time to agree more or slow down.
scenario
-
Logging time in Teamwork.com means finding the right project and task, converting a rough duration into hours and minutes, and remembering whether you already logged it. Pick the wrong task or log twice and timesheets and budgets go wrong.
What popdock provides
--
Give the project, the task, the time spent and an optional description, and it finds both in Teamwork.com, listing candidates if either is ambiguous and asking before logging against a completed task. The duration is parsed into hours and minutes, and it asks if it is unclear, zero or over 12 hours. If an entry with the same minutes already exists today, it asks whether this is a second one. Nothing is logged until you confirm, then the entry is created once and read back.
Business outcome
---
Time lands on the right task once, keeping timesheets and project budgets accurate.
scenario
-
Turning a written brief into a Teamwork.com task list means breaking the work down, estimating it, spreading due dates and typing every task in. It is slow, and when the list already exists it is easy to add tasks that are already there.
What popdock provides
--
Give a project, a task list name, the brief and an optional finish date, and it drafts three to fifteen tasks with verb-first names, descriptions, estimates, priorities and due dates spread in working order. If the list already exists in Teamwork.com, tasks already in it are skipped. You see the plan as a table and nothing is created until you approve or edit it. Tasks are then created in order and checked back, a failed create stops the run without a retry, and it notes that tasks are left unassigned.
Business outcome
---
A brief becomes a ready, estimated task list in minutes, without duplicating work already planned.
scenario
-
Moving a Teamwork.com milestone means checking the open work behind it to pick a realistic date, then telling people why it moved. Without that check, a new deadline is often as unrealistic as the old one.
What popdock provides
--
Name the project and milestone, and optionally a new date, and it finds the milestone in Teamwork.com and reads its open tasks: the count, overdue work, the latest due date, undated tasks and remaining estimates. With no date given it proposes the latest task due date plus two working days, and it warns if your date falls before open work. You confirm the date change and, separately, an explanatory comment. Only the deadline is changed, the result is read back, and task dates are left for you to decide.
Business outcome
---
Milestones move to dates the remaining work supports, with a recorded reason everyone can see.
scenario
-
Before giving someone more work you need to know what they already have in Teamwork.com: overdue tasks, what is due soon, and how much time they have logged. Pulling that together across projects is slow, so decisions get made on a hunch.
What popdock provides
--
Name the person and a window, and it reads their open Teamwork.com tasks grouped into overdue, due in the window, due later and undated, their logged hours for the last two weeks by project, and the projects they belong to. It compares estimated hours due against working hours in the window, labelled as an assumption, and calls them overloaded, busy or has room with the reason. It is read-only, notes how many tasks lack estimates, and does not suggest handing tasks to named colleagues.
Business outcome
---
Managers make assignment decisions from real workload evidence rather than guesswork, before anyone is overloaded.
scenario
-
Before billing or payroll, someone has to go through Teamwork.com time entries looking for time with no task, blank descriptions, impossible hours and unbillable time on billable projects. Scanning hundreds of rows by eye misses things.
What popdock provides
--
Give a date range, and optionally a person, and it reads the time logged in Teamwork.com and each project's billable setting. It flags entries with no task, no description, more than eight hours, or marked unbillable on a billable project, notes weekend entries, and lists person-days over ten hours and unverified entries. You get totals and billable share per person with the flagged entries grouped by reason. It is read-only, words each flag as a question, and says when the 500-entry limit means the audit may be incomplete.
Business outcome
---
Timesheet problems are caught before invoices and payroll go out, without reading every entry.
scenario
-
A risk register is only useful if it is kept up, but in Teamwork.com risks go stale, severe ones sit without a mitigation plan, and troubled projects often log no risks at all. Checking all of that by hand rarely happens.
What popdock provides
--
Optionally name a project and a staleness threshold, and it reads the open risks in Teamwork.com and flags each that has no mitigation, is stale or is severe, putting severe unmitigated risks first. It also checks active project updates rated bad and lists those projects with no open risk as gaps in the register. You get counts, a sorted table and up to three recommendations naming the risks or projects concerned. It is read-only and recommends new risks rather than creating them.
Business outcome
---
Your register reflects real risk again, with the dangerous gaps called out for an owner to act on.
scenario
-
Rating a portfolio of Teamwork.com projects means checking each one's health score, latest status update, late milestones and open risks. By the time it is compiled by hand, the picture is already out of date.
What popdock provides
--
Optionally name a company or category, and it lists the active Teamwork.com projects and pulls health scores, active status updates, late milestones and open risks in one pass. Each project is rated red, amber or green by stated rules, with dormant projects marked separately, and every red and amber rating carries its reason. The report ends with the three projects most in need of attention. It is read-only, shows a missing health score as no score rather than good, and warns when the list may be truncated.
Business outcome
---
Leaders see which projects need attention across the portfolio, with a clear reason behind every rating.
scenario
-
Writing a weekly status report for a Teamwork.com project means collecting the latest health update, milestones, overdue tasks, risks and logged time from different views. The result often repeats the posted status instead of the evidence.
What popdock provides
--
Name the project and a lookback period, and it reads the active status update and health score, open milestones, overdue tasks, open risks and time logged in Teamwork.com. It gives a verdict of on track, at risk or off track using stated rules, flags a status update older than 14 days, and lists late milestones, the most overdue tasks, unmitigated risks and billable versus non-billable hours, with up to three next actions. It is read-only, reports only what it found, and calls an empty risk register empty.
Business outcome
---
Status reports are built from evidence in minutes, so stakeholders get an honest verdict each week.
scenario
-
Overdue tasks pile up in Teamwork.com, and the list does not say which matter, who owns them, or which are actually finished. Going through them one by one to decide what to chase takes longer than the chasing.
What popdock provides
--
Optionally name a project or person, and it reads overdue open tasks in Teamwork.com, puts names on assignees and projects, and ranks them by priority and then days overdue. You get totals, high-priority and unassigned counts, overdue tasks per assignee, and the top 20 with their progress. Each of the top ten gets a recommendation to chase the assignee, find an owner, re-date it or close it if it looks finished. It is read-only, carries out none of the advice, and stops rather than widening a scope that matches nothing.
Business outcome
---
Overdue work gets a clear next step per task, so the important items are chased first.
No items found.
Ready to unlock your data?
Start building tools that turn your business systems into AI superpowers
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.