A homeowner asks for a different cabinet layout. An installer finds a condition that was not visible during estimating. A drawing revision changes the work. The useful first step is to preserve what happened, then compare it with the agreed scope before assigning a price or calling it approved.
This guide offers a recordkeeping workflow you can use with your current tools. Follow the project's agreed change procedure; these records alone do not establish a right to additional payment.
1. Capture the original observation
Record the date, job location, who made the request and what was observed. Separate a person's request from your interpretation of its effect on the work.
- Keep original photos and documents. Add annotations as a separate reviewed view so the original remains available.
- Name the drawing sheet and revision being discussed. A screenshot of a detail should stay linked to the full sheet.
- For audio, obtain the appropriate consent and confirm which sources are actually captured. Microphone-only recording may not include remote participants.
- Write down what is missing: dimensions, access, finish selection, schedule constraints or the person who needs to clarify the request.
A useful note describes an observable condition: “Backing is requested at the revised cabinet location; the wall remains open.” Avoid turning that into “approved extra work” before scope and authority are reviewed.
2. Compare it with the confirmed scope
Find the applicable scope version, its supporting drawings, exclusions, allowances and approved amendments. A generated scope draft is not the confirmed baseline.
Give the observation one of three provisional outcomes: included work, potential additional work, or unclear. Save the specific scope passage or drawing reference behind that judgment. If the source does not resolve the issue, record the question instead of inventing an exclusion.
Check whether the same request has already been recorded. Link repeated observations to the existing change rather than pricing the same work twice.
3. Review quantities and company prices
List the proposed work and exclusions before building a price. Verify quantities against field measurements or calibrated drawing geometry; unknown scale means an area or length is not ready to price as a physical measurement.
- Identify the source and effective date of each labor or material rate.
- Check quantities, units, waste assumptions and any assembly components.
- Keep supplier cost separate from the company's reviewed selling price.
- Record schedule effects and unresolved conditions as questions or qualifications.
Leave a missing quantity or rate unresolved until someone supplies and reviews it. An AI suggestion does not fill the gap simply because it sounds plausible.
4. Record a decision on the exact version
Identify the person authorized to decide under the project's process. Present the scope, price, exclusions and selected supporting attachments together, with a clear version identifier.
Retain the actual decision, who made it, when it was recorded and the version they reviewed. An employee's internal attestation, a development test or a drafted approval request is not a customer decision.
If the scope, price or attachments change, create a revised version and obtain the required new decision. Keep the earlier record as history instead of carrying its approval label onto revised work.
5. Keep billing and payment separate
Check that the approved version is the version being used for the customer invoice. Keep a link back to the change and its evidence so another person can understand the charge.
A draft invoice, an exported PDF, an issued invoice and a recorded payment are separate events. A download should not issue an invoice, and an issued invoice should not become paid until a payment is recorded. Review supplier invoices in their own ledger rather than treating them as customer receivables.
A fictional renovation example
A revised cabinet wall
The homeowner requests a new cabinet location. A field note says backing may be needed before the open wall is closed. The crew retains a photo, the request and the current drawing revision.
The manager compares those sources with the confirmed scope. If the backing requirement is unresolved, the record stays “unclear” while the team asks for clarification. The photograph alone does not prove additional entitlement.
After scope and quantities are reviewed, Version A describes backing only. The customer's recorded decision applies to A. A later request adds patching and painting, producing Version B. B needs its own pricing review and decision; A's status does not authorize billing B.
The approved version can then support an invoice draft. Its PDF remains a download until the explicit issuance step, and its balance stays outstanding until an attributed payment is recorded.
A reusable review checklist
Copy these fields into a job note or your existing change form:
- Job, location, observation date and requestor.
- Original photos, notes, audio or documents; drawing sheet and revision.
- Confirmed scope reference and approved amendments checked.
- Included, potential additional work or unclear; supporting reason.
- Missing information and the person responsible for clarification.
- Reviewed quantities, units, rate sources and effective dates.
- Proposed scope, exclusions and schedule effects.
- Exact change version, decision-maker, decision and selected attachments.
- Invoice draft or issued invoice reference, with payment recorded separately.
Questions worth resolving
Does a field photo prove work is billable?
It can support what was observed. Scope, agreed procedures, quantities, pricing and the authorized decision still need separate review.
Can an AI flag approve a change?
No. A flag is a suggestion for review. It must not change permissions, establish approval, invent a quantity or record a payment.
What if part of the meeting was not transcribed?
Keep the original audio and show the missing coverage. Review the unfinished batches or add reviewed notes; do not present a partial summary as covering the whole recording.
How Evrulo fits
Evrulo brings job evidence, scope and pricing review, version-specific change records and separate billing views into one workspace. Manual entry and drawing measurements remain available when a model capability is unavailable.
The product is in development. AI drafts require review, and feature availability depends on the configured owned-model service. Development demonstrations do not establish production readiness or construction accuracy.
See the illustrative Evrulo workflow · Pricing and availability · Evrulo help