# Convert Signed Agreement to Word: A Working Copy Method

- Author: Schema Law (https://www.schemalaw.com/)
- Published: 2026-09-23T05:41:39Z
- Updated: 2026-10-11T19:22:20Z
- Category: Contracts and agreements
- Canonical: https://www.schemalaw.com/blog/convert-signed-agreement-to-word

> How to convert a signed agreement to Word from a scan: the steps for a contract, the signature block, working-copy labels and broken cross-references.

To convert a signed agreement to Word when only a scan exists, run the scan through OCR, export a DOCX, and proofread it against the signed pages. Then make the Word file plainly a working copy: remove the signatures, label every page, and repair the cross-references and defined terms before you draft from it.

The conversion is the short part. The work that makes the file safe to use takes longer, and it is specific to contracts. A converted letter that keeps a stray signature scrawl is untidy. A converted contract that keeps one can be mistaken for a signed instrument, and a single section number that came out wrong can redirect an indemnity.

Before you draft, compare the Word text of any rescission language and any repudiation sentence with the scan. Read each instance of the word not on the page image. If the signed pages change a figure, type that figure from the image and cite the page. Confirm the party names and the dates from the preamble through the signature blocks.

## Why would you convert a signed agreement to Word?

You convert a signed agreement to Word because the next piece of work needs its language in editable form and the original Word file cannot be found. Renewals, amendments, restatements and new deals on the same terms all start from the signed text, since the signed pages show the wording the parties put their names to.

The usual occasions:

| Occasion | What you need from the Word copy |
| --- | --- |
| Renewal or extension | The term, pricing and notice clauses, ready to mark up |
| Amendment | Exact existing wording to quote in "is deleted and replaced with" |
| Amended and restated agreement | The whole text as a base for a redline |
| Next deal with the same counterparty | The negotiated positions, as a starting draft |
| Template for similar deals | A clean form with the deal facts taken out |
| Internal summary or advice | Clauses to paste and annotate |

### Why not the last draft on the system?

If a Word draft does exist, it is tempting to use it. Be careful. The last draft in your files is whatever was saved before signing, and it may not match what was signed. Late changes can be made on the other side's version, or by hand at the signing table. The scan of the executed pages shows the text as signed.

If you have both, the draft is still useful. Convert the scan, then compare the converted text with the draft to see whether they differ. The post on [comparing two scanned contracts](https://www.schemalaw.com/blog/how-to-compare-two-scanned-contracts) covers checking a signed scan against the draft sent for signature.

### When Word is the wrong target

If you only want to find or quote a clause, a searchable PDF does the job and still shows the signed pages. If you only want the dates and amounts for a chart, plain text is enough. Choose Word when you intend to edit. The post on [scanned contracts](https://www.schemalaw.com/blog/scanned-contracts) maps each task to its output.

## Converting a scanned contract to an editable Word file

Converting a scanned contract to an editable Word file has three contract-specific stages around the generic conversion: decide which pages belong in the working copy, convert, and proofread the terms a contract turns on. The upload-and-export mechanics are the same as for any scan.

Those mechanics, and the first checks to run on any DOCX that came from a scan, are in the guide on [how to convert a scanned PDF to Word](https://www.schemalaw.com/blog/how-to-convert-a-scanned-pdf-to-word). What follows assumes you have read it or done it before.

### Before converting

1. **Use the fully executed copy.** If you hold two scans, one signed by each side, pick the one with every signature, or assemble the set first.
2. **Collect the amendments.** If the agreement has been amended, you need those scans too. A Word copy of the original alone is a copy of a contract that no longer reads that way.
3. **Decide on the exhibits.** Body and exhibits can go into one Word file or separate ones. Separate files work better when an exhibit is a table-heavy schedule or an attached form with its own section numbering, since Word's numbering will otherwise run them together.
4. **Leave the scan alone.** Convert a copy, or upload the file without altering it.

### Converting

Upload the scan and export Word. In Schema Law the file can be a PDF, PNG or JPEG of up to 20 MB, and the Word export holds editable text with its headings, lists and tables. The free plan exports Word for a document of up to three pages, which is enough to try a signature page and two pages of clauses. Longer agreements need a paid plan, and the [pricing page](https://www.schemalaw.com/pricing) gives the page limits.

### After converting: the contract read

A scanned contract becomes editable text you can trust only after a read against the image. For a contract, cover these in order.

- **Parties.** Full names and entity types in the preamble.
- **Money.** Every amount, rate and percentage, in the body and the schedules.
- **Time.** Every date and every period of days, months or years.
- **Section numbers.** That the sequence is unbroken and matches the scan. A list that restarts at 1 halfway through article 6 is a conversion artifact.
- **Negatives and exceptions.** The sentences containing "not", "except", "unless" and "provided that".
- **Page-break joins.** Where a sentence ran across two pages, check the footer text did not land inside it.

How recognition behaves differently in the preamble, the clauses, the signature block and the exhibits is described in the scanned contracts post, under [how OCR treats each part of a signed agreement](https://www.schemalaw.com/blog/scanned-contracts#how-does-ocr-treat-each-part-of-a-signed-agreement). Use it to decide where to read slowly.

Make these corrections with tracked changes off. They restore the signed text. They are not edits to the deal.

### A worked example

Bellhaven Dental Group PLLC wants to renew a three-year equipment maintenance agreement with Ostrander Medical Systems, Inc. Nobody has the Word file. The scan is 11 pages plus a two-page fee schedule. After conversion, the contract read finds four problems: "Ostrander Medical Systems, lnc." with a lower-case L for the capital I; a response time of "4 hours" that the scan shows as "24 hours", the 2 lost against a punch hole; section 7 numbered as a second section 1; and a footer, "Bellhaven / Ostrander MA v6", sitting in the middle of clause 9.2. Four corrections, twenty minutes, and the second of them would have been an expensive promise to make by accident.

## What should happen to the signature block in the Word copy?

In the Word copy, the signature block should keep its printed structure and lose everything that records the act of signing. Delete the residue of signatures and initials, replace handwritten dates with a bracketed note, and keep the entity names, "By:" lines, typed names and titles.

### What conversion leaves behind

OCR treats a signature as marks on the page. In the DOCX you may find nothing where the signature was, or a few stray characters, or a small picture. Initials at the foot of each page turn into two or three odd letters after the last line of text. A handwritten date may come through as a plausible but wrong date.

### What to do with each element

| Element on the signed page | In the working copy |
| --- | --- |
| Ink signature | Delete any residue; leave a blank signature line |
| Typed name and title under the line | Keep, after checking spelling against the scan |
| Entity name above "By:" | Keep exactly |
| Handwritten date | Replace with `[signed 14 March 2023 per executed copy]`, or a blank for a new instrument |
| Page-foot initials | Delete the residue from every page |
| Witness or notary block | Keep the printed form; delete filled-in particulars and any seal residue |
| "Signature page follows" legends | Keep; they are part of the text |
| E-signature ID strings or stamps printed beside a signature | Delete; they belong to the signed file |

### Why remove the signatures at all?

There are two reasons. The first is that a Word file showing a signature image looks executed. Someone who opens it later, or receives it by mistake, may take it for the agreement. The second is that a signature image in an editable file can be copied onto something else. Neither risk is worth the small convenience of seeing who signed.

Record the signing facts in words instead. A one-line note above the block does it: `[Executed copy signed by D. Ostrander, President, and R. Bellhaven, Managing Member, on 14 March 2023.]` Reading the names, capacities and dates off a scanned block has its own difficulties, and the post on [extracting signatures and dates from scanned documents](https://www.schemalaw.com/blog/extract-signatures-and-dates-from-scanned-documents) deals with them.

### Handwriting elsewhere on the signed pages

Signatures are not the only ink. A clause struck through and initialed, or a figure corrected by hand, is part of what was agreed, and the converted text will probably show the printed version only. Do not guess. The post on [handwritten changes to a contract](https://www.schemalaw.com/blog/handwritten-changes-to-a-contract) explains how to find them and carry them into the working copy.

## Labeling the Word file so nobody mistakes it for the executed agreement

Label the Word file in four places: the file name, a note at the top of page one, the header of every page, and the document properties. Each label should say that the file is a working copy converted from a scan, and should name the scan.

Four places may seem excessive. Each one covers a different way a file travels. File names are changed by email and downloads. First-page notes are lost when someone copies sections into a new document. Headers survive printing. Properties survive when the visible labels are stripped for a client-ready draft.

### The file name

```text
Ostrander Maintenance Agreement 2023-03-14 - WORKING COPY from signed scan.docx
```

Keep the agreement's own date in the name, since that identifies which contract it is. Put the status in capitals. Avoid "final", "executed" and "signed" as stand-alone words anywhere in a working copy's name. "From signed scan" is safe because it describes the source.

### The first-page note

Put a boxed or shaded paragraph above the title.

```text
WORKING COPY. NOT THE EXECUTED AGREEMENT.
Converted by OCR on 9 October 2026 from the scan
"Ostrander MA signed 2023-03-14.pdf" (13 pages).
Proofread against the scan by [initials] on [date].
Signatures removed. The scan is the record of what was signed.
```

The proofreading line matters. A working copy that has been read against the scan and one that has not are different things, and the next user needs to know which they hold. Leave the line blank until the read is done.

### The header

A short running header on every page: `Working copy from signed scan. Not the executed agreement.` Use the header, not a diagonal watermark. Watermarks make redlines hard to read and get switched off.

### The properties

In the document properties, set the title to the agreement's name plus "working copy", and use the comments field for the source scan's file name. When you later save a clean draft of a new instrument from this file, the properties are the one place the lineage can stay.

### When the labels come off

The labels belong to the working copy. When you draft an amendment or a renewal from it, the new document is a new instrument and carries its own status, for instance "Draft" with a date. Remove the working-copy header and note from the new draft, not from the working copy. Keep the working copy itself intact and read-only as the base you compare against.

One more rule: when anyone asks for "the contract", send the scan. The Word file goes out only as what it is, for instance as the base of a redline, with a covering line that says so.

## Turning a converted agreement into a reusable template

To turn a converted agreement into a reusable template, strip out the facts of the deal it came from, mark the choices that were negotiated, rebuild the formatting with proper styles, and record where the template came from. A signed contract is one outcome of a negotiation. A template has to be neutral again.

Work on a copy of the verified working copy, never on the working copy itself.

1. **Replace the deal facts with placeholders.** Party names, addresses, dates, amounts, product descriptions, notice details. Use a consistent, searchable bracket style such as `[COUNTERPARTY NAME]`.
2. **Hunt for facts hiding in the body.** The preamble is easy. The stragglers are a party's name inside a defined term ("Ostrander Software"), a city in the venue clause, a named individual in the notices clause, a product name in a warranty.
3. **Flag the negotiated clauses.** A liability cap of twice the annual fees was agreed with one counterparty for reasons of that deal. Mark such clauses with a drafting note, or restore your standard position and keep the negotiated wording as an alternative.
4. **Remove one-off provisions.** Special terms, side arrangements and transitional clauses written for the original parties.
5. **Rebuild the structure.** Apply heading styles and automatic numbering, so that later insertions renumber correctly. The post on [whether OCR keeps formatting](https://www.schemalaw.com/blog/does-ocr-keep-formatting) explains what state the numbering is in after conversion.
6. **Replace typed cross-references with fields,** as the next section describes.
7. **Clear the metadata.** Remove the working-copy labels, tracked changes, comments and the document properties that name the old deal.
8. **Write a provenance note** and keep it outside the template: which agreement it came from, who converted it, who cleaned it, on what date.

### A placeholder check

Before the template goes into use, search it for every fact you removed. Search for each party's name, including short forms, the city and state, the year of signing, and the main dollar figures. Then search for an opening bracket and read each placeholder in context. A template that still contains the previous client's name in clause 18 will send it to the next counterparty.

### Should this agreement be a template at all?

Check two things first. Whose paper was it? If the agreement was drafted by the counterparty, its defaults may favor the other side of the table from where your client usually sits. And is anything in it confidential to the original parties? Read that contract's own confidentiality clause, and consider any duty owed to the client, before deal terms are taken out of it and reused elsewhere. That is a question for the lawyer responsible, under your firm's or company's precedent policy.

## Cross-references and defined terms that break in a converted contract

In a converted contract, cross-references arrive as plain typed numbers with no link to the clauses they point at, and defined terms can lose the capitals and quotation marks that mark them. Both look fine on the page, and both fail quietly the moment you edit.

### Cross-references

In the original Word file, "subject to Section 8.2" was probably a field that tracked its target. In the converted file it is four typed characters. Two things follow.

First, the number may have been misread. A reference to "Section 3.2" in the converted text that should read "Section 8.2" still points at a real clause, so nothing looks wrong. Check each reference against the scan.

Second, even when correct, it is frozen. Insert a new clause 5 while drafting the renewal, and every later clause renumbers if you rebuilt the numbering, while every typed reference stays as it was. Now "Section 8.2" points at the old 8.1.

A repair routine:

1. Search for "Section", "Clause", "Article", "paragraph", "Schedule", "Exhibit" and "Annex", and list every reference with the clause it sits in.
2. Check each number against the scan.
3. Open the target and confirm it is about what the referring clause expects. A reference to "the indemnity in Section 12" should land on an indemnity.
4. Once the document has automatic numbering, replace each typed reference with a Word cross-reference field.
5. After every round of edits, update fields and search for the error text Word shows when a target has been deleted.

References to exhibits deserve the same check. "Exhibit C" should exist, and should be the document the clause describes.

### Defined terms

A contract's defined terms depend on exact, consistent form. Conversion disturbs that in several ways.

| What happens | Example | Why it matters |
| --- | --- | --- |
| Lost capital | "the services" for "the Services" | Reads as the ordinary word; scope becomes arguable |
| Gained capital | "the Agreement" where the scan has "an agreement" | An ordinary word now reads as the defined term |
| Lost or altered quotation marks at the definition | (the Fee) for (the "Fee") | The definition no longer looks like one |
| Lost bold or underline | Definitions blend into the paragraph | Harder to find; no legal change, but slows every later reader |
| Split by a line break | "Confidential" at a line end, "Information" after a stray paragraph mark | Searches for the full term miss it |
| Character substitution | "Deliverab1es" | Searches miss it; spell-check may catch it |

### A defined-terms pass

1. From the scan, list every defined term in the definitions clause and every term defined in passing in the body.
2. Search the Word file for each term with "match case" switched on, then again with it switched off. Different counts mean some instances have the wrong capitalization.
3. Read each mismatch against the scan. Some lower-case uses are deliberate.
4. Search for each definition itself and restore the quotation marks and emphasis.
5. Look for terms used with a capital and never defined. Some are OCR errors and some are drafting gaps in the signed agreement. Note the second kind and leave them as signed.

That last distinction runs through the whole exercise. The working copy should reproduce the executed agreement, errors included. A typo the parties signed stays in the working copy, with a comment if you like. It gets fixed in the amendment or the template, where fixing it is a decision someone makes on purpose.

## Try it on a real document

Upload a scanned PDF and export it as Word, a searchable PDF or plain text on the free plan. Your documents are never used to train an AI model. [Start free](https://www.schemalaw.com/api/auth/google)