Requests provide auditors with the information they need to evaluate an organization's compliance posture. Most objects in Hyperproof, including proof, can all be linked to a request. As with other objects in Hyperproof, requests can be assessed and assigned to members of the organization. Requests can be found in both audits and assessments.
​

When a request assignee is sure all relevant information has been linked, they can move it to Submitted to auditor status. This status alerts the external auditor that the request is ready for evaluation.

The fields on requests have been changed to ensure consistency and alignment with other work items (tasks, repeating tasks, evaluations, and issues).
​

ID
​

As with issues and evaluations, ID is now an auto-generated, unique field within an organization. The pattern for the IDs is R-N, where N is a sequential number.
​

All existing requests (active and archived) in an organization will receive a unique ID, starting with the oldest request, R-1.
​

Why the change? Per user feedback, requests will eventually be able to show up in more than one audit. To make this possible, requests require unique IDs that can be referenced from each audit.
​

ID renamed to Reference
​

The existing ID field was renamed to Reference, preserving existing values, to support the new auto-generated ID field. Reference allows customers to capture audit references provided by an auditor.
​

Example:

A request on a SOC2 audit might have a reference to CC1.1, which references the requirement against which the request is made.
​​

Description renamed to Summary, Notes to Description
​

To present all work items in a unified listing, this update renames some fields to create a common set of fields across work item types. The Description field is renamed to Summary, and Notes is renamed to Description. This aligns with how most users have been using these fields.

Import request CSV fields changed in August 2023. If you have a CSV that has not yet been updated, see the information below. For additional information on changes to request fields, refer to Requests as work items.

There is now a simple way to view objects linked to a request—typically controls and labels—in the Linked Objects section. Note that linked objects are only a utility for reference—they do not provide any inherited permissions.

​

​