01Research & decisions
Research a market, vendor, or policy question.
Use when a decision needs evidence from permitted websites, PDFs, or tenant files.
- Route
- Frame the question → compare allowed sources → preserve citations with the findings.
- Review
- The user checks source relevance, assumptions, and unresolved gaps.
- Output
- Cited brief, ranked source pack, evidence table, or grounded summary.
02Client delivery
Prepare a proposal, report, or client deliverable.
Use when approved source material needs to become a structured, reviewable business document.
- Route
- Collect permitted context → build the working document → review → produce the final artifact.
- Review
- A responsible person verifies facts, commitments, and the release version.
- Output
- Proposal, report, tracker, presentation, or finished PDF package.
03Communication & follow-through
Turn project email into owned actions.
Use when separately authorized Gmail or Outlook communication needs to remain connected to the active tenant project.
- Route
- Open permitted mail → identify decisions and actions → prepare drafts and task updates.
- Review
- The user directs sending, replying, forwarding, and consequential task changes.
- Output
- Reply drafts, decision notes, task list, and current project record.
04Projects & accountability
Launch a project with clear owners and review points.
Use when a new initiative needs scope, responsibilities, schedule, decisions, and approvals connected from the start.
- Route
- Establish permitted context → shape the plan → assign work → route the kickoff review.
- Review
- Named owners confirm scope, responsibilities, dates, and approval gates.
- Output
- Kickoff brief, owner plan, schedule, decision register, and approval record.
05AEC project setup
Prepare a standards-led design project setup.
Use when a design team needs permitted project files, templates, references, and standards assembled before authoring work begins.
- Route
- Confirm project context → collect applicable references → prepare setup and coordination checks.
- Review
- The project lead confirms applicable standards, assumptions, and the enabled design environment.
- Output
- Project setup checklist, standards evidence pack, and coordination brief.
06Design review
Review a design package before handoff.
Use when source documents, model or authoring output, specifications, and coordination notes need one visible review route.
- Route
- Open allowed project context → compare design information → record issues → prepare handoff.
- Review
- The responsible design professional verifies technical content and release readiness.
- Output
- Coordination brief, issue log, design review record, and delivery evidence.
07Commercial construction
Build a bid or no-bid recommendation.
Use when an opportunity, scope, project documents, and trade fit need structured review before estimating effort continues.
- Route
- Collect permitted opportunity context → classify scope and risk → assemble the recommendation.
- Review
- A responsible estimator or business lead makes the bid decision.
- Output
- Bid recommendation, opportunity evidence index, scope notes, and decision record.
ConstructConnect information may be used only on authorized, configured deployments with an active account and subscription.
08Project document control
Coordinate an RFI, submittal, or field decision.
Use when a project question needs permitted drawings, specifications, attachments, status, and review history attached.
- Route
- Ground the question in project records → prepare the review package → route it to the responsible person.
- Review
- The designated project professional verifies and releases the response or record.
- Output
- Review-ready RFI or submittal record, field decision brief, and supporting evidence.
Procore project records can be used only on configured deployments with explicit tenant authorization.
09Handover & facilities
Assemble commissioning and closeout handover.
Use when current project records need to be reconciled, indexed, reviewed, and delivered for owner or facility use.
- Route
- Collect allowed records → identify gaps and current versions → assemble the turnover structure.
- Review
- Project and owner representatives confirm completeness and accepted delivery state.
- Output
- Handover index, missing-item list, commissioning evidence, and owner-delivery package.
10Procedures & controlled work
Create and approve an SOP or work instruction.
Use when approved operational context needs to become a clear procedure with a visible review and release point.
- Route
- Collect permitted requirements → draft the procedure → review → release the approved version.
- Review
- The process owner verifies steps, responsibilities, risks, and the release version.
- Output
- Approved procedure, work instruction, checklist, and linked review record.
11Repeatable execution
Turn an approved plan into visible execution.
Use when a plan needs owned tasks, checkpoints, progress state, approvals, and evidence that can be reviewed later.
- Route
- Break down the approved plan → assign work → govern transitions → preserve receipts.
- Review
- Configured approval transitions can pause for the named reviewer or authorized owner.
- Output
- Work queue, recorded progress state, approval record, artifacts, and execution receipts.
12Operations & recovery
Review an incident and prepare recovery work.
Use when events, health state, queues, policies, and operational context need to become a controlled diagnostic or recovery route.
- Route
- Inspect current evidence → reconstruct the timeline → prepare repair or recovery steps → verify fresh state.
- Review
- A technical operator approves consequential changes and verifies the result.
- Output
- Health summary, incident timeline, recovery plan, and post-action evidence.
13Decisions & handoffs
Turn a meeting into decisions and a clean handoff.
Use when permitted notes or a transcript need to become accountable decisions, actions, unresolved questions, and the next team’s working context.
- Route
- Open the allowed meeting context → identify decisions and actions → name owners → prepare the handoff.
- Review
- The meeting owner verifies meaning, assignments, dates, and anything that remains unresolved.
- Output
- Decision log, owned action list, open-question register, and current handoff brief.
14Facility follow-through
Turn handover records into an operating action plan.
Use when permitted project, commissioning, handover, and facility documents need to support accountable follow-up after delivery.
- Route
- Index allowed records → connect current versions → identify open obligations → prepare operating actions.
- Review
- The owner or facility representative confirms applicability, priorities, responsibilities, and accepted source records.
- Output
- Source-backed records index, open-item register, responsible-owner plan, and operating follow-up package.
15Service health & change
Prepare a service-health or change-approval package.
Use when permitted service, route, queue, policy, and dependency state need review before a consequential technical change.
- Route
- Inspect current evidence → summarize health and impact → prepare change, backout, and verification steps.
- Review
- An authorized administrator approves the proposed scope and decides whether execution can proceed.
- Output
- Health brief, reviewed change plan, backout path, verification checklist, and available evidence.
16Estimating & proposal
Prepare an estimate and construction proposal package.
Use when permitted scope, drawings, specifications, and assumptions need to become a reviewable estimating and proposal working package.
- Route
- Index allowed bid documents → classify scope and assumptions → assemble estimate inputs → prepare the proposal package.
- Review
- The responsible estimator validates quantities, pricing, exclusions, risk, and every external commitment.
- Output
- Estimate working package, scope summary, assumptions and exclusions register, and reviewed proposal.
