Create documents and collect evidence

Open Management systems, choose a system, then open an entry from Requirements and find Governance artifacts. Expected templates are grouped as Required, Auditor expected, or Good practice. Their state can show Not in place, Draft, Awaiting approval, Not verified, Gaps found, or Approved.

An expected document and an assessment verdict answer different questions. Check document approval as well as assessment findings. Files and folders have no approval status; review the requirement assessment for their coverage. An evidence request describes what to provide and is not evidence by itself.

Create content from an expected templateCopy Anchor Link

1. Choose Create from template on a missing expected document, or Create or import for the general creation form.
2. Set Create content to Create from an expected template and select the Expected artifact template.
3. Read its preview, revision, outline, and checklist.
4. Review Also link to. Choose Only this requirement, every requirement in this system that expects the template, or every requirement in the workspace that expects it.
5. In Save content to, use the Domain destination or Choose another project. You need contributor access to the destination project. This individual creation flow does not automatically create a missing destination project.
6. Optionally enter an Artifact name and Artifact code, then submit using the action shown for the selected content family.
7. Read the result and any skipped links. Open the created content and review it before approval or assessment.

Wider linking can skip entries already fulfilled or excluded. When importing a document, links are added after the import finishes. If the requirement has no expected templates, import without a template or link existing content instead. A withdrawn template cannot create new content.

Import a file as a documentCopy Anchor Link

1. Choose Create or import, then set Create content to Import a file as a document.
2. Optionally select a Document template, or choose Import without a template.
3. Select a Source project you can read and a file whose text processing has completed.
4. Choose a destination project where you have contributor access. Review the Document name and any selected template defaults.
5. Request the import preview and read Review document import, including the destination, section outline, proposed defaults, and any missing template headings.
6. Correct blocking source violations before confirming the import. Once confirmed, it runs in the background; open the linked document to review the result when available.

The preview has not created a document or started a job. Source text is imported verbatim and source headings remain authoritative. An optional template provides a drafting checklist. Template defaults apply only as selected suggestions for the new draft; source content and your values take precedence.

An empty source, too many headings, excessive nesting, or text over the displayed limits can block import. Missing template headings are review guidance and can be reviewed after import. If the source, destination, or requirement changes after previewing, prepare a fresh preview before confirming.

Collect evidence in foldersCopy Anchor Link

Choose Create evidence folder for an expected external-evidence template. Review its domain destination or select Override destination for requested evidence (optional). Use domain destinations removes the temporary override. If there is no usable destination, choose a writable project or ask an administrator to configure one.

For additional evidence, use Add another evidence location and select the Evidence project when offered. Existing records can also be connected with Link evidence or Link content.

Inside an evidence folder:

1. Open Instructions to read the evidence request.
2. Select Upload files, or drop files onto the folder, when you have project contributor access.
3. Follow each upload's progress. Cancel a pending upload if needed; use its retry control after a failure.
4. Open a file to inspect it, use Previous files or Next files to browse, or choose Open in drive for the full folder.

If files cannot load, use Retry or open the folder in Drive. Check the file list before repeating an upload. No evidence uploaded yet means that records still need to be supplied; a request document alone does not satisfy that work.

Read linked artifacts through IMSCopy Anchor Link

Open a linked artifact from the requirement. The IMS reader adapts to its type: organizational document, contract, assessment, or timeline. For an organizational document, use the section outline and overview, inspect stakeholders, references, and controls, and choose Download Markdown if needed. For an assessment, search and filter Artifact Items and open an item. For a timeline, browse its available categories and events.

The reader can show remaining manual work from a template. Review that work and any template-update or history controls offered. Open in project appears when your project access permits it; use the project workspace for editing and approval work available there.

Activity offers requirement histories for links, assessments, and reviews. Full artifact change history requires project access. Organizational-document section discussions are read-only here; use Comment in project when offered to continue the discussion in its project. Timeline readers also require the workspace's timeline artifact access and offer their available classic or cockpit views and exports.

Restricted project details can remain hidden while an artifact is readable through IMS. Source files and folders still require access to their project. A missing item or section in an old link may leave the rest of the artifact readable: choose another item, section, or the overview. If the requirement link was removed or access changed, return to the current requirement and open a current link.