Monday.com Project Timeline From a Brief
Plan phases, dependencies and dates for a timeline view.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Create a project timeline for monday.com from this brief: [PROJECT_BRIEF]. Start date: [START]. Deadline: [DEADLINE]. People available and their time: [PEOPLE]. Known fixed dates: [FIXED_DATES]. Public holidays: [HOLIDAYS]. Return phases as groups and tasks as items with owner role, start date, end date, duration, dependency (by item name), status and a risk level. Show date arithmetic in a table of item, start, working days and end, counting weekends out and moving any weekend end date to the next working day; state which holidays you ignored. Example: a start on Monday 3 March, 10 working days for Design, then 15 for Build, then 5 for Test. Identify the critical path as a list, flag items that exceed a named person's capacity in the same week, and show where the plan meets or misses the deadline. If it misses, give two options: reduce scope (name items) or add capacity (state roles). Do not invent people or dates. Add What could move the deadline: the three items whose delay would move it most and what to do if each slips; a risk register of three risks with trigger dates and responses; a weekly review of four steps (update statuses on Monday, check critical path items first, flag anything more than two days late, decide by Wednesday what to cut or re-plan); a plain-text version of milestones and dates for email; and a weekly sponsor update stating progress against plan in one number. Dependency columns and timeline views vary by plan [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.
See an example result (fictional data)
Invented example: start Monday 3 March, 10 working days for Design, then 15 for Build, then 5 for Test. Design ends Friday 14 March. Build runs 17 March to 4 April (15 working days). Test runs 7 to 11 April. Deadline 11 April met with zero spare days. Critical path: Design, Build, Test. Risk: Build has no slack. Check of the dates: Design 3 to 14 March is 10 working days; Build 17 March to 4 April is 15 working days; Test 7 to 11 April is 5 working days. Total 30 working days. If Build slips by two days, the deadline is missed by two days unless Test is shortened. Suggested mitigation: start Test planning during Build.
Illustrative only, made-up data. Your results will differ and must be reviewed.