Unify request intake workflow and replace Estimate/Contract split with Project Request → Proposal → Project Agreement#61
Merged
Conversation
Copilot created this pull request from a session on behalf of
iaretechnician
May 31, 2026 14:19
View session
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR consolidates the dashboard and intake pipeline around one customer-facing flow: Project Request → Proposal → Project Agreement → Payment/Approval → Work. It removes overlapping request concepts, standardizes IDs as
Request ID, and makes proposal/agreement generation editable, linked, and role-visible.Workflow + terminology unification
Request IDacross request, proposal, and agreement flows.estimate_idrecords continue to load/display as request IDs.Data model + persistence
data/project_requests.jsondata/proposals.jsondata/project_agreements.jsonestimate_requests.jsonreadable during transition.Public intake + messaging updates
estimate.phpinto a Project Request entry point (same route, updated language and fields).Request IDand the new process expectations.proposals.php,contracts.php(Project Agreements messaging), andpayments.phpto concise, professional workflow-aligned content.Staff workflow implementation
staff/estimate-requests.php) as the unified Project Requests module with:staff/create-proposal.php?request_id=...staff/create-agreement.php?proposal_id=...(and request-based fallback)Client dashboard/view alignment
client/request.phpclient/proposal.phpclient/agreement.phpRouting + legacy surface cleanup