Build Construction Schedules That Teams Actually Trust

In partnership with

Welcome back to Beyond Deadlines newsletter—a free perk for people looking to improve in Planning and Scheduling. Each week, we provide tactics, prompts, jobs and food for thought. We want you to succeed today, tomorrow and throughout the rest of your career.

❝

Most first drafts can be cut by 50 percent without losing any information or losing the author’s voice.

On Writing Well by William Zinsser

Scheduling Tactic: Build the Plan Where the Work Lives

Your schedule does not start in P6.

It starts in the heads of the people closest to the field, the constraints and the sequence. The software is where the plan gets formalized. But if you build it only inside a CPM tool, far from the people doing the work, you end up with a technically correct document that nobody trusts.

The best tactic a scheduler can use? Start planning in the language of the team. Then translate it into contract logic.

Too many schedules are built backward. A scheduler develops a polished network first, then pushes it downhill to the project team for "buy in." The field reviews it late. They spot sequence issues, means and method conflicts, missing handoffs, access problems and trade stacking concerns. Then the schedule gets revised under pressure.

A better approach is to build in two layers.

Layer one: Collaborative planning. Start with whiteboarding, pull planning, sticky notes, phase maps or any visual method that helps the team think about how the work should flow. This is where you uncover the truth of the job. Who needs access first? What inspections will break flow? Where are the crew bottlenecks? Which handoffs are fragile? What work can actually run in parallel versus what only looks parallel on paper?

Layer two: CPM translation. Once the team driven sequence is clear, the scheduler structures it into formal logic, durations, calendars, milestones and reporting frameworks. The scheduler's value is not typing activities into software. It is converting field reality into a plan you can govern, defend and analyze.

A schedule built only for compliance becomes brittle. A schedule built from collaborative sequencing and then elevated into CPM becomes resilient. It is easier to update, easier to defend and far more likely to reflect how the project will actually move.

This also improves adoption. Supers and trade partners use a schedule they helped shape. PMs trust it more. Executives get a cleaner signal because the logic is grounded in execution, not theory.

The trap is thinking collaboration means giving up rigor.

It does not. Collaborative planning without schedule discipline becomes sticky note theater. CPM without field input becomes spreadsheet fiction. The winning move is joining both worlds.

So here is the takeaway for your next project kickoff. Do not start by asking what activities belong in the software. Start by asking how the work will flow. Then build the schedule around that answer.

That is how you create a plan people can execute. Not just admire.

Become An AI Expert In Just 5 Minutes

If you’re a decision maker at your company, you need to be on the bleeding edge of, well, everything. But before you go signing up for seminars, conferences, lunch ‘n learns, and all that jazz, just know there’s a far better (and simpler) way: Subscribing to The Deep View.

This daily newsletter condenses everything you need to know about the latest and greatest AI developments into a 5-minute read. Squeeze it into your morning coffee break and before you know it, you’ll be an expert too.

Subscribe right here. It’s totally free, wildly informative, and trusted by 600,000+ readers at Google, Meta, Microsoft, and beyond.

Convert a .pdf into Excel

Copy and paste this prompt into ChatGPT, Gemini or Claude.

Act like a senior Primavera P6 scheduler and PDF-to-data extraction specialist.

Your goal is to convert a Primavera P6 schedule PDF export into an Excel-ready table with one row per activity, using only the information visible in the PDF.

Task: Extract all activities from the PDF and output a clean CSV that can be pasted into Excel.

Step-by-step process:
1) Scan the entire PDF to understand the report layout (tabular report, grouped by WBS, multi-page headers, wrapped text, etc.). Identify the exact column headings that appear and how WBS group rows are displayed.
2) Create the target Excel schema with these columns in this exact order:
- WBS Name
- Activity ID
- Activity Name
- Start
- Finish
- Original Duration (days)
- Remaining Duration (days)
- % Complete
- Total Float (days)

If any of these fields are not present in the PDF, include the column anyway and leave those cells blank.

3) Extract every activity row across all pages. When the PDF shows WBS/group header lines, treat them as the current WBS Name and apply that WBS Name to subsequent activity rows until a new WBS header appears.
4) Clean and normalize the extracted values:
- Dates: output as YYYY-MM-DD (do not change the meaning of the dates).
- Durations and Total Float: numeric days only (remove units, commas, or extra text).
- % Complete: numeric 0–100 (remove the percent sign if present).
- Preserve Activity ID exactly as shown.
- Merge wrapped cell text so each activity stays on one row.
5) Validate: ensure one activity per row, no duplicated rows, and that Activity ID and Activity Name are captured whenever legible.
6) Output: Provide a single CSV inside one code block with a header row. If the CSV is very large, split into multiple code blocks labeled Part 1, Part 2, etc., repeating the header each time.
7) After the CSV, add “Data quality notes” listing: missing columns, any UNREADABLE fields, and the page number(s) where issues occurred.

Constraints:
- Do not invent or infer values. If uncertain, leave blank or write UNREADABLE.
- Do not ask clarifying questions; proceed with the best faithful extraction from the PDF.

Take a deep breath and work on this problem step-by-step.