Register Your AI Tool or Custom Prompt Workflow

1. Contributor & Team Details

Please complete this section so the review team knows who submitted the entry and how to follow up. Answer as accurately as you can; you can update details later if they change.

 

Full name

Employee, contractor, or staff identifier

Work email address

Department, business unit, or function

Job title or role

Which option best describes your current working arrangement with the organization?

 

Please describe your working arrangement

Manager, supervisor, or team lead name

How many people are on your immediate team?

What is your primary work arrangement?

 

Please describe your work arrangement

Country or region where you primarily carry out this work

Your usual time zone (UTC offset)

What is the best way to reach you about this submission?

Is this the first time you are registering an AI tool or prompt for your workflow?

 

What prompted you to submit this entry now?

 

Roughly how many entries have you submitted before?

Date of this submission

2. AI Tool & Use-Case Overview

Describe the tool and how it fits into your day-to-day work. Please avoid pasting personal, confidential, or third-party restricted material into any free-text field.

 

Name of the AI tool, assistant, or service

Provider, developer, or internal team that maintains the tool

Tool website, app link, or internal address (optional)

How do you currently access this tool?

 

Which team or person manages this account?

 

What did you find when reviewing the provider's data handling and retention settings for this free version?

 

When does the trial or evaluation period end?

Which category best matches what this tool does for you?

 

Please name the category that fits best

Describe the workflow or task where you use this tool, from input to final output

Which task types does this tool support for you?

 

What kinds of text do you draft most often?

 

Which languages, frameworks, or systems do your code or scripts target?

 

Which repetitive steps do you automate, and how are they triggered?

 

Please describe the other task type

How often do you use this tool in your normal work week?

Do you use a custom or reusable prompt with this tool?

 

Paste your prompt text or a shortened version of it, with any personal or confidential details removed

 

What guidance or default instructions, if any, do you give the tool when you use it?

Prompt name or internal label

Prompt version or date of last revision

Which kinds of input do you normally provide to the tool?

 

Please describe the structured data you provide and how it is prepared

 

Please describe the other input type

What kind of output do you typically receive?

 

How do you decide which recommendation to act on?

Do you review or edit the tool's output before it is used or shared?

 

Please describe your review or editing steps

 

Thank you for the honest answer. Many teams add a short review step before outputs are shared, so you may wish to consider one and update this entry later.

How reliable do you find the tool's output for this specific use case?

Please rate the tool on the following aspects for your use case

Poor

Below expectations

Meets expectations

Exceeds expectations

Outstanding

Accuracy of the output

Relevance to the task

Consistency across repeated runs

Ease of use

Speed of results

Ease of correcting mistakes

Prompt and Use-Case Inventory

Prompt or use-case name

Task it supports

Model or tool version used

Last tested

Works as intended

Notes or known quirks

A
B
C
D
E
F
1
Weekly status summarizer
Draft weekly project updates
General assistant, current release
2/2/2026
Works best when notes are grouped by topic first.
2
Meeting action extractor
Turn meeting notes into action items
Meeting summary tool, current release
2/9/2026
Sometimes merges two owners into one line; needs a manual check.
3
 
 
 
 
 
4
 
 
 
 
 
5
 
 
 
 
 
6
 
 
 
 
 
7
 
 
 
 
 
8
 
 
 
 
 
9
 
 
 
 
 
10
 
 
 
 
 

3. Data Privacy & Compliance Check

This section helps your organization understand what kind of information passes through the tool. It records your observations only and does not provide legal, privacy, or compliance advice. If you are unsure about anything here, please speak with your internal privacy, security, legal, or compliance contact before entering sensitive information.

 

What is the highest sensitivity of information you typically enter into this tool?

 

Which categories of personal information are involved?

 

What makes you unsure about the sensitivity level?

Have you entered information that could identify an individual person?

 

Which steps do you take before entering that information?

 

Thank you for noting this. Consider adding one of the earlier steps before your next use, and update this entry when your approach changes.

 

Thank you. Please continue to avoid entering identifying information unless your internal guidance clearly allows it.

Have you entered confidential, unpublished, or restricted business information into this tool?

 

Please describe the type of information and any safeguards you applied before entering it

Which safeguards do you apply when using this tool?

 

Please describe your record-keeping approach

 

Please describe the other safeguard

Where is the tool's output stored after it is generated?

 

Please name where the output is stored

Has this tool or use case been looked at by an internal privacy, security, legal, or compliance contact?

 

Reviewer name or team, and the date of that review

 

Would you like help requesting an internal review?

Does the tool provider state where data is processed or stored?

 

Please note the stated processing or storage location

 

You may wish to review the provider's documentation or ask an internal contact before entering sensitive information into this tool.

Known limitations, risks, or concerns you have noticed with this tool

How confident are you that this use case fits your organization's internal policies and guidance?

I confirm that my answers in this section reflect my own observations, and that I have not included confidential source material anywhere in this form.

4. Expected Productivity ROI

Share your best estimates of the time and quality effects of using this tool. Estimates are welcome; you do not need exact measurements. Figures are used for internal planning discussions and are not a guarantee of results.

 

Reference formula used in the table below

Monthly Hours Saved=Times per Week×Minutes Saved Each Time×460\text{Monthly Hours Saved}=\frac{\text{Times per Week}\times\text{Minutes Saved Each Time}\times 4}{60}

 

Estimated minutes saved on a typical task thanks to this tool

Approximate number of times this task occurs each week

Estimated value of one hour of your working time, in your local currency

Task-Level Time and Value Estimate

Task description

Times per week

Minutes saved each time

Estimated hourly value in local currency

Monthly hours saved

Estimated monthly value

A
B
C
D
E
F
1
Drafting weekly status summaries
5
25.0
$45.00
8.33
$374.85
2
Summarizing long project documents
3
40.0
$45.00
8.00
$360.00
3
 
 
 
 
0.00
$0.00
4
 
 
 
 
0.00
$0.00
5
 
 
 
 
0.00
$0.00
6
 
 
 
 
0.00
$0.00
7
 
 
 
 
0.00
$0.00
8
 
 
 
 
0.00
$0.00
9
 
 
 
 
0.00
$0.00
10
 
 
 
 
0.00
$0.00

Overall, how has this tool affected the quality of your work output?

Please rate how much you agree with each statement about this use case

Strongly disagree

Disagree

Neutral

Agree

Strongly agree

It reduces repetitive work

It makes my output more consistent

It frees time for higher-value work

It speeds up turnaround for stakeholders

It reduces errors or rework

It improves my confidence in first drafts

Which outcome matters most to you in this use case?

 

Please name the outcome that matters most to you

Have you compared results before and after you started using this tool?

 

Please describe what you compared and what you noticed

 

Would you like simple ideas for measuring the effect over time?

Known cost of using this tool, such as subscription, usage fees, or internal charges (optional)

How many colleagues could realistically adopt this use case in the next three months?

Do you expect other teams or departments could benefit from this use case?

 

Which teams could benefit, and why?

5. Peer-Sharing & Prompt Repository Authorization

This section records how you would like your entry to be handled internally. Your choices here describe your preferences for internal sharing only and can be changed at any time by contacting the repository curators. Please make sure any prompt text or examples you shared earlier contain no personal, confidential, or third-party restricted information.

 

Do you authorize this submission to be added to the internal prompt and tool repository for colleagues to view?

 

What visibility level would you prefer for your entry?

 

What would you prefer instead?

How would you like to be credited if your entry is shared internally?

What may colleagues do with your shared prompt or use case?

 

Are there any conditions you would like to add to internal sharing?

 

How should external discussion be handled?

I have removed personal, confidential, and third-party restricted information from any prompt text, examples, or attachments included in this submission.

Are you willing to demonstrate or present this use case to colleagues?

 

Which session format would suit you best?

 

That is completely fine. Your entry can still be shared in written form if you authorized sharing above.

Which topics could you cover in a peer session if needed?

 

What is your most useful prompt-writing tip?

 

Please name the other topic

How useful do you think this use case would be to colleagues outside your own team?

Best contact for questions about this use case

Preferred date for a short follow-up conversation (optional)

Anything else you would like the repository curators to know?

Typed or drawn confirmation that the details in this form are accurate to the best of your knowledge

Analysis for AI Tool & Prompt Usage Registration Form for Employees

Important Note:

This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.

AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.

This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.

Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.

Please delete this section before publishing your form. See our Terms of Service for further information.


 

Form Overview

This registration form is designed for corporate employees to log AI tools and custom prompts they use in daily workflows. It is organized into five clearly defined sections: Contributor & Team Details, AI Tool & Use-Case Overview, Data Privacy & Compliance Check, Expected Productivity ROI, and Peer-Sharing & Prompt Repository Authorization. The structure moves logically from identity capture through tool description, privacy observations, productivity estimates, and finally sharing preferences, creating a coherent narrative flow that mirrors the review process an internal team would follow.

 

Section 1: Contributor & Team Details

This section establishes who submitted the entry and provides context for follow-up. The introductory paragraph sets expectations by noting that details can be updated later, which reduces anxiety about getting everything perfect on the first pass.

 

Full name — Captures the contributor's identity so the review team can attribute the submission and reach out if clarification is needed. The placeholder example provides a clear format expectation.

 

Employee, contractor, or staff identifier — Collects an organizational identifier that likely supports record-keeping, duplicate detection, and linking the submission to existing internal systems. The placeholder suggests a structured ID format.

 

Work email address — Provides a direct communication channel for follow-up questions or updates. Using a work email rather than a personal one helps keep organizational records consistent.

 

Department, business unit, or function — Helps the review team understand the organizational context of the submission, which can inform how widely the use case might apply.

 

Job title or role — Adds professional context to the submission, helping reviewers understand the type of work the tool supports.

 

Which option best describes your current working arrangement with the organization? — Distinguishes between employment types, which may be relevant for how the organization manages tool access and internal sharing. The conditional follow-up for "Other" allows respondents to describe arrangements not covered by the predefined options.

 

Manager, supervisor, or team lead name — Identifies a point of contact in the contributor's reporting line, which may support internal review or approval workflows.

 

How many people are on your immediate team? — Collects team size as optional context, potentially useful for estimating the broader impact of a tool adoption.

 

What is your primary work arrangement? — Captures whether the contributor works on-site, remotely, or in a hybrid model. This is optional and includes a conditional follow-up for "Other," providing flexibility.

 

Country or region where you primarily carry out this work — Records the geographic context of the work, which may be relevant for understanding regional considerations around tool usage and data handling.

 

Your usual time zone (UTC offset) — Supports scheduling of follow-up conversations and helps reviewers account for regional differences in communication timing.

 

What is the best way to reach you about this submission? — Allows the contributor to specify their preferred communication channel, improving the efficiency of any follow-up.

 

Is this the first time you are registering an AI tool or prompt for your workflow? — Distinguishes between new and returning contributors. The conditional follow-ups capture either the motivation for a first-time submission or the approximate number of prior entries, giving the review team useful context.

 

Date of this submission — Records when the entry was submitted, supporting version tracking and chronological record-keeping.

 

Section 2: AI Tool & Use-Case Overview

This section is the core of the form, collecting detailed information about the tool, how it is used, and what it produces. The introductory paragraph includes a practical reminder to avoid pasting personal or confidential material into free-text fields, which is a thoughtful data-hygiene prompt.

 

Name of the AI tool, assistant, or service — Identifies the specific tool being registered. The placeholder uses generic descriptions, encouraging respondents to name the tool clearly.

 

Provider, developer, or internal team that maintains the tool — Captures who built or maintains the tool, which helps the organization understand whether it is externally sourced or internally developed.

 

Tool website, app link, or internal address (optional) — Provides a reference link for reviewers who want to learn more about the tool. Marked optional, which is appropriate since not all tools have a shareable link.

 

How do you currently access this tool? — Distinguishes between company-provided accounts, personal subscriptions, free versions, internal builds, and trials. The conditional follow-ups are particularly effective: they ask who manages a company account, what the respondent observed about data handling for free versions, and when a trial period ends. These follow-ups demonstrate thoughtful design tailored to each access scenario.

 

Which category best matches what this tool does for you? — Categorizes the tool's primary function, enabling the review team to group and analyze submissions by use type. The "Other" option includes a follow-up to capture custom categories.

 

Describe the workflow or task where you use this tool, from input to final output — Collects a narrative description of the end-to-end workflow. This is one of the most valuable fields in the form, as it captures the practical context that structured fields cannot.

 

Which task types does this tool support for you? — Allows multi-selection of task types with targeted follow-ups for drafting, code generation, automation, and other categories. This granularity helps the review team understand the breadth of the tool's application.

 

How often do you use this tool in your normal work week? — Captures usage frequency, which is essential for prioritizing review efforts and understanding the tool's operational significance.

 

Do you use a custom or reusable prompt with this tool? — Distinguishes between ad hoc use and prompt-based workflows. The yes follow-up asks for the prompt text (with a reminder to remove sensitive details), while the no follow-up captures any general guidance given to the tool. This dual-path design is well thought out.

 

Prompt name or internal label — Provides a short identifier for the prompt, making it easier to reference in the repository and in follow-up discussions.

 

Prompt version or date of last revision — Optional field that supports version tracking, useful for maintaining an up-to-date prompt repository.

 

Which kinds of input do you normally provide to the tool? — Multi-select field covering text, documents, spreadsheets, code, images, audio, video, and structured data. Conditional follow-ups for structured data and "Other" capture additional detail where needed.

 

What kind of output do you typically receive? — Captures the type of output produced, with a follow-up for "Recommendations or options" that asks how the respondent decides which recommendation to act on. This is a nuanced question that reflects awareness of human-in-the-loop workflows.

 

Do you review or edit the tool's output before it is used or shared? — Probes the quality-control step in the workflow. The no follow-up is notably non-judgmental, acknowledging the honest answer and gently suggesting a review step. This is an excellent example of supportive form design.

 

How reliable do you find the tool's output for this specific use case? — A five-point rating scale capturing the respondent's subjective reliability assessment, providing a quick quality signal.

 

Please rate the tool on the following aspects for your use case — A matrix rating covering accuracy, relevance, consistency, ease of use, speed, and ease of correction. This structured comparison is efficient and yields actionable data.

 

Prompt and Use-Case Inventory — A table collecting multiple prompt/use-case entries with columns for name, task, tool version, last tested date, works-as-intended status, and notes. The pre-populated example rows demonstrate the expected format and make the table approachable.

 

Section 3: Data Privacy & Compliance Check

This section records the contributor's observations about data sensitivity and safeguards. The introductory paragraph is well crafted: it clearly states that the section records observations only and does not provide legal or compliance advice, and it directs respondents to internal contacts if they are unsure. This is responsible framing.

 

What is the highest sensitivity of information you typically enter into this tool? — A six-option single-choice field ranging from public information to confidential records, with "Not sure" as a valid option. The follow-ups for personal information (asking which categories) and uncertainty (asking what causes the doubt) are practical and well designed.

 

Have you entered information that could identify an individual person? — Directly addresses the risk of entering personally identifiable information. The yes follow-up asks about specific mitigation steps, while the no follow-up provides a gentle reminder. The nested follow-up for "No specific steps yet" is supportive rather than punitive.

 

Have you entered confidential, unpublished, or restricted business information into this tool? — Probes whether sensitive business data has been shared with the tool. The yes follow-up asks for a description of the information and safeguards, capturing useful context.

 

Which safeguards do you apply when using this tool? — Multi-select field covering common protective practices. The follow-ups for personal record-keeping and "Other" capture additional detail. This field helps the review team understand the contributor's data-handling habits.

 

Where is the tool's output stored after it is generated? — Captures the storage destination of tool outputs, which is relevant for understanding data flow and retention practices.

 

Has this tool or use case been looked at by an internal privacy, security, legal, or compliance contact? — Asks whether internal review has occurred. The no follow-up offers to route the submission for review, which is a helpful and proactive design choice.

 

Does the tool provider state where data is processed or stored? — Optional question about data processing locations. The no follow-up provides a gentle suggestion to review provider documentation, which is proportionate and non-alarming.

 

Known limitations, risks, or concerns you have noticed with this tool — Open-ended field for the respondent to share their own observations. This is valuable for capturing real-world issues that structured questions might miss.

 

How confident are you that this use case fits your organization's internal policies and guidance? — A five-point confidence scale that captures the respondent's self-assessment without asserting any specific policy requirement.

 

I confirm that my answers in this section reflect my own observations, and that I have not included confidential source material anywhere in this form. — A checkbox confirmation that serves as a practical reminder and a lightweight attestation of data hygiene.

 

Section 4: Expected Productivity ROI

This section collects time-savings and quality estimates. The introductory paragraph sets expectations appropriately by noting that estimates are welcome and that figures are for internal planning, not guarantees.

 

Reference formula used in the table below — An equation element displaying the monthly hours saved formula. This transparency helps respondents understand how their inputs are used in calculations.

 

Estimated minutes saved on a typical task thanks to this tool — Captures per-task time savings as a numeric input with one decimal place, enabling precise calculations.

 

Approximate number of times this task occurs each week — Captures task frequency, a key variable in the time-savings formula.

 

Estimated value of one hour of your working time, in your local currency — Optional currency input that enables monetary value estimates in the table below.

 

Task-Level Time and Value Estimate — A table with pre-populated example rows that calculates monthly hours saved and estimated monthly value using formulas. The formula columns (ROUND(column2*column3*4/60,2) and ROUND(column5*column4,2)) automate the math, reducing respondent effort and improving consistency.

 

Overall, how has this tool affected the quality of your work output? — A five-point rating from "Much worse" to "Much better," capturing the respondent's perception of quality impact.

 

Please rate how much you agree with each statement about this use case — A matrix rating covering six statements about work reduction, consistency, time freed, turnaround speed, error reduction, and confidence. This structured approach yields comparable data across submissions.

 

Which outcome matters most to you in this use case? — Single-choice field with a follow-up for "Other," helping the review team understand what the contributor values most.

 

Have you compared results before and after you started using this tool? — Asks whether the respondent has done any before/after comparison. The no follow-up offers simple measurement ideas, which is a supportive touch.

 

Known cost of using this tool, such as subscription, usage fees, or internal charges (optional) — Optional currency input capturing the cost side of the ROI equation.

 

How many colleagues could realistically adopt this use case in the next three months? — Captures adoption potential, useful for planning internal rollouts.

 

Do you expect other teams or departments could benefit from this use case? — Asks about cross-team applicability, with a follow-up for yes that captures which teams and why.

 

Section 5: Peer-Sharing & Prompt Repository Authorization

This section records the contributor's preferences for internal sharing. The introductory paragraph clearly states that choices can be changed at any time, which reduces pressure on the respondent.

 

Do you authorize this submission to be added to the internal prompt and tool repository for colleagues to view? — The central authorization question. Both yes and no paths lead to mandatory follow-ups: yes asks for a visibility level, and no asks what the respondent prefers instead. This binary-with-branching design is efficient and respectful of contributor preferences.

 

How would you like to be credited if your entry is shared internally? — Offers five attribution options from full name to no attribution, giving the contributor control over their visibility.

 

What may colleagues do with your shared prompt or use case? — Multi-select field covering viewing, adapting, internal sharing, training materials, newsletters, and external discussion. The follow-ups for internal sharing conditions and external discussion handling show careful attention to contributor preferences.

 

I have removed personal, confidential, and third-party restricted information from any prompt text, examples, or attachments included in this submission. — A checkbox confirmation reinforcing data hygiene before sharing.

 

Are you willing to demonstrate or present this use case to colleagues? — Asks about willingness to present, with a follow-up for yes capturing preferred session format. The no follow-up is reassuring, noting that written sharing is still possible.

 

Which topics could you cover in a peer session if needed? — Multi-select field covering potential presentation topics, with follow-ups for prompt-writing tips and "Other."

 

How useful do you think this use case would be to colleagues outside your own team? — A five-star rating capturing the respondent's assessment of broader applicability.

 

Best contact for questions about this use case — Provides a specific contact point for follow-up about the use case, which may differ from the general contact captured earlier.

 

Preferred date for a short follow-up conversation (optional) — Optional date field for scheduling follow-up, giving the contributor control over timing.

 

Anything else you would like the repository curators to know? — Open-ended field for additional context, ensuring nothing important is left out.

 

Typed or drawn confirmation that the details in this form are accurate to the best of your knowledge — A signature field serving as a final confirmation of accuracy.

 

Overall Summary

This form is well-structured and thoughtfully designed for its purpose of registering AI tool and prompt usage in a corporate setting. Its five-section architecture follows a logical progression from identity through tool description, privacy observations, productivity estimates, and sharing preferences. The form makes effective use of conditional follow-ups throughout, tailoring questions to the respondent's earlier answers and avoiding irrelevant fields. The introductory paragraphs in each section set clear expectations and provide practical reminders about data hygiene. The inclusion of pre-populated example rows in tables, formula transparency in the ROI section, and non-judgmental language in follow-ups all contribute to a positive user experience. Areas for improvement include the overall length of the form, which may present a completion barrier for some respondents; the high number of mandatory fields across all sections, which could be reviewed to identify which are truly essential at the point of submission versus which could be collected in a follow-up; and the potential for some redundancy between fields such as contact preferences and best contact for questions. Additionally, the form could benefit from a progress indicator given its length, and the optional fields could be more clearly visually distinguished from mandatory ones to help respondents prioritize their effort.

 

Mandatory Question Analysis for AI Tool & Prompt Usage Registration Form for Employees

Important Note:

This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.

Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.

Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.

Please delete this section before publishing your form. See our Terms of Service for further information.

 

Mandatory Question Analysis

Question: Full name
Requiring this field ensures each submission can be clearly attributed to a specific contributor, supporting accurate record-keeping and enabling the review team to follow up with the right person. The form creator may wish to confirm whether informal display names or formal legal names better suit their internal record-keeping needs.

 

Question: Employee, contractor, or staff identifier
Making this field mandatory supports linking the submission to existing organizational records and helps prevent duplicate entries. The necessity of this field may depend on whether the organization maintains a formal identifier system that the review team can reference.

 

Question: Work email address
Requiring a work email ensures a reliable channel for follow-up communication and potential submission updates. This supports operational processing by giving reviewers a direct way to reach the contributor. Depending on organizational data-handling practices, consider whether a privacy notice about how contact details will be used would be appropriate.

 

Question: Department, business unit, or function
Making this field mandatory provides organizational context that helps the review team understand the scope and applicability of the submission. This supports record-keeping by enabling grouping and analysis of entries by business area.

 

Question: Job title or role
Requiring a job title adds professional context to the submission, helping reviewers understand the type of work the tool supports. This may inform decisions about internal sharing and peer-learning opportunities.

 

Question: Which option best describes your current working arrangement with the organization?
Making this field mandatory helps the review team understand the contributor's employment context, which may be relevant for how tool access and internal sharing are managed. The conditional follow-up for "Other" ensures that non-standard arrangements are captured.

 

Question: Manager, supervisor, or team lead name
Requiring this field identifies a secondary point of contact in the contributor's reporting line, which may support internal review or approval workflows. The necessity of this field depends on whether the organization's review process involves managerial oversight.

 

Question: Country or region where you primarily carry out this work
Making this field mandatory captures the geographic context of the work, which may be relevant for understanding regional considerations around tool usage and data handling. Requirements may vary by jurisdiction, and this field helps the review team account for those differences.

 

Question: Your usual time zone (UTC offset)
Requiring a time zone supports efficient scheduling of follow-up conversations and helps reviewers account for regional communication differences. This is a practical operational field that reduces coordination overhead.

 

Question: What is the best way to reach you about this submission?
Making this field mandatory ensures the review team knows the contributor's preferred communication channel, improving the efficiency of any follow-up. This is a practical field that respects the contributor's communication preferences.

 

Question: Is this the first time you are registering an AI tool or prompt for your workflow?
Requiring this field helps the review team distinguish between new and returning contributors, which may inform how they approach the review. The conditional follow-ups capture useful context regardless of the answer.

 

Question: Date of this submission
Making this field mandatory ensures each entry has a clear submission timestamp, supporting chronological record-keeping and version tracking. This is a standard operational field for maintaining organized records.

 

Question: Name of the AI tool, assistant, or service
Requiring the tool name is essential for identifying what is being registered. Without this field, the submission cannot be meaningfully processed or catalogued in the repository.

 

Question: Provider, developer, or internal team that maintains the tool
Making this field mandatory helps the review team understand the tool's origin and maintenance responsibility, which supports operational processing and potential follow-up with the tool's provider or internal team.

 

Question: How do you currently access this tool?
Requiring this field captures how the tool is accessed, which is relevant for understanding account management, data handling, and potential cost implications. The conditional follow-ups provide targeted detail for each access scenario.

 

Question: Which category best matches what this tool does for you?
Making this field mandatory enables the review team to categorize and group submissions by function, supporting analysis and prioritization of review efforts.

 

Question: Describe the workflow or task where you use this tool, from input to final output
Requiring a workflow description is central to understanding the practical application of the tool. This narrative field captures the context that structured fields alone cannot, supporting thorough review and potential peer-sharing.

 

Question: Which task types does this tool support for you?
Making this field mandatory captures the breadth of the tool's application, helping the review team understand its versatility and potential for broader adoption. The conditional follow-ups add useful detail for specific task types.

 

Question: How often do you use this tool in your normal work week?
Requiring usage frequency helps the review team prioritize submissions based on operational significance. Tools used daily may warrant different review attention than those used occasionally.

 

Question: Do you use a custom or reusable prompt with this tool?
Making this field mandatory distinguishes between ad hoc and prompt-based workflows, which is central to the form's purpose of registering reusable prompts. The conditional follow-ups capture the prompt text or general guidance as appropriate.

 

Question: Prompt name or internal label
Requiring a prompt name provides a short identifier that makes the entry easier to reference in the repository and in follow-up discussions. This supports organized record-keeping and efficient retrieval.

 

Question: Do you review or edit the tool's output before it is used or shared?
Making this field mandatory captures whether a quality-control step exists in the workflow, which is relevant for understanding the reliability of the tool's outputs in practice. This supports the review team's assessment of the use case.

 

Question: How reliable do you find the tool's output for this specific use case?
Requiring a reliability rating provides a quick quality signal that helps the review team assess the use case. This subjective assessment, combined with other data in the form, contributes to a more complete picture.

 

Question: What is the highest sensitivity of information you typically enter into this tool?
Making this field mandatory is important for understanding the data sensitivity context of the tool's use. This supports the review team's ability to assess whether appropriate safeguards are in place and whether further internal review may be warranted.

 

Question: Have you entered information that could identify an individual person?
Requiring this field directly addresses the risk of entering personally identifiable information, which is a key operational consideration. The conditional follow-ups capture mitigation steps or provide gentle reminders, supporting responsible data-handling practices.

 

Question: Have you entered confidential, unpublished, or restricted business information into this tool?
Making this field mandatory probes whether sensitive business data has been shared with the tool, which is relevant for the review team's assessment. The yes follow-up captures the type of information and safeguards applied.

 

Question: Has this tool or use case been looked at by an internal privacy, security, legal, or compliance contact?
Requiring this field helps the review team understand whether internal review has already occurred, which may inform their own review process. The no follow-up proactively offers to route the submission for review, which is a helpful operational touch.

 

Question: How confident are you that this use case fits your organization's internal policies and guidance?
Making this field mandatory captures the contributor's self-assessment of policy alignment, which provides useful context for the review team. This is a subjective measure and should be interpreted alongside other information in the form.

 

Question: I confirm that my answers in this section reflect my own observations, and that I have not included confidential source material anywhere in this form.
Requiring this checkbox confirmation serves as a practical reminder and a lightweight attestation of data hygiene. It reinforces the expectation that respondents provide accurate observations and avoid including sensitive material.

 

Question: Estimated minutes saved on a typical task thanks to this tool
Making this field mandatory ensures the review team has the core input needed for time-savings calculations. Without this field, the productivity estimates in the ROI section cannot be meaningfully computed.

 

Question: Approximate number of times this task occurs each week
Requiring task frequency is essential for the time-savings formula used in the ROI section. This field, combined with minutes saved, enables the calculation of monthly hours saved.

 

Question: Overall, how has this tool affected the quality of your work output?
Making this field mandatory captures the contributor's perception of quality impact, which complements the quantitative time-savings data. This qualitative signal helps the review team understand the tool's broader effects.

 

Question: Do you authorize this submission to be added to the internal prompt and tool repository for colleagues to view?
Requiring this authorization question is central to the form's purpose of managing internal sharing. Both the yes and no paths lead to mandatory follow-ups that capture the contributor's specific preferences, ensuring their wishes are clearly recorded.

 

Question: What visibility level would you prefer for your entry? (Yes follow-up)
Making this follow-up mandatory ensures that when a contributor authorizes sharing, their specific visibility preference is captured. This supports appropriate handling of the entry in the repository.

 

Question: What would you prefer instead? (No follow-up)
Making this follow-up mandatory ensures that when a contributor declines sharing, their alternative preference is clearly recorded. This supports respectful handling of the submission and prevents unintended disclosure.

 

Question: How would you like to be credited if your entry is shared internally?
Requiring this field ensures the contributor's attribution preference is recorded before any sharing occurs. This supports respectful handling of contributor identity in the repository.

 

Question: I have removed personal, confidential, and third-party restricted information from any prompt text, examples, or attachments included in this submission.
Making this checkbox mandatory reinforces data-hygiene expectations before the entry is shared. It serves as a practical reminder and a lightweight confirmation that the contributor has taken steps to protect sensitive information.

 

Question: How useful do you think this use case would be to colleagues outside your own team?
Requiring this rating helps the review team assess the broader applicability of the use case, which may inform prioritization of peer-sharing and repository curation efforts.

 

Question: Best contact for questions about this use case
Making this field mandatory ensures there is a specific point of contact for questions about the use case, which may differ from the general contact captured earlier. This supports efficient follow-up by repository curators and interested colleagues.

 

Question: Typed or drawn confirmation that the details in this form are accurate to the best of your knowledge
Requiring a signature serves as a final confirmation of accuracy and completeness. This supports record-keeping integrity and reinforces the contributor's responsibility for the information provided.

 

Overall Mandatory Field Strategy Recommendation

This form contains a substantial number of mandatory fields across all five sections — approximately 35 mandatory questions in total. While many of these fields are operationally important for the form's purpose, the high proportion of required fields may present a completion barrier, particularly for respondents who are filling out the form during a busy workday.

 

Balancing data collection depth against completion rates: Consider whether all currently mandatory fields are essential at the point of initial submission. Fields such as Manager, supervisor, or team lead name, Your usual time zone, and Best contact for questions about this use case could potentially be collected in a follow-up step or made optional without significantly impacting the review team's ability to process the entry. Reducing the mandatory field count even modestly can improve completion rates while still capturing the core information needed.

 

Conditional logic for targeted data collection: The form already makes excellent use of conditional follow-ups, particularly in the access-method, prompt, and privacy sections. This approach could be extended further. For example, fields like Prompt name or internal label could be made conditional on answering "Yes" to the prompt question, rather than being unconditionally mandatory. Similarly, the ROI fields could be grouped behind a question asking whether the respondent has time estimates available.

 

Best practices for mandatory field selection and placement: Generally, mandatory fields are most effective when they capture information that is essential for the form's core processing — identity, the primary subject of the submission, and authorization decisions. Fields that provide supplementary context, enrichment, or optional detail are often better left optional. Placing mandatory fields early in the form (as this form does with contributor details) helps establish momentum, but the sustained mandatory requirement through all five sections may cause fatigue. Consider a tiered approach: mandatory for core identity and authorization fields, recommended (but optional) for descriptive and estimation fields.

 

Observations on mandatory field placement: The mandatory fields are distributed across all five sections, with the heaviest concentration in Sections 1 and 2. Section 3 (Data Privacy & Compliance Check) also contains a high number of mandatory fields, which is understandable given the section's purpose but may benefit from review to determine which questions are truly essential versus which could be collected as part of an internal review process. Sections 4 and 5 have fewer mandatory fields relative to their total question count, which is a positive design choice. Overall, a review of the mandatory field list with the form's stakeholders — focusing on which fields are needed for initial processing versus which can be gathered later — could meaningfully improve the respondent experience without sacrificing data quality.

 

To configure an element, select it on the form.

To add a new question or element, click the Question & Element button in the vertical toolbar on the left.