Admin-only notice: this static hosted file uses fake/demo data. Login rules, role views, property filters, local save/offline behavior, and reports are prototype controls until a real backend is connected.
LPMS Dashboard
This dashboard shows the properties, reports, action items, proposals, and alerts available to the signed-in user's approved property scope.
You are previewing a restricted user view. Exit simulation to return to Tim Baker system admin access.
This signed-in user does not have permission to open that LPMS area.
v51 Manager Review Checklist
This version is ready for manager feedback. Review should focus on clarity, field workflow, report usefulness, and whether the app explains BrightView follow-up cleanly. It is still fake/demo data only.
| Dashboard clarity | Managers should understand portfolio condition, below-standard properties, active corrective actions, proposal status, and alerts within 30 seconds. |
| Inspection flow | The app should feel like a field workflow: document the official Westgate-selected score, explain deductions, and create follow-up when needed. |
| Action Center | Action items should clearly show ownership, due date, status, pending approval, outside scope, and completion notes without making photos mandatory. |
| Final Report | The report should read like the official inspection record: score, deductions, corrective actions, pending approvals, scheduled work, photos, and manager summary. |
| Proposal tracking | Proposal Drop Box should remain a tracking tool for existing BrightView proposals only. It should not look like LPMS is creating proposals. |
| Access confidence | Each role should only see the properties and screens appropriate to that user. Standard users should not see admin/build controls. |
| Manager feedback | Best test question: “Would this help you explain the inspection result, defend scheduled/pending work, and track follow-up without extra confusion?” |
Manager Review Focus
Use this section as the test script when walking managers through LPMS. The goal is to confirm the workflow makes sense before adding more features.
Active Dashboard View
Signed-in user
Loading dashboard access...
Admin test control: this selector previews dashboard scope only. Use Role Testing to verify full user views, including property access and admin-only navigation.
End-of-Month / Action Progress Summary
Proposal & Approval Summary
Proposal items are tracked separately from inspection scoring so work waiting on Westgate approval does not appear as an unresolved BrightView service miss.
Notifications & Approval Alerts
Alerts are created automatically from proposals, corrective actions, reports, and sync status. Users only see alerts for their approved property access.
Portfolio Attention List
| Property | Latest Score | Status | Hot Spot | Owner / Exposure |
|---|
Category Hot Spots
Pending Westgate Approval
Pending approvals are tracked separately so they do not appear as unresolved BrightView service misses.
BrightView-Owned Items
BrightView-owned items stay visible until completed and documented with required notes/photos.
Dashboard Visibility Rules
| User Type | Dashboard View | What They Should See |
|---|---|---|
| Property GM | Single property | Their property score, reports, photos, action progress, and open/past-due items only. |
| Florida Regional Westgate | Florida portfolio | Villas, Lakes, Towers, River Ranch, Leisure, Palace, and Cocoa. |
| Westgate Executive | Full portfolio | All Westgate properties, chargeback exposure, risk, trends, and corrective action status. |
| BrightView Portfolio Lead | Full portfolio | All properties, all action status, portfolio risk, meeting support, and report history. |
| BrightView Branch Manager | Assigned branch properties | Only properties assigned to that branch or manager. |
| Admin | User/access management | User creation, role assignment, property access, disabled users, and audit logs. |
Developer rule: do not rely on hiding buttons. If a Villas GM tries to access a Lakes report by URL, the database/API must deny access.
System Admin Dashboard
Admin-only landing view for Tim Baker as LPMS System Admin / Builder. Standard Westgate users, property GMs, regional users, and branch users would not see this screen unless they are specifically granted admin rights.
Signed In As
Tim Baker
LPMS System Admin / Builder · BrightView · Full Westgate Portfolio + Admin Control
Admin Rule
BrightView owns and controls LPMS. Westgate may approve or request user access for their team, but unrestricted system administration remains with approved BrightView admins. A backup BrightView admin is required before production rollout.
Portfolio Oversight
See the same full portfolio dashboard used for executive review, including properties below 80, breach risk below 70, chargeback exposure, action progress, and pending Westgate approvals.
User & Property Access
Create approved users, assign roles, assign property visibility, resend invites, disable users, and review access status.
Role Simulation
Preview exactly what a Villas GM, Florida regional user, Westgate executive, BrightView branch manager, backup admin, or system admin would see after sign-in.
Action Center Oversight
Review open, in-progress, past-due, completed, pending Westgate, scheduled/not due, and outside-scope corrective actions across the assigned portfolio.
System Documentation
Admin-only reference area for data tables, role rules, report rules, photo integrity, validation, offline sync, and production build requirements.
Offline / Sync Monitoring
Review offline logic from the admin documentation area. This is not part of the regular user navigation.
Reports & PDF Output
Preview final reports with inspection metadata, scores, photos, deduction reasons, corrective actions, and executive summary language.
What Tim Can Do As System Admin / Builder
| Area | Admin Capability | Production Control |
|---|---|---|
| Users | Add, approve, disable, resend invite, assign role, assign company. | All changes are audit logged. |
| Property Access | Assign Villas only, Florida region, branch properties, or full portfolio. | Access is enforced by database/API rules. |
| Dashboards | View full portfolio and role-based previews. | Standard users only see their approved scope. |
| Inspections | Review reports, photos, scores, deductions, and validation history. | Westgate remains the official scoring authority. |
| Action Center | Track open, due, completed, pending approval, and outside-scope items. | Completion requires notes/date/by. Action photo upload is available but optional and does not block completion or report preview. |
| Audit | Review who changed access, reports, action status, and submitted records. | Submitted/synced records lock with history. |
Production Visibility Rule
This System Admin Dashboard is not part of the normal user experience. A Villas GM signs in and sees Villas only. A Florida regional user sees Florida properties. A Westgate executive sees the portfolio dashboard but not admin controls. Tim and approved backup BrightView admins see the control room behind LPMS.
Role Simulation / User View Testing
Admin-only testing area. Use this to confirm what each user type can see before LPMS moves into real authentication and database-controlled access.
Current Test User
Tim Baker
LPMS System Admin / Builder · Full portfolio + Admin
Testing Rule
This page is not part of the normal user experience. It exists so the LPMS builder/admin can prove that role and property access are working: property users see one property, regional users see their region, executives see the full portfolio, and only BrightView admins see admin/build screens.
User View Test Checklist
| Test | Expected Result | Why It Matters |
|---|---|---|
| Villas GM | Dashboard, reports, photos, inspections, and actions for Villas only. No System Admin, System Docs, Database Model, or Admin Access. | Protects property-level access. |
| Florida Regional | Florida properties only: Villas, Lakes, Towers, River Ranch, Leisure, Palace, and Cocoa. | Supports Stacey/Doug-style regional visibility without exposing the full portfolio. |
| Westgate Executive | Full portfolio visibility, but no BrightView system admin controls. | Gives leadership the portfolio view without giving client users unrestricted system control. |
| BrightView Branch Manager | Assigned branch properties only, Action Center visibility for assigned scope. | Keeps operations focused on what they own. |
| Backup BrightView Admin | Full admin visibility, user management, system documentation, audit support. | Prevents LPMS from depending on one person only. |
| Tim System Admin / Builder | Full portfolio, admin control, role testing, system docs, database/offline build notes, and audit requirements. | Owner/builder view for governance and continued development. |
Production Rule
In production, this testing screen should remain admin-only or be removed from standard navigation. The real app will not let users pick roles. Their role, company, property access, and permissions will load automatically after approved sign-in.
Mobile / iPhone Formatting Notes
v34 keeps the PC version intact and adds responsive phone behavior for field use. The mobile menu opens from the header, dashboard cards stack, inspection tabs scroll sideways, forms use touch-friendly spacing, and report/table areas become easier to read on smaller screens.
Admin / System Documentation
v43 update: added a working Property dropdown. Multi-property users can choose All Properties or a specific property, and Dashboard, Action Center, Proposals, Photos, Notifications, and Past Inspections update to that selected view.
v45 update: strengthened the Action Center with visible filters, action validation, quick status controls, and an end-of-month action summary for BrightView-owned, Westgate pending, scheduled/not-due, and outside-scope items.
Admin-only control room for build documentation. These pages support development, testing, and governance. They are not part of the normal Westgate or BrightView user experience.
Production Rule
Normal users should not see database tables, offline sync design, permission matrices, or developer notes. A Villas GM sees Villas. A regional user sees their region. Executives see portfolio dashboards. System documentation stays admin/developer-only.
Who Sees This
Westgate users do not need access to this section unless BrightView specifically grants a limited review role.
Database Model
Background structure for users, properties, inspections, category scores, photos, corrective actions, reports, sync queue, and audit history.
Admin Access Logic
Admin invite flow, approved users, role assignment, property access, disabled users, permission matrix, and access-change audit requirements.
Role Testing
Admin-only simulation for user views, property access, restricted navigation, and dashboard scope before real database authentication.
Offline Sync Logic
Offline draft storage, queued uploads, sync states, locked records, conflict handling, photo sync, and server validation rules.
Report / PDF Logic
Final report structure, photos, deduction support, corrective action summary, and executive summary output.
Action Center Logic
Corrective action ownership, completion rules, status tracking, before/after proof, and monthly progress summary.
Proposal Approval Logic
Proposal uploads, document status, approver notifications, approval history, and pending-Westgate dashboard tracking.
User-Facing vs Admin-Only
| Area | Normal User Visibility | Admin / Build Visibility |
|---|---|---|
| Dashboard | Yes, filtered by assigned property/role. | Yes, full portfolio plus role previews. |
| Inspections | Yes, assigned properties only. | Yes, full portfolio review if approved. |
| Action Center | Yes, assigned properties only. | Yes, portfolio-wide oversight. |
| Final Reports | Yes, assigned properties only. | Yes, full portfolio access if approved. |
| Proposal Drop Box / Approval Tracking | Yes, assigned properties only. | Yes, full portfolio proposal visibility and document upload capability if approved. |
| Admin Access | No. | Yes, approved BrightView admins only. |
| Database Model | No. | Yes, developer/build reference only. |
| Offline Sync Logic | No, except simple sync status messages. | Yes, full build/testing logic. |
| Audit Log | No, unless authorized. | Yes, admins and approved reviewers. |
Rollout Cleanup Rule
Before the final user rollout, this documentation area should either remain hidden behind admin permissions or be removed from the standard production navigation entirely. It exists so LPMS can be built correctly without exposing technical details to everyday users.
Property Access
Users only see assigned properties. Production version must enforce access at the server/database level.
Database Structure / Data Model
v23/v24/v25/v26 defines what the real LPMS build needs behind the screens. This is not a user-facing database editor. It is the developer blueprint for users, properties, inspections, photos, corrective actions, offline sync, reports, admin access, system admin ownership, and audit history.
Core Rule
auth_users
Authentication account created by approved invite or SSO.
user_profiles
Approved user details used by LPMS screens and reports.
properties
Master list of Westgate properties and regional grouping.
property_access
Controls which user can see which property and what actions they can take.
inspections
One submitted inspection record for a property and date.
inspection_categories
The six KPI category scores and required deduction support.
inspection_photos
Photo metadata and scoring/reference photo status.
corrective_actions
Action Center records created from inspections or manual follow-up.
proposal_documents
Copies of already-created BrightView proposals tied to a property, approval email, approver, status, and uploaded document. LPMS does not create the proposal.
proposal_updates
Approval history, revision requests, comments, notification events, and status changes.
action_updates
Completion notes, optional action photos, status changes, and follow-up history.
reports
Final PDF/report record and executive summary text.
offline_sync_queue
Local drafts and uploads waiting for internet connection.
audit_log
System record of who changed what and when.
Validation Rules Stored in the Data Layer
| Rule | Database / API Requirement |
|---|---|
| Allowed scores | Score must be one of 100, 85, 70, 50, or 0. |
| Category weights | Use preserved weights: Turf 20, Flowers 20, Shrubs/Trees 20, Debris 20, Irrigation 10, Mulch/Ground Cover 10. |
| Score below 100 | Observed condition/location and deduction reason are required before submission. |
| Corrective Action = Yes | Action description, owner, and due date are required. |
| Completed action | Completion note, completed by, and completed date/time. Action photo upload remains optional and does not block completion/report preview. |
| Submitted inspection | Record locks after sync; later changes create audit entries instead of overwriting history. |
Dashboard Data Sources
| Dashboard Item | Primary Source |
|---|---|
| Portfolio / property average | inspections + inspection_categories |
| Below 80 / Below 70 | inspections weighted_score and chargeback tier |
| Open / past-due actions | corrective_actions |
| Completed action proof | action_updates + inspection_photos |
| Pending Westgate approval | corrective_actions status / owner |
| Outside scope items | corrective_actions status + report notes |
| User dashboard scope | user_profiles + property_access |
Developer Notes
- Do not build production security by hiding buttons. Every report, photo, inspection, and action request must check user access on the server/database side.
- Photos should store the file plus metadata: property, inspection date, category, uploaded by, local capture/upload time, server sync time, location/note, and reference photo flag.
- Offline records should keep a temporary local ID until the server confirms the permanent record ID after sync.
- Dashboards should read from the same tables as reports, so leadership sees the same story that appears in the formal PDF/report.
- Audit history should show edits after submission, status changes, deleted/disabled users, access changes, and completed corrective actions.
Admin / User Access
v30 keeps the admin access workflow and adds role simulation so approved administrators can test how each user view behaves after sign-in. It also identifies Tim Baker as the LPMS System Admin / Builder, with a required BrightView backup admin and full audit controls. This is admin-only functionality and should not be visible to standard Westgate or BrightView users.
Core Access Rule
System Admin Ownership
| Admin Role | Who | Purpose | Control Level |
|---|---|---|---|
| LPMS System Admin / Builder | Tim Baker | Primary owner of the Westgate LPMS workflow, user setup direction, property access structure, and prototype-to-build decisions. | Full LPMS admin rights for Westgate portfolio. |
| Backup BrightView Admin | Assigned BrightView backup / IT / leadership | Continuity, security oversight, emergency access changes, and support if Tim is unavailable. | Full or delegated admin rights. |
| Westgate Access Approver | Designated Westgate contact | Approves which Westgate users should be added, removed, or assigned to properties. | Request / approval only, not full system admin. |
| Westgate Executive User | Peter / approved executive users | Portfolio visibility, dashboard review, reports, corrective action status, and risk oversight. | Full portfolio visibility, no system administration. |
Production rule: every admin action must be logged, including who changed access, what changed, when it changed, and why.
Create / Approve User
Prototype form showing the fields an admin should control. Production data should save to auth_users, user_profiles, and property_access tables.
Prototype note: buttons are visual only. Real production actions must create/update database records and write to the audit log.
Assign Property Access
Admins assign property visibility based on the user's approved responsibility. This drives dashboards, reports, inspections, photos, and corrective actions.
| Access Type | Example Scope |
|---|---|
| Single Property | Villas GM sees Villas only. |
| Florida Region | Stacey / Doug see Villas, Lakes, Towers, River Ranch, Leisure, Palace, Cocoa. |
| Full Portfolio | Peter and BrightView portfolio lead see all Westgate properties. |
| Branch Assignment | Branch manager sees properties assigned to that branch. |
| LPMS System Admin / Builder | Tim sees full Westgate portfolio and manages LPMS users/access for the Westgate build. |
| Backup BrightView Admin | Backup admin has approved access for continuity and emergency support. |
| Westgate Access Approver | Can approve or request Westgate user access changes, but does not control BrightView system administration. |
| Admin | Admin can manage users/access but still should be limited to approved administration scope. |
Role Permission Matrix
| User Type | Dashboard Scope | Can Inspect | Can Complete Actions | Can Manage Users |
|---|---|---|---|---|
| Property GM | Assigned property only | Yes, if assigned | Review / comment only unless approved | No |
| Florida Regional Westgate | Florida properties | Yes, if approved | Review / approve status | No |
| Westgate Executive | Full portfolio | Usually review only | Review / executive visibility | No |
| Westgate Access Approver | Assigned approval scope | Usually review only | Review / approve access requests only | Request / approve Westgate users only |
| LPMS System Admin / Builder | Full portfolio + admin | Yes | Yes | Yes |
| Backup BrightView Admin | Approved admin scope | Only if separately assigned | Only if separately assigned | Yes |
| BrightView Portfolio Lead | Full portfolio | Yes | Yes | Yes, if assigned as LPMS admin |
| BrightView Branch Manager | Assigned branch properties | Yes | Yes, for assigned properties | No |
| BrightView Account / Production Team | Assigned properties | Yes, if assigned | Yes, for assigned actions | No |
| Admin | Admin scope | Only if separately assigned | Only if separately assigned | Yes |
User Directory Preview
Admin-only list of approved users. Production version should support search, filter by company/role/status, resend invite, disable access, and view audit history.
| User | Company | Role | Access | Status |
|---|---|---|---|---|
| Tim Baker | BrightView | LPMS System Admin / Builder | Full Portfolio + Admin | Active |
| Backup BrightView Admin | BrightView | Backup Admin | Admin Continuity | To Assign |
| Peter | Westgate | Executive | Full Portfolio | Active |
| Stacey | Westgate | Florida Regional | Florida Properties | Active |
| Doug | Westgate | Landscape Director | Florida Properties | Active |
| Villas GM | Westgate | Property GM | Villas Only | Pending Invite |
Admin Actions
| Action | Required Control |
|---|---|
| Send invite | Secure token with expiration date. |
| Approve Westgate user request | Westgate can approve/request access, but BrightView admin finalizes and audit logs it. |
| Change role | Audit old role and new role. |
| Add/remove property | Audit property access change. |
| Disable user | Immediately block login and API access. |
| Reset password / SSO | Use approved authentication process. |
| Review access history | Show who changed access, when, and why. |
Production Build Notes
- Remove any production ability for users to self-register without admin approval.
- User name, company, role, dashboard scope, and property access must load from the database after authentication.
- Every API call must verify the user's property access before returning reports, inspections, photos, actions, or dashboard data.
- Disabling a user must immediately stop access across the app, including any saved sessions when practical.
- Tim Baker should be set as LPMS System Admin / Builder for the Westgate portfolio, with at least one backup BrightView admin assigned before production rollout.
- Westgate should have an access approver role for their users, but should not have unrestricted BrightView system admin control.
- All user creation, role changes, property access changes, disabled users, and invite actions should be recorded in the audit log.
- Admin screens should be hidden from standard users and blocked at the server level even if someone attempts to access the admin URL directly.
Local Save & Offline Simulation Controls
Admin-only live-test area for checking local draft save/restore, offline simulation, queue tracking, and last-sync behavior before the hosted prototype is shared with managers.
Live-Test Local Save Controls
These controls are admin-only in the hosted prototype. They simulate offline behavior for testing and do not claim real backend storage, real authentication, or real file sync.
Offline Timeline
The inspector should only need to sign in while online. After that, the inspection should continue even if the connection drops.
What Downloads Before the Walk
| Item | Purpose |
|---|---|
| Assigned properties | User only sees properties allowed by their approved profile/access record. |
| Inspection template | Preserves the existing Westgate KPI categories, weights, allowed scores, and required fields. |
| Open corrective actions | Shows unresolved items for that property before the next inspection begins. |
| Past inspection summary | Provides reference history without requiring full portfolio access. |
| User/role permissions | Controls whether the user can inspect, view reports, complete actions, or administer access. |
What Saves Locally
| Local Record | Stored While Offline |
|---|---|
| Inspection draft | Property, date/time, representatives, weather, notes, and category progress. |
| Category scores | Westgate-selected score, checked observation items, deduction reason, and observed location. |
| Photos | Photo file, category, local capture/upload time, location/note, and reference photo flag. |
| Corrective actions | Action required flag, owner, due date, status, completion notes, and before/after photo references. |
| Audit draft | Local user, device ID, temporary local record ID, and local save timestamps. |
Record Status Flow
| Status | Meaning | User Impact |
|---|---|---|
| Local Draft | Saved on the device but not submitted. | User can keep editing. |
| Queued | Submitted or saved while offline and waiting for connection. | User sees pending sync status. |
| Syncing | Device is sending records/photos to the server. | User should not close app until sync confirms when possible. |
| Synced | Server accepted the record and assigned permanent IDs. | Report/dashboard can update. |
| Locked | Submitted inspection is final after sync. | Later changes create audit entries, not silent edits. |
| Conflict / Needs Review | Server finds duplicate, outdated, or competing changes. | Admin or authorized reviewer resolves before final lock. |
Sync Validation Rules
- Do not sync a completed inspection if any score below 100 is missing observed condition/location or deduction reason.
- Do not sync a corrective action marked required if action description, owner, or due date is missing.
- Do not mark a corrective action complete unless completion note, completed by, and completed date/time are present.
- Action Center completion photos may be uploaded when useful for verification, but they must not block action completion or report completion.
- Photos must keep both local capture/upload time and server sync time.
- Old photos must remain labeled as reference photos and not scoring photos.
Conflict Handling
| Conflict | LPMS Rule |
|---|---|
| Two users edit same draft | Flag as Needs Review; do not overwrite silently. |
| Submitted report changed after sync | Keep original locked and write a new audit/change record. |
| Photo upload fails | Keep inspection/action queued until photo is uploaded or intentionally removed by authorized user. |
| User loses access before sync | Hold queued item for admin review instead of publishing automatically. |
| Duplicate inspection submission | Compare local ID/device ID/date/property and flag duplicate before report creation. |
Queued Uploads
Prototype queue view. In production, this should be stored locally on the device first, then confirmed by the server with permanent record IDs after sync.
| Type | Local ID | Property | Saved | Status | Next Step |
|---|---|---|---|---|---|
| No queued items. | |||||
Production Build Notes
- Use durable offline storage such as IndexedDB or a mobile app local database, not only browser localStorage.
- Use temporary local IDs for drafts, category records, corrective actions, and photos until server IDs are returned.
- Sync should be resumable, especially for large photo uploads.
- Dashboards should only use server-confirmed synced records, not unverified local drafts.
- Submitted reports should lock only after all required records and required photos have synced successfully.
- Every sync, failed sync, edit, lock, unlock, and corrective action completion should write to the audit log.
New Inspection
Inspection information from the existing KPI field inspection template converted into app fields.
No local draft saved yet.
Inspection Information
Inspection Categories
Westgate selects the official score. Checkboxes document what was reviewed and do not create or recommend a score.
Changes can be saved locally and queued while offline.
Inspection Summary
Report completion is blocked until required documentation is complete.
Score Summary
| Category | Weight | Score | Status | Weighted | Notes |
|---|---|---|---|---|---|
| Total | -- | -- | |||
Executive Summary / Email Summary
Action Center Workflow
Tracks what was documented, who owns it, when it is due, current status, completion proof, pending approval, scheduled/not-due work, and outside-scope items before leadership review.
Action Center Filters
Filters apply to this Action Center view only. Dashboard and report totals still follow the signed-in user's approved property access.
BrightView-Owned
0 active items
Service items assigned to BrightView remain visible until completed and documented.
Westgate / Approval
0 active items
Pending approval, access, or Westgate-owned items are tracked separately from BrightView service misses.
Immediate Attention
No critical items selected.
Past-due and breach-related actions should be visible without reading every inspection note.
Action Register
These rows can come from failed categories, manual follow-up items, or items already scheduled / pending / outside scope.
| # | Property / Category / Issue | Owner / Due | Status | Completion | Detail |
|---|
Action Detail
End-of-Month Action Summary
Shows what opened, what closed, what is still BrightView-owned, what is pending Westgate, and what should be separated as scheduled/not-due or outside scope.
| Property | Category | Issue | Owner | Due | Status | Completion / Proof |
|---|---|---|---|---|---|---|
| No visible action items. | ||||||
Status Rules
| Status | Meaning | Score / Meeting Use |
|---|---|---|
| Open | Action has been created but work has not started. | Visible on dashboard and monthly review. |
| In Progress | Work has started but is not complete. | Visible as BrightView-owned unless another owner is selected. |
| Completed | Completion has been documented. | Requires completion note, completed by, and completed date/time. Action photo upload is available but optional; it does not block report completion. |
| Pending Westgate Approval | Work is waiting for approval or PO. | Track separately from service miss. |
| Scheduled / Not Due | Work is scheduled or not due during this inspection period. | Track, but do not score as failed before due date. |
| Outside Scope | Work is not part of current maintenance scope. | Note separately / proposal required. |
| Unable to Complete / Needs Review | Work cannot be closed without decision, access, or scope clarification. | Escalate for review. |
Photo Register
Photos are tied to property, inspection, category, corrective action, and report records. Scoring photos should be taken during the inspection. Older photos must be marked as reference photos.
Photo Gallery
Prototype stores uploaded images locally in the browser session. Production should store photos in secure file storage with metadata and sync history.
Photo & Audit Metadata
| Property | Inspection Date | Category | Photo Type | Uploaded By | Local Time | Server Sync | Reference? | Note |
|---|
Proposal Drop Box / Approval Tracking
Drop in copies of proposals that BrightView has already created and sent by email. LPMS should not recreate the proposal process. It simply stores the document, notifies the assigned property users, and tracks approval status.
Purpose
BrightView still builds and emails proposals the normal way. LPMS only keeps a copy tied to the property so leaders can see what is pending, approved, revised, declined, scheduled, or completed.
Example
Palace — Tree Removal Proposal
Proposal is generated outside LPMS and emailed for approval. BrightView drops the PDF into LPMS, Palace users are notified, and the dashboard shows Pending Westgate Approval until a decision is made.
Drop In Existing Proposal
Low-work rule: upload the existing proposal document and select the property. Everything else should be optional or auto-filled when possible.
Notifications
Pending Westgate Review
Simple Workflow
Proposal Register Filters
Filters respect the signed-in user's property access and the selected Property View in the header.
Proposal Register
| Property | Title / Notes | Category | Amount | Status | Approver / Target | Email / Upload | Document | Actions |
|---|
Proposal Activity / Approval Log
Prototype audit trail showing uploads, status changes, and approval movement. Production version should store this as immutable proposal history.
| Date / Time | Property | Proposal | Activity | User | Comment |
|---|
Production Rules
| Rule | Production Requirement |
|---|---|
| No duplicate proposal work | LPMS stores and tracks existing BrightView proposals. It does not require users to rebuild proposals inside LPMS. |
| Property access | Users only see proposal documents for properties assigned to their approved profile. |
| Notifications | Assigned property or regional users receive email/app notifications when a proposal document is dropped into LPMS or status changes. |
| File security | Proposal files are stored securely and linked to the property, status, uploaded user, and approval record. |
| Audit history | Status changes, comments, approvals, declines, and revisions are audit logged. |
| Inspection connection | Proposal-required items can be referenced from corrective actions or reports without changing Westgate's official inspection score. |
Notification Center
Alerts for proposals, approvals, corrective actions, reports, risk scores, and offline sync activity. Alerts follow each user's approved role and property access.
How Alerts Work
LPMS should create alerts automatically when a proposal is dropped in, a status changes, a corrective action is due or past due, a report is submitted, or a sync issue needs review.
Access Rule
Notifications follow the same role/property access rules as the dashboard. A Palace GM sees Palace alerts only. A Florida regional user sees Florida alerts. Tim sees the full portfolio and admin/system alerts.
Notification Filters
Default view shows active unread alerts only. Filters respect the signed-in user's property access and the selected property scope in the header.
Visible Alerts
| Priority | Status | Type | Property | Alert | Source | Created | Action |
|---|
Production Rules
| Rule | Requirement |
|---|---|
| No extra work | Alerts are generated from existing activity. Users should not have to manually create notification records. |
| Proposal drop box | When an existing proposal is uploaded, the assigned property/regional approver receives an app/email alert. |
| Corrective actions | Due soon and past-due BrightView-owned actions appear for the assigned BrightView users and portfolio lead. |
| Westgate approvals | Pending approval items appear for the assigned Westgate property/regional users and leadership views. |
| Reports | Submitted reports and below-80/below-70 risk alerts appear based on property access. |
| Audit | Delivered, opened, read, status changed, and approval/decline events should be audit logged in production. |
Past Inspections
Review finalized/submitted inspection reports by property, score tier, category hot spot, and action status. Drafts and inspections still in progress should not appear here.
Finalized Report History
| Property | Date | Score | Tier | Hot Spot | Inspector | Action Status | Report |
|---|
Trend Notes
Trend notes load based on visible property access.
Final Report / Manager Review
Clean report preview for manager review, print/PDF, and executive email summary. Only finalized/submitted reports should be stored in Past Inspections. This report uses the official Westgate-selected scores and keeps scheduled, pending approval, outside-scope, and BrightView-owned items separated.