Journee is a lead marketplace. A bid opens a conversation; it does not award a contract, select a vendor, collect payment, or close the job. The customer and vendor decide how to work together outside those assumptions while Journee tracks listing, completion, and reciprocal-review state.
Send interest in an open job
A signed-in party with completed onboarding can bid on another party's open, unexpired job. On the job page, Send interest asks for:
an optional amount and pricing unit, which must be supplied together;
a required opening message explaining how the vendor can help.
The job's country determines the displayed currency; the bidder does not select another currency. Pricing units come from the current Journee catalog, so use the choices shown by the form. An initial bid cannot include an attachment.
Submitting a first bid creates the bid and its chat conversation together. If either part cannot be created, neither should appear as successfully sent. A current submitted bid can use Update Bid to change its pricing. Its original message remains the opening conversation message. Use chat for later details or documents after the customer replies.
Withdraw ends a still-submitted vendor bid and deactivates its conversation. It is not the same as temporarily hiding the bid, and Journee does not present a restore action to the vendor.
A signed-out visitor can save a private, expiring bid draft in the same browser. After sign-up or sign-in and onboarding, the recovered page still requires an explicit Send action. Recovery never submits the bid automatically, and an expired or wrong-browser draft must be started again.
Review incoming bids as the customer
The owner sees a Bids section only when incoming bids exist. Each row can show the vendor profile, submitted time, pricing, an opening-message preview, and the actions currently valid for that bid. Use Older bids to continue through a long history; Journee keeps the server's ordering rather than sorting only the visible page.
For an active submitted bid, the customer can Message the vendor or Reject the bid. Reject is a private workbench disposition: it moves that bid behind active interest and removes actions that require an active disposition, but it does not invent a new vendor bid status or select another vendor. While the job is still open, Restore returns it to active consideration.
The customer's first qualifying text reply in the bid conversation marks that conversation as engaged. Engagement is still required before a vendor can request completion or share the service address. It is not required for the customer's later completed-close review choice: work may have been coordinated off Journee.
Complete or close a job
An engaged vendor sees Request completion only while all required state is current: the job is open and unexpired, the submitted bid and conversation are active, the customer has not rejected it, no request is already pending, and any retry wait has ended. The completion task includes a required star rating and an optional private review of the customer.
A pending completion request does not close or unlist the job. Until the current response window ends, the vendor may Withdraw completion request and the customer may Confirm or Decline:
Withdraw or Decline leaves the job open, voids the provisional vendor review, and can require a wait before another request.
Expiry of the response window likewise ends the request without declaring the job complete.
Confirm closes the job as completed, activates the vendor's held review, and starts the reciprocal-review cycle.
Confirmation also ends marketplace bidding, resolves competing pending completion requests, makes the job conversations read-only, and retains eligible job pictures with the completed record. Those changes are atomic; a successful confirmation cannot leave the listing open with only part of the workflow updated.
The customer can instead choose Close Job on any owned open, unexpired job and record Completed or Not completed. This action does not choose or award a vendor. Either outcome ends the listing, stops outstanding bids, and makes its conversations read-only. Completed makes the customer's job eligible for the completed Archive and schedules a separate review follow-up. Not completed does not create completed-work or review eligibility.
From the completed follow-up, the customer chooses an otherwise eligible active bidder and submits a review. An on-app customer reply is not required, but a withdrawn or privately rejected bid is not eligible. Journee orders the available choices using bounded conversation activity and stable tie-breaking; the order does not mean Journee selected or endorsed a vendor. Listing expiry is different from customer closure: it removes the job from the marketplace but never asserts completion or starts reviews. The current policy controls response, retry, reminder, and reciprocal-review timing; trust the dates and controls shown in Journee rather than a fixed number in this guide.
Understand reciprocal reviews
Every review task uses a one-to-five-star rating and optional written review. The first submitted direction is held privately. The other participant cannot read its rating or text while deciding what to submit.
When the counterpart submits a review, both directions publish together. If No thanks appears, the invited participant may decline to add a review and allow the already-held counterpart review to publish. If nobody takes the remaining action before the displayed deadline, Journee reveals the held review or reviews when that deadline is processed.
Only published reviews contribute to the public profile rating and review history. A customer sees their completed jobs in Archive. A vendor gains Archive access to completed work only through a qualifying customer-to-vendor review record; that private archive eligibility does not make held review text public.
Recover when an action is unavailable
Controls disappear as state changes. Reopen the canonical job page when a bid, completion, close, or review action says it is no longer available. Confirm the job is still open when bidding, that the same party owns the bid or job, and that the current conversation and deadline still qualify.
Do not repeat a high-consequence action only because the browser response was interrupted. First inspect the job, Dashboard Bids or Archive tab, chat, and notifications for the resulting state. If the first submission actually succeeded, the refreshed page will replace the form with the next valid action or remove it entirely.