Feature 1
Build a guided submission
Configure the questions, content and defaults needed to create a useful record.
- Add fields
- Arrange pages
- Set incident defaults
Capability
Forms
Give staff a guided way to submit structured information without needing access to the underlying register.
The outcome
Collect complete, consistent information and create a usable incident record from every submission.
How it helps
How Forms works
This capability connects with the wider Apollo platform, so information can support action, evidence and reporting without being entered again.
Feature 2
Publish a simple staff experience
Let staff submit information and evidence without exposing administrative records.
- Preview the form
- Publish the version
- Create the incident
What is included
One capability, connected to the wider platform
Use the capability you need now while keeping its records, work and evidence ready for related capabilities across Apollo.
Included features
- Form catalogue
- Drag-and-drop form builder
- Questions, content and pages
- Default incident values
- Preview and publication
- Staff submissions and attachments
Connected platform
Keep exploring Apollo
See where this capability is available and the related capabilities and solutions that use the same connected information.
Workflows
Route record events through configured tasks, decisions and outcomes with accountable assignees.
Explore capabilityIncident Register
Record incidents, response activity, decisions, related work and lessons in one governed record.
Explore capabilityAvailable in:Organisational GRC
Questions and answers
Questions about Forms
Practical answers to common questions about managing this responsibility well.
Why does forms matter?
Collect complete, consistent information and create a usable incident record from every submission.
What should forms include?
It should cover form catalogue, drag-and-drop form builder, questions, content and pages, default incident values and preview and publication, with enough context to support action and explain decisions.
Who should be responsible for forms?
Ownership should sit with the person who can make decisions and keep the information current. A specialist or governance team may provide the method, but accountability should not be left with an unnamed group.
How do you keep forms current?
Set review dates according to risk and reassess after relevant incidents, material change, new evidence or overdue follow-up work. Preserve the history so changes remain explainable.
What evidence should be retained for forms?
Keep the source information, owner, review and approval history, supporting documents and resulting actions needed to show what was considered and what happened next.
See Forms in Apollo
Book a focused demonstration and we will show how the capability fits your current responsibilities, existing information and next practical priorities.