BOOK LIBRARY · Complete books · Purchases disabled
TrendWindow

← Book Library · Complete book

Front cover of Contracts for Work You Cannot See

Business, Career & Money

Contracts for Work You Cannot See

By TrendWindow Library

A museum guide and twelve web pages reveal how a small service can become an undefined promise. Eight practical chapters follow Tess, Jo and Kiran through a fictional commission: scope, evidence, dependencies, fees, changes and a clear final handoff.

Read this complete edition, including its ending and notes. No purchase is required.

About this book

### Clear scope and usable handoffs for small maintenance and editorial services

This original practical short book uses an entirely fictional commission. It helps clients and service providers prepare a clear operational brief; it is not a ready-to-sign legal contract. Local law, professional duties and the actual relationship matter. Obtain suitable advice on enforceability, intellectual property, liability, employment status, privacy and tax where relevant. None of the examples authorizes access, publication, payment or work on a real system.

Original complete practical short book prepared with AI assistance. Tess, Jo, Kiran, quantities and project decisions are fictional teaching examples. General operational education, not a ready-to-sign legal contract, legal advice or market-price guidance. Local obligations and qualified advice remain relevant. Translation meaning reviewed with AI, without independent native-language certification.

1. Start with an object and a decision

Tess ran a small neighborhood museum with a visitor guide and a modest website. She wanted both “looked after.” Jo, an editor, heard a request to improve the guide's language. Kiran, a website caretaker, heard a request to inspect pages. Tess also expected someone to correct old opening times whenever they appeared. Three reasonable interpretations were waiting to become one unreasonable disagreement.

The first useful question was not “How much?” It was “Which thing will be different when this work is finished?” A service can be valuable without producing a new object, but it still needs an identifiable subject. A guide can be edited. A list of pages can be inspected. A response service can be available during agreed hours. “Everything stays good” is too broad to review.

Tess identified a five-thousand-word guide, version three, and twelve website addresses. The shop and the volunteer login area were outside the list. The guide's words were not automatically the website's words, even where they described the same exhibit. That distinction prevented one commission from silently becoming two.

Then they named the decisions. Tess would answer factual questions about the museum. Jo would propose language changes. Kiran would report page observations. Tess alone could approve publication under the museum's process. Being able to edit a file did not give either supplier permission to put it online.

Write a short object statement before discussing polish: the file or asset, its version, its intended use and the person who can make the next decision. If nobody can identify the current version, version selection is itself a task. Do not hide it inside an assumed start date.

For recurring services, name the period as well. A check performed in November does not establish what will happen in December. An inspection of a page at a recorded time does not promise that an outside link will remain available forever.

The title of this book concerns contracts, but the work begins before clauses. A shared description gives a qualified adviser and both parties something concrete to assess. It also gives the person doing the work a reasonable answer to the question: where does this assignment end?

2. Describe the service with verbs

Jo asked what “edit” meant to Tess. Did she want the order of the exhibit descriptions reorganized, sentences clarified, spelling made consistent, or a final designed booklet checked? Those are related activities, not interchangeable names for an unlimited improvement service.

The Chartered Institute of Editing and Proofreading distinguishes copyediting from proofreading after layout. The distinction is useful here: agree the stage, not merely the label. Jo's fictional commission covered a language and consistency edit of the supplied guide. It did not include a new exhibition narrative, independent historical research, image permissions, translation or checking a later designed PDF.

Tess wanted unclear facts flagged, not silently invented. Jo would query contradictory dates and uncertain names, while Tess would supply authoritative answers. “Check facts” alone would have concealed whether Jo was expected to research a century of local history or point out contradictions within the supplied material.

Kiran replaced “maintain the website” with a bounded first service: inspect the twelve listed pages once during the agreed monthly window, record whether they load in the agreed test conditions, inspect listed navigation paths and report visible layout or content problems. Repairs would require a separate approved scope. An inspection was useful even when it changed nothing.

Use verbs that distinguish observation from action. Inspect, report, propose, replace and publish are different promises. So are acknowledge, investigate and resolve. A provider may be able to acknowledge a report by a particular time without being able to promise resolution by then.

Name exclusions without using them to empty the service of value. “Not responsible for anything” tells the client little. “This check excludes the shop and login area; problems visible from the listed public pages will still be reported” is more informative. It preserves a sensible route for an unexpected discovery.

Ask the provider to explain one ordinary example and one boundary case. If “one revision” means correcting a spelling inconsistency in the agreed text, say so. If it does not mean rewriting a new chapter, say that too. Clear verbs allow a small job to be small without making it mysterious.

3. Agree the evidence before anyone starts

A client should not need to watch every minute to understand what was delivered. Nor should a provider have to reconstruct a week from memory because nobody agreed what a handoff would contain. Decide what evidence fits the work before the work begins.

Jo proposed a marked-up guide, a clean copy reflecting agreed decisions, a short style sheet and a query list. A clean copy alone would hide important choices. A marked-up copy alone might leave Tess unsure what could actually go to the designer. The filenames would identify version and date, with one clearly designated current copy.

Kiran proposed a page list with the time checked, the agreed viewing conditions, observations and unresolved items. Screenshots would support particular findings, not serve as a blanket claim that every page had been checked. A green status beside an inaccessible page would be false evidence, however tidy the report looked.

Their completion criteria described inspectable results. All twelve page entries would have a truthful status. Every issue would identify a location and enough context for Tess to understand it. “Blocked” would count as an honest observation, but not as proof that a page passed. Whether a blocked item required another visit would be agreed separately.

For the guide, all supplied sections would appear in the returned files. Changes would be traceable. Queries would be answered, explicitly left open or removed only through an agreed decision. The handoff would say whether any unresolved matter prevented publication. “Looks professional” could be a preference, but it was not the only acceptance criterion.

Do not demand evidence unrelated to the service. Continuous screen recordings might expose private material and consume time without helping review. A compact record of relevant outputs can be more useful. Agree what sensitive information should be omitted or redacted from evidence.

Avoid promising a perfect result merely because you can define a checklist. A checklist describes what was examined and what remains. It cannot make every future defect impossible. Useful evidence gives the next person enough confidence to act within the stated limits, not a reason to stop thinking.

4. Put dependencies on the calendar

Jo could not finish a clean version while six questions about dates remained unanswered. Kiran could not inspect a listed page that redirected to an access screen. Neither problem became solved because the original deadline was close.

Tess prepared a dependency list: the final source file, the museum's existing style preferences, factual answers, permitted access where needed and one person to combine feedback. Each item had an owner and a needed date. “Client to provide materials” became several things a person could actually deliver.

A deadline should say what it assumes. If a source arrives late, agree how the schedule will be reviewed. Do not assume the provider can absorb every delay by working overnight. Equally, a provider should report a missing input promptly rather than reveal it for the first time when delivery is due.

Separate access from authority. A shared link may allow viewing without allowing alteration. A login may permit several actions technically while the agreement permits only one. State the permitted environment and actions. Use the organization's approved access process; do not solve a blocked task by borrowing unrelated credentials or disabling a safeguard.

Kiran recorded the inaccessible page as blocked and told Tess what was needed. The page had been moved behind the museum's review access by mistake. Tess used the museum's normal process to arrange permitted viewing. Kiran did not invent a successful result or treat the problem as permission to change settings.

Recurring work needs a contact arrangement. Define where ordinary requests go, when messages are reviewed and how genuinely urgent issues reach the responsible person. Do not sell “support” as if it means permanent availability unless that service really exists and is agreed.

A dependency can remain unresolved at handoff. Record its consequence plainly: “The final wording of the date note awaits Tess's answer.” That is more useful than burying it in a cheerful completion message. A project may contain finished work and a blocker at the same time. The record should show both.

5. Attach money to a defined boundary

A fee is easier to understand when the reader can see what it purchases. A fixed price for the supplied guide is different from a monthly availability fee, a per-page inspection or time spent investigating an unknown fault. None of these structures is automatically fair in every situation.

Australian Government guidance on preparing contracts identifies the work, payment and completion conditions as matters to state clearly. Its legal context is Australian. This book uses original fictional planning examples, not imported clauses or universal legal rules.

Tess and Jo separated the agreed editing fee from the price of possible new work. Their written commercial schedule named the currency, any applicable tax treatment, the invoice trigger, the due date and the agreed correction process. They did not use “pay when happy,” which could leave both completion and timing undefined.

If charging by time, define how time is recorded and what happens near the agreed limit. A budget cap is not a promise to finish an unknown amount of work for that cap. A useful update might say that the remaining allowance will cover the current investigation, but a repair estimate cannot yet be given. The client can then choose whether to authorize more work.

If charging a recurring fee, explain the included service period and the treatment of unused capacity. Does a month buy one inspection, reserved hours, or access to a request queue? Does unused time expire or carry forward? These are choices to agree, not assumptions to smuggle into an invoice.

Discuss additional costs before they arise. A supplier should not discover after delivery that an essential file conversion was treated as an unpaid favor. A client should not discover that ordinary review was billed as a surprise extra. Name what requires advance approval and who can give it.

Do not confuse a payment milestone with publication permission or ownership of every working tool. Those are separate subjects requiring clear terms and, where appropriate, qualified advice. The operational brief should expose the questions rather than pretend that a friendly sentence settles them everywhere.

The aim is not a clever way to avoid paying or doing work. It is a boundary both sides can recognize before either side has invested more than it can afford to lose.

6. Change the scope without rewriting the past

Halfway through the edit, Tess found twelve hundred additional words about a new exhibit. She also wanted four more pages inspected. She called both requests “small additions.” They might be worthwhile, but their size was not determined by the word small.

Jo compared the new text with the frozen source. It was new content, not correction of an editing mistake. She explained the effect on time and fee. Kiran similarly separated the four new addresses from the twelve-page list. Neither supplier silently inserted the request and hoped to recover the cost later.

A change note can be brief: what is added or removed, why, the effect on outputs, timing and price, and who approved it. Keep the earlier scope identifiable. If every file is simply overwritten, a later reviewer cannot tell whether something was forgotten or deliberately removed.

Distinguish a defect from a new preference. Jo had accidentally reversed two digits in a date while editing. Correcting that introduced error belonged to the agreed correction process. Adding the newly written exhibit section was different. Calling both a “revision” would hide the distinction and invite argument.

Some requests reveal that the original brief was wrong. In that case, stop and redefine the work rather than build a large project inside a misleading small label. A structural rewrite should not be disguised as proofreading because that is the line already approved.

Tess decided to finish the original guide first. The new exhibit text would become a separately commissioned supplement after its facts were ready. She deferred the four extra website pages to a later agreed inspection. This was a decision about sequencing, not a trick to get free labor.

Record a declined or deferred change too. “Not in this delivery” is useful information for the person checking the result. It prevents an old request from returning at handoff as though it had been accepted.

Keep changes visible to the people doing the work. A client-side discussion is not an instruction until the authorized contact communicates it through the agreed route. A provider's private assumption is not approval. The written record should show a decision, not merely the existence of a conversation.

7. Review the handoff against the agreement

Jo delivered the edited guide, its marked-up counterpart, the style sheet and the query record. Tess checked the filenames, opened the files and compared the section list with the source. She answered the remaining date questions before Jo produced the final clean copy. The introduced digit error was corrected and the revised file clearly identified.

Kiran's first report showed eleven inspected pages and one blocked entry. After permitted access became available, the agreed follow-up covered the remaining page. The updated report preserved the earlier status and added the later observation. It did not pretend that all twelve had been inspected on the first date.

Review should be a real activity with an owner and a workable period. Agree how feedback is consolidated, how defects are reported and how a revised delivery is checked. Do not assume that silence has a particular legal meaning; that depends on terms and applicable rules, not this book.

Tess collected comments from two volunteers into one response. She separated errors against the brief from suggestions for a future edition. The providers did not have to choose between contradictory instructions arriving through three unrelated messages.

A useful defect report identifies the file or page, the location, what was expected and what was observed. “The guide is wrong” is hard to act on. “In section four, the returned date differs from the answer in query six” gives the editor a specific comparison. Screenshots can help with a visible layout issue, but they should be tied to the relevant page and conditions.

Acceptance need not erase remaining limitations. Tess could acknowledge that the agreed inspection was complete while deciding separately what repairs to commission. She could accept the edited source while still needing a designer and a final proof check. The record would say which stage was finished.

Do not turn review into an endless reopening of settled choices. Equally, do not use a narrow review window as an excuse to conceal a known defect. Use the agreed correction and dispute routes, with appropriate advice where necessary. A good handoff makes disagreements easier to locate; it does not guarantee that none will arise.

8. End with a record the next person can use

At the end of the month, Tess had two distinct completed assignments. Jo's guide was ready for the next production stage, with factual answers recorded and the agreed language work finished. Kiran's report covered the twelve listed pages, including the later authorized check. Nothing in either handoff claimed that the website had been repaired or the booklet published.

The supplement and four additional pages sat in a future-work list. They were not hidden inside “almost done.” Tess could now decide whether to commission them, with their own inputs and review criteria. The original job had an ending because its boundary had survived contact with new ideas.

Make the closing package readable without the whole conversation history. Identify the final outputs, the decisions that shaped them, outstanding dependencies, known limitations and the next responsible person. Keep credentials out of an ordinary handoff document. Handle access return or revocation and data retention through the agreed secure process and applicable obligations.

For continuing services, closing one period does not cancel the next or authorize it by implication. Record what renews, what needs a new decision and what happens if either party ends the arrangement. Continuity depends on usable records, not on making one supplier indispensable.

Before starting your next small commission, answer five questions in plain language. What exactly is being worked on? What actions are included? What will demonstrate completion? What must each party provide? How will changes and the final review be handled? Then address the commercial and legal terms appropriate to the actual work.

Ask someone who was not in the original discussion to read the brief. Can they identify the current file, the permitted action and the person who decides the next step? If not, improve those parts before adding more formal language. Complexity is not the same as clarity.

Tess put the final guide in the designer's intake folder and the inspection report in the museum's maintenance record. The future supplement had its own blank brief. She no longer needed to ask whether somebody was “looking after everything.” She could see what had been done, what had not, and which decision belonged to her next.

Sources and limits: [Australian Government, *Prepare a contract*](https://business.gov.au/people/contractors/prepare-a-contract); [Chartered Institute of Editing and Proofreading, *About proofreading and editing*, 11 January 2024](https://www.ciep.uk/resource/about-proofreading-and-editing.html). Consulted 9 November 2026. All people, quantities and project decisions are fictional. The practical examples are original discussion aids, not approved legal clauses, market-price guidance or a guarantee of flawless work.

Explore more books →