Prepare the scope
Use clear service and material descriptions, quantities and the intended site.
Connect the customer, site, proposed work and decision in one readable process. Give the attending team and office a clear account of what the customer has been asked to approve.
14-day trial · No credit card required · Rand pricing
Use clear service and material descriptions, quantities and the intended site.
Inspect the proposal and configured options in the customer-facing workflow.
Distinguish approval, decline and an outstanding review, then identify the next action.
Check readiness and give the attending team the current agreed scope.
WorkOrderPro product guide · Updated 12 September 2026.
A useful quotation explains the work the customer is being asked to approve. The total matters, but the site, service description and scope boundary matter too. A proposal that depends on an earlier conversation can leave the customer, attending team and office reviewer with different interpretations. Start with a record that another person can read and explain without hearing the original call.
WorkOrderPro's quotation workflow connects the customer, job site and service or material lines with the proposed work. Customer-review workflows include an approval page that can display the proposal and receive a decision. Use the trial to follow the full handover: prepare the scope, inspect the customer-facing result, record the relevant decision and review what the team should do next.
The aim is a clear commercial record. A quote builder does not determine technical suitability, establish a customer's authority or guarantee how quickly someone will decide. Those responsibilities remain part of your business process. The software is most useful when it preserves the proposed work and decision clearly enough that colleagues can act on the same information.
The person requesting a quotation may not be the person paying for the work. A tenant can report a problem while a landlord approves the repair, or a facilities contact can arrange an assessment while another department authorises expenditure. Identify the commercial customer and the contact responsible for the relevant decision before sending the proposal.
Use the job site to distinguish where the work will happen. One customer may have several properties, and a generic address or familiar site nickname can be ambiguous. The quotation should make the intended location recognisable to the customer and the team. Confirm any account reference needed by the office rather than assuming the caller's name supplies the full billing context.
During the trial, create a proposal for one of two sites belonging to the same customer. Ask another employee to identify the intended place and approving person from the record. If they need clarification, fix the source information before adding more detail to the quote. A clear total attached to the wrong property is still an unusable proposal.
A customer enquiry may describe a symptom that still needs inspection. Keep that report separate from a technical conclusion or repair scope that has not yet been established. If the first appointment is an assessment, explain its purpose and any agreed charge. The customer should not mistake an assessment booking for a promise to complete every possible repair during that visit.
After the responsible person records the findings, prepare the proposed next work. The quote should identify what is now being offered and which decision remains with the customer. An assessment record and a repair proposal are connected, but they answer different questions. Preserving that distinction helps the office explain why a job has reached the quotation stage.
Use an example in which the first visit does not finish the repair. Ask the reviewer to identify the original request, the assessment outcome and the proposed work. This is more informative than a perfect example where the diagnosis, price and appointment are all known from the first enquiry. It tests the commercial handover your team must manage when new information changes the plan.
A reusable catalogue can help the team use consistent descriptions and rates. The individual quotation still needs to explain the particular job. Distinguish labour, materials and other agreed items in a way the customer can understand. A broad line such as general repairs may be insufficient when the proposal covers several tasks or a specific replacement item.
Review quantities and units carefully. A catalogue entry is a starting point, not evidence that the quantity is correct or the item is suitable for the site. The responsible specialist verifies technical requirements, while the office checks that the commercial description matches the proposed work. The calculation should support those decisions rather than hide an unclear assumption behind a precise total.
Prepare a trial quote with more than one line type and ask a colleague to explain it. Include an ordinary material and a labour item, then inspect the customer-facing descriptions. If the business uses optional work or alternative proposals, demonstrate that exact arrangement rather than relying on several line items to imply a formal choice structure.
The customer needs to understand how the proposed amount relates to the work. Inspect line totals, any discount, tax presentation and the final amount in the actual output. A reviewer should be able to follow the calculation without referring to an internal note that the customer cannot see. Where a figure depends on an assumption, keep that assumption understandable.
Use the billing and tax settings appropriate to your business and confirm consequential requirements with the responsible accounts person. This page describes the quote workflow rather than determining the correct commercial or tax treatment of a particular transaction. A calculated amount does not establish that the agreement includes every condition the business needs to communicate.
During the trial, change a quantity or a proposed item and inspect the resulting total and description together. The exercise should show whether the updated proposal remains coherent. A technically correct recalculation can still leave a confusing customer document if the scope text describes the previous version of the work.
WorkOrderPro's public quote-review workflow can display a single proposal or configured proposal options. Where options are present, the customer-facing experience can distinguish the available choices and the selection required for approval. Demonstrate the full preparation and review path in the intended account setup so the office understands how the choices are represented.
An option should explain a meaningful difference in proposed work, not simply repeat the same description with a different total. Identify what is included in each choice and keep the comparison understandable. The responsible person still determines technical suitability. An option card is a commercial presentation, not a recommendation that every displayed alternative is appropriate in every circumstance.
Use a trial customer view and ask a colleague to explain the difference between the choices. They should recognise which option is being selected and what happens after that decision. If your business needs a more specialised proposal or design comparison, identify that requirement separately rather than assuming the general option workflow satisfies every format.
A customer-facing review is an important part of the quotation handover. WorkOrderPro has a public quote-review page for valid approval links, with proposal information and approve or decline actions. The recipient does not need an ordinary team account to use that public review page. The link itself provides access to the specific review, so send it only through the intended customer process.
Demonstrate the actual link-generation and delivery workflow configured for your business. A working review page and successful message delivery are separate things. Confirm any required messaging connection, plan availability and recipient information rather than assuming WhatsApp or email delivery is already configured simply because an approval page exists.
Open a trial proposal as the recipient and inspect its site, scope, line items and total. Check the result of the decision in the office. The exercise is complete when the reviewer can identify the current proposal and the recorded outcome, not merely when a link has been created or a message has been submitted for delivery.
Review the customer page on a small screen as well as the office display. Long descriptions, several options or unfamiliar units can make a proposal harder to compare even when the underlying calculation is correct. Ask the recipient to identify the site, intended work and final amount before selecting an action. If they misunderstand a description, improve the wording and review the current proposal again. This keeps the decision focused on the work offered rather than the mechanics of finding a button.
Approval links are intended for a specific review, and their validity can end. WorkOrderPro validates a link before presenting or accepting the decision. The customer should not be expected to approve through an invalid or already-used link. If the review cannot proceed, the office needs a clear way to check the current proposal and arrange the appropriate next action.
Test an unsuccessful or no-longer-valid review alongside a successful approval in the demonstration. Ask the office participant to explain how they will help the customer without treating the original request as accepted. The relevant question is what decision is currently recorded and which proposal the customer needs to review now.
Do not assume that reopening a link changes an earlier decision or that a new message automatically establishes a new agreement. Preserve the current commercial context. If the scope has changed, make the revised proposal clear before requesting another review. This helps prevent the team from relying on a decision that concerned different work.
An outstanding proposal means the next decision has not yet been established through the relevant process. A declined proposal means the customer has chosen not to proceed with that proposal. These situations need different follow-up. The office should recognise the current position without assuming silence is acceptance or treating every uncompleted job as a scheduling problem.
Record the next action appropriate to the customer relationship. The person handling the account may need clarification, a revised scope or a decision to close the request. Keep that responsibility explicit. An approval feature should support the conversation by preserving its outcome, rather than encourage repeated requests that ignore the customer's recorded response.
| Customer-review situation | What the office needs to establish | Next action to consider |
|---|---|---|
| Proposal prepared | The scope and intended approving contact | Review the customer-facing output |
| Review requested | Which current proposal was provided | Wait for or follow up the relevant decision |
| Clarification requested | The question or proposed change | Prepare a clear response or revision |
| Proposal approved | The work or option covered by the decision | Review readiness for the next operational step |
| Proposal declined | The recorded decision and current context | Agree an appropriate account follow-up |
| Link unavailable | Whether the current review remains valid | Check the proposal before arranging another review |
A customer may discuss a proposal in person or by telephone. The office needs an accurate record of the relevant decision and who made it. Demonstrate the approval methods available for the job and selected plan. A note about a conversation, a signature workflow and a public link decision are different records and should not be described as interchangeable.
Do not assume the system automatically records audio, sends a confirmation message or captures every contextual detail of a verbal conversation. If a particular approval method or confirmation process is essential, inspect it directly. The responsible person should understand what the saved record establishes and what additional process the business uses to confirm agreement.
Use a trial where the customer asks a question before deciding. Ask the office to distinguish the discussion from approval of the proposed work. This keeps the commercial position clear and prevents a helpful conversation note from being treated as a broader decision than the customer actually made.
Additional work should remain distinguishable from the original agreement. The customer may request another task or an assessment may reveal a change in the proposed scope. Keep enough context to explain what changed, why it changed and which decision is now required. Simply overwriting the earlier description can make the final record difficult to interpret.
Review the effect on price, timing and preparation before treating the change as authorised. The person available on site may need to refer the decision to another contact. Keep the outstanding approval visible and assign responsibility for follow-up. A technician recording the request is not the same as the customer approving the resulting additional work.
Include a variation after the trial job has been scheduled. Ask the field participant and office reviewer to identify the currently agreed scope and the proposed addition. They should be able to explain the next step without consulting separate private messages. The quotation workflow is more useful when it supports this ordinary change rather than only the first ideal proposal.
An approved quotation establishes a commercial decision about the proposal; the office still needs to review operational readiness. Confirm the relevant people, materials, access and appointment arrangements before committing the visit. Approval should not be described as automatic proof that every prerequisite is satisfied or the crew is available immediately.
Use the dispatch workflow to evaluate the next handover. The attending user should see a brief that reflects the current agreed work. If the schedule changes, confirm how the office and field users identify the latest plan. A useful connection between quoting and dispatch preserves the scope rather than asking the technician to infer it from a total alone.
Test the handover with a different employee from the person who prepared the proposal. They should understand the relevant site, work and outstanding operational action. This shows whether the saved quotation supports execution after the sales conversation has ended, which is often where an apparently complete proposal still needs office attention.
The final office review should compare what was agreed with what was actually performed. A completed visit may include an unresolved item, returned material or additional request that was not approved. The billing reviewer needs that context before preparing the customer charge. A quote total should not automatically be treated as proof of the final outcome.
Inspect the customer-facing document and relevant references in the trial. Check that the scope, quantities and current commercial position remain understandable. If the business needs deposits, stage payments or a specialised reconciliation process, demonstrate the full arrangement separately. A quote builder and final invoice do not automatically provide every project-accounting capability.
Ask a colleague who did not attend to explain the proposed and performed work from the saved records. If they need another conversation, identify the missing information and improve the handover. The useful result is a coherent commercial story from request through agreement to the office review, including the details that changed along the way.
Use one representative customer, site and proposal with an ordinary scope change. Include a public review where configured, inspect the decision record and follow the approved work into an appointment brief. Add one unsuccessful or outstanding review so the office can practise the next action when the customer decision is incomplete.
| Evaluation item | Evidence to inspect |
|---|---|
| Clear proposal | A colleague can explain the work and amount |
| Correct recipient | The relevant approving contact and site are identifiable |
| Meaningful options | The customer can distinguish configured choices where used |
| Recorded decision | The office can identify what was approved or declined |
| Operational handover | The attending team sees the current agreed scope |
| Changed work | A variation remains distinct from the original agreement |
Review the intended plan and full active-team total on the pricing page. Active administrators, dispatchers and field users count; disabled accounts are excluded. Confirm the approval methods and delivery configuration your business needs before rollout. A confident purchase decision comes from a demonstrated proposal-to-work handover, with the customer decision, next action and complete subscription cost all clear.
Identify the customer, intended site, proposed work and relevant labour or material lines. Review quantities, units, totals and the scope boundary. Another employee should be able to explain what the customer is being asked to approve without hearing the original conversation.
WorkOrderPro has a public quote-review page for valid approval links, with proposal information and approve or decline actions. The recipient does not need an ordinary team account for that page. Demonstrate link generation and the configured delivery workflow separately.
The public review workflow supports a single proposal or configured options and the relevant selection. Demonstrate the complete preparation and review path in your intended setup. Options should describe meaningful differences in work, with suitability verified by the responsible person.
No. A review page and successful message delivery are separate parts of the process. Confirm the required connection, plan availability and recipient details, then demonstrate the channel your business intends to use.
The review checks link validity before presenting or accepting the decision. The office should check the current proposal and recorded outcome before arranging another review. An unavailable or already-used link should not be treated as approval of new or changed work.
Do not assume automatic audio capture or confirmation-message delivery. Demonstrate the approval methods available for the job and selected plan, and understand what the saved record establishes. A conversation note, signature and public-link decision are different records.
No. Approval concerns the proposal; the office still reviews people, materials, access and appointment arrangements. Hand the current agreed scope into the field brief and keep operational prerequisites visible.
Count active administrators, dispatchers and field users; disabled accounts are excluded. Review the current base fee, per-active-user charge, billing cycle and VAT. Confirm the approval methods and delivery setup needed for the workflow you demonstrate.
Use a representative job, inspect the office result and confirm your essential requirements and full active-team subscription.