Managing Client Handover and Quote Approval
Package completed work for customers, publish controlled handover access, and capture customer quote decisions without losing the audit trail.
Before you start
- The customer account, site, and source records already exist.
- Reports, inspections, quotes, or work orders are ready to share with a customer.
- You have admin access to CRM and quote workflows.
Expected outcome
Customers receive controlled access to the right handover material and quote decisions are recorded against the quote that caused the work.
Use the right workflow
Use Client Handover when the customer needs a package of completed output such as reports, inspections, quotes, or work orders.
Use the quote detail Approval Workflow when the customer needs to approve or decline a quote.
Do not use either workflow as a replacement for fixing source data. Handover packages and quote approval links are customer-facing, so correct the source report, quote, site, or work-order record before publishing.
Create a handover package
- Open
Client Handover. - Select
New package. - Enter the package title and site ID.
- Add the CRM account ID when the package should be tied to a customer account.
- Add source items as JSON. Supported source types are
generated_report,inspection,quote, andwork_order. - Add grants as JSON when you already know who should receive the package.
- Create the package, then inspect the package detail before publishing.
The current package creation form is intentionally explicit. Source items and grants are entered as JSON rather than selected from a picker, so use the IDs from the owning report, inspection, quote, work-order, contact, or customer user record.
[
{
"sourceType": "generated_report",
"sourceId": "report-id",
"customerSafeTitle": "Final certificate"
}
]Check readiness before publishing
- Open the package detail.
- Review each package item.
- Resolve any item with a blocked inclusion state or a readiness state other than
client_ready. - Confirm the grants table shows the expected recipients and permissions.
- Publish only when the package has no readiness blockers.
Published packages can be opened by granted customers through the customer handover endpoints. Revoking the package removes current customer access. Revoking a grant removes access only for that recipient.
Manage handover grants
Handover grants can use view, download, or respond permission.
- Use
viewwhen the customer should only review package metadata. - Use
downloadwhen the customer can download the package items. - Use
respondwhen the customer workflow needs a response path. - Revoke a grant when the contact is wrong, the link is no longer needed, or the customer should not retain access.
Package activity records creation, publication, customer views, downloads, denied access, expired access, and revocations. Use the activity table before assuming a customer has not opened the package.
Send a quote for customer approval
- Open
Quotes. - Open the quote detail.
- Check customer, site, line items, totals, validity date, contact, and account context.
- Select
Send for Approvalwhile the quote is still draft. - Enter an invite email when the link should be associated with a specific recipient.
- Set the expiry window. The dialog accepts 1 to 90 days and defaults to 30 days.
- Create the link and copy it for customer delivery.
The approval panel shows link status, invited email, created and expiry dates, last viewed date, latest response, response detail, submitted date, and approval events. Raw token material is not shown in the quote detail after the link is created.
Capture customer decisions
When the customer uses the approval link, Deucalion records the response against the quote and updates the quote workflow.
When the decision arrives outside the portal:
- Open the sent quote.
- Select
Manual ApproveorManual Decline. - Choose the decision source: email, phone, customer portal, in person, or other.
- Enter a decision note.
- Save the decision.
Manual decisions are for real external decisions that happened outside the approval link. They should not be used to skip commercial review.
Follow through after approval
- When a quote becomes accepted, check the quote detail for the work-order handoff state.
- If a linked work order exists, open it and plan delivery.
- If the accepted quote has no linked work order yet, use
Create Work Orderfrom the quote detail. - Check Finance when the accepted quote or completed work order becomes ready to invoice.
The accepted quote to work-order handoff is hardened, but it still depends on customer, site, quote, and line-item context being valid.
Send reminders carefully
- Use
Send Reminderonly for quotes insentstate. - Confirm the quote email before sending.
- Check approval events before sending repeated reminders.
- Do not send reminders for expired, rejected, or accepted quotes.
Troubleshooting
| Problem | What to check |
|---|---|
| Publish is disabled on a handover package | Open the item table and resolve readiness blockers first. |
| A customer cannot open a handover package | Confirm the package is published, the grant is not revoked or expired, and the customer identity matches the grant. |
| A source item will not download | Confirm the item source type and ID still point at a customer-safe report, inspection, quote, or work order. |
| The quote approval link is not available | Check that the quote is still draft before creating the link. |
| A reminder cannot be sent | Only sent quotes can receive approval reminders. |
| Accepted quote work is not visible in Work Orders | Use the quote detail handoff state and create or open the linked work order from there. |
Reference surfaces
- Use Client Handover for route-level package and grant behavior.
- Use Quotes for approval link, manual decision, reminder, and work-order handoff details.
- Use Finance when an accepted quote becomes invoice-ready.
Running the Scheduler Day to Day
Run the refined scheduler with backlog control, quick-view edits, sticky actions, and the right planner surface for each decision.
Using Collaboration, Notifications, and Activity Feed
Use the notification bell and the Collaboration activity feed to keep cross-resource changes visible without relying on memory or inboxes.