Programme of works
Misr Abu Dhabi for Real Estate Investments · Belmazad with GAT
Company says who is responsible; Discipline says which team; Belmazad + GAT is joint work (split bar, task text names who leads). Tick tasks to select them (a bar appears with Delete selected); tick exactly two to link them, or type links in Comes after: 12 = after 12 finishes · 12SS+3 = 3 days after 12 starts · 12FF = finish with 12. A typed Start is pinned; clear it to return to automatic. Days = 0 makes a milestone. Rows marked edited or added were changed by the team and are kept when the standard plan is updated. Drag header edges to resize columns; drag the table's bottom-right corner to make it taller.
Company is the responsible party; Discipline the team; Belmazad + GAT is joint work (split bar). Milestones are diamonds; the last row of each project is held float. Hover a bar for its dates. Use the tabs to view each project or both together, zoom with − / Fit / +, and export to Excel or PDF.
Sphinx runs on its own clock; its Day 1 is placed so that its launch (M3) falls the chosen number of weeks after Roshdy's launch. Hatched bars and the purple chip are Sphinx; solid bars are Roshdy. Tasks from both projects are listed in one sequence, ordered by start date and then end date, so you can see what both projects and the shared GAT / software teams are doing in the same week.
Each programme assumes two negotiation rounds in two weeks (clarifications, then best and final offers); each additional round adds about one week. MAD approvals are shown at 5 working days (10 for the full RFP); a longer approval moves everything after it. The last row of each project is held float — contingency before the commitment date.