You know the moment. A deal is moving and someone asks for a schedule that ties to carry and a credible stabilization date. You can sketch phases on a pad, but that falls apart once you need dependencies, float, and a real critical path. Building it properly in Excel takes time and focus. You have to sequence predevelopment, entitlements, design, permitting, financing, construction, and lease up, then tie the dates back to the business plan. It is repetitive work, and it still calls for judgment. Development ~10 min to run Build a Development Schedule from Site Control to Stabilization Vic prompt Use Vic to build a development schedule for a project from site control through stabilization. Purpose Reconciles the timeline to carry costs and time-to-stabilization so teams can price entitlement risk and maintain schedule contingency. A human analyst takes about 90 minutes; this completes in about 10 minutes. Inputs Property Type Optional Development Program Optional Entitlement Status Optional Phase Durations Optional Start Date Optional Outputs An Excel schedule listing phases and milestones with start, duration, finish, predecessors, and float, plus critical path highlighted and a short summary of date drivers and likely slippage points. Time saved Turns roughly 90 minutes of manual work into about 10 minutes. How it works Run the task with a simple command: "Use Vic to build a development schedule for a project from site control through stabilization." Then hand over what you have. Property type, development program, current entitlement status, assumed phase durations, and a start date all help, but none are required. Vic lays the project out on a timeline from site control through stabilization. The schedule orders the core phases: predevelopment, due diligence, entitlements, design, permitting, financing close, construction, lease up, and stabilization. Each phase is linked with predecessors so the timeline behaves like a real project instead of a list of dates. The output is an Excel schedule with phases and milestones, including start, duration, finish, predecessors, and float. The critical path is called out so you can see what drives the end date. Vic also flags entitlement risk and adds contingency to phases that tend to vary, so the plan does not pretend to be more precise than it is. Alongside the file, you get a short summary that names the date drivers and likely slip points. This is the part most teams try to explain in a meeting. Writing it down forces clarity about where the schedule is tight and where it has room. The value is not just a neat spreadsheet. The schedule ties back to carry costs and time to stabilization, which is what your capital partners and IC care about. When entitlement risk is visible in the timeline and contingency sits on the right phases, you can price that risk instead of hand waving it. It also makes iteration cheap. If the entitlement status changes or you want to test a faster permitting assumption, rerun the task with updated inputs and get a revised critical path in minutes. That beats editing a fragile workbook late at night. This used to take a focused hour and a half from someone who knows the work. Now it is about ten minutes to a clean first pass, with the right structure in place. You still set durations and judge risk, but you are not burning time on setup. If you run development or acquisitions, this closes a common gap between a concept and a schedule you can defend. You get a timeline you can show, tweak, and stand behind.