A clear next phase.
The reported foundation, what needs activation and the proposed improvements—kept separate so scope and readiness stay honest.
Reported foundation
Prior implementation review—not freshly audited
Invite-only tenant/company/project access; company directory; cited contract extraction and reviewed save; private originals and File Room search; shared PM modules; controlled changes, SOV billing and prime pay apps; dated obligations, selected portal workflows and reviewed project AI.
Activation & validation
Configuration and real-user proof required
Operational email delivery, sender verification, inbound matching and digests; universal sharing and acknowledgment; nightly alerts; current-source visibility; external financial scenarios and AI audit coverage. Directory entries do not automatically grant login access; earlier uploads may need migration and search is not vector-semantic.
Proposed expansion
Product direction—not a live commitment
Complete role-specific dashboards, shared schedule and financial context, recipient selection, explicit acknowledgment, trade checklists, supplier and additional participant portals, integrations and the improvements below. This website does not operate the production project workflows.
The delivery agenda.
High and medium are initial discussion priorities, not approved scope or delivery dates.
01Accounting sync
HighQuickBooks or Sage reconciliation for approved invoices, cost codes and payments, with duplicate and conflict controls.
02Operations email activation
HighWhose-turn notices, recipient-bound item links, retained replies and optional digests after delivery and inbound routing are verified.
03Dependency-aware scheduling
HighApproved baseline, reviewed revisions, lookaheads and delay links—without silently moving contractual dates.
04Offline field tools
HighDaily reports, located photos and punch, safety and inspections, with visible sync-conflict resolution.
05Cost forecasting
HighFinal cost and cash-flow forecasts by cost code, separating budget, commitments, actuals and exposure.
06Subcontractor prequalification
MediumReviewed bonding, safety and performance evidence to support active-project awards.
07Owner monthly reports
MediumReviewed photos, schedule, financial summaries and risks; acknowledgment remains distinct from approval.
08Closeout package builder
MediumAs-builts, warranties, manuals and attic stock organized into a searchable owner handoff.
09Drawing comparison and takeoff
MediumRevision comparisons and suggested quantities tied to source drawings and human verification.
10Lessons learned
MediumReviewed findings carried into future execution, procurement and contract standards—not a sales or pre-bid expansion.
11Inspections and permits
MediumPermit expiry, inspections and certificate-of-occupancy prerequisites tracked against established dates.
12Broader e-signatures
HighControlled signing with identity, intent, exact version and history, subject to legal and template review.
13Role-specific home screens
HighActionable document, schedule and financial-responsibility views rather than generic summaries.
14Real-user portal testing
HighOwner, design, trade, field and accounting participants test realistic cross-role scenarios.
15Clear AI review
MediumSources, named reviewer and accept/reject outcomes for drafts; never autonomous financial approval.
Proof before rollout.
A / Agree the model
Confirm role-specific homes, precise statuses, schedule source and owner, accounting provider, access rules and approval limits. Acceptance: stakeholder-approved examples of who sees and does what.
B / Actionable dashboards
Connect summaries to exact authorized records with current versions, actors and deadlines. Acceptance: no contradictory counts or statuses; primary actions remain usable on a phone.
C / Schedule & commitments
Link baseline/current activities, reviewed revisions, dependencies and financial records. Acceptance: a late shop-drawing review shows the same actor, downstream activity, commitment and hold reason in each authorized view—without leaking prices or silently shifting contract dates.
D / Email handoffs
Verify delivery, sender, recipient-bound links, step-up checks, replies and preferences. Acceptance: send, respond and read back history; deny expired, reused and wrong-recipient links.
E / Integrations & field
Add selected accounting, offline work and forecasting capabilities. Acceptance: provider reconciliation, duplicate handling, sync failures and audit trails tested.
F / Go-live proof
Pilot with GC, owner, design, trade, field and accounting users. Acceptance: complete change, pay-app, hold-clearance and closeout flows, training and rollback plan.
Decisions that shape the pilot
Select must-have, nice-to-have and deferred proposals; first project, portal and pilot trade; required documents and actions; acknowledgment vs. approval; named recipient accountability; reminders and escalation owners; approval limits; version-change reapproval rules; source systems; legal standards; email/IT owners; named testers and acceptance date.
The direction is not a fixed-price agreement, legal or security certification, or production-readiness sign-off. Scope, owners, integration providers and delivery dates remain to be agreed.