Johndorf Ventures Corporation × Symph Agency

Johndorf Core — Unified Operations Command Center

A centralized platform giving Johndorf leadership real-time visibility across Sales, Finance, HR, and operations. V1 is a read-and-manage command center built on three modules, hosted on GCP Philippines region.

Engagement Start

Apr 6, 2026

Pricing

P1,200/user/mo

User Limit

50 users

Target Go-Live

Week 6 Milestone

V1 Modules

📊

Executive Dashboard

View-only analytics for leadership

Finance: Collections, AR, Cash Flow
Sales: Reservations, Performance vs Target
Business Dev: Project Lifecycle, Construction
Documentation: Unit Status, RFO Tracking

🏗

Project Management

Data entry and lifecycle tracking

Project Lifecycle Management
Construction Milestone Tracking
Permits & Licenses Tracking
Community Engagement: Punchlist, Unit Acceptance

📄

Documentation + System Default

Document generation & platform admin

Document Template Auto-Generation
Buyer Pre-Qualification Tracking
Move-In Endorsement Monitoring
RBAC, User Management, @johndorf.com.ph auth

Platform Scope

✅ In Scope (V1)

Three modules: Executive Dashboard, Project Management, Documentation
System Default: RBAC, user management, 50-user cap
@johndorf.com.ph domain-restricted authentication
Read-only integrations: SAP, CRM, Payruler (where API access is granted)
Data entry interfaces for non-API data (Project Lifecycle, Construction, Permits)
Document template auto-generation
GCP Philippines region hosting (RA 10173 compliant)
99.5% uptime SLA, daily backups, 24-hr support
Full 50-user onboarding before go-live
Unlimited feature requests within agreed modules

🚫 Out of Scope (V1)

Write-back to CRM, SAP, or Payruler
Bidirectional sync with any third-party system
Contract management (handled in CRM)
SAP / CRM / Payruler configuration or vendor changes
Leasing Monitoring (Phase 2 / Nice-to-have)
HR/Admin module (pending requirements from Liz)
BDO module (pending requirements from Frances Abegail)
ERP implementation work
On-premise infrastructure or hardware
Internal IT staffing

Project Team

Symph Agency

Gee Quidet

Account Owner
Chief Revenue & Solutions Officer

Ranil Jaramillo

Embedded DTL
Interim Digital Transformation Lead

Frances Teves

Account Management
Virtual

Nick Gandionco

Account Management
Virtual

Tom Garcia

Builder
Full-Stack Engineer

Jap Balane

Builder
Full-Stack Engineer

Vince Tapdasan

Business Development
Strategic Alignment

Johndorf Ventures Corporation

Faith Hatamosa

CFO — Primary Contact
Senior Stakeholder

Liz Tagimacruz-Vecina

VP Human Resource & Admin
HR Governance

Requirements by Department

Sourced from Johndorf Core Requirements & Monitoring sheet. Priorities confirmed Apr 7, 2026.

Finance Urgent Faith Hatamosa — CFO

Feature

Description

3rd Party

Track

Collections & Take-Out Monitoring

Track equity vs financing take-out, units taken out, project-level collection breakdown. Visibility on collection efficiency vs expected revenue.

SAP

Track B

Accounts Receivable (AR) Management

Receivables aging, projected AR, overdue accounts. Identify collection risks and outstanding balances.

SAP

Track B

Cash Flow Monitoring

Track operational expenses and CAPEX. Visibility on cash movement and spending patterns.

SAP

Track B

Project Performance Overview

Consolidated view per project: reservation sales, cancellations, construction status, take-out status, JVC Tower performance. Note: construction status and JVC leasing/occupancy are tracked outside SAP.

SAP +

Track B

System Administration Urgent Ranil Jaramillo — Embedded DTL

Feature

Description

3rd Party

Track

User Management & Access Control

RBAC with role-based restrictions. Create/edit/deactivate users. 50-user cap enforcement. @johndorf.com.ph domain-only login. Admins see active vs inactive users.

None

Track A

Business Development High Genevieve Lim — Project Development Manager

Feature

Description

3rd Party

Track

Project Lifecycle Management

End-to-end project tracking from concept to launch. Steps/stages with owner per step, start/target/actual dates, Not Started / Ongoing / Completed status. Identify delays vs target. Currently in spreadsheets.

Sheets

Track A

Construction Milestone Tracking

CMD Gantt as baseline. Track milestones: Mobilization, Site Works, Topping Off, Water Tight, Elevator, Take-out phases, Turnover. Current vs completed vs upcoming milestones per project/building.

Sheets

Track A

Permits & Licenses Tracking

Monitor required permits per project. Track responsible department, status, timelines. Identify delays and bottlenecks. Based on existing major permits tracker.

Sheets

Track A

Department Targets (Performance Tracking)

Monthly targets per department. Track actual vs target, variance. Visibility on performance gaps. Can be derived from Project Lifecycle and Construction data.

Derived

Track A

Leasing Monitoring

Cost of leased spaces, rent collection, building dues, SKF fees. Occupied vs available spaces per property. Finance side from SAP; occupancy tracking from scratch.

SAP +

Phase 2

Sales & Marketing High Francis Icamen — AVP Sales & Marketing

Feature

Description

3rd Party

Track

Sales Reservation Productivity

Track reservation processing within 7-day cycle. Monitor efficiency and turnaround time of reservations.

CRM

Track B

Booking to Take-Out Tracking

Conversion from booking to take-out per financing option (bank, Pag-IBIG). Timelines and conversion rates per option.

CRM

Track B

Cancellation & Delinquency Monitoring

Cancellation rates and trends across projects. Monitor delinquent accounts. Enable early intervention.

SAP

Track B

Project Planning to Launch Tracking

Track project pipeline from planning to official launch. Visibility on timelines and readiness. Helps align campaigns with actual project status.

Sheets

Track A

Sales Performance vs Target

Actual sales vs revenue targets per project. Variance analysis. Performance evaluation and strategic adjustments.

Sheets

Track A

Construction Turnover vs Sellout

Compare construction progress (turnover readiness) against units sold (sellout). Identify gaps between supply and demand timing.

Sheets

Track A

Price Monitoring

Track and compare pricing across projects. Visibility on pricing changes and competitive positioning.

Sheets

Track A

Documentation Urgent Mid Claribel Fernandez — Doc Manager

Feature

Description

3rd Party

Track

Document Template Auto-Generation Urgent

Centralized template library (Affidavit, Contract to Sell, Deed of Sale, etc.). Dynamic fields/placeholders. Form-based data input. WYSIWYG output. PDF download & print. Conditional sections (with/without co-borrower). Admin template management with version control.

None

Track A

Reopened Units Monitoring

Total reopened units. Units previously reserved and subsequently reopened. Visibility on ownership and responsibility once tagged as RFO.

SAP

Track B

RFO (Ready for Occupancy) Tracking

All RFO units under Documentation team. Document completion status per unit. Ready vs pending for move-in.

CRM

Track B

Document Delay Tracking

Monitor document processing delays. Capture and categorize reasons: loss of buyer income, incomplete requirements, financing issues.

Internal

Track A

Buyer Pre-Qualification Visibility

Track buyer financing preferences (Pag-IBIG, bank). Identify buyers not meeting qualification requirements. Visibility on financing intent vs actual eligibility mismatches.

Internal

Track A

Move-In Endorsement Monitoring

Units endorsed as "Ready for Move-In." Endorsement status from Documentation to PMD. Timeline from reservation to move-in readiness.

Internal

Track A

Reporting

Generate: Reopened Units Report, RFO Unit Status Report, Document Delay Report (categorized), Buyer Qualification Report, Move-In Endorsement Report.

Internal

Track A

Community Engagement Mid Lhynshine Arcilla

Feature

Description

3rd Party

Track

Unit Status Tracking

Centralized view of each unit's status post-takeout. Standardized status values. Visible to all relevant departments.

None

Track A

Client Booking for Unit Acceptance

Clients select date/time slots (9AM-4PM) for unit acceptance visits. Department receives and confirms. Confirmation visible to client.

None

Track A

Punchlist Management

Digital punchlist during unit acceptance visits. Log issues visible to all departments. Acceptance document handed to Community Engagement when no issues found.

None

Track A

Move-In Reporting

Summary of total move-ins. Aging report from Takeout to Move-in. Filterable by project and date range.

None

Track A

Unit History / Timeline

Full historical view per unit. Vertical timeline: Reservation → Sales → Takeout → Turnover → Unit Acceptance. Timestamps and status per stage.

None

Track A

HR / Admin Pending Liz Tagimacruz-Vecina — VP HR & Admin

No requirements submitted yet. Deadline: April 11, 2026. Module deferred to Phase 2 if not received by then.

Business Development Operations Pending Frances Abegail Lim — AVP Business Development Operations

No requirements submitted yet. Deadline: April 11, 2026. Module deferred to Phase 2 if not received by then.

Project Plan

Both tracks run in parallel from Week 1. Track A can complete earlier — everything needed is available now. Track B is blocked on external API access regardless of effort.

Track A — No API Dependencies (Ships First)

Sort by:

Feature	Department	Module	Data Source	Complexity
User Management & RBAC	System Admin	System Default	Build from scratch	Medium
Document Template Auto-Generation	Documentation	Documentation	Drive templates (link provided)	High
Project Lifecycle Management	Business Dev	Project Management	Google Sheets (Ranil to share)	High
Construction Milestone Tracking	Business Dev	Project Management	CMD Gantt spreadsheet	Medium
Permits & Licenses Tracking	Business Dev	Project Management	Existing permits tracker	Medium
Department Targets	Business Dev	Dashboard	Derived from above	Low-Med
Project Planning to Launch	Sales & Mktg	Dashboard	Spreadsheets	Low-Med
Sales Performance vs Target	Sales & Mktg	Dashboard	Spreadsheets	Low-Med
Construction Turnover vs Sellout	Sales & Mktg	Dashboard	Spreadsheets	Low-Med
Price Monitoring	Sales & Mktg	Dashboard	Spreadsheets	Low-Med
Document Delay Tracking	Documentation	Documentation	Internal entry	Low
Buyer Pre-Qualification Visibility	Documentation	Documentation	Internal entry	Low
Move-In Endorsement Monitoring	Documentation	Documentation	Internal entry	Low
Documentation Reporting	Documentation	Documentation	Internal	Low
Unit Status Tracking	Community Eng.	Project Management	Build from scratch	Low
Client Booking (Unit Acceptance)	Community Eng.	Project Management	Build from scratch	Medium
Punchlist Management	Community Eng.	Project Management	Build from scratch	Medium
Move-In Reporting	Community Eng.	Project Management	Internal	Low
Unit History / Timeline	Community Eng.	Dashboard	Build from scratch	Medium

Track B — API-Dependent (Blocked Until Access Confirmed)

⚠️ All Track B features are blocked until SAP, CRM, and/or Payruler API access is confirmed. The Apr 8 vendor meeting must produce a written commitment and timeline.

Sort by:

Feature	Department	Module	Blocked On	Priority
Collections & Take-Out Monitoring	Finance	Dashboard	SAP API	Urgent
Accounts Receivable (AR) Management	Finance	Dashboard	SAP API	Urgent
Cash Flow Monitoring	Finance	Dashboard	SAP API	Urgent
Project Performance Overview	Finance	Dashboard	SAP API	Urgent
Sales Reservation Productivity	Sales & Mktg	Dashboard	CRM API	High
Booking to Take-Out Tracking	Sales & Mktg	Dashboard	CRM API	High
Cancellation & Delinquency Monitoring	Sales & Mktg	Dashboard	SAP API	High
Reopened Units Monitoring	Documentation	Dashboard	SAP API	Mid
RFO (Ready for Occupancy) Tracking	Documentation	Dashboard	CRM API	Mid

Project Timeline

Both tracks run in parallel from Week 1. Toggle between two schedule options below.

View:

OPTION 1 — Both tracks target Week 6. Subscription starts when both are ready.

Week

Track A (No Dependencies)

Track B (API-Dependent)

Week 1

Apr 6-12

Track A — Foundation

- ERD and architecture documentation (Tom & Jap)
- Module definition locked with Ranil & Faith
- Requirements collection: HR & BDO deadline Apr 11
- Google Sheet access confirmed (Ranil)
- Sprint 1 planning

Track B — API Alignment

- Apr 8: Vendor meeting (SAP, CRM, Payruler)
- Confirm API availability: yes/no
- If yes: API specs + sandbox access requested
- Written timeline commitment from vendors

Week 2

Apr 14-18

Track A — Platform Core

- System Administration: RBAC, user management
- @johndorf.com.ph auth setup
- 50-user cap enforcement
- Document template foundations

Track B — Waiting on APIs

Blocked until API access granted.
If granted by Apr 12: integration architecture begins.

Week 3

Apr 21-25

Track A — Project Management Module

- Project Lifecycle Management (CRUD)
- Construction Milestone Tracking
- Permits & Licenses Tracking
- Document Template Auto-Generation (cont.)

Track B — Integration Architecture

- SAP integration design and pipeline setup
- CRM integration design
- Data mapping and transformation layer

Week 4

Apr 28-May 2

Track A — Documentation + Community

- Documentation module: delay tracking, buyer pre-qual, move-in
- Community Engagement: unit status, booking, punchlist
- Sales spreadsheet-based features
- Department Targets (derived)

Track B — Finance Dashboard Build

- Collections & Take-Out Monitoring (SAP)
- AR Management (SAP)
- Cash Flow Monitoring (SAP)

Week 5

May 5-9

Track A — QA & Polish

- QA all Track A features
- Internal UAT with Frances & Nick
- Bug fixes and refinements
- Track A features demo-ready

Track B — Sales Dashboard + QA

- Sales Reservation, Booking-Takeout (CRM)
- Cancellation & Delinquency (SAP)
- Project Performance Overview
- Track B QA

Week 6+

May 12+

SUBSCRIPTION MILESTONE

- Combined QA: Track A + Track B
- Client review & acceptance
- Dashboard view finalizations
- 50-user onboarding & training
- Go-live on GCP Philippines region
- Subscription billing begins

Risk: API Delay = Subscription Delay

If Track B APIs not granted by Apr 12, Finance & Sales dashboards will not be ready for Week 6. Track A can still go live. Subscription may be partial or deferred.

OPTION 2 — Track A ships at Week 5. Subscription starts early. Track B follows at Week 7-8 when APIs come through.

Week

Track A (Ships Week 5)

Track B (Ships Week 7-8)

Week 1

Apr 6-12

Track A — Foundation

Track B — API Alignment

- Apr 8: Vendor meeting (SAP, CRM, Payruler)
- Confirm API availability: yes/no
- If yes: API specs + sandbox access requested
- Written timeline commitment from vendors

Week 2

Apr 14-18

Track A — Platform Core

- System Administration: RBAC, user management
- @johndorf.com.ph auth setup
- 50-user cap enforcement
- Document template foundations

Track B — Waiting on APIs

Blocked until API access granted.
If granted by Apr 12: integration architecture begins.

Week 3

Apr 21-25

Track A — Project Management Module

- Project Lifecycle Management (CRUD)
- Construction Milestone Tracking
- Permits & Licenses Tracking
- Document Template Auto-Generation (cont.)

Track B — Integration Architecture

- SAP integration design and pipeline setup
- CRM integration design
- Data mapping and transformation layer

Week 4

Apr 28-May 2

Track A — Documentation + Community + Sales (Spreadsheet)

- Documentation module: delay tracking, buyer pre-qual, move-in
- Community Engagement: unit status, booking, punchlist
- Sales spreadsheet-based features, Department Targets
- Track A feature complete — entering QA

Track B — Finance Dashboard Build

- Collections & Take-Out Monitoring (SAP)
- AR Management (SAP)
- Cash Flow Monitoring (SAP)

Week 5

May 5-9

🟢 TRACK A GO-LIVE — SUBSCRIPTION STARTS

- Track A QA + UAT with Frances & Nick
- 50-user onboarding begins (Track A scope)
- Go-live on GCP Philippines region
- Subscription billing begins on first login

Track B — Sales Dashboard + QA

- Sales Reservation, Booking-Takeout (CRM)
- Cancellation & Delinquency (SAP)
- Project Performance Overview
- Track B internal QA

Week 6

May 12-16

Track A — Live & Stable

- Bug fixes and refinements from live usage
- Remaining user onboarding
- Feature requests begin (within agreed modules)

Track B — UAT with Johndorf

- Client UAT: Finance & Sales API dashboards
- Feedback and refinements
- Final acceptance sign-off

Week 7-8

May 18+

Track A — Ongoing

Stable platform, active users, subscription running.

🟢 TRACK B GO-LIVE (if APIs granted Apr 12)

- Finance dashboards live (SAP)
- Sales dashboards live (CRM)
- Full platform now available to all 50 users

⚠️ Option 2 requires API access confirmed by Apr 12. If APIs are delayed past that date, Track B completion shifts beyond Week 8 accordingly.

Key Milestones

Milestone	Target Date	Owner	Status
Kickoff Meeting	Apr 6, 2026	Frances / Nick	Done
API Vendor Meeting (SAP, CRM, Payruler)	Apr 8, 2026	Ranil + Tom	Scheduled
Module Definition Locked (Ranil + Faith)	Apr 8, 2026	Gee	Pending
HR/Admin + BDO Requirements Deadline	Apr 11, 2026	Liz / Frances Abegail	Pending
ERD + Architecture Documentation	Apr 12, 2026	Tom Garcia	In Progress
API Access Granted (Cutoff for Week 6)	Apr 12, 2026	Vendors	Pending
Track A Feature Complete	May 9, 2026	Tom / Jap	Pending
Combined QA + UAT	May 12-16, 2026	Frances / Nick	Pending
50-User Onboarding	May 18-23, 2026	Ranil + Symph	Pending
Go-Live + Subscription Start	Week of May 25, 2026	All	Pending

Sprint Feature Breakdown

Which features are targeted per sprint. Week 1 is setup and planning - no feature sprint until Week 2. CRUD confirmed by Ranil (Apr 7) - all Track A features are data entry screens, not view-only. Synced with timeline toggle above.

Sprint 1 - Week 2 Track A Apr 14-18, 2026

Features

User Management & RBAC

@johndorf.com.ph Auth Setup

50-User Cap Enforcement

Document Template Library (foundations)

Module

System Default

Documentation

Sprint 2 - Week 3 Track A Apr 21-25, 2026

Features

Project Lifecycle Management (CRUD - confirmed)

Construction Milestone Tracking (CRUD)

Permits & Licenses Tracking (CRUD)

Document Template Auto-Generation (full)

Module

Project Management

Documentation

Sprint 3 - Week 4 Track A Track B begins Apr 28 - May 2, 2026

Track A Features

Documentation: Delay Tracking, Buyer Pre-Qual, Move-In Endorsement, Reporting

Community Engagement: Unit Status, Client Booking, Punchlist, Move-In Report, Unit History

Sales: Project Planning to Launch, Performance vs Target, Turnover vs Sellout, Price Monitoring

Department Targets (derived)

Track B (if APIs confirmed Apr 12)

Collections & Take-Out Monitoring (SAP)

Accounts Receivable Management (SAP)

Cash Flow Monitoring (SAP)

Integration architecture and data mapping

Sprint 4 - Week 5 Track A QA Track B features May 5-9, 2026

Track A

QA all Track A features

Internal UAT with Frances & Nick

Bug fixes and polish

Track A demo-ready for client

Track B Features

Sales Reservation Productivity (CRM)

Booking to Take-Out Tracking (CRM)

Cancellation & Delinquency (SAP)

Project Performance Overview (SAP)

Track B QA

Sprint 5 - Week 6+ (Go-Live) May 12+, 2026

Milestone Activities

Combined Track A + Track B QA

Client review and acceptance testing

50-user onboarding and training sessions

Go-live on GCP Philippines region

Subscription billing begins

Risk: If Track B APIs Delayed

Track A goes live as planned

Finance + Sales dashboards deferred to Phase 1b

Subscription may be partial or split

Track B gets its own go-live sprint once APIs confirmed

Sprint 1 - Week 2 Track A Apr 14-18, 2026

Track A Features

User Management & RBAC

@johndorf.com.ph Auth Setup

50-User Cap Enforcement

Document Template Library (foundations)

Module

System Default

Documentation

Sprint 2 - Week 3 Track A Track B begins Apr 21-25, 2026

Track A Features

Project Lifecycle Management (CRUD)

Construction Milestone Tracking (CRUD)

Permits & Licenses Tracking (CRUD)

Document Template Auto-Generation (full)

Track B (if APIs confirmed Apr 12)

SAP integration design and pipeline setup

CRM integration design

Data mapping and transformation layer

Sprint 3 - Week 4 Track A - Final Sprint Track B features Apr 28 - May 2, 2026

Track A - Last Features

Documentation: Delay Tracking, Buyer Pre-Qual, Move-In Endorsement, Reporting

Community Engagement: Unit Status, Client Booking, Punchlist, Move-In Report, Unit History

Sales spreadsheet features, Department Targets

Track A feature complete - entering QA

Track B

Collections & Take-Out Monitoring (SAP)

AR Management (SAP)

Cash Flow Monitoring (SAP)

Sprint 4 - Week 5 - TRACK A GO-LIVE May 5-9, 2026

Track A - Go-Live Activities

QA all Track A features

UAT with Frances & Nick

50-user onboarding begins

Go-live - subscription starts on first login

Track B

Sales Reservation Productivity (CRM)

Booking to Take-Out Tracking (CRM)

Cancellation & Delinquency (SAP)

Track B internal QA

Sprint 5 - Week 6 Track A Live Track B UAT May 12-16, 2026

Track A - Stable

Bug fixes from live usage

Remaining user onboarding

Feature requests begin (within agreed modules)

Track B - Final UAT

Client UAT: Finance & Sales dashboards

Feedback and refinements

Final acceptance sign-off

Sprint 6 - Week 7-8 - TRACK B GO-LIVE May 18+, 2026 (if APIs granted Apr 12)

Track B - Go-Live

Finance dashboards live (SAP)

Sales dashboards live (CRM)

Full platform available to all 50 users

Complete V1 platform live

Risk

If APIs not confirmed by Apr 12, Track B shifts beyond Week 8

Track A subscription unaffected - already live

Dependency Map

What needs to be resolved before which features can proceed.

Critical Blockers

SAP API Access

→

Finance Dashboard (all 4 features), Cancellation & Delinquency Monitoring, Reopened Units Monitoring

CRM API Access

→

Sales Reservation Productivity, Booking to Take-Out Tracking, RFO Tracking

Ranil + Faith: Module Definition Confirmed (written)

→

All feature development. Without locked modules, scope is undefined and sprint planning cannot begin.

Tom Garcia: ERD + Architecture Doc

→

Final sprint estimates, Jap sprint assignment, data model design for CRUD features

Ranil shares Google Sheet access (Project Lifecycle, CMD Gantt, Permits)

→

Project Lifecycle Management, Construction Milestone Tracking, Permits & Licenses Tracking

HR/Admin requirements from Liz (deadline Apr 11)

→

HR/Admin module scope and build. No requirements = deferred to Phase 2.

BDO requirements from Frances Abegail (deadline Apr 11)

→

BDO module scope and build. No requirements = deferred to Phase 2.

Internal Build Dependencies

System Administration (RBAC, Auth)

→

All other modules. RBAC must exist before any user can access any feature.

Project Lifecycle Management (CRUD)

→

Department Targets (Performance Tracking) — derived from lifecycle data

Document Template Library

→

Document Auto-Generation. Library must exist before generation can work.

Unit Status Tracking

→

Unit History / Timeline — status history feeds the timeline view

Flags, Clarifications & Risks

Items requiring action or decision before or during build. Each flag includes the issue, our assumption, and a concrete suggestion.

For Ranil — To Resolve Before Build Starts

Module Definition — Are the 3 V1 Modules Formally Locked?

Critical

🚩 Issue

Ranil has been pushing for "unlimited modules." The signed proposal states "limited modules, unlimited features." Gee is managing this conversation. But without formal written confirmation of which 3 modules are in V1, scope is undefined and no development sprint can be properly planned.

💭 Assumption

We are proceeding with: (1) Executive Dashboard, (2) Project Management, (3) Documentation. System Default (RBAC, auth) is the platform foundation — not a separate billable module. This is aligned with internal Symph discussions as of Apr 7.

✅ Suggestion

Gee to send a written summary email to Ranil and Faith by Apr 8 (before the vendor meeting) confirming the 3 modules. One email, one confirmation. Development does not start until this is received in writing.

Project Lifecycle / Construction / Permits — CRUD or View Only?

Critical

🚩 Issue

These features have no third-party data source — the data currently lives in spreadsheets. Tom flagged this in the Apr 7 meeting: if these require data entry (CRUD), the build is significantly larger than if they're view-only dashboards. Ranil hasn't explicitly confirmed either way.

💭 Assumption

We are assuming CRUD (data entry). Since no third-party system currently holds this data, users will need to enter and update it in Johndorf Core. This replaces the spreadsheets. Build estimates are based on this assumption — if view-only, estimates shrink significantly.

✅ Suggestion

Treat as CRUD in planning. This is the more useful and future-proof approach. Confirm with Ranil in the Apr 8 meeting. If answer is view-only (e.g., read from Google Sheets via API), the timeline shortens — a positive outcome. Build for CRUD; downscope if needed.

Google Sheet Access for Project Lifecycle, CMD Gantt & Permits

High

🚩 Issue

Ranil shared Google Sheet links in the requirements document. Tom and Jap need access to these to understand the data model before building. Without seeing the actual spreadsheet structure, the ERD cannot be finalized.

💭 Assumption

The spreadsheet links are shared or will be shared promptly. Tom will use these to design the data model and confirm whether CRUD or import-based approach is appropriate.

✅ Suggestion

Ranil to verify all linked Google Sheets have symph.co team read access before Apr 8. Tom to confirm access and review structure on Apr 8. Unblock this before ERD is finalized.

Community Engagement — Is This in V1 Scope?

Medium

🚩 Issue

Lhynshine Arcilla's requirements (unit status, client booking portal, punchlist) were not in the original kickoff portal scope. They appeared in the requirements sheet but were not discussed in the Apr 7 alignment meeting.

💭 Assumption

Community Engagement is in V1 scope since requirements were submitted. However, Client Booking (scheduling portal) and Punchlist Management are interactive features that go beyond a dashboard — we are categorizing them under Project Management module.

✅ Suggestion

Confirm with Ranil: are Community Engagement features expected by Week 6 go-live, or can they be delivered in Week 8-10 as a post-go-live sprint? Setting a later delivery date here reduces pressure on the critical path without removing the scope.

Leasing Monitoring — Confirm Out of V1

Low

🚩 Issue

Marked "Nice-to-have / Phase 2" in the requirements sheet, but has not been explicitly communicated to Ranil or Johndorf that this will not be in V1.

💭 Assumption

Leasing Monitoring is out of V1 scope. It requires a partial SAP integration (finance side) and custom occupancy tracking, making it a significant addition to an already packed V1 build.

✅ Suggestion

Add a visible "Phase 2" placeholder in the platform UI so Johndorf can see what's coming next. Communicate this explicitly to Ranil in writing during Week 1. Include in the scope alignment email from Gee.

For Johndorf — Actions Required from Client

HR/Admin Requirements Missing — Deadline April 11

Urgent

🚩 Issue

Liz Tagimacruz-Vecina (VP HR & Admin) has not submitted requirements. Without this, the HR module cannot be scoped, estimated, or built. Priority is listed as "Pending" in the requirements sheet.

💭 Assumption

HR module will not be included in the V1 build if requirements are not received by April 11. It will be formally deferred to Phase 2 and communicated to Liz and Faith.

✅ Suggestion

Ranil to follow up with Liz directly and set April 11 as a hard deadline. If no response by April 11, Frances to send a formal note to Faith: "HR module requirements not received. HR is deferred to Phase 2 per agreed process." Do not chase indefinitely.

BDO Requirements Missing — Deadline April 11

Urgent

🚩 Issue

Frances Abegail Lim (AVP Business Development Operations) has not submitted requirements. Same situation as HR.

💭 Assumption

BDO module will not be in V1 build. Deferred to Phase 2 if requirements are not received by April 11.

✅ Suggestion

Same approach as HR. Ranil follows up. April 11 is the cutoff. After that, a Phase 2 placeholder is added to the platform and the module is formally deferred. This protects the build schedule.

API Access Timeline from SAP, CRM & Payruler

Critical

🚩 Issue

All Finance and most Sales dashboard features are blocked until API access is confirmed. The Apr 8 vendor meeting needs to produce a clear yes/no and, if yes, a specific date. A verbal "we'll try" is not sufficient for planning.

💭 Assumption

If API access is not confirmed by April 12, Track B features are formally deferred. The Finance dashboard — Faith's highest priority — will not be ready at Week 6. Subscription start may need to be adjusted or split.

✅ Suggestion

In the Apr 8 meeting, request: (1) written confirmation of API availability, (2) API documentation or specs, (3) sandbox/test environment access. Do not proceed to integration design without written confirmation. If vendors cannot commit, escalate to Faith immediately — this is her priority area and she has leverage with the vendors.

Project Performance Data Outside SAP — Who Owns It?

High

🚩 Issue

Construction status and JVC Tower leasing/occupancy are noted in the requirements sheet as "monitored outside the system." These are part of the Finance Project Performance Overview feature. There is no automated source — someone has to own updating this data.

💭 Assumption

These fields will require manual data entry in Johndorf Core. Symph will build a simple admin entry form for construction status and JVC leasing data. The respective department head will own updating this on a defined cadence (weekly or per milestone).

✅ Suggestion

Ranil to confirm: (1) Who owns construction status data? (2) Who owns JVC Tower occupancy data? (3) What is the expected update frequency? Symph will build an admin input form. If Johndorf eventually connects these to a third-party system, the form can be replaced with an integration later.

Risks

🔴 API Delays = Subscription Milestone Delay

Risk

Most of what Faith (CFO, primary contact) wants is SAP-dependent. If SAP API is delayed or unavailable, the Finance dashboard — the highest-value deliverable for the primary decision-maker — slips. This threatens the Week 6 subscription milestone.

Assumption

If APIs are not confirmed by April 12, we formally treat Week 6 as a Track A go-live only. Track B becomes "Phase 1b" with its own timeline established after API access is received. We do not delay Track A for Track B.

Suggestion

Build and demo Track A features in Weeks 3-4 to show Johndorf visible progress. This maintains momentum and confidence even if Finance dashboard is delayed. Frame it as: "Your platform is live and growing — Finance dashboards will be added as soon as vendor access is granted."

🔴 Scope Creep via Ranil

Risk

Ranil represents multiple departments each with competing priorities. He believes modules are unlimited. Each new department head he speaks to may add new requests. Without a formal "V1 is locked" signal, feature requests will keep flowing in during the build.

Assumption

Once Gee communicates the 3-module definition in writing, V1 scope is locked. Any new requests after Week 1 go into a formal backlog — they do not automatically enter the V1 build. Unlimited features = unlimited features within the 3 agreed modules, not unlimited new modules.

Suggestion

Implement a feature request process: any new request after Week 1 is logged, estimated, and scheduled in a named sprint or backlog. Frances and Nick manage this queue. Ranil is told: "That's a great request — it's logged and will be prioritized in the next sprint cycle." This is normal SaaS cadence.

🟠 Missing Requirements (HR, BDO)

Risk

Liz (HR) and Frances Abegail (BDO) have not submitted any requirements. If these come in late (Week 3+), there is no time to scope, estimate, and build before the Week 6 milestone.

Assumption

April 11 is the hard cutoff. Any department that misses this deadline has their module formally deferred to Phase 2. This protects the build schedule for departments that did submit on time.

Suggestion

Ranil follows up with both by April 9. If no response by April 11, Frances sends a formal notice to Faith: "HR and BDO modules will be delivered in a post-go-live sprint. V1 will proceed with the 5 departments that submitted requirements." Build placeholder cards in the UI for these modules so Johndorf can see what's planned.

🟠 CRUD vs. View-Only Ambiguity

Risk

Project Lifecycle, Construction Milestones, and Permits are estimated as CRUD (data entry) features. If Johndorf later clarifies they only want view-only dashboards pulling from Google Sheets, the estimates change significantly — either direction.

Assumption

CRUD is the correct approach. These features currently live in spreadsheets with no third-party API. Building CRUD forms replaces the spreadsheets and keeps Johndorf Core as the system of record. This is higher effort but delivers more value.

Suggestion

Estimates use CRUD as the baseline. Confirm in the Apr 8 meeting. If Ranil says "just pull from Google Sheets," Tom evaluates feasibility (Sheets API integration is possible but has its own complexity). CRUD is the safer assumption — if the answer is Sheets, timelines shorten.

Architecture & Integration

System architecture, data model, and integration flows. Source: System Integration Requirements doc by Ranil Jaramillo, Apr 7, 2026. Subject to revision after Apr 8 vendor alignment session.

System Roles

🏗️

SAP

Source of Truth

Customer master data
Projects and units
Reservations (final status)
Financial data: invoices, payments, commissions

All critical transactions finalized here before reflecting in other systems.

🤝

CRM

Front-Facing Sales Layer

Lead and client management
Reservation initiation
Broker/seller data capture
Sales and marketing workflows

CRM captures data and sends to SAP for validation. SAP returns confirmed records.

📊

Johndorf Core

Consolidation Layer (New)

Reads from SAP and CRM (read-only)
Dashboards: Finance, Sales, Project, Documentation
CRUD for non-SAP/CRM data (confirmed by Ranil Apr 7)

JC does not replace SAP or CRM. It orchestrates and visualizes data across systems.

System Architecture — v3

JOHN
DORF

Johndorf Core

Unified Operations & Insights Platform

Always There

Your Existing Systems

🕐

CRM

Sales & Reservations

⊞

SAP

Finance & ERP

👤

Payruler

HR & Payroll

● Data syncs automatically in the background

→

Secure Access

🔒

Google Sign-In

Use your Johndorf email to access the platform securely from anywhere

@johndorf.com.ph only

→

Central Hub

✳️

Johndorf Core

Your Unified
Operations Center

Role-Based Access

Each user sees only what's relevant to their role

→

Modules

⊞Executive Dashboard

Real-time summary view across all departments and projects

Aggregates data from CRM, SAP & Payruler

💲Finance

Collections, AR, Cash Flow & Project Performance

📈Sales & Marketing

Reservations, Pipeline & Sales Performance

🏗️Project Management

Project Lifecycle, Construction & Permits

📄Documents

Document Generation, RFO Tracking & Compliance

👥Community Engagement

Unit Acceptance, Punchlist & Client Booking Portal

⚙️User Management

ADMIN ONLY

Access Control, Roles & User Provisioning

Confidential — Prepared for Johndorf Ventures Corporation | Powered by Symph

Integration Flows (7 Defined)

From Ranil's System Integration Requirements doc. These flows describe the SAP-CRM integration. Johndorf Core reads from both as a consolidation layer. Integration build responsibilities to be finalized Apr 8.

Flow	Direction	Description	Johndorf Core Role
3.1 Project List	SAP → CRM	CRM retrieves project list from SAP. All project data in CRM reflects SAP records.	JC reads project data from SAP (source of truth)
3.2 Unit Management	SAP → CRM	CRM retrieves unit list and details from SAP. Unit status updates must originate from SAP - no manual updates in CRM.	JC reads unit data and status from SAP
3.3 Customer Information	CRM → SAP → CRM	CRM captures customer data, sends to SAP for validation. SAP returns confirmed record (Customer Code). SAP is master.	JC reads confirmed customer records from SAP
3.4 Unit Reservation	CRM → SAP → CRM	CRM initiates reservation, SAP validates and updates unit status + customer linkage, SAP returns confirmation. Reservation status finalized in SAP.	JC reads finalized reservation status from SAP
3.5 Invoices & Payments	SAP → CRM (read)	SAP manages all invoices and payments. CRM retrieves for visibility only. No financial duplication across systems.	JC reads financial data from SAP for Finance Dashboard
3.6 Broker/Seller Info	CRM ↔ SAP	CRM captures broker/seller data, syncs to SAP for validation and storage. Data ownership TBD in Apr 8 session.	JC reads validated broker/seller records from SAP
3.7 Commissions & Incentives	SAP → CRM (read)	SAP calculates and manages all commissions. CRM retrieves for visibility only. Financial calculations stay in SAP.	Not in V1 JC scope (Finance Dashboard focuses on collections/AR)

Entity Relationship Diagram

erDiagram USERS { string id PK string email string full_name string role_id FK string department string status } ROLES { string id PK string name json permissions } PROJECTS { string id PK string sap_project_code string name string phase string status date start_date date target_completion } PROJECT_LIFECYCLE_STEPS { string id PK string project_id FK string step_name string owner date start_date date target_date date actual_date string status } CONSTRUCTION_MILESTONES { string id PK string project_id FK string building string milestone_name date baseline_date date actual_date string status } PERMITS { string id PK string project_id FK string permit_name string responsible_dept string status date target_date } UNITS { string id PK string project_id FK string sap_unit_code string building string unit_no string status } CUSTOMERS { string id PK string sap_customer_code string name string financing_type string qualification_status } DOCUMENT_TEMPLATES { string id PK string name string type int version json field_schema } DOCUMENTS { string id PK string template_id FK string unit_id FK string customer_id FK string generated_by FK string status datetime created_at } FINANCE_SNAPSHOTS { string id PK string project_id FK date snapshot_date decimal collections_total decimal ar_total decimal cash_flow } SALES_SNAPSHOTS { string id PK string project_id FK date snapshot_date int reservations int cancellations decimal performance_vs_target } USERS }|--|| ROLES : "assigned" PROJECTS ||--o{ PROJECT_LIFECYCLE_STEPS : "has" PROJECTS ||--o{ CONSTRUCTION_MILESTONES : "tracks" PROJECTS ||--o{ PERMITS : "requires" PROJECTS ||--o{ UNITS : "contains" PROJECTS ||--o{ FINANCE_SNAPSHOTS : "has" PROJECTS ||--o{ SALES_SNAPSHOTS : "has" UNITS }o--o| CUSTOMERS : "reserved-by" UNITS ||--o{ DOCUMENTS : "referenced-in" CUSTOMERS ||--o{ DOCUMENTS : "subject-of" DOCUMENT_TEMPLATES ||--o{ DOCUMENTS : "generates" USERS ||--o{ DOCUMENTS : "creates"

18 entities — Auth, Core, Documents, Project Modules, Community, Sync, Snapshots. Updated by Tom Garcia, Apr 7, 2026.

Open Architecture Questions

Confirmed

SAP is single source of truth for all financial and unit data
CRM reads from SAP - no independent financial records
Johndorf Core reads from both - no write-back to either
Track A features (Project Lifecycle, Construction, Permits, Docs) are CRUD
Goal: "put everything in Johndorf Core, avoid creating info in sheets" (Ranil, Apr 7)
Export to PDF/CSV OK - data creation stays in JC

Pending - Apr 8 Vendor Meeting

Which vendor exposes APIs vs. batch data exports
Sync frequency per flow (real-time vs. nightly)
Who builds the integration layer - JC team or vendor-side
Sandbox/test environment availability from SAP, CRM, Payruler
Handling of duplicate records between SAP and CRM
Document storage model: per project or per unit/buyer (OPEN - needs Ranil confirmation)

Build Plan — v1 Draft

Batch-based delivery · Agile · Vendor-aware · April 2026. Work is organized into 4 batches — not phases. Batches are flexible delivery units that can shift, run in parallel, or reorder based on dependencies and vendor readiness.

Batch 1 — Foundation (No Vendor Deps) · 2–3 wks

Batch 2 — Data + Finance + Sales (Vendor-Conditional) · 3–4 wks

Batch 3 — Operations (No Vendor Deps) · 2–3 wks

Batch 4 — Engagement + Intelligence (Payruler-Conditional) · 2–3 wks

Vendor Dependency Risk — SAP & CRM APIs: Finance and Sales modules depend on third-party vendor API access. Batch 2 is designed to handle this — Track A builds immediately against mock data, Track B slots in live vendor connectors once credentials are received.

User Stories

28 stories derived from the Johndorf Core Requirements and Monitoring sheet. Track A = buildable now. Track B = blocked on API access.

ID	As a...	I want to...	So that...	Priority	Track
Finance - Faith Hatamosa (CFO)
US-FIN-001	CFO	Monitor collections and take-out per project with equity vs financing breakdown	I can track collection efficiency vs expected revenue in real time	Urgent	Track B
US-FIN-002	Finance Manager	See AR aging, projected receivables, and overdue account summaries	I can identify collection risks before they become defaults	Urgent	Track B
US-FIN-003	CFO	Monitor operational cash flow with OPEX and CAPEX visibility	I have a clear picture of cash movement and spending patterns across projects	Urgent	Track B
US-FIN-004	CFO	View a consolidated project performance overview across reservations, cancellations, construction, and take-out	I can assess every project's health in one screen without switching tools	Urgent	Track B
System Administration - Ranil Jaramillo (Embedded DTL)
US-SYS-001	System Admin	Create, edit, and deactivate users with role-based permission groups	Only authorized @johndorf.com.ph users with the correct role can access specific features	Urgent	Track A
US-SYS-002	System Admin	Have the platform automatically enforce a 50-user cap	Subscription limits are maintained without manual oversight	Urgent	Track A
Business Development - Genevieve Lim (Project Dev Manager)
US-BIZ-001	Project Manager	Track each project lifecycle step with owner, start/target/actual dates, and status	I can identify delays vs targets and manage the project end-to-end in one place	High	Track A
US-BIZ-002	Project Manager	Track construction milestones against the CMD Gantt baseline	I can monitor progress and surface delayed milestones before they impact the schedule	High	Track A
US-BIZ-003	Project Manager	Monitor permits and licenses with responsible department and status per project	I can identify bottlenecks and escalate before delays impact construction timelines	High	Track A
US-BIZ-004	Department Head	Track monthly actual performance vs targets with variance visibility	I can identify performance gaps early and course-correct before end-of-period	High	Track A
Sales and Marketing - Francis Icamen (AVP Sales)
US-SAL-001	Sales Manager	Track reservation productivity within a 7-day processing cycle	I can ensure reservations are processed on time and identify bottlenecks quickly	High	Track B
US-SAL-002	Sales Manager	Track booking to take-out conversion per financing option (bank, Pag-IBIG)	I can monitor and optimize conversion rates per financing path	High	Track B
US-SAL-003	Sales Manager	Monitor cancellation rates and delinquent accounts across projects	I can identify at-risk accounts and intervene early	High	Track B
US-SAL-004	Sales Director	Track project pipeline from planning to official launch with timeline visibility	Marketing campaigns align with actual project readiness	High	Track A
US-SAL-005	Sales Manager	See actual sales vs revenue targets per project with variance analysis	I can evaluate performance objectively and make data-driven strategy adjustments	High	Track A
US-SAL-006	Sales Director	Compare construction turnover readiness against units sold per project	I can identify timing gaps between unit availability and demand	Mid	Track A
US-SAL-007	Sales Manager	Monitor pricing across all projects with change history	I have visibility on pricing movements and can maintain competitive positioning	Mid	Track A
Documentation - Claribel Fernandez (Doc Manager)
US-DOC-001	Documentation Officer	Generate legal documents from a template library using dynamic field inputs	I can produce accurate, consistent documents quickly without manual copy-paste errors	Urgent	Track A
US-DOC-002	Documentation Manager	Monitor reopened units and RFO status per unit	I know documentation ownership and responsibility for each RFO-tagged unit	Mid	Track B
US-DOC-003	Documentation Manager	Track document processing delays with categorized reasons	I can identify and address systematic bottlenecks rather than individual cases	Mid	Track A
US-DOC-004	Documentation Officer	View buyer pre-qualification status with financing preference and eligibility flag	I can identify financing mismatches early and escalate before take-out	Mid	Track A
US-DOC-005	Documentation Manager	Track move-in endorsements from Documentation to PMD with timeline per unit	I can monitor readiness and flag units overdue for endorsement	Mid	Track A
US-DOC-006	Documentation Manager	Generate standard reports: Reopened Units, RFO Status, Document Delay, Buyer Qualification, Move-In	Stakeholders have consistent, up-to-date visibility without requesting custom exports	Mid	Track A
Community Engagement - Lhynshine Arcilla
US-CE-001	CE Officer	View a centralized unit status board with standardized values across all projects	All departments see the same unit status without conflicting spreadsheet versions	Mid	Track A
US-CE-002	CE Officer	Allow clients to book unit acceptance visit slots (9AM-4PM) through the platform	Scheduling is managed efficiently without back-and-forth coordination	Mid	Track A
US-CE-003	CE Officer	Log issues on a digital punchlist during unit acceptance visits	Issues are documented on-site and visible to all departments immediately	Mid	Track A
US-CE-004	CE Officer	Generate move-in reports with aging from takeout, filterable by project and date range	I can track community progress and report move-in velocity to leadership	Mid	Track A
US-CE-005	CE Officer	View a full unit history timeline per unit (Reservation - Sales - Takeout - Turnover - Unit Acceptance)	Every stakeholder can trace a unit's complete journey without digging through records	Mid	Track A

Billing & Commercial Summary

Subscription structure, engagement phases, and billing milestones. Internal reference - Symph use only.

Subscription Pricing

P1,200

per user / per month

P60,000

max monthly (50 users)

P720,000

max annual (50 users)

Billing Details

Billing model

Per active user, billed monthly at end of each cycle

SaaS Subscription

User cap

Platform enforces maximum 50 users automatically

50 users

Subscription start

Begins at Week 6 go-live, contingent on client acceptance

Week 6 - May 25, 2026 est.

Domain restriction

Only @johndorf.com.ph accounts are billable users

@johndorf.com.ph

Engagement History

Phase

Description

Amount

Status

Phase 1 - Development

Initial platform build

P200,000

Completed

Phase 2 - Development

Extended build - additional modules

P220,000

In Progress

Staff Augmentation

Embedded DTL (Ranil) - monthly retainer

P180,000/month

Active

SaaS Subscription

P1,200/user/month starting Week 6

P1,200 x users

Starts Week 6

What is Included in Subscription

Included in P1,200/user/month

Unlimited feature requests within the 3 agreed V1 modules
GCP Philippines region hosting (RA 10173 compliant)
99.5% uptime SLA
Daily backups with 30-day retention
Security updates and platform patches
24-hour support response SLA
Full 50-user onboarding session
Quarterly business reviews with Symph account team

Not Included (Separate Engagement)

New modules outside V1 scope (Phase 2 features)
ERP or third-party system configuration
SAP / CRM / Payruler vendor coordination
Custom integrations beyond agreed Track B APIs
HR module (deferred to Phase 2 if reqs not received by Apr 11)
BDO module (deferred to Phase 2 if reqs not received by Apr 11)
Staff Augmentation services (separate billing)

Billing Milestones

Milestone	Target Date	Billing Event	Status
Engagement Kickoff	Apr 6, 2026	No billing event	Done
Week 6 Go-Live + Client Acceptance	May 25, 2026 est.	Subscription billing begins	Pending
Month 1 Invoice	Jun 25, 2026 est.	Active users x P1,200	Pending
Month 2 Invoice	Jul 25, 2026 est.	Active users x P1,200	Pending
50-User Milestone	TBD	Max monthly: P60,000	Pending

Project Updates

Weekly progress log. Updated after every sprint check-in.

📣

No updates yet

Updates will appear here after each weekly check-in. First update expected after Week 1 wrap-up (Apr 12, 2026).

UI Screens — V1 Design System

10 annotated screens covering the full V1 experience: Login, Personalized Dashboard, Project Management, Create Project Wizard, Construction Milestones, Document Generator (buyer selection & review), Finance (Track B empty state), Permits & Licenses, and User Management. Each screen includes UX annotations for non-technical stakeholders. All data is representative of real Johndorf operations.

1. Login 2. Home Dashboard 3. Project Cards 4. Create Project Wizard 5. Construction Milestones 6. Doc Gen — Buyer 7. Doc Gen — Review 8. Finance (Track B) 9. Permits Tracker 10. User Management

1 Login

Full-screen split layout with Johndorf branding. Left panel builds brand confidence; right panel provides a clean, focused sign-in experience.

JOHNDORF VENTURES CORPORATION

JVC

Johndorf Core

Unified Operations Command Center

Real-time visibility across Projects, Finance, Sales, and Documentation — all in one secure platform.

📊 Executive Dashboard & KPIs

🏗 Project & Construction Management

📄 Auto-Fill Documentation

💰 Finance & Collections

Welcome back

Email Address

Password

Forgot password?

Access is restricted to authorized @johndorf.com.ph email addresses.
Contact your system administrator for account provisioning.

💡

UX Decision: Split-screen login creates a strong brand first impression. The JVC logo block and tagline "Unified Operations Command Center" immediately communicate authority. The right panel is distraction-free with a single CTA. The decorative grid subtly evokes building/planning themes. Domain restriction messaging (@johndorf.com.ph) is visible up front so employees understand access is controlled.

2 Home Dashboard (Personalized)

The landing screen after login. Personalized greeting, proactive attention items surfacing blockers, KPI overview, quick-access module cards with honest "coming soon" states, and recent activity feed.

🔔 Needs Your Attention

OVERDUE 3 construction milestones overdue in Tierra Verde Phase 3

View Milestones →

DEADLINE API vendor deadline: 2 days remaining — confirm access

Confirm Access →

EXPIRING 2 permits expiring within 30 days — review required

Review Permits →

Active Projects

across 3 phases

Active Users

12 / 50

seats used

Pending Approvals

documents awaiting review

Open Blockers

SAP integration pending

Quick Access

📊

Executive Dashboard

KPIs across all modules. Collections, sales, project health at a glance.

🏗

Project Management

5 active projects. Milestones, permits, progress tracking.

📄

Documentation & System

CTS, DAS, endorsement forms. Auto-fill from buyer database.

📈

Sales Performance

Reservations, pipeline, conversion rates by project.

Track B · Week 8

💰

Finance Collections

Collections, AR aging, take-out monitoring. Requires SAP API.

🔒

Track B · Week 8

🤝

Community Engagement

Events, stakeholder tracking, engagement logs.

Quick Activity Last 48 hours

Claribel Fernandez generated CTS for Maria Santos — Unit B3-1204, Tierra Verde Ph. 3

2 hrs ago

R. Santos updated milestone: Roofing marked 85% complete — Tierra Verde Ph. 3

4 hrs ago

Francis Icamen approved DAS document for J. Reyes — Summerhills Block 4

Yesterday

System DENR permit for Palmera Heights expires in 12 days — auto-alert sent

Yesterday

Genevieve Lim created new project: Cielo Residences (Planning phase)

Apr 5

💡

UX Decision: The "Needs Your Attention" card is the first thing Genevieve sees — it surfaces blockers proactively so she never has to hunt for problems across modules. Orange dot indicators and severity badges (OVERDUE, DEADLINE, EXPIRING) create visual urgency without alarm. Module cards with "Track B - Week 8" badges and lock icons set honest expectations about Finance availability. The greeting is personalized with day/date for situational awareness.

3 Project Management — Project Cards View

Card-based project view with progress rings for instant health scanning. Each card shows project phase, manager, target date, and status — all visible at a glance without drilling in.

All (5) Active (3) In Planning (1) On Hold (1)

Tierra Verde Phase 3

Construction Phase 3

In Progress

Manager: Genevieve Lim

Target: Aug 2026

3 milestones overdue

Cielo Residences

Pre-Development

Planning

Manager: Tom Garcia

Target: Dec 2026

Summerhills Block 4

Contractor Bidding

In Bidding

Manager: Gee Lim

Target: Oct 2026

💡

UX Decision: Card layout with SVG progress rings replaces a data table for instant visual scanning. Colored left borders match status badges (green=active, blue=planning, yellow=bidding) so even a quick scroll reveals project health. The "3 milestones overdue" warning in red on Tierra Verde immediately flags the problem without requiring a click. Filter pills let managers narrow by status without learning a complex filter UI.

4 Create Project — Wizard Step 1 of 3

Guided wizard flow for creating a new project. Step 1 collects basic information with contextual help (info icons) and helper text on key fields. Reduces errors by breaking a complex form into digestible steps.

Basic Info

Assign Team

Review & Confirm

Project Details

Project Name

Used as the internal reference across all modules

Project Location

Property Type ℹ

Estimated Units

Start Date

Target Completion

💡

UX Decision: A 3-step wizard prevents overwhelming non-technical users with all project fields at once. The step indicator at top shows exactly where you are and what comes next. Helper text under "Project Name" sets expectations. The info icon on "Property Type" provides on-demand context (determines milestone templates) without cluttering the form. "Next: Assign Team" clearly names the next action — no ambiguity.

5 Construction Milestones — Tierra Verde Phase 3

Visual phase bar tracking 6 construction phases with status icons. Overdue alert card surfaces the critical blocker immediately. Detailed milestone table below provides granular tracking with days variance.

✓

Foundation

✓

Structure

🔄

Roofing

⏳

MEP

⏳

Finishing

⏳

Turnover

Overall Progress:

33%

⚠ Roofing is 14 days behind schedule

Contractor: ABC Construction · Expected: Mar 24, 2026 · Actual: TBD
Impact: Delays MEP and Finishing phases downstream

Phase	Milestone	Contractor	Target	Actual	Status	Var
Foundation	Piling complete	XYZ Foundations	Oct 15, '25	Oct 12, '25	Done	+3d
Structure	Column & beam pour	ABC Construction	Jan 10, '26	Jan 14, '26	Done	-4d
Roofing	Truss installation	ABC Construction	Mar 10, '26	Mar 18, '26	Delayed	-8d
Roofing	Roofing sheet lay	ABC Construction	Mar 24, '26	—	Overdue	-14d
MEP	Rough-in electrical	PowerGrid Elec.	Apr 14, '26	—	Pending	—
Finishing	Interior plastering	TBD	May 20, '26	—	Pending	—

💡

UX Decision: The visual phase bar with status icons (checkmark, spinning, hourglass) gives executives an instant read on construction progress without reading a single number. The overdue alert card with red left border and impact statement ("Delays MEP and Finishing phases downstream") connects the delay to business consequences. The days variance column uses color coding (green positive, red negative) for at-a-glance health — no mental math required.

6 Document Generator — Wizard Step 2 of 4 (Select Buyer)

Buyer search with auto-populated results from the reservation database. Selected buyer highlighted with green checkmark. Blue tip callout explains the auto-fill behavior to build user confidence in the system.

✓

Doc Type

Select Buyer

Review

Generate

Maria Teresa Santos ✓

Unit B3-1204 · Tierra Verde Phase 3 · Bank Financing (BDO)

Selected

Maria Lourdes Cruz

Unit A1-0503 · Summerhills Block 4 · In-House Financing

Maria Fe Gonzales

Unit C2-0801 · Cielo Residences · Pag-IBIG

💡

Buyer info is pulled from the reservation database. Fields will auto-fill in the next step — no manual data entry required.

💡

UX Decision: The search + select pattern prevents typos and ensures data consistency. The green checkmark and "Selected" state give clear visual confirmation. The blue tip callout ("fields will auto-fill") builds confidence for documentation officers who may worry about manual data entry errors. Showing unit numbers and financing type in results helps disambiguate buyers with common names like "Maria."

7 Document Generator — Wizard Step 3 of 4 (Review)

Split-panel review screen: left shows auto-filled and editable fields with yellow highlights; right shows a live document preview. Validation row confirms all fields pass before generation.

✓

Doc Type

✓

Buyer

Review

Generate

Document Fields

Buyer NameMaria Teresa Santos

Buyer TIN123-456-789-000

ProjectTierra Verde Phase 3

UnitB3-1204

TCP₱2,850,000.00

Date of SigningApril 7, 2026

Payment SchemeBank Financing (BDO) ▾

Special ConditionsEarly move-in clause ✎

Auto-filled Editable

✓ 6 fields auto-filled · 2 editable · 0 errors

Live Preview

CONTRACT TO SELL

Johndorf Ventures Corporation

This Contract to Sell is entered into by and between Johndorf Ventures Corporation, hereinafter referred to as the "SELLER", and:

Buyer: Maria Teresa Santos

TIN: 123-456-789-000

Property: Unit B3-1204, Tierra Verde Phase 3

Total Contract Price: ₱2,850,000.00

Payment: Bank Financing (BDO)

💡

UX Decision: The split-panel layout lets documentation officers verify data (left) against the actual document output (right) simultaneously. Yellow-highlighted auto-filled values in the preview create a visual link between the field list and the generated text — nothing feels like a black box. The validation row (6 green, 0 errors) provides confidence before generation. The gold CTA "Looks good — Generate Document" is intentionally warm and affirming rather than a cold "Submit" button.

8 Finance Dashboard — Informative Empty State (Track B)

Instead of a blank page, this empty state explains what is coming, why, and when. A progress timeline sets honest expectations about the SAP/CRM integration dependency.

Finance dashboards activate in Week 8

SAP and CRM API integration is required before collections, AR aging, and take-out monitoring can go live. Vendor meeting is scheduled for April 8.

API Meeting
Apr 8

Access Granted
pending

Integration
Wk 3-4

Finance Live
Week 8

💡

UX Decision: Empty states should inform, not confuse. Instead of a blank page or generic "Coming Soon," this screen explains WHY the module is unavailable (SAP integration dependency), WHAT needs to happen (4-step timeline), and WHEN it will be ready (Week 8). The faded bar chart silhouette hints at what the dashboard will eventually look like. "Notify me when ready" gives the user an action to take — even an empty state deserves a CTA.

9 Permits & Licenses Tracker

KPI summary with expiry urgency levels, alert strip for immediate attention, and a detailed permit table with color-coded countdown days. Red for critical (14 days or less), orange for warning (30 days or less), green for safe.

Active

Expiring Soon

within 30 days

Overdue

Completed

⚠️ 3 permits expire within 30 days — review required

Permit	Project	Dept	Issued	Expiry	Status	Days Left
DENR ECC	Palmera Heights	Compliance	Apr 19, '25	Apr 19, '26	Expiring	12 days
Fire Safety Cert	Palmera Heights	Engineering	May 1, '25	May 1, '26	Expiring	24 days
Building Permit	Tierra Verde Ph. 3	Engineering	Jan 15, '25	Jan 15, '27	Active	283 days
HLURB License	Cielo Residences	Legal	Mar 1, '26	Mar 1, '28	Active	693 days
Zoning Clearance	Summerhills Block 4	Legal	Feb 10, '26	May 10, '26	Expiring	33 days

💡

UX Decision: Permits are a compliance risk that non-technical managers struggle to track in spreadsheets. The KPI row gives an instant health summary. The orange alert strip creates urgency for items needing immediate action. The "Days Left" column uses a 3-tier color system (red under 14 days, orange under 30, green over 30) that works even for users who skim — red numbers jump off the page. The "Download Report" button supports offline review and executive reporting.

10 User Management — Redesigned

Card-based user view with seat capacity bar, role badges, module access chips, and a compact role matrix. Designed for quick scanning of who has access to what.

12 of 50 seats used

76% available

Faith Hatamosa Admin

faith.hatamosa@johndorf.com.ph

All Modules Users Settings

Last login: Today 8:12 AM

Genevieve Lim Manager

genevieve.lim@johndorf.com.ph

Projects Docs Sales Community

Last login: Today 7:45 AM

Francis Icamen Manager

francis.icamen@johndorf.com.ph

Projects Docs Permits

Last login: Yesterday 4:30 PM

Claribel Fernandez Standard

claribel.fernandez@johndorf.com.ph

Docs

Last login: Today 9:00 AM

Role Access Matrix

Role	Proj	Docs	Sales	Fin	Admin
Admin	●	●	●	●	●
Mgr	●	●	●	●	●
Std	●	●	●	●	●

● Access ● No access

💡

UX Decision: Cards replace a dense user table — each card shows the user's avatar, role badge, module access chips, and last login at a glance. The seat capacity bar (12/50) provides a visual budget for license planning. The side-panel role matrix gives admins a compact reference for permission levels without navigating away. Role badges use consistent colors (blue=Admin, gold=Manager, gray=Standard) that match throughout the system.

Feedback & Discussion Points

(1) "Needs Your Attention" widget — are 3 action items the right density, or should this show more/fewer?
(2) Progress rings vs. progress bars on project cards — preference?
(3) Construction milestone phase bar — timeline visualization vs. list preferences.
(4) Finance "Coming Soon" empty state — does the 4-step timeline set the right expectation?
(5) Permit countdown color thresholds (14-day red, 30-day orange) — right urgency levels?
(6) User card layout with side-panel role matrix vs. the original table approach.
(7) Document Generator wizard flow — is 4 steps the right granularity, or should steps be combined?