Fictional project record
Harbor Street Bakery at a glance
- People
- Sam, owner and approver, works with Jordan Lee of Jordan Lee Studio.
- Original scope
- Five responsive pages, a catering form, analytics handoff, editor access, and an update guide.
- Approved change
- HSB-WEB-01-CR02 adds Wedding Catering and Corporate Catering pages and moves launch to December 2, 2026.
- Price
- $5,600 original fee plus $1,200 approved change, for $6,800 total.
| Date | Trigger | Amount | Status |
|---|---|---|---|
| October 15, 2026 | Base milestone 1 — kickoff and structure | $1,400 | Paid |
| October 24, 2026 | Base milestone 2 — design direction approved | $1,400 | Paid |
| November 7, 2026 | Change milestone 1 — CR02 approved | $600 | Paid |
| November 18, 2026 | Base milestone 3 — staging accepted | $1,400 | Paid |
| December 5, 2026 | Base handover ($1,400) plus accepted CR02 work ($600) | $2,000 | Paid December 12 |
| Project total | $6,800 | Paid in full | |
You can read the entire walkthrough without using Lucy. Tool links open the existing blank tool for that project stage; no example or user information is transmitted merely by following a link. If you choose to submit text, remove names, credentials, account details, and unnecessary confidential information first. Read how requests are handled.
01
Sam identifies a business need
The project starts with a problem customers and staff can observe, not a feature list or a promised business result.
Fictional timeline · October 1, 2026
Harbor Street Bakery’s one-page site makes product and catering information difficult to find on a phone. Customers call for answers, and Sam wants a clearer inquiry path before the holiday catering campaign.
Sam describes the need and known inputs, then asks Jordan whether the work appears aligned. The inquiry leaves page count and form details open for discovery.
Freelancer perspective
What Jordan is working through
- Decide whether the broad need fits your service, capacity, and ethical boundaries.
- Avoid confirming a price, schedule, or solution before the dependencies are understood.
Client perspective
What Sam is working through
- Explain what is difficult now, who is affected, and why the timing matters.
- Share known constraints while leaving room for the freelancer to ask questions.
Initial client inquiryOctober 1, 2026Sam describes the business need without pretending the scope is already final.Open fictional document
Fictional educational example — not a user document
Subject: Harbor Street Bakery website inquiry Hi Jordan, I own Harbor Street Bakery. Our current one-page website is difficult to use on a phone, and customers often call for product and catering information. We would like a small website with clearer pages and a catering inquiry form. We hope to launch before our early holiday catering campaign. I can provide our copy, logo, product photos, prices, and domain access. I am still working out the exact page list and what the form should collect. Are you available to discuss whether this fits your work? Thanks, Sam
02
Sam turns the need into a bounded brief
A useful brief gives candidates the same starting facts without pretending every technical decision is settled.
Fictional timeline · October 3, 2026
Sam records five expected pages, the catering form, supplied assets, a $6,000 planning ceiling, the target date, exclusions, and Sam’s role as final approver.
The brief labels open hosting and content-system questions instead of hiding uncertainty.
Freelancer perspective
What Jordan is working through
- Use the brief to identify assumptions, missing dependencies, and work that may need a specialist.
- Do not treat the client’s planning ceiling as proof of the correct project price.
Client perspective
What Sam is working through
- Name tangible outputs, important exclusions, supplied inputs, and the person who can approve.
- Keep passwords, customer data, and account details out of the brief.
Client project briefOctober 3, 2026The first shared record defines the five-page request, responsibilities, exclusions, and open questions.Open fictional document
Fictional educational example — not a user document
# Client Project Brief — Harbor Street Bakery Fictional educational example · prepared October 3, 2026 ## Organization and context Harbor Street Bakery is a fictional neighborhood bakery with one location and a growing catering service. Sam, the owner, is the final project approver. ## Business problem Customers repeatedly call because the current one-page site does not make products, catering details, or the inquiry process easy to find on a phone. ## Audience and desired outcome Local customers planning everyday purchases, celebrations, and small catered events should be able to understand the bakery’s offer, find practical information, and send the details needed for a catering follow-up. The site cannot guarantee inquiries or sales. ## Deliverables Five responsive pages: Home, Products, Catering, About, and Contact; a catering inquiry form; basic analytics handoff; bakery-owned editor access; and a short update guide. ## Exclusions Ecommerce, online payments, copywriting, photography, ongoing website administration, and guaranteed lead volume. ## Budget and timing Planning ceiling: $6,000 USD including approved expenses and contingency. Target launch: November 21, 2026, subject to content, access, review, and testing dependencies being confirmed. This is a fictional planning figure, not a market benchmark. ## Supplied assets, responsibilities, and approval Sam supplies approved copy, prices, logo files, photographs, and domain access through an approved secure method. No credentials are included here. Sam consolidates stakeholder feedback and returns one response per review round. ## Acceptance indicators Approved pages and copy are present; navigation works; the form validates, reaches the designated inbox, and confirms submission; agreed device, browser, keyboard, and accessibility checks pass; access and documentation are handed over. ## Open questions Which content system and hosting approach fit staff capacity? What ongoing costs or licenses should the bakery expect? How will post-launch corrections be separated from new work?
03
Jordan evaluates fit before promising
The freelancer’s first decision is whether to continue the conversation, not how quickly to close the work.
Fictional timeline · October 6, 2026
Jordan checks service fit, availability, the likely skills involved, Sam’s decision authority, and risks around content, access, ecommerce assumptions, and the holiday date.
The project appears potentially suitable, but discovery must confirm the actual pages, form behavior, handover, and review process.
Freelancer perspective
What Jordan is working through
- Identify what would make the project unsuitable or require a referral, partner, or different schedule.
- Respond with focused next steps rather than a premature fixed quote.
Client perspective
What Sam is working through
- Expect relevant questions. They are part of responsible evaluation, not evidence that the freelancer is difficult.
- Use the response to assess whether the freelancer recognizes constraints and uncertainty.
Freelancer inquiry evaluationOctober 6, 2026Jordan checks fit and risks before promising a price or date.Open fictional document
Fictional educational example — not a user document
# Inquiry evaluation — Jordan Lee Studio Fictional internal note · October 6, 2026 ## Likely fit A bounded informational website and form fit Jordan’s web development service. Sam appears able to act as decision-maker and supply content. ## Information still needed Page count, content readiness, form fields/routing, hosting and content-system constraints, accessibility expectations, review availability, launch reason, budget range, source-file and handover expectations. ## Risks to test in discovery The holiday date may depend on content and access. ‘Catering website’ could expand into ecommerce or payment collection. Photography and copywriting may be assumed unless excluded. ## Response Acknowledge the inquiry, say the project appears potentially aligned, and propose a 30-minute discovery call. Do not confirm a price or launch date yet.
04
Both sides test the assumptions
Discovery turns an attractive idea into information that can support scope, price, timing, and responsibilities.
Fictional timeline · October 8, 2026
Sam and Jordan clarify the audience, five initial pages, form purpose, content readiness, access, approval, accessibility checks, handover, and excluded ecommerce/payment work.
Campaign landing pages are explicitly outside the first release. That detail later makes the change discussion concrete.
Freelancer perspective
What Jordan is working through
- Ask about the business process around the deliverable, not only visual preferences.
- Record assumptions and open items so the proposal does not silently fill gaps.
Client perspective
What Sam is working through
- Bring the person who can decide and say honestly which inputs are not ready.
- Confirm how staff will operate the result after handover.
Discovery agenda and notesOctober 8, 2026The call resolves key assumptions and leaves specific open items for the proposal.Open fictional document
Fictional educational example — not a user document
# Discovery agenda and notes — HSB-WEB-01 Fictional educational example · October 8, 2026 ## Business and audience The bakery needs customers to find current product context, practical visit information, and the information required for a catering follow-up. Sam will answer inquiries; the site will not quote or accept payment. ## Confirmed first-release pages Home, Products, Catering, About, and Contact. The Catering page explains the service and contains an inquiry form. Campaign-specific landing pages are not part of the first release. ## Inputs and decisions Sam supplies approved copy, logo, photographs, prices, inbox routing, domain access, and one consolidated response per round. Jordan recommends the content/hosting approach and documents ongoing costs. ## Acceptance signals Approved content, working navigation, successful form validation/routing/confirmation, agreed responsive/browser/keyboard/accessibility checks, and complete handover. ## Constraints and open items No ecommerce, payment collection, copywriting, photography, or ongoing administration. Final hosting choice and third-party license list will be confirmed in the proposal/SOW.
05
Jordan proposes one testable approach
The proposal connects Sam’s need to a defined approach rather than presenting a price without boundaries.
Fictional timeline · October 10, 2026
Jordan proposes the five-page site, form, handover, four $1,400 base milestones, November 21 target, client responsibilities, included revision rounds, and explicit exclusions.
The proposal states that timing depends on agreement approval, inputs, and review dates.
Freelancer perspective
What Jordan is working through
- Tie the fee to the described work and surface assumptions that could change it.
- Explain what creates an agreement and what must move into the SOW.
Client perspective
What Sam is working through
- Compare the proposal against the brief and discovery notes, not only the total.
- Look for missing outputs, expenses, dependencies, acceptance, and close-out.
Freelance proposalOctober 10, 2026Jordan connects the stated need to an approach, boundaries, price, and next step.Open fictional document
Fictional educational example — not a user document
# Proposal — Harbor Street Bakery website Fictional educational example · sent October 10, 2026 Jordan Lee Studio proposes a responsive five-page website and catering inquiry form based on the October 8 discovery record. The approach includes content structure, key-page design, build, agreed checks, launch, basic analytics handoff, bakery-owned editor access, and a short update guide. ## Price and stages $5,600 USD fixed fee in four $1,400 milestones: kickoff/structure, design approval, staging acceptance, and final launch/handover. Approved third-party expenses are separate. ## Timing Target launch November 21, 2026, provided the agreement is approved October 15 and Sam supplies recorded inputs and consolidated feedback by the agreed dates. ## Boundaries Ecommerce, online payments, copywriting, photography, ongoing administration, and new pages are excluded. One consolidated design round and one staging correction round are included. Material changes require a written decision before changed work begins. ## Next step Resolve the listed questions, then carry the accepted decisions into the SOW and controlling agreement. This proposal is a fictional example, not a universal agreement.
06
Sam asks about the terms that affect use
A useful proposal review turns broad phrases into shared decisions before they harden into an agreement.
Fictional timeline · October 13, 2026
Sam asks who owns hosting accounts, what one revision round means, which accessibility checks are included, and what support follows launch.
Jordan answers specifically and agrees to carry the clarifications into the SOW.
Freelancer perspective
What Jordan is working through
- Answer the actual question and revise ambiguous wording instead of relying on reassurance.
- Do not dismiss operational, accessibility, rights, or security questions as boilerplate.
Client perspective
What Sam is working through
- Ask how an important promise will be observed or recorded.
- Distinguish required project decisions from optional enhancements.
Proposal clarification recordOctober 13, 2026Sam’s questions turn ambiguous phrases into decisions that can enter the SOW.Open fictional document
Fictional educational example — not a user document
# Proposal questions and clarifications Fictional educational example · October 13, 2026 Sam: Who owns the hosting and site accounts? Jordan: The bakery will own the primary accounts. Jordan receives only the access needed for the project. Sam: What does one revision round mean? Jordan: One consolidated response to the presented design direction. Corrections needed to meet agreed criteria are not counted as new creative direction. Sam: What accessibility work is included? Jordan: The recorded content, keyboard, focus, form-label/error, heading, alternative-text, contrast, and agreed browser/device checks. This is not a certification or guarantee of universal compliance. Sam: What happens after launch? Jordan: The update guide, access handover, and a bounded correction window are included. Ongoing administration or new features need a separate agreement. Decision: These clarifications will be reflected in the SOW before approval.
07
Both sides make the boundary visible
Scope is easier to manage when deliverables, exclusions, responsibilities, and shared decisions appear in the same record.
Fictional timeline · October 15, 2026
The scope matrix names the five pages and handover items, excludes ecommerce and campaign pages, and assigns inputs, feedback, testing, and approval responsibilities.
It also distinguishes Jordan’s work from decisions both sides must approve together.
Freelancer perspective
What Jordan is working through
- Check that the scope matches the work you estimated and can actually deliver.
- Name third-party and client dependencies rather than absorbing them into an optimistic schedule.
Client perspective
What Sam is working through
- Confirm that the described outputs match the business need and available internal work.
- Do not assume adjacent features are included because they seem related.
Scope and responsibility matrixOctober 15, 2026Included work, exclusions, and each party’s responsibilities appear together.Open fictional document
Fictional educational example — not a user document
# Scope and responsibility matrix — HSB-WEB-01 Fictional educational example · October 15, 2026 Included: five named pages; catering form; responsive implementation; recorded accessibility/browser checks; analytics handoff; editor access; update guide; source assets and license list stated in the SOW. Excluded: ecommerce; online payments; copywriting; photography; ongoing administration; campaign landing pages; guaranteed inquiries or sales. Jordan owns: recommendation, design, build, testing, risk/status reporting, delivery, and documented handover. Sam owns: approved copy/assets, secure access, inbox/form decisions, timely consolidated feedback, acceptance, bakery-owned accounts, and payment under the agreement. Shared decisions: material scope changes, schedule changes, third-party expenses, acceptance exceptions, and close-out record.
08
They connect money to observable project events
A milestone is useful when both sides can tell what event triggers review and payment.
Fictional timeline · October 15, 2026
The SOW records four $1,400 base milestones: kickoff/structure, design approval, staging acceptance, and final handover. It also names review expectations, acceptance checks, change handling, rights/security prompts, and close-out.
The original fixed fee is $5,600 USD. The later change is not part of this starting amount.
Freelancer perspective
What Jordan is working through
- Make cash-flow and work-start assumptions explicit.
- Use observable outcomes rather than vague percentages or calendar dates alone.
Client perspective
What Sam is working through
- Reserve time to review each milestone and understand when payment is triggered.
- Check that the milestone evidence is proportional to the payment decision.
Statement of Work and milestone scheduleOctober 15, 2026The approved project record connects scope, acceptance, four base milestones, changes, rights, and close-out.Open fictional document
Fictional educational example — not a user document
# Statement of Work — Harbor Street Bakery Website Fictional educational example · HSB-WEB-01 · approved October 15, 2026 ## Parties and objective Harbor Street Bakery (client), represented by Sam, and Jordan Lee Studio (independent freelancer). The project will make product and catering information easier to find and provide a usable catering inquiry path. No inquiry or sales volume is guaranteed. ## Original scope and exclusions Included: Home, Products, Catering, About, and Contact pages; catering form; basic analytics handoff; editor access; update guide; agreed source assets and license list. Excluded: ecommerce, online payments, copywriting, photography, and ongoing administration. ## Responsibilities and dependencies Jordan designs, builds, tests, reports risks, and completes handover. Sam supplies approved content, brand assets, secure access, decisions, and one consolidated response per review. Dates depend on inputs and approvals arriving as recorded. ## Base milestones and payments 1. October 15 — kickoff and structure confirmed; $1,400 due. 2. October 24 — key-page design approved after one consolidated round; $1,400 due. 3. November 18 — staging build passes the agreed checks; $1,400 due. 4. November 21 target — launch and handover completed; $1,400 final base milestone due under the agreed payment term. Base fixed fee: $5,600 USD. Hosting or licensed assets require written preapproval. Tax treatment follows applicable requirements and is not invented here. ## Acceptance and revisions Approved content is present; navigation and links work; the form validates, reaches the designated inbox, and confirms submission; agreed mobile, desktop, browser, keyboard, and accessibility checks pass; handover items are supplied. One consolidated design round and one staging correction round are included within the accepted scope. ## Changes New pages, ecommerce, a new design direction, or other changed requirements need a written scope, price, schedule, dependency, acceptance, and approval decision before changed work begins. ## Rights, security, and close-out prompts The controlling agreement distinguishes project-specific work, Jordan’s reusable components, and third-party assets; identifies transfer or license triggers; and requests portfolio permission separately. Access is shared securely, limited to the work, and removed or reduced after verified handover. The controlling agreement governs pause, termination, payment, disputes, and applicable law.
09
Approval identifies the controlling record
A clear approval says who accepted what, through which method, and what must happen before work starts.
Fictional timeline · October 15, 2026
Sam and Jordan identify the SOW, controlling agreement, and clarification record. They confirm authority and the first milestone trigger.
They also preserve the rule that material changes need a recorded decision rather than an informal suggestion.
Freelancer perspective
What Jordan is working through
- Confirm the approved version and required payment or access conditions before beginning.
- Preserve the record in the agreed project channel.
Client perspective
What Sam is working through
- Verify the final documents match the last conversation and that the approver has authority.
- Do not rely on silence or an outdated proposal version.
Agreement approval recordOctober 15, 2026Both parties identify the approved documents, authority, and work-start trigger.Open fictional document
Fictional educational example — not a user document
# Project approval record — HSB-WEB-01 Fictional educational example · October 15, 2026 Sam and Jordan confirm that the October 15 SOW, the identified controlling agreement, and the recorded clarifications form the working project record. Sam is authorized to approve for Harbor Street Bakery. Jordan is authorized to approve for Jordan Lee Studio. The first $1,400 milestone is triggered at kickoff under the approved terms. Work begins after the required approval and payment conditions are met. Future material changes use the written change process; an informal suggestion does not alter the scope by itself.
10
Jordan starts with a shared operating record
Kickoff is where the written project becomes a working routine for decisions, inputs, status, and access.
Fictional timeline · October 15–17, 2026
Jordan records the communication channel, weekly status day, approval authority, decision-log rule, and next review. Sam supplies content and access securely by October 17.
No credential is copied into the project documents.
Freelancer perspective
What Jordan is working through
- Confirm received inputs, access boundaries, next decision, and known blockers.
- Use written recaps so later work is not reconstructed from memory.
Client perspective
What Sam is working through
- Provide only the access needed and use organization-owned accounts where practical.
- Verify that the freelancer received usable, approved material.
Kickoff recap and decision logOctober 15–17, 2026The project channel, approver, inputs, next decision, and secure-access rule are recorded.Open fictional document
Fictional educational example — not a user document
# Kickoff recap and decision log Fictional educational example · October 15–17, 2026 Project channel: the recorded project email/thread. Weekly status: Tuesday. Sam is the sole final approver and consolidates bakery feedback. Decisions that affect scope, price, schedule, acceptance, access, or rights are summarized in writing. Received October 17: approved five-page copy, logo files, selected photos, product/practical information, form recipient, and secure access through the bakery’s approved method. No password or recovery code appears in the project record. Next approval: key-page design direction by October 24. Known dependency: delayed or materially changed content can move build/review dates.
11
Sam supplies decisions; Jordan reports progress
Delivery depends on both sides completing the responsibilities attached to the work.
Fictional timeline · October 17–November 4, 2026
Sam supplies approved materials and gives one consolidated design response. The key-page design is approved October 24, triggering the second $1,400 base milestone.
Jordan’s November 4 update separates completed work, current work, decisions, and a possible request for two landing pages.
Freelancer perspective
What Jordan is working through
- Report progress and emerging risks before the schedule is in danger.
- Record a possible new request as unapproved until the baseline comparison is complete.
Client perspective
What Sam is working through
- Consolidate stakeholder feedback and answer the requested decision, not every possible preference.
- Acknowledge how late or changed inputs affect dependent work.
Project status updateNovember 4, 2026Progress, current work, and the first mention of possible added pages are separated clearly.Open fictional document
Fictional educational example — not a user document
# Project status update — HSB-WEB-01 Fictional educational example · November 4, 2026 Completed: approved design direction, five-page structure, shared navigation, initial responsive build, and first form path. In progress: content entry, form validation/confirmation, agreed browser and keyboard checks, analytics setup, and handover documentation. Decisions needed: none for the original scope. Sam mentioned that separate wedding and corporate catering pages may be useful. Jordan recorded this as a possible change, not approved work, and asked for the intended audience, copy readiness, timing, and priority. Current target: November 21, subject to the original record unless a written change is approved.
12
Sam asks for two additional landing pages
The request is reasonable to discuss, but it is not automatically included merely because it supports the same website.
Fictional timeline · November 6, 2026
Sam asks for separate Wedding Catering and Corporate Catering pages after the original design direction is approved. Jordan compares the request with the five named pages and the explicit campaign-page exclusion.
They discuss the audience, supplied copy, navigation, testing, price, timing, and whether anything should be removed or deferred.
Freelancer perspective
What Jordan is working through
- Do not begin the added work while the impact is still being negotiated.
- Distinguish a requested addition from a correction needed to meet the existing agreement.
Client perspective
What Sam is working through
- Explain the new need and priority rather than assuming the existing fee covers it.
- Consider adding, swapping, deferring, or declining work based on budget and timing.
Project status updateNovember 4, 2026Progress, current work, and the first mention of possible added pages are separated clearly.Open fictional document
Fictional educational example — not a user document
# Project status update — HSB-WEB-01 Fictional educational example · November 4, 2026 Completed: approved design direction, five-page structure, shared navigation, initial responsive build, and first form path. In progress: content entry, form validation/confirmation, agreed browser and keyboard checks, analytics setup, and handover documentation. Decisions needed: none for the original scope. Sam mentioned that separate wedding and corporate catering pages may be useful. Jordan recorded this as a possible change, not approved work, and asked for the intended audience, copy readiness, timing, and priority. Current target: November 21, subject to the original record unless a written change is approved.
13
CR02 changes price, schedule, inputs, and acceptance
A useful change record explains more than the added fee: it shows what work, dates, responsibilities, and checks move.
Fictional timeline · November 7–8, 2026
Sam and Jordan approve two added pages for $1,200: $600 on change approval and $600 after acceptance. The launch moves from November 21 to December 2.
Sam supplies copy and images by November 8; feedback remains due within three business days. The original SOW continues except where CR02 changes it.
Freelancer perspective
What Jordan is working through
- Check authorization and the first change-payment trigger before beginning.
- Update the working plan and final invoice logic, not only the scope list.
Client perspective
What Sam is working through
- Confirm the budget and schedule effect before approval.
- Meet the new input deadline so the revised launch remains realistic.
Approved change request and revised scheduleNovember 7, 2026CR02 adds two pages, $1,200, content dependencies, acceptance checks, and a December 2 launch.Open fictional document
Fictional educational example — not a user document
# Project Change Request — HSB-WEB-01-CR02 Fictional educational example · approved November 7, 2026 ## Original scope reference Harbor Street Bakery website, SOW HSB-WEB-01. The original scope contains five responsive pages; campaign landing pages are excluded. ## Requested and approved change Add Wedding Catering and Corporate Catering responsive landing pages using the approved visual system. Added work includes two layouts, build, supplied-content entry, navigation links, and agreed checks. No original work is removed or exchanged. ## Reason The bakery decided to give two catering audiences separate entry points after the original site structure and design direction were approved. ## Price and payment impact Additional fixed fee: $1,200 USD. $600 is triggered by written change approval; $600 is included in the final invoice after the two pages pass their acceptance checks. These are fictional figures. ## Schedule impact The target launch moves from November 21 to December 2, 2026, provided Sam supplies approved copy and images by November 8 and consolidated feedback within three business days. ## Responsibilities and acceptance Sam supplies approved copy and images. Jordan confirms whether existing licensed assets cover the added use. Both pages must use approved content, link from the agreed navigation, pass the project’s mobile, desktop, keyboard, browser, and accessibility checks, and route inquiry links correctly. ## Decision Sam and Jordan approve CR02 through the agreement’s recorded approval method on November 7. Added work begins after approval and the first $600 payment trigger. All unchanged SOW terms continue.
14
Jordan delivers the seven-page project
A delivery message should make the review task clear instead of simply announcing that the work is done.
Fictional timeline · December 2, 2026
Jordan delivers the five original pages, two CR02 pages, form, analytics handoff, editor access, source assets, license list, update guide, and backup record.
The delivery note restates the agreed checks and asks for one consolidated response.
Freelancer perspective
What Jordan is working through
- Enumerate every output and where it can be reviewed or retrieved.
- Distinguish final delivery from an informal preview and preserve submission evidence.
Client perspective
What Sam is working through
- Review against the original SOW plus CR02, not memory or unrelated new preferences.
- Use the agreed environment and report issues specifically.
Delivery note and acceptance checklistDecember 2, 2026Jordan identifies all seven pages, handover items, and the checks Sam should perform.Open fictional document
Fictional educational example — not a user document
# Delivery note and acceptance checklist Fictional educational example · delivered December 2, 2026 Delivered: seven live pages (the five original pages plus Wedding Catering and Corporate Catering), catering inquiry form, analytics handoff, editor access, source assets, license list, update guide, and launch backup record. Acceptance checks: approved content; navigation and inquiry links; form required fields, routing, and confirmation; agreed mobile/desktop/browser behavior; keyboard flow and visible focus; headings, labels, and alternative text; documented accounts, dependencies, and handover items. Review window: Sam will return one consolidated response. A failure against an agreed check is a correction. A new idea or changed direction is recorded separately.
15
One defect is corrected; one new idea is parked
A precise review separates a failure against agreed criteria from a new feature request.
Fictional timeline · December 4, 2026
Sam reports that the form confirmation is not exposed correctly on an agreed mobile browser and supplies reproduction steps. Jordan confirms it is a correction and fixes it within the included round.
Sam also asks about online deposits. Both sides record that as future work because ecommerce and online payments are excluded.
Freelancer perspective
What Jordan is working through
- Acknowledge a reproducible defect and correct it without reframing it as paid scope.
- Record the separate new idea so it is not lost or confused with acceptance.
Client perspective
What Sam is working through
- State the environment, steps, actual result, and expected result.
- Do not hold accepted work open for an excluded enhancement.
Revision request and responseDecember 4, 2026One reproducible defect is corrected while a new payment idea is deferred as future scope.Open fictional document
Fictional educational example — not a user document
# Final review and correction record Fictional educational example · December 4, 2026 Sam’s report: On the agreed mobile browser, the Catering form submits but its confirmation is not visible without scrolling. Expected: the submitted state should move focus to and expose the confirmation. Steps and environment are included. Jordan’s response: Confirmed as a failure against the agreed form and keyboard checks. Jordan corrects the focus/confirmation behavior and returns it for recheck within the included staging correction round. Separate idea: Sam asks whether customers could pay deposits online. Both sides record it as future scope because ecommerce and online payments are excluded. It does not block acceptance of the current project. Result: Sam rechecks the correction and confirms it passes.
16
Sam accepts the recorded deliverables
Written acceptance identifies what passed, what was corrected, and what is not an outstanding item.
Fictional timeline · December 5, 2026
Sam confirms the seven pages, form, agreed checks, handover items, and December 4 correction. The acceptance message explicitly leaves online deposits as future scope.
The message asks Jordan for a final invoice showing prior payments and the two remaining amounts.
Freelancer perspective
What Jordan is working through
- Preserve the acceptance record and confirm the next close-out steps.
- Do not bundle portfolio or testimonial permission into project acceptance.
Client perspective
What Sam is working through
- Confirm completion in the form required by the agreement.
- List any real outstanding item; do not rely on silence to close the project.
Final acceptance messageDecember 5, 2026Sam confirms the accepted record and distinguishes future work from outstanding work.Open fictional document
Fictional educational example — not a user document
# Final acceptance message Fictional educational example · December 5, 2026 Hi Jordan, I checked the seven delivered pages, navigation, catering form routing and confirmation, the agreed responsive/browser/keyboard/accessibility items, analytics handoff, editor access, source assets, license list, update guide, and backup record. The December 4 confirmation issue is corrected. I accept the project deliverables under HSB-WEB-01 and CR02. The online-deposit idea remains future work and is not an outstanding item. Please send the final invoice showing prior payments and the remaining base and CR02 amounts. Thanks, Sam
17
Jordan reconciles the complete payment record
The final invoice makes the base fee, approved change, prior payments, and remaining balance easy to verify.
Fictional timeline · December 5, 2026
Jordan invoices $2,000: the $1,400 base handover milestone plus the remaining $600 CR02 installment. The invoice shows $4,800 already paid and a $6,800 total project value.
Payment instructions remain in the approved secure channel, not the public project document.
Freelancer perspective
What Jordan is working through
- Match line items and triggers to the SOW, change request, and acceptance record.
- Show prior payments so the client can reconcile the balance without reconstructing the project.
Client perspective
What Sam is working through
- Verify the project reference, amounts, prior payments, payee, currency, and internal routing requirements.
- Resolve an arithmetic or record question promptly rather than leaving the invoice unacknowledged.
Final invoice and payment ledgerDecember 5–12, 2026The $2,000 final invoice reconciles $4,800 already paid with the $6,800 total project value.Open fictional document
Fictional educational example — not a user document
# Invoice HSB-WEB-01-INV-04 Fictional educational example · issued December 5, 2026 From: Jordan Lee Studio To: Harbor Street Bakery Project: HSB-WEB-01 Currency: USD Current invoice - Base milestone 4 — accepted launch and handover: $1,400 - CR02 installment 2 — two added pages accepted: $600 - Amount due under the recorded payment term: $2,000 Prior project payments - October 15 — base kickoff: $1,400 - October 24 — base design approval: $1,400 - November 7 — CR02 approval installment: $600 - November 18 — base staging acceptance: $1,400 - Prior payments total: $4,800 Project reconciliation - Original fixed fee: $5,600 - Approved CR02: $1,200 - Total project value: $6,800 - Prior payments: $4,800 - This invoice: $2,000 - Balance after payment: $0 Payment instructions are supplied through the parties’ approved secure process and are not included in this public example. Payment received December 12, 2026.
18
Sam pays and both sides update the ledger
Payment completion is a recordable project event, not an assumption based on sending an invoice.
Fictional timeline · December 12, 2026
Sam processes the $2,000 invoice under the agreed term. Jordan records receipt. The ledger now shows $5,600 in base payments and $1,200 under CR02, totaling $6,800.
Neither side publishes payment credentials or sensitive account details in the educational record.
Freelancer perspective
What Jordan is working through
- Acknowledge receipt and update the project balance.
- Retain the invoice/payment record according to the business’s actual administrative requirements.
Client perspective
What Sam is working through
- Retain the approved invoice and payment evidence with the project record.
- Keep tax and vendor documentation in the organization’s appropriate secure system.
Final invoice and payment ledgerDecember 5–12, 2026The $2,000 final invoice reconciles $4,800 already paid with the $6,800 total project value.Open fictional document
Fictional educational example — not a user document
# Invoice HSB-WEB-01-INV-04 Fictional educational example · issued December 5, 2026 From: Jordan Lee Studio To: Harbor Street Bakery Project: HSB-WEB-01 Currency: USD Current invoice - Base milestone 4 — accepted launch and handover: $1,400 - CR02 installment 2 — two added pages accepted: $600 - Amount due under the recorded payment term: $2,000 Prior project payments - October 15 — base kickoff: $1,400 - October 24 — base design approval: $1,400 - November 7 — CR02 approval installment: $600 - November 18 — base staging acceptance: $1,400 - Prior payments total: $4,800 Project reconciliation - Original fixed fee: $5,600 - Approved CR02: $1,200 - Total project value: $6,800 - Prior payments: $4,800 - This invoice: $2,000 - Balance after payment: $0 Payment instructions are supplied through the parties’ approved secure process and are not included in this public example. Payment received December 12, 2026.
19
They close access, records, and future-work boundaries
A clean close protects both parties by confirming operational ownership and separating future work from the finished engagement.
Fictional timeline · December 13, 2026
Sam verifies bakery-owned accounts, documentation, files, licenses, analytics, and the backup. Jordan reduces temporary access after verification.
The correction window, future-work process, and portfolio permission are recorded separately. No testimonial or referral is assumed.
Freelancer perspective
What Jordan is working through
- Leave the client able to operate the delivered work and remove access you no longer need.
- Ask for portfolio, testimonial, and referral permission as separate choices.
Client perspective
What Sam is working through
- Verify access and recovery ownership before the freelancer leaves.
- Know which post-launch issues are included corrections and which require a new project.
Handover and follow-up recordDecember 13, 2026Access, files, payment, support boundaries, and portfolio permission close independently.Open fictional document
Fictional educational example — not a user document
# Final Delivery and Handover — Harbor Street Bakery Fictional educational example · project HSB-WEB-01 · completed December 13, 2026 ## Deliverables and acceptance - [x] Home, Products, Catering, About, Contact, Wedding Catering, and Corporate Catering pages are live at the recorded address. - [x] The catering inquiry form validates, routes to the designated inbox, and shows its confirmation. - [x] Agreed mobile, desktop, browser, keyboard, and documented accessibility checks passed. - [x] The mobile confirmation defect reported December 4 was corrected and rechecked. - [x] The online-deposit idea remains future scope, not an unfinished deliverable. ## Files, licenses, documentation, and backup - [x] Agreed source assets, production exports, analytics handoff, editor update guide, third-party license list, renewal responsibilities, and launch backup are recorded in the bakery’s project folder. ## Accounts and access - [x] Sam verified bakery-owned editor and administrative access through the bakery’s secure process. No credentials appear here. - [x] Jordan’s temporary access was reduced after handover verification. ## Approval and payment - [x] Sam confirmed final acceptance in writing on December 5. - [x] Final invoice HSB-WEB-01-INV-04 requested $2,000: the $1,400 base handover milestone plus the $600 CR02 acceptance installment. - [x] Sam paid the final invoice on December 12. Total project payments are $6,800 USD: $5,600 base fee plus $1,200 approved change. ## Support and permissions - [x] The bounded post-launch correction window and the process for separately quoted new work are recorded. - [x] Portfolio permission was requested and recorded separately. No testimonial or referral permission was assumed. # Close-out and follow-up record Fictional educational example · December 13, 2026 Sam verified bakery-owned editor and administrative access, recovery ownership, the update guide, source assets, third-party license/renewal list, analytics handoff, and launch backup. Jordan’s temporary access was reduced to the level needed for the bounded correction period. The final $2,000 payment was recorded December 12. Total project payments are $6,800. No deliverable or payment remains outstanding. The correction window covers failures against accepted work for the recorded period. New pages, online deposits, ongoing administration, and later enhancements require a separate request and estimate. Jordan asked separately for permission to show the public site in a portfolio. Sam approved that limited use in writing. No testimonial, referral, private analytics, customer inquiry, or administrative-screen access was assumed.
Keep going
Adapt the process to your next project
Freelancer pathway
Build the process from your side
Define a service, respond to inquiries, estimate, propose, deliver, invoice, and close deliberately.
Client pathway
Prepare and manage a first hire
Turn a business need into a brief, compare proposals, provide feedback, accept work, and close access.
Reusable documents
Open the template library
Copy blank project briefs, proposals, SOW outlines, change requests, invoices, and handover checklists.