Describe the task.
- Who starts it: a customer, office employee or technician?
- What information should already be available?
- Where does someone need another call, message or spreadsheet?
- What does a finished task look like to the next person?
Project preparation
Bring the task, the tools and one real difficulty.
You do not need a finished software specification. A clear example helps establish whether the first step should be a website change, an existing-tool adjustment or custom development.
List the existing tools.
Name the website, field-service platform, customer records, scheduling and messaging tools involved. Identify the account owners and any vendor restrictions you know about. Do not send passwords or access keys with the inquiry.
Include recurring exceptions.
Prepare anonymized examples of rescheduling, failed access and follow-up that remains unresolved. Note how staff currently find those cases and whether the customer receives an update.
Choose how to check the result.
Use a fictional inquiry and appointment to show that the right person receives the needed information. Include a repeated update and a changed visit. Decide how staff should see and correct an incomplete handoff.
Agree on ownership after launch.
Identify who maintains website services and approved instructions, who manages accounts and who handles a connection that stops working. Separate the first delivery from any ongoing support arrangement.
Start with a short summary.
Tell Faith Forge Labs about the task, your tools and any important date. A redacted example can be discussed later through an agreed channel.