AIM Work Study

Prepare a Work Study without launching employee capture.

Share review-ready setup context for a process-focused Work Study. This does not send employee links, collect payment, schedule work, or activate service.

Start setup request Learn about Work Study

Process-focused, not individual ranking.Employee capture is not launched from this form.Confidential detail is not required.

Setup readiness

Configure the study before capture starts.

Share the business context needed to review a possible AIM Work Study. Keep the request practical and avoid confidential detail. This study is for process improvement, not employee ranking.

Review Data & Trust

Study duration: Recommended study duration: 5-10 business days.
Visibility: Participants and reporting viewers stay separate.
Launch state: Review request only. It does not create CRM or opportunity state, and no employee links are sent.

Business basics

Use plain business context so the request can be reviewed clearly.

Business namePrimary sponsorSponsor emailTimezoneApproximate participating team size

Study goal

Choose one practical operating question. The study should help explain process friction, not compare individual employees.

What do you want to understand?

Guardrail

Work Study should focus on systems, handoffs, tools, process friction, and work patterns. It is not a performance review, employee ranking, or attendance tracking.

After submission, Informive reviews the setup context before any participant access is prepared.

Team participation and visibility

Separate employee capture access from aggregate dashboard visibility.

Who should participate?Who should see aggregate visibility?

Visibility rule

Participants provide activity context. Sponsors/reporting viewers see aggregate visibility. Participant access does not provide aggregate dashboard access.

Read how Work Study handles employee trust

Roles and focus areas

Start with recognizable work functions and broad activity choices. These can be refined before employee links are shared.

Common role categoriesCommon focus areas

Example role groups

Front Desk, Technician, Customer Support, Manager, Admin, Field Staff, Production, Delivery.

Example focus areas

Follow-up, scheduling, handoffs, reporting, waiting, rework, tool switching, repeated admin.

Study quality and employee trust

Use this request to prepare a study employees can trust before any capture begins.

Use broad work areas instead of confidential customer or personnel details.

Keep the study question practical enough to review in a short study period.

Confirm who participates and who receives aggregate visibility.

Explain the employee trust boundary before any participant communication is prepared.

Employee announcement gap

Employee announcement preview is not currently implemented in this public setup form. S339 documents the gap and does not add notification or storage behavior.

Review before capture

This request prepares setup information for review. It does not send invitations, start tracking, create reports, create automatic recommendations, book a call, collect payment, create a proposal, create an opportunity, or activate service.

Study purpose

Define the operating question.

Frame what the business needs to understand before any participant access is prepared.

Participant boundary

Separate roles from people.

Use role groups and work areas so the study stays process-focused and employee-safe.

Review gate

Request review before capture.

This path prepares setup context. It does not send employee links or activate a study.