/
/
Move a Teamwork.com milestone to a date the work supports
For project managers who want a realistic new milestone date in Teamwork.com, based on the open work, by asking their AI assistant.
On this page
Connector
Connect Teamwork.com, pick your AI tool and paste the prompt.
The problem
Moved milestones that miss their new date too
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, the new deadline is often as unrealistic as the old one.
Without PopdockAI
- Open every task list behind the milestone
- Count overdue and undated tasks by hand
- Pick a new date that feels about right
- Explain the change in a separate message
With PopdockAI
- Open tasks, overdue work and remaining estimates are read
- A date is proposed, or yours is tested against open work
- You confirm the date and the comment separately
- Only the deadline changes, and the result is read back
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Move the deadline of the milestone matching {milestone-name} in the Teamwork project matching {project-name} to {new-deadline}, or to a proposed date when that is blank, and record why.
**Step 1: Identify the project**
Call `teamwork-get-projects` with `name.contains` set to {project-name}. If nothing matches, say so and stop. If more than one project matches, list them with `project-name`, `company-name` and `status`, ask which one is meant, and stop. Keep the `project-id` for every later call.
**Step 2: Identify the milestone**
Call `teamwork-get-milestones` with `project-id` and `name.contains` set to {milestone-name}. If more than one matches, list them with `deadline` and `completed`, and stop. If it is already completed, say so and stop. Keep `milestone-id`, `deadline` and `original-due-date`.
**Step 3: Look at the remaining work**
Call `teamwork-get-tasklists` with `milestone-id`, then `teamwork-get-tasks` with each `task-list-id`. Ignore completed tasks. Work out: open task count, overdue open tasks, the latest open `due-date`, open tasks with no due date, and total `estimate-minutes` remaining.
**Step 4: Settle the date**
* When {new-deadline} is given: check it is an ISO date after today. Warn, but do not refuse, when it falls before the latest open task due date.
* When it is blank: propose the latest open task due date plus two working days. If no open task has a due date, ask the user for a date and stop.
**Step 5: Confirm, then write**
Show the milestone, its current deadline, the new deadline, and the evidence from Step 3. Draft a one-paragraph comment giving the old date, the new date and the reason. Ask the user to confirm the date change and, separately, whether to post the comment. Only after an explicit yes:
1. Call `teamwork-update-milestone` once with `milestone-id` and `deadline`, and nothing else.
2. If the user agreed to the comment, call `teamwork-create-comment` once with `object-type` milestone, `object-id` the milestone-id, and `body` the agreed text. Leave `notify` blank unless the user named who to notify.
**Step 6: Verify**
Call `teamwork-get-milestones` with `project-id` and `name.contains` again and confirm the new `deadline`. Report the before and after dates.
**Rules & Guidelines:**
* The only write tools this prompt may call are `teamwork-update-milestone` and `teamwork-create-comment`, each once, after confirmation.
* Do not change task due dates with `teamwork-update-task`, and do not call `teamwork-complete-milestone`. List tasks whose due dates now fall after the new deadline so the user can decide.
**Validation:**
* When the milestone has no task lists, say so, and base the proposal on the user's date only.
* When the update fails, report the error and do not post the comment.Who it's for
One answer, three teams that use it
Project managers
Pick a date you can actually hit
See the open and overdue work behind the milestone before you commit to a new date with the client.
What is a realistic new date for the UAT sign off milestone on the Contoso rollout in Teamwork.com?
Delivery leads
Test a date someone has asked for
Check a requested date against open work and get a warning if tasks are still due after it.
Can we move the Go live milestone on the Northwind Traders project to 12 December? Check the open tasks first.
Project coordinators
Record why a date moved
An explanatory comment goes with the change, so everyone following the project can see the reason.
Move the Design complete milestone on the Fabrikam site project to 20 November and add a comment explaining why.
How it works
What PopdockAI does when you ask
You name the milestone and your AI assistant checks the work behind it before suggesting a date. Nothing changes until you confirm, and task dates are left for you to decide.
01
Ask
You name the project and milestone, and optionally a new date.
02
Check
It reads open tasks, overdue work, latest due date and remaining estimates.
03
Confirm
You agree the date and, separately, the explanatory comment.
04
Update
It changes only the deadline and reads the before and after dates back.
What PopdockAI provides
The tools behind the answer
Ready made tools for Teamwork.com and one secure connection to your AI tool. No code, no exports.
teamwork-com-get-projects
teamwork-com-get-milestones
teamwork-com-get-tasklists
teamwork-com-get-tasks
teamwork-com-update-milestone
teamwork-com-create-comment
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
Milestones moved to dates the work supports
Related use cases
More ways to put this data to work
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

.webp)
