Managing an attached agreement

A service agreement attached to an inspection is managed from the project’s Document Center, in the By inspection view. This page describes each action, when to use it, and what happens when you remove an agreement.

Where the actions are

On the inspection card (Inspections tab), the Agreement pill shows the state — to create, draft, sent, signed — and a click opens the Center on that inspection. There:

under ① Generate, the Service agreement chip (click it to open its sheet);
under ② Send and signatures, its checklist line, then its state (to sign · draft, sent on …, signed on …);
View all unfolds the full row with its icons.

Viewing the agreement

View (eye) opens the agreement in a new tab: the prefilled PDF as the client will read it, with its annexes. Once signed, the sealed copy opens instead (initials, signature, certificate page).

Use it to check the ticked options before sending, or to download a copy for your records. The action is read-only.

Sending for signature

Tick the agreement under ② Send and signatures (it already is while in draft) and click Send for signature. The email window opens, built on your quote template, editable; one email goes out, with no attachment, with the Open my client portal button. The client reads and signs in their portal. See Signing the agreement.

The same icon (pen) is available on the document’s row and in its sheet.

Sending the PDF

The paper plane icon on the row sends the agreement as an attachment, without online signature. It is the fallback for a client who prefers signing in Acrobat or on paper; in that case, upload the signed version you receive into the Center.

Reminding

An agreement sent but not yet signed is never re-sent: the journey’s next step becomes Remind. The client receives a generic reminder (“one or more documents are awaiting your signature”) with their portal button. 24-hour lock between two reminders. See Reminding a client.

Agreement with two signers (co-client): the journey shows one line per signer — signed on … or awaiting — with its own Remind (the reminder goes to that person’s portal, 24-hour lock per signer), and on the co-client’s line Remove as long as they have not signed. Add …‘s signature appears under an agreement sent to the client alone when the project has a co-client with an email. See Multiple clients.

Removing the agreement

Remove (trash), on the row or in the sheet, archives the agreement: it leaves the journey and the Center, the history is kept. Possible as long as the agreement is not signed. Depending on the moment:

Before sending — nothing reached the client: the agreement disappears, you generate another one.
Sent, not signed — it leaves the client’s portal and its signing request is cancelled: a client who still had the signing screen open gets “This document was withdrawn by the inspector”. Let them know if needed.
Co-signed, one signature of two — possible, with a warning: the signature already given is cancelled with the request (the history keeps it). If it is the signer you want to change, prefer Remove or Add on the co-client’s line.
Signed — impossible: a signed agreement is a contract; it stays readable and downloadable by both parties.

When to remove

You need to change it — Lumos attaches one agreement per inspection. Switching template (APCHQ → AIBQ), adding a forgotten annex (divided co-ownership), correcting an amount: remove + generate again.
The inspection is cancelled before signature.
Sending error — wrong client or wrong options.

Effects

The client is not notified; if they had received the email, the agreement simply disappears from their portal. Let them know if needed.
The linked quote is untouched: the two documents are independent.
You can generate a new agreement with Quote and/or agreement under ① (untick the quote if it already exists).

Removal is final for the journey. Before removing, open the agreement with View and download the PDF if you want to keep a copy outside Lumos.

Editing an agreement without removing it

You cannot edit a generated agreement. It is frozen at creation. Any change goes through remove + generate again: the agreement is a contractual document, and every version must be traced by a new send.