SALES DESK / REFERENCE 07
Carry the context.
Return the question.
A handoff should let the next person see where a statement came from, what remains undecided and who should answer next. Move the record and its questions together. A clean page is not a cleared job.
What needs to travel with the statement?
A useful handoff carries four things: the statement, the source, the unresolved boundary and the next reader’s question. HOMEFRONT’s record → source → question → return loop comes from the tested Passport and Sales Desk workflow. It organizes reports; it does not approve work.
- Capture. Keep the speaker’s report distinct from your own observation. Name the recorder and source.
- Compare. Put a discussion beside the actual writing reference. Keep differing reports and missing documents visible.
- Carry. Give the coordinator access, protection, selection and source questions with their next owner roles.
- Return. Record the answer and its source, preserve the earlier snapshot, and review the updated handoff with the next reader.
CSLB’s contract checklist asks about detailed work/materials and written changes. The source document belongs with the conversation; a Passport reference does not attach or authenticate it. CSLB — Homeowner contract checklist · CSLB — What is a contract?
What should the next reader be able to find?
The portable record
Retain complete JSON before moving to another desk. TXT/copy/print are readable handoffs; JSON reopens the structured record. Navigation does not carry page memory. Review every section before sharing.
The documents held separately
Identify the scope version, selection reference and evidence label you actually hold. Say when a document is missing. A source label is not an attachment or a verified signature.
The question register
Read the question, response, state and next owner together. A blank response is not a completed answer, even if an imported state says answered. An empty register does not prove that nothing remains to ask.
The return path
Ask the recipient to restate the unresolved point and name the next role to check it. Readback is a coordination check; it grants no authority and sends no reminder.
How would the record travel in a practice case?
Fictional demo data only — no real homeowner, address, employer, contract, permit, license, customer outcome or HOMEFRONT project.
Practice file: Fictional handoff practice / Cedar. The fictional visit note reports a preference to retain a counter. A separately held fictional draft does not resolve that work boundary; the finish remains unapproved. The office question travels to the field with those unknowns, rather than becoming an installation instruction.
| Record | What is actually recorded | Source and responsibility |
|---|---|---|
| Speaker report[9a710000-0000-4000-8000-000000000001] | Fictional homeowner preference: retain the existing counter if feasible. | Fictional SRC-A visit note; speaker report, not inspection |
| Discussion[9a710000-0000-4000-8000-000000000002] | Fictional discussion: review the retention preference against the draft scope before describing the work as included. | Fictional SRC-A visit note; discussed only |
| Scope boundary[9a710000-0000-4000-8000-000000000003] | Fictional draft scope does not resolve whether retaining or replacing the existing counter belongs in the work. | Fictional SRC-B draft scope held separately; no acceptance reported |
| Selection[9a710000-0000-4000-8000-000000000004] | Fictional finish sample Alpha | Fictional SRC-C sample note; choice unconfirmed |
| Next question[9a710000-0000-4000-8000-000000000005] | Fictional next question: which separately held written scope resolves the counter-retention preference, and which selection still needs a recorded decision? | Fictional SRC-D office comparison question |
| Authority question[9a710000-0000-4000-8000-000000000006] | Fictional exercise: which responsible building authority should answer the project-specific approval question? | Fictional SRC-D source question; no agency checked |
| Coordination[9a710000-0000-4000-8000-000000000007] | Fictional household report: keep the study access route available. Coordinator still needs to confirm the access/protection plan. | Fictional SRC-A access conversation; report only |
| Coordination[9a710000-0000-4000-8000-000000000008] | Fictional office action: obtain the scope clarification, record its source and return the amended record to the field lead. No start permission or reminder. | Fictional SRC-D proposed next action; not scheduled |
Download fictional practice Passport JSON
Before importing a practice file, export your current work. An import replaces the whole in-page Passport after your explicit confirmation; it does not merge records. The file above is an exercise, not a starting file for a real job.
What should a readback sound like?
FICTIONAL DIALOGUE / COORDINATION ONLY
Fictional sales recorder: “The retention preference is a speaker report from SRC-A. SRC-B doesn’t settle the work boundary. SRC-C is an unapproved selection. The office owns the question in SRC-D.”
Fictional field lead: “I can identify those reports. I still need the scope clarification and the coordinated access plan. I’m returning that question to the office; this record isn’t permission to begin.”
Fictional office coordinator: “I’ll record the answer and the actual writing reference when available, keep the prior snapshot and return the updated record. No answer or scheduled event is invented.”
A real recipient’s answer belongs in your record with its own recorder and source. Do not paste the practice dialogue as a real conversation or claim that an acknowledgment is a contract signature.
What changes when the source changes?
Keep the earlier exported snapshot. Identify which writing or selection was changed, record the new report with its source, and tell the next reader which question still remains. Preserve disagreement until it is actually resolved; do not promote the newest wording into an automatic approval.
Promise-to-Scope and Follow-Up have local content-change checks for their own linked records. A matching check is not authenticity or truth. The Concern Coach keeps historical exercises without an unchanged-source claim. Read the current record and each tool’s own warning before relying on an earlier output.
Use this return note in your own words: “This source changed. These records may need another review. This is the question and next owner role.” A handoff can get clearer without becoming ready to start.
How do you rehearse the complete loop?
- Download the fictional JSON and open it in Job Passport after protecting current work.
- Inspect the recorder/source, undecided scope, unapproved selection, authority question and office-owned next question. Keep their IDs and states.
- Open the same exported file in Production Handoff, read the complete appendix and print it. An executive preview is only a preview.
- Use Promise-to-Scope to prepare a user-owned clarification draft; apply only with a recorder/source. It determines no agreement.
- Use Follow-Up for a neutral agenda from actual questions and proposed next actions. Nothing is sent or scheduled.
- Return a sourced answer, export a new revision, reopen it and compare what changed. Preserve the earlier file; inspect every output before sharing.
The Appointment Prep desk supports the capture step. The Concern Coach supports explaining uncertainty without pressure. These tools remain independently usable; none is a CRM, job approval or synchronized team record.
Give the next reader the actual file.
Open the Job Passport for your own records. Use the reference desk when the unanswered question concerns a California role or consumer-rights source.
End of complete reading. Sources, limitations and fictional examples above belong with any printed or downloaded copy.