Laserfiche WebLink
A P P R O A C H & M E T H O D O L O G Y <br />Scheduling <br />“A schedule that no one updates is a schedule no one believes. Ours <br />is reviewed every week, in writing, with the owner.” <br />SCHEDULE DISCIPLINE IS A DELIVERABLE, NOT A BYPRODUCT. <br />How we build the schedule. Every task order begins with a <br />backward-planned milestone schedule built from the owner’s required <br />completion date, not forward from the notice to proceed. We fix the <br />permit submittal date first, then work backward through the 100%, <br />90%, 60%, and 30% design reviews required under RFQ Section 3.4, <br />adding explicit float ahead of any authority-having-jurisdiction review <br />we do not control. Durations come from a logged history of <br />comparable projects. <br />How we maintain it. The schedule is issued as a one-page milestone <br />view the owner can read in thirty seconds. It is updated weekly and <br />reissued at every Gateway Review with three items flagged in plain <br />language: what moved, why it moved, and what it costs in calendar <br />days. <br />Example — concurrent review to protect a permit window. On <br />Gelato & Co (Jupiter, FL), imported Italian equipment, landlord design- <br />standard review, and Palm Beach County health department <br />requirements all sat on the critical path. Rather than sequence them, <br />we released a landlord-review set and a health-department equipment <br />package in parallel with ongoing construction documentation, holding <br />a single coordinated model so that comments from either reviewer <br />could be absorbed without restarting the set. The permit application <br />went in on the originally committed date. <br />Challenge — a mid-design change of ownership. On Urban Roast <br />(West Palm Beach, FL), the property was sold partway through design, <br />requiring renewed approvals from an entirely new landlord while the <br />operator’s opening date held firm. We froze the drawing set at its <br />then-current state, produced a short conformance package the new <br />ownership could approve on its own terms, and ran consultant <br />coordination on the unaffected building systems concurrently rather <br />than pausing the team. The approval reset consumed the float we had <br />reserved ahead of permitting; the project reached closeout in July <br />2026. <br />S CH E D U L IN G TOOL S <br />REP O RTI NG CA D E NCE <br />W HE R E F LOAT IS R ESE R VE D <br />Float is held ahead of the three review gates we do not control — Miami- <br />Dade County and DERM permitting, City building review, and utility or <br />franchise coordination — rather than distributed evenly across the design <br />phases. This keeps schedule contingency where schedule risk actually <br />lives. <br />HOW T HE P R O G RA M ME I S B UILT <br />PLANNED BACKWARD FROM <br />THE OWNER’S DATE <br />Discovery <br />Concept <br />Design Dev <br />Const. Docs <br />Permitting FLOATOWNER <br />DATE <br />Permitting overlaps the close of <br />documentation — it does not follow it. <br />Gateway Review — go or revise <br />Float, held ahead of agency review <br />Durations set from the fixed date <br />Responds to RFQ # 26-07-01, Section 5, Item 4 — Approach / Methodology (scheduling). <br />One-page owner milestone view, reissued at every Gateway Review– <br />Autodesk Construction Cloud — live model and document status– <br />Historical duration log from comparable South Florida projects– <br />Permit-tracking log per authority having jurisdiction– <br />Weekly — written progress note; two-week look-ahead– <br />Per phase — Gateway Review; schedule reissued– <br />Within 1 business day — written notice of any slip over five working <br />days <br />– <br />Construction — weekly site meeting; field observation report– <br />DEMPSEY DESIGN S CHE DULING · RFQ # 26-07-01 PAGE 7 5 OF 113←→↑APPROACH