Download workbook
Local Files
Ready
Upload files
Use source PDFs, schedules, pasted text, and demo documents for local analysis.
- Imported
- 0 sources
- Last activity
- No run yet
Durham Electric project controls workspace
ScopeLine
Parse project records, summarize scope and constraints, draft submittal/RFI candidates, and keep material handoff review-gated. Scope, constraints, Q&A, drafts, and reviewed handoff.
Gate
Human approval
Audit
Sources + confidence
Scope
Constraints first
Project intelligence workflow
Scope answers require project sources
MVP
Procore
Connected
Azure AI
Ready
Standards
Fresh
Remarcable
Pending
Project dashboard
No run
Action queue and daily summary
Start here each day. Review what changed, what is blocked, and what needs to be finalized before handoff.
Action Queue
Prioritized work items with direct links into the workflow.
Run an analysis or import project sources to build the first action queue.
Daily EOD Summary
Internal draft preview for PM, estimator, and field handoff. Finalize manually at end of day.
No EOD draft yet. Complete intake and run analysis first.
Workflow Status
Progress is based on source and review state, not button clicks.
Ready Outputs
Workbook, controls, EOD, and Remarcable readiness.
Focused view: dashboard
Current lane
Intake: build the trusted project record
Add SharePoint, upload, or Procore source documents before asking questions, drafting controls, approving material rows, or preparing Remarcable handoff.
Boundary: project sources only
Gate: classify before analysis
Output: controlled source register
Workflow blocker
Locked
Step is locked
Complete the required prior review state before opening this step.
1. Project Record Intake Bulk upload, SharePoint, Procore Ready Ready
Choose Intake Source
Start with uploaded files, SharePoint project records, or Procore records. Connector setup stays in Admin; this step only shows sources ready for the project workflow.
SharePoint
Checking
Import SharePoint records
Pull controlled folder metadata first, then extract file content for analysis.
- Imported
- 0 sources
- Last activity
- Waiting for readiness
Procore
Checking
Import Procore records
Use Procore as an optional source system when the admin readiness gate is configured.
- Imported
- 0 sources
- Last activity
- Waiting for readiness
Connector import results appear here after SharePoint or Procore actions. Use Admin for credential readiness and raw audit output.
Project Document Register
Classified drawings, specs, schedules, RFIs, submittals, and Procore records appear here before takeoff review.
Run an analysis to replace preview rows with classified source evidence.
Document Scope Summaries
Per-document scope contribution, constraints, QA flags, and reviewer action before Q&A, controls, or material approval.
Run analysis to summarize individual drawings, specs, schedules, submittals, RFIs, and addenda.
Project Record Control
Procore-style control view for drawings, specs, submittals, RFIs, revisions, and unresolved scope blockers before material review.
Run analysis to classify drawings, specs, schedules, submittals, RFIs, and addenda.
Missing revisions and outdated-answer feedback appear here before approval or export.
Submittal and RFI candidates stay internal until edited and approved by a person.
Drawing / Spec Control Matrix
Preview
Document control preview
Review source system, sheet/doc number, revision evidence, extraction state, scope use, blockers, and handoff policy before relying on project records.
Run analysis to replace this preview with controlled drawing, specification, schedule, submittal, RFI, and addendum rows.
Project Record Change Watch
Revision, ETag, Procore revision, and open answer-feedback signals to review before daily summaries or handoff.
Run analysis to check source revision evidence and open project-record feedback.
Bulk Upload Intake Upload or paste source text for local analysis. Ready
Connector Intake Import SharePoint library files or Procore project records. Ready
2. Scope & Constraint Summary
Summarizes what the job appears to include, what constraints override normal practice, and what needs a person to confirm.
No run
Upload or import project files to summarize included scope, unclear scope, and cited source coverage.
Conduit, wire, support, enclosure, standards, testing, and manufacturer constraints appear here.
The assistant proposes draft log items and questions. Nothing is submitted without review.
End-of-day summaries will roll up changed project records, open questions, and Procore/Remarcable status.
Scope Review Acknowledgement
Confirm whether the scope brief, requirements matrix, open issues, and action recommendations are ready to influence downstream work.
Guarded Project Q&A
Ask project-scope questions. The assistant answers from the current project record first and says when the record is insufficient.
Ask this first
Start with review-safe project questions
Use imported sources, Durham rules, metadata-only standards snapshots, and reviewer-attached references.
Refuse broad internet answers, uncited product assumptions, stale revisions, and copied paid-standard text.
Wrong, missing-source, or outdated answers create review items until a reviewer resolves the record.
Answer Source Boundary
Shows what the assistant may use, what is blocked, and what a reviewer must fix before relying on an answer.
Run an analysis to inspect the project-record, standards, external-evidence, AI-provider, and feedback boundaries.
External References
Attach precise AHJ, vendor, manufacturer, or standards-metadata links to the project record before using them as evidence.
External Evidence Requests
Precise lookup queue. Attach exact URLs below before Q&A, controls, or handoff can rely on outside evidence.
Run an analysis to see targeted AHJ, manufacturer, source-revision, and project-record lookup requests.
No external references attached. Answers stay limited to the project record until a reviewer attaches precise evidence.
Run an analysis, then ask about scope, constraints, submittals, RFIs, QA flags, standards, or material handoff readiness.
Answer Review Queue
Wrong, missing-source, and outdated-revision answers stay open until a reviewer resolves the project record.
Ask a project question, then mark the answer correct, wrong, missing source, or outdated revision.
Daily EOD Snapshot Review
Review the secret-free daily summary before forwarding. Procore and Remarcable status should be synced before anyone sends the email.
Recommended roles appear here after the daily snapshot draft is available.
Changed documents, open questions, QA flags, and handoff state are summarized from the active run.
No email is sent by the hub. A person must review and forward the downloaded draft.
EOD Connector Snapshot
Preview
Connector preview
Confirm Procore source freshness, SharePoint/upload evidence, Remarcable status sync, high-QA state, and secret-free delivery mode before forwarding the daily EOD snapshot.
Run analysis to replace this preview with Procore, SharePoint/upload, Remarcable, and delivery-gate evidence.
Project Controls Drafts
Draft submittal, RFI, daily field report, and daily EOD items created from the project record. These stay internal until a person edits and approves them.
No run
Spec and submittal-derived review items will appear here with source context.
Missing, conflicting, schematic-only, or not-estimated scope questions will appear here.
A daily field report draft will summarize scope status, blockers, and review notes for human editing.
The EOD summary rolls up changed records, open questions, QA, and material handoff state.
Controls Drafts Review
Decide whether RFI, submittal, daily report, or EOD draft outputs can be downloaded as an internal packet.
Go-Live Blockers
Live production gate status for SharePoint, Procore, Azure AI, standards metadata, reviewer approval, and Remarcable handoff.
Checking
Project Summary
Live run status, source coverage, takeoff confidence, QA flags, standards, and Remarcable handoff state.
No source documents analyzed yet.
Run an analysis to populate BOM candidates.
Durham review checks appear here.
Awaiting estimator review.
Edition metadata loads with each run.
No material requests exported.
3. Material Review Queue
Material candidates are one output of the scope assistant. Rows must show source, basis, confidence, and Durham QA state before Remarcable export.
Run an analysis to review candidate material rows.
Workbook Review
Confirms the generated Excel workbook contains each Durham estimating section before review/download.
Run an analysis to inspect workbook tabs and row counts.
Handoff Gate Checklist
Confirm review gates before workbook, controls packet, EOD, or Remarcable outputs leave ScopeLine.
Run analysis and complete review gates to see handoff readiness.
Remarcable Handoff Audit / Export History
After export, Remarcable owns procurement status while this hub keeps the source and approval audit trail.
Approved rows exported to Remarcable will appear here with request IDs, statuses, and source citations.
Project Setup Guide
Follow the sequence for each project workspace. The guide updates as the active analysis run gains sources, answers, approvals, snapshots, and handoff records.
Every source is classified, versioned, and cited before it is used for scope, constraints, or material decisions.
Conduit, wire, supports, standards, exclusions, and unclear scope are separated from material takeoff rows.
Routes are built before quantities; route LF, conduit LF, and wire/cable LF stay separated.
Submittal/RFI/material drafts stay local until a person reviews the sources and approves the next action.
Project workspace template
Start each project from the latest approved package
New projects get a fresh SiteAssets workspace, project libraries, source register, assumptions, RFI/submittal drafts, daily snapshots, and audit exports. Existing projects keep their recorded template version until intentionally upgraded.
v0.1.0
Project Rollout Checklist
Per-project setup checklist for the selected project profile, static config, source libraries, and upgrade evidence.
Takeoff Evidence Source register, symbols, assemblies, standards, QA No sources No run
Source Document Register
Each drawing, spec, schedule, submittal, or addendum is classified before quantities are trusted.
Analyzed source documents will appear here with estimate use and confidence.
Source Register Review Gate
Mark whether this source set is usable enough for Scope Review. Gaps remain visible downstream.
Legends, Symbols & Acronyms
Drawing-specific meanings are captured with citations and must be confirmed before takeoff use.
Legend notes, symbols, and acronyms will appear here after analysis.
Physical Assembly Review
Durham oversight builds route assemblies before counting conduit LF or wire/cable LF.
Physical routes, duct banks, racks, trenches, and not-estimated warnings appear here.
Run Standards Used
AHJ Adoption Review lists project references first; latest known registry editions are shown separately with source links.
Run an analysis to snapshot exact standards editions and project references.
QA Flags & Assumptions
Open estimator risks, not-estimated quantities, and production assumptions stay visible before procurement.
Run an analysis to review QA flags, assumptions, exclusions, and unresolved export risks.
Production Setup Readiness, standards registry, deployment bundle, acceptance plan Checking Not loaded
Integration Readiness
Standards Registry
Not loaded
Deployment Manifest
Not loaded
Deployment Bundle
One secret-free handoff artifact for site package files, API checks, standards metadata, acceptance evidence, Durham export gates, and go-live validation.
Production Acceptance Plan
Credentialed checks for SharePoint, Procore, Azure AI, standards metadata, review gates, and Remarcable vendor confirmation.
Not loaded
Download evidence packet
Admin, Configuration & Audit API keys, readiness, acceptance evidence, rule candidates, raw response Ready No run
Admin, Configuration & Audit
ReadyThe static site hosts the UI; server-side routes own ingestion, analysis, exports, audit, and admin actions.
Use Azure app settings, Key Vault, Entra ID, OAuth, or a protected proxy for production credentials.
New project sites should start from the latest approved package; active projects stay pinned until upgraded.
Strict go-live needs real SharePoint, Procore, Azure, Remarcable, standards, and review-gate evidence.
Configuration belongs outside page code.
Use public/config.json for static API host/key references only when an authenticated proxy is not available. Production secrets should live in Azure app settings, Key Vault, Entra ID, or vendor-managed OAuth flows.
Project Profile Preflight
Validate the configured project selector defaults before this workspace is used for intake, analysis, or handoff.
Demo Output
No runRun the demo analysis to see the workbook model and audit fields.