Kenji SatoTuesday, ten o'clock. Legal comes back. The approval you had as one step is really three, and one of them needs a fortnight. You know exactly what the plan should say now. You cannot change it.
This is for the person who owns one branch of a bigger plan, while someone else maintains the master. Today your choices are to message them and wait, or to let your part quietly become wrong. It is not a fit if you are the only person in the plan.
In plain English: if the branch is yours, you describe the change in a sentence, review the Ask AI patch, and apply it — without waiting until Thursday.
What a small change actually costs
At 10:05 you could have fixed it. At 16:00 you message the person who maintains the plan. They are in back-to-backs until Thursday. Wednesday they reply asking what you meant, and you explain again, in more words than the first time. Thursday they make the edit. It is nearly right. You let it go, because asking a third time costs more than the inaccuracy does. Friday somebody plans their own work against the version that is nearly right.
Four days of latency and one small permanent error, from a change you understood completely before your first coffee on Tuesday.
If Tuesday at ten already happened this month, keep reading. The next part is the conversation, then the draft beside the tree.
If the branch is yours, you talk to it yourself
In Goalpen, seeing a branch and being able to change it are two different things. Amend rights go to the person named as owner of that branch, and to the people assigned to it. If that is you, you do not wait on the person who owns the master.
You open the branch. You select the part that moved — the legal approval, not the whole delivery. You tell Ask AI what happened, the way you would tell a colleague: “This is no longer one step. Split it into submit, review, and countersign. Countersign takes ten working days. Keep the rest of the branch as it is.”
What comes back is a proposed patch sitting beside the live tree: the work renamed, the extra steps added underneath, the durations changed. You can argue with it before any of it is real. “More detail on the review.” “Shorter.” “Rebuild this part under the goal a different way.” Nothing on the live tree moves until you press Apply. Undo is there afterwards. When a patch would touch sub-tasks that already exist, it tells you how many and waits for you to confirm — so reshaping your branch cannot quietly swallow work somebody else is in the middle of.
While it is drafting it will not delete, move or reorder your existing work, and it will not touch a branch when you have nothing selected, unless you are asking about the whole tree. Ask AI is on the Team and Business plans. A Free workspace sees a demo of that helper, plus an upgrade prompt.
The four-day wait becomes a minute of reading. The nearly-right edit never happens, because you were the person who understood the change.
Try it on the last change you had to ask someone else to make
Open that branch. Select the part it affected. Describe the change in one sentence. Read the patch. Apply it or dismiss it — either way you will know within a minute whether this removes a Thursday from your week.
Prefer to talk it through first? Use Contact us. Want the numbers before anything else? Skim Pricing. No hard sell either way.
*Current page check: “without waiting until Thursday” (13 August 2026).*