Amal is a fictional freelance editor in Albany, WA, considering an enquiry about editing a small business’s customer information booklet. The request sounds manageable, but the phrase tidy the booklet leaves several decisions unclear.
This planning story follows the questions Amal prepares before accepting work. The editor, client and draft project are invented. No contract is signed, no client response is received and no completed work, payment or legal outcome is reported.
The first question concerns what editing means
Amal notices that the enquiry could refer to proofreading, restructuring or writing new material. Those tasks would require different inputs and a different account of the work.
The proposed question asks what the client wants changed and what condition the supplied text will be in. A sample could help clarify the scope, provided it is shared appropriately.
Amal would distinguish editing the client’s wording from verifying every factual statement or designing the final booklet. The purpose is to describe a service both sides can understand, not assume that a short request includes every task connected with publication.
The deliverable is separated from the publication
The next question concerns what Amal would hand over. An editable document with marked changes is different from a final print-ready layout or a live update to a website.
Business.gov.au’s contract preparation guidance recommends clear descriptions of work or results, timing and payment. Amal uses that principle to identify the proposed file format and review stage.
The booklet’s later printing or distribution would remain a separate decision. Sending an edited draft would not establish that the client had approved it or that every production check had been completed.
Amal also notes that a later layout stage might introduce changes or require another proof. That check would need its own place in the scope, rather than being presumed part of editing a different earlier version.
The deadline reveals a dependency
Amal’s draft schedule initially contains only a delivery date. It says nothing about when the client will supply the complete text or who will answer a factual query.
Amal therefore prepares questions about inputs, review time and the person authorised to consolidate feedback. If several people send conflicting changes, the project needs a way to identify the client’s agreed direction.
A missing price, opening arrangement or service description would be marked as a query rather than invented for a polished page. The fictional freelancer would not turn uncertain client information into a confident public claim.
A revision request becomes a scope question
Amal imagines the client adding several new sections after the first edit. Calling that another correction could hide a materially different task.
The proposed agreement would need to explain the included review process and how changes to content, timing or deliverables are discussed. Amal would ask how an extra request affects the work before treating it as automatically included.
The aim is not to resist every useful change. It is to keep a changed project recognisable so both parties understand the revised scope and any effect on payment or delivery.
The fee needs a completion and payment basis
An attractive total is difficult to assess without the work it covers. Amal would need to understand whether the offer concerns a defined project, time worked or another arrangement.
The draft questions ask what stage triggers invoicing, what information the invoice must contain and when payment is due under the actual agreement. Any applicable tax presentation would need to be understood without assuming Amal’s registration status.
No fee, deposit percentage or universal payment deadline is supplied by the story. Amal’s planning note leaves those details unresolved rather than creating a fictional accepted commercial term.
Use of the material is not assumed from possession
The client would provide existing text and perhaps images, while Amal might create revised wording. The parties need to understand which material they may use and what permissions or restrictions apply.
Amal would ask about confidentiality, the proposed use of the deliverables and whether any public portfolio use is appropriate. Holding a file would not be treated as permission to publish the client’s material or disclose the project.
Where rights or liability clauses are unclear, Amal would seek suitable legal advice. The story does not determine ownership of every commissioned work or claim that one default rule resolves every type of material.
The final check comes before acceptance
The ACCC’s contract guidance explains that acceptance may occur by words or actions as well as a signature. Amal would not assume that an informal proceed message has no possible significance until a document is signed.
The proposed checklist now records:
- The editing task and exclusions.
- The supplied material and required permissions.
- The deliverable and completion stage.
- Inputs, deadlines and consolidated feedback.
- The included review and change process.
- Payment, confidentiality and exit questions.
The fictional story ends with questions ready for discussion. Managing freelance work in Albany, WA, can begin with that clarity, while acceptance waits on understanding the actual offer and resolving the matters that affect the commitment.