| A manager-approved follow-up rule finds an unresolved proposal question in a permitted estimating-tool export and Gmail thread. |
Can assemble the current proposal reference, original question and latest supported response, then prepare a draft follow-up. A short acknowledgment remains distinct from acceptance, and unavailable source records appear as unchecked rather than settled. |
The owner or authorized project manager checks the current scope reference, wording and recipient. A person sends the approved message. Revised scope, terms and commitments remain separate human decisions through the established proposal process. |
The office can see exactly what the customer has not answered without treating a reminder or friendly reply as an accepted proposal. |
| A subcontractor handoff in a permitted Procore or Buildertrend export lacks the confirmation required by the project manager. |
Can prepare the project reference, approved schedule context and specific confirmation request. Connections and available fields require discovery. The queue distinguishes a message acknowledgment from the actual readiness or dependency confirmation staff require. |
The project manager decides assignments, schedule changes and work release. A person reviews and sends external coordination messages. Qualified staff handle construction methods and site safety; the assistant does not dispatch workers or issue field instructions. |
The unresolved dependency has a named owner and clear review question without an automatically changed schedule or promise about job completion. |
| A customer-requested change appears in approved meeting notes, Gmail or a Google Sheets register without the established approval recorded. |
Can preserve the request alongside the current approved scope reference and identify the missing administrative approval. It does not reinterpret a discussion as consent, produce an approved change order or remove the dependency from the owner review. |
The owner and project manager assess the request through the established change process, with the customer providing the required approval. People send proposed clarifications. Any commercial, schedule or financial decision remains with authorized staff. |
Proposed work remains visibly separate from approved scope until the proper human process establishes the next permitted action. |
| An office review identifies a draw-related milestone awaiting evidence or staff review in a permitted project record and QuickBooks export. |
Can organize the project reference, recorded milestone and missing confirmation for the authorized reviewer. It shows unchecked accounting sources explicitly and does not infer entitlement to bill from a task marked complete or a generated project summary. |
Authorized accounting staff and the owner decide billing, invoice contents and payment actions. A person approves and sends financial communications. The assistant provides no legal, tax or financial advice and does not issue an invoice or initiate payment autonomously. |
The reviewer receives the specific administrative question and available evidence while every financial action retains its established approval. |
| The owner requests outstanding project obligations from the approved Sheets queue and Calendar review list. |
Can group unanswered proposals, subcontractor dependencies, unsigned changes and billing questions by project, retaining source observations and named reviewers. It keeps these categories distinct so a response in one cannot silently close another. |
Project managers confirm supported administrative updates, while the owner retains commercial commitments. A person approves and sends customer updates. Missing records and conflicting responses remain visible for staff review rather than being converted into a confident completion statement. |
The owner sees the decision still needed on each project, with a manual route available when evidence or access is incomplete. |