DELIVER WORK / 3 MINUTES
Agree on what done means
A promise becomes a plan only after everyone knows the promise.
Your little win: Create a delivery plan from the agreed scope rather than assumptions in the posting.
01 / SEE HOW IT FITS
The big picture, in little steps.
Bring the reference material
Prepare delivery shows the original posting and saved submitted proposal. Compare both with what the customer actually agreed.
02 / YOUR TURN
Have a little go.
This is your practice table. Everything stays here—no account, real AI calls, or changes to Seerist.
Setting out the pencils…
03 / DO IT IN SEERIST
Ready for the real thing?
Before you start: A proposal recorded as Won and access to start delivery.
- 1
Bring the reference material
Prepare delivery shows the original posting and saved submitted proposal. Compare both with what the customer actually agreed.
- 2
Confirm the actual brief
Enter agreed scope, acceptance criteria, a QA owner and optional deadline. Include assumptions, exclusions and milestones. Explicit copying into the brief does not confirm agreement.
- 3
Respect the accepted scope
Where a manual Upwork accepted scope exists, Delivery uses its exact immutable version read-only. Resolve a scope conflict by reloading and reviewing rather than substituting newer text.
- 4
Create the plan
Confirm brief & create plan starts from the reviewed agreement. Choose the client-required stack when one exists; otherwise the displayed default applies.
A little thing to rememberA job posting, a proposal and an agreed brief are three different things. Seerist’s record is not external proof of a contract.
Opens the real app in a new tab. Sign in and check the selected workspace before acting.
Take a little note with you.
About this lesson
Checked September 13, 2026 against app source a365066. Based on web/src/pages/DeliveryPage.tsx; docs/source-independent-workflow.md. This is a source-based guide, not a claim that every provider action was live-tested.