Input checklist

• Confirmed project code, name, status, location, and description.
• Relevant organizations, collaborators, affiliations, and roles.
• Confirmed keywords, parameters, values, units, amounts, and dates.
• Current, authorized reference documents in the correct scope.
• Deliverable objective, recipient, language, tone, period, and constraints.
• Unknown items that must remain blank, be marked for confirmation, or become a question.

Write the request

Name the document type offered in the interface, the project, and the expected result. State important limitations and ask for unknown data to be identified rather than invented. Avoid copying an entire file into the request when it is already attached or available in the authorized library.

Practical guidance

Start with the authoritative project record and the selected private or shared scope. Confirm which facts are established, which attachments are current and which values remain unknown. State the document language explicitly, and provide any document-specific code or recipient requested by the supported workflow instead of relying on an old conversation’s context.

Advanced tips

Prepare a short input record containing source versions and unresolved questions before a significant generation. Reuse that record during review to distinguish a wrong input from a generation error; correct the owning data before requesting another output.