A more complete starting point
Use forms to ask for the information your service needs.
AMS · Connected business workflows
Turn a request into work your team can start.
Collect the essentials, prepare the brief and give the next person the context.
Turn a vague request into work your team can start.
For service businesses collecting enquiries and preparing a useful brief. Give the next person the details they need before the work starts.
“Can you help?” is a conversation, not a brief.
The request arrives without the scope, the deadline or enough context. Your team spends its first exchange asking the same basic questions, then rewrites the answers for somebody else.
Collect the essentials. Give them a useful structure.
Forma Studio requests an autumn launch. The form captures the business, the work needed and the target date. A person reviews the response and prepares the working brief.
Fictional people, records and figures. This example does not change a live workspace.
- The work
- A request for an autumn launch arrives with a business name, deliverables and target date.
- The people
- The requester supplies the details. A person reviews them, writes the brief and chooses the next owner.
- Where to start
- Choose the questions needed to assess the service, then make the form available to the requester.
- Client and brand context
- A response is not automatically a client, project or task. Add the appropriate business context and next action after review, or configure a supported workflow explicitly.
Follow the work, step by step
Ask better questions
Start with more than “Can you help?”
- What you do
- Use a form to collect the business, the request and the timing. A consistent starting point helps your team understand the work.
- What changes
- The response names Forma Studio, describes the 12-asset launch and gives a target date of 21 October.
- Why it helps
- The person assessing the request has concrete information to discuss with the requester.
Business name, work needed and target launch are separate required questions.
Prepare the brief
Make the request useful to the team.
- What you do
- Review the response, then prepare a working document that sets out the scope, deliverables and next people involved.
- What changes
- A person turns the response into the Autumn collection brief, recording deliverables and naming Nour and Layla.
- Why it helps
- The next person receives a working agreement rather than a copied fragment of a conversation.
The brief names the work, the review date and the people involved.
Make the handoff clear
Show what happens after the brief.
- What you do
- Use a diagram to explain the review path and keep supporting files with the work. The team chooses each next step.
- What changes
- The diagram shows Brief → Review → Launch assets. It explains the intended process; it does not run it.
- Why it helps
- Discuss who checks the brief and what should happen next before handing over the work.
Follow the connectors from the brief through review to the assets.
What your team gains
A brief people can use
Prepare the scope in a document, then export or share the supporting material as appropriate.
An understandable process
Use a diagram to explain who reviews the work and what happens next.
Prepare your workflow
- Choose the fields your team needs to assess a request, including required information.
- Place the form where your audience will find it, alongside a page explaining the service.
- Review submissions, prepare the brief and assign the next action to a person.
A form submission and a project task are separate steps here. Any automated connection needs a supported trigger, action and explicit workflow configuration.
Understand each tool without leaving this page
Forms — its role in this workflow
- What it does
- Forms collect structured responses using fields and validation chosen for the request.
- In this example
- Ask for the business name, work needed and target date so a person can assess the autumn launch.
- What to prepare
- Decide what must be required. A submitted response stays a response; creating a lead or task is a separately configured step.
Landing pages — its role in this workflow
- What it does
- A landing page explains the service and gives visitors a clear place to take the next step.
- In this example
- Explain the launch service before inviting someone to complete the request form.
- What to prepare
- Prepare the service content and the form destination. Review publication and access settings for the page you intend to share.
Documents & PDFs — its role in this workflow
- What it does
- Documents give the working brief a readable structure that people can review and use.
- In this example
- Turn the reviewed request into the Autumn collection brief, with deliverables and the people responsible.
- What to prepare
- Review and edit the content before sharing or exporting it. The form-to-document transition shown here is a person’s preparation step.
Diagrams — its role in this workflow
- What it does
- Diagrams make a process visible through connected nodes and decision points.
- In this example
- Show how the brief reaches review before the team prepares launch assets.
- What to prepare
- Agree the meaning of the path with the team. Drawing a connector explains a process; it does not execute an automation.