How Sentinel decides to wake
On most construction projects, a project engineer begins the day by catching up on changes that came in since the last review. An RFI has a new response, two submittals have moved, someone updated the procurement log, and the schedule has several activities to check before the next coordination meeting.
Looking through those updates is familiar work. Sentinel helps with the preparation by reviewing available project activity and bringing relevant changes together. We designed its review timing around the way project teams work: some items need attention as they happen, while many others are easier to evaluate together during a routine review.
Sentinel therefore uses immediate triggers for certain important changes alongside scheduled weekday reviews. The timing is intended to make the findings useful to the people managing the project without adding another stream of low-value notifications.
A project update that needs attention starts a review now. Routine updates collect until the next weekday review. Your team can also ask for an immediate review.
What merits an immediate review
An RFI can be edited several times for ordinary reasons, from a revised description to an updated reference. If that RFI is then marked urgent or given a cost or schedule impact, the new information may affect work already being coordinated in the field.
Sentinel can initiate a review when supported project records show signals such as a blocked or nearly due task, an urgent RFI, a new cost or schedule impact, or a submittal returned for revision. A person can also request a run directly when they want a fresh project review.
During that review, Sentinel looks at the changed record and the related information it can access. A submittal rejection is more useful to the project team when it arrives with the reviewer comments, outstanding follow-up, and any connected procurement or schedule activity that helps explain its significance.
Connected systems don't all report changes in the same way. Where a provider event is unavailable, a scheduled connector check can supply updates for Sentinel to consider. The review depends on the records actually available, so its findings should be read alongside their sources.
The routine reviews
Most project updates can be collected into a regular review. New documents are filed, due dates are revised, and tasks change status as teams work through the day's coordination. Reviewing several changes together can reveal a connection that would be difficult to see from one notification.
Sentinel's scheduled reviews run on weekdays in the morning and early afternoon, according to the project's local time. The morning review can collect activity that accumulated overnight; the afternoon review gives the team another look at developing items without requiring anyone to start the scan manually.
A document revision that doesn't warrant an immediate run may still matter when reviewed with an open RFI or an upcoming activity. Sentinel can surface that relationship for a project engineer to inspect rather than interrupting the team for every document update.
One issue can generate plenty of updates
Consider an RFI that remains open for several days. Its due date changes, someone adds a sketch, the architect posts a comment, and the project engineer updates the impact field. A connected system may also send a repeated event for one of those edits.
If each update created a separate item for the team, the review would quickly fill with versions of the same problem. Sentinel keeps its attention on the project record so new information can be added to the issue already being tracked.
An RFI that was first noted as overdue might later be identified as affecting a scheduled installation. Keeping those developments together lets the project manager see how the situation evolved and what the team still needs to resolve.
The project team already maintains and interprets its RFI log. Sentinel can reduce the manual effort of keeping up with repeated updates and collecting the relevant context for follow-up.
Repeated updates to the same RFI feed the existing issue. Sentinel keeps the latest information together instead of starting disconnected work.
From a finding to useful follow-up
Suppose a mechanical equipment submittal comes back for revision shortly before its planned release for fabrication. The engineer handling the package can evaluate the technical comments, but first needs the returned submission, procurement milestone, and any prior correspondence in one place.
Sentinel can review the available records and prepare the issue for follow-up. A Clevis bot can then help draft a question to the supplier or organize the documents needed for the team to decide how to proceed.
The project's established permissions and approval requirements apply to that work. Preparing an internal summary is different from sending instructions to an outside party or changing a contractual record. The relevant person reviews consequential proposed actions before they are issued.
That approach lets an agent complete much of the searching and preparation while keeping the team's ordinary responsibilities intact.
Work continues while one decision is pending
A project manager may need time to review a proposed supplier instruction, particularly if it could affect fabrication or delivery. During that time, new RFIs arrive, submittals are returned, and other coordination work keeps moving.
Sentinel can continue its scheduled reviews while an individual approval is pending. The proposed action remains available to the person responsible for it, and unrelated issues can still be investigated and surfaced.
This matters for a bot that has an ongoing assignment. The team can ask it to monitor the project without needing to restart that assignment each time a decision requires a person's attention.
Sentinel investigates and prepares work. An action needing approval waits for your decision. In parallel, Sentinel continues its next review and investigates other issues.
A quiet review is useful too
Some scheduled reviews turn up routine edits without anything that needs to be escalated. Sentinel can record the review and return to its schedule without sending another notification to the team.
Project engineers already have email, calls, meetings, and updates from several systems competing for attention. A regular review that leaves ordinary activity alone helps keep the useful findings visible when something does need follow-up.
Fitting into the project team's day
Sentinel's immediate triggers, scheduled reviews, and record-based follow-up all serve the same practical purpose: reduce the routine checking involved in keeping up with a changing project. The team can still inspect the source material, ask for another review, and decide how to handle the issues that come back.
As the project develops, the agent can continue reviewing the available activity and preparing useful context for the people managing it. That gives project engineers and managers more time for coordination, field questions, and decisions that benefit from their experience.