The schedule, current every week.
Included in Full Office and Enterprise, or priced by the job on its own
Send what you have. Get the finished document.
You send
- The contract schedule or the milestone dates, and the plan set
- The super's weekly update: what finished, what started, what slipped, as a text, a photo or a marked-up sheet
- Lead times for long-lead items, from the submittal log or the suppliers' quotes
- The inspections the permit calls for, and any special inspections
- The subs' start dates and your crew's availability
- The format the owner or GC wants the schedule in, if the contract names one
You get
- A job schedule built from the contract dates and updated every week
- A two-week look-ahead by trade for the crew and the subs, sent every week
- Inspections requested and deliveries confirmed against the look-ahead
- Sub start dates confirmed in writing, with the look-ahead attached
- The schedule update in the owner's format when the contract asks for one with the pay app
- A line in the daily note when a date moves: what slipped, why, and what it pushes
4 steps, one of them a person.
- Step 1
You send the dates
The contract dates, the plan set and the super's update. A text or a photo of the board is enough.
- Step 2
Agents update the schedule
Finished work is marked, slipped work is moved, and everything that depends on it moves with it. Lead times come from the submittal log.
- Step 3A person checks this
A person checks every date
Moved dates are checked against the super's update, the inspections and the subs' confirmations before anything goes out.
- Step 4
The look-ahead goes out
The crew and the subs get the two-week look-ahead. The owner gets the schedule update in the format the contract names.
Notes from the desk
Notes from the scheduling desk
Most schedules go stale for one of four reasons. The update comes from memory at the end of the month instead of from the field every week. Lead times are guessed instead of taken from the submittals. Inspections are not on the schedule, so work waits on them. A slipped activity moves, but what depends on it does not.
We check all four every week, before the look-ahead goes out.
The two-week look-ahead
The look-ahead is the part of the schedule the crew uses: two weeks, by trade, with the inspections and deliveries on it. It goes to the super and the subs every week, and a sub's start date is confirmed in writing before it goes on the sheet.
When a date moves
Send the reason the day it happens: a late delivery, a failed inspection, a change order, the weather. The schedule moves once, with everything that depends on it, and the daily note says what slipped and what it pushes. If the contract asks for written notice of a delay, the notice is drafted for your signature the same day.
On the page, like everything else.
One-off
Let's talk
priced by the job
The weekly look-ahead on Full Office. CPM schedules, site logistics and safety plans on Enterprise.
Asked on the first call.
Which software do you keep the schedule in?
Yours, or the format the contract names for schedule updates. Where there is none, a PDF and a spreadsheet the super can read on a phone.
Do you book the inspections?
We request them the way your building department takes requests, against the look-ahead, and log each result. Your super meets the inspector.
A sub is late. What happens to the schedule?
The late activity moves, everything that depends on it moves with it, and the look-ahead shows the new dates. The daily note says what slipped and what it pushes.
Usually handed over together.
RFIs and submittals
RFIs drafted, submittal registers built from the spec, every review chased to a stamp.
Permit paperwork
Permit filings and renewals prepared, checked by a person, chased to the permit.
Pay applications
G702 and G703 built from your SOV, waivers attached, in by the cutoff every month.
Hand this one over.
Tell us about the job. Shahzeb calls within 12 hours. You get the first finished document in 2–7 days.
Prefer the phone? Call (718) 213-0230, Mon–Fri, 7:00 am – 5:00 pm ET.