# PRI-001 — Planning Experience Full Revamp (Budget-First Wedding Planning)

Act as Senior Product Manager, Senior UX Designer, Senior Product Designer, Senior Wedding Planning Consultant, Senior PHP Engineer, and Senior Backend Architect.

====================================================
IMPORTANT
====================================================

This is NOT a feature release.

This is NOT a bug fix.

This is a COMPLETE PRODUCT EXPERIENCE REVAMP.

The objective is to redesign the entire Planning experience.

====================================================
DO NOT TOUCH
====================================================

KEEP the existing database.

KEEP all calculations.

KEEP budget_settings.

KEEP budget_categories.

KEEP budget_expenses.

KEEP budget_payments.

KEEP vendors.

KEEP timeline_tasks.

KEEP actual_cost.

KEEP estimated_cost.

KEEP payment calculations.

KEEP variance calculations.

KEEP all backend business logic.

DO NOT redesign database architecture.

DO NOT redesign business logic.

This is a USER EXPERIENCE redesign.

====================================================
PRODUCT PHILOSOPHY
====================================================

The current Planning module feels like accounting software.

That is NOT our product.

Our users are wedding couples.

Wedding couples do NOT think like accountants.

Wedding couples think like this:

"I have 150 million."

↓

"I want to spend 40 million on Venue."

↓

"I found Grand Empire."

↓

"The deal is 38 million."

↓

"I already paid 20 million."

↓

"I still owe 18 million."

↓

"Done."

That is the entire mental model.

====================================================
NEW PLANNING STRUCTURE
====================================================

Planning

├── Budget Planner
├── Timeline Planner
└── Wedding Insights

Vendor is NOT a standalone planning module.

Vendor becomes a supporting object inside Budget Planner.

====================================================
REMOVE
====================================================

Remove or hide from the UI:

Expense terminology

Expense Description

Expense Status

Expense Dashboard

Expense List

Expense Table

Expense Manager

Vendor Manager

Vendor Dashboard

Vendor CRM

Quotation Comparison

Communication Log

Meeting Log

Contract Management

Package Comparison

Category Manager page

Category CRUD page

Accounting wording

Technical finance wording

Anything that makes the product feel like ERP software.

====================================================
KEEP
====================================================

Internally,

Estimated Cost

Actual Cost

Payments

Status

Variance

remain exactly as implemented.

Only rename them in the UI.

====================================================
NEW WORDING
====================================================

Estimated Cost

↓

Planned Budget

----------------------------

Actual Cost

↓

Deal Price

----------------------------

Expense

↓

Wedding Item

or simply

Budget Item

----------------------------

Payments

↓

Installments

or

Payments

----------------------------

Variance

↓

Difference

====================================================
NEW USER FLOW
====================================================

Step 1

Set Total Wedding Budget

↓

Step 2

Review default wedding categories

↓

Step 3

Allocate Budget for each category

↓

Step 4

Assign Vendor

↓

Step 5

Enter Deal Price

↓

Step 6

Record Payments

↓

Finished.

====================================================
BUDGET PLANNER
====================================================

The Budget Planner homepage becomes the financial command center.

Display each category as cards.

Example

Venue

Budget

40.000.000

Deal

38.000.000

Paid

20.000.000

Remaining

18.000.000

Difference

+2.000.000

----------------------------

Photography

Budget

15.000.000

Deal

17.000.000

Paid

5.000.000

Remaining

12.000.000

Difference

-2.000.000

At the bottom

display

Wedding Budget

Total Budget

Total Deal

Total Paid

Remaining Balance

Overall Difference

No accounting tables.

No ledger feeling.

====================================================
CATEGORY DETAIL
====================================================

Clicking a category opens

Budget Detail.

Display

Category

Vendor

PIC

Phone / WhatsApp

Budget

Deal Price

Paid

Remaining

Next Payment

Payment History

Notes

Nothing else.

====================================================
PAYMENT HISTORY
====================================================

Simple timeline.

Example

1 May

DP

5.000.000

----------------

15 June

Progress Payment

5.000.000

----------------

20 August

Final Payment

8.000.000

====================================================
VENDOR
====================================================

Vendor is only supporting Budget.

Vendor stores only:

Vendor Name

PIC

Phone / WhatsApp

Deal Price

Paid

Remaining

Next Payment

Notes

Vendor pages should feel like a detail card,

NOT a CRM workspace.

====================================================
TIMELINE
====================================================

Timeline becomes a Wedding Planner.

NOT a Task Manager.

Display activities such as

Meet Photographer

Venue Survey

Food Tasting

Invitation Distribution

Final Meeting

Pay Decoration

If a timeline item requires payment,

provide a shortcut

"Open Budget Item"

Do NOT embed financial forms inside Timeline.

====================================================
WEDDING INSIGHTS
====================================================

Wedding Insights remains read-only.

No editing.

No financial forms.

No planning forms.

====================================================
DESIGN LANGUAGE
====================================================

Use cards.

Progress bars.

Status chips.

Timeline components.

Soft spacing.

Simple typography.

Avoid tables whenever possible.

Avoid ERP layouts.

Avoid accounting layouts.

The experience should feel modern,

friendly,

premium,

and simple.

====================================================
SUCCESS CRITERIA
====================================================

A first-time wedding couple should understand the Planning module without explanation.

The user should never feel they are using accounting software.

The user should feel they are planning their wedding.

====================================================
DELIVERABLES
====================================================

Provide

1. Complete Planning UX redesign

2. Updated navigation

3. Updated Budget Planner

4. Updated Vendor experience

5. Updated Timeline experience

6. Updated page hierarchy

7. Components removed

8. Components simplified

9. Backend components reused

10. Browser screenshots

11. PHP syntax validation

12. Responsive verification

====================================================
IMPORTANT
====================================================

Prioritize SIMPLICITY over FEATURES.

Reduce clicks.

Reduce forms.

Reduce terminology.

Reduce complexity.

Do NOT add new functionality.

Do NOT add new database tables.

Do NOT expand the product scope.

The goal is to transform Planning into a beautiful Wedding Planning experience while reusing the powerful backend that already exists.