Procore submittal dates need a schedule revision trace

Keep the planned date attached to its inputs

Procore's September 15 update says its open-beta Dynamic Submittal Plan links a submittal to a schedule activity, works backward from when material is needed on site, calculates a submit-by date, and marks a record on time or at risk. That gives project teams a useful planning signal. The date still depends on the selected activity, the schedule revision, the need-on-site date, the review duration and other lead-time assumptions supplied by the project. Preserve those inputs with the calculated result so a reviewer can explain why a date appeared at a particular point in time.

For each submittal, record the project and package identifiers, specification section, linked activity identifier, schedule data date and version, material need-on-site date, assumed fabrication and delivery windows, review cycles, calculated submit-by date, actual submission and response dates, and the party responsible for each input. A planning screen may display only the latest date. The decision record should retain prior values and the reason for each change, because a later schedule import can make an earlier deadline look inexplicable if its source version is lost. This is an editorial control recommendation, not a claim that Procore stores every listed field.

Treat a schedule change as a new planning decision

When a linked schedule activity moves, the project should compare the old and new required dates before replacing a submit-by target. Identify whether the activity moved because the controlling schedule was formally updated, a tentative activity changed, an internal look-ahead was revised, or an upstream dependency was unresolved. Those cases carry different authority. Link the date change to its approved schedule record where one exists, and label the date provisional where it does not. A submittal tool cannot turn an unapproved schedule revision into a contract instruction merely by recalculating a date.

A useful exception queue shows the prior and current submit-by dates, the source activity and version for each, elapsed review time, work remaining, affected procurement and installation milestones, and the named person who accepted or challenged the revised plan. Preserve alerts as dated observations. A red at-risk flag can prompt action, but it does not say who caused the risk, whether a contractual notice is required, or whether procurement is authorized. Those decisions depend on project records, contract terms, and accountable project roles outside the calculation.

Separate predicted review completion from material readiness

Procore describes an Anticipated Delivery Date that projects completion from the current pace of review. The label can help a team see an emerging slip. It should remain a forecast until the actual review response, fabrication or purchase authorization, supplier confirmation, shipment, receipt, inspection, and installation readiness are evidenced in their own records. A projected review date is not the date on which a product is physically available, accepted, or approved for field use.

A buyer test should follow one package from specification requirement to generated log item, linked schedule activity, first calculated date, reviewer response, supplier lead-time confirmation, and material receipt. Then revise the schedule while the package is under review. Ask the system to show which dates changed, which remained fixed, who was notified, what history can be exported, and how it distinguishes the calculation from an approved project decision. Test an unlinked activity, an outdated schedule version, a rejected submittal, and a material with a longer supplier lead time than the original plan assumed.

Check beta availability and contractual limits

The September update describes Dynamic Submittal Plan as an open beta through Procore Explore. A buyer should confirm availability for its account and region, the feature's current field definitions, schedule import behavior, permissions, notification rules, version history, export capability, and support terms before making it a required control. The same provider note describes other Submittals changes, but those are separate capabilities with their own availability and terms. This article addresses the schedule-to-date decision and does not imply that the full update is one generally available product bundle.

Contract schedules, submittal clauses, design-review obligations, procurement authority, field release, and delay notice rules vary by project. The provider source establishes what Procore says the beta calculates; it does not verify a customer's schedule quality, lead-time inputs, account configuration, actual use, timing improvement, entitlement, or project outcome. Keep the responsible scheduler, submittal manager, trade partner, supplier, design reviewer, and contract administrator visible at the points where their records and approvals matter.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Contractor Systems Index will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.