Give every inquiry a next step.

Start with the work you already have.

An inquiry arrives in an inbox, a conversation, or a form. It becomes difficult to manage when nobody owns the reply or the next action exists only in memory. A useful system makes the handoff visible.

Use the fictional example in the workspace first. For your own practice, use brief references and information you have permission to manage. Keep contact details, confidential conversations, and client files in their appropriate private systems.

No account or purchase is required. The workspace sends no inquiry entries to us. Saving on your device is optional; an exported workspace can be restored later.

1. Define what your words mean.

Use stages consistently. These are operating definitions for this exercise.

• New inquiry: interest has arrived and a first response is needed.
• In conversation: you are clarifying the request and whether you can help.
• Meeting arranged: a conversation has been agreed.
• Proposal sent: the prospect is considering a defined scope.
• Won: the inquiry has progressed to agreed work. This does not establish that payment was collected.
• Closed: no further follow-up is planned; record the reason in your own appropriate business records.

Practice: choose a response and review standard you can honor. For example: “Reply within one business day and review open inquiries each morning.” Adjust it to your actual availability. Record the standard in the workspace.

2. Assign one owner.

The owner is responsible for the next move. A team name or a shared inbox can help route work, but a person should know when the responsibility belongs to them.

Practice: add an inquiry with a short reference, the request, the received date, and an owner. Choose the stage that describes what has actually happened.

Worked example: Cedar Studio asks about a booking website. Avery owns the first response. The record begins as a new inquiry; no sale or payment has occurred.

3. Name the action and its date.

Write an action someone can perform. “Follow up” is vague. “Ask which booking process needs improvement” tells the owner what to do. Choose a date for the next review or action.

Practice: give each open inquiry a next action and a follow-up date. Edit the Cedar Studio example and move its review date. Open the Due view to see which active records need attention.

Due now includes today and earlier dates. Won and closed records stay out of that queue. Dates organize your review; this workspace does not send reminders or messages.

4. Close the loop and keep evidence.

At each review, confirm what happened, update the stage, and choose the next action. Keep your review dates honest. Closing a record should describe an actual decision or outcome.

1. Review the Open and Due views.
2. Check that every active inquiry has an owner, action, and date.
3. Update one record to reflect a real action or a clearly labeled fictional exercise.
4. Export a CSV for a spreadsheet and a workspace file for restoration.
5. Complete the review checklist and export your evidence.

Reflection: which handoff was unclear before this exercise? What did you change? What still depends on memory? When will you review the system again?

Your completion evidence

Keep your response standard, a completed inquiry workspace, and a brief reflection. Use fictional examples or redact private details if you choose to discuss your work. Public posting is optional.

The checklist is your own review record. Course completion requires doing and reviewing the work; a checkbox alone is not an independently verified credential.

Connect the system when the process is clear.

An implementation conversation can cover a business intake form, a shared pipeline, assigned ownership, reminders, reporting, exception handling, and an operating handoff. Agree scope, responsibilities, access, and completion evidence before implementation.

Opening the help page does not send your workspace records. Choose separately what you share through its request form.