The complete workflow

Roles and access

A person sees only the projects and actions allowed by their role. The tenant administrator manages the organization; the project manager controls project inputs and approvals; engineers develop assigned deliverables.

Create a project

Tenant administrators and project managers can create projects. A project needs a project manager as its owner before source work begins.

1. Create the project

   Enter a clear project name and code that your team will recognize.

2. Set the project manager

   A tenant administrator selects an active project manager. A project manager creating a project becomes its owner.

3. Grant engineer access

   Use project access to add only the engineers who will work on its deliverables.

Result The project opens in Sources and is ready for its first controlled PDF.

Add and index source documents

Source management belongs to the project manager. Add the tender, requirements and other governing PDFs that define the work, then build the shared project index.

1. Open Sources

   Choose Manage sources, add one or more PDF files and wait until each upload appears in the source set.

2. Select Analyse sources

   Vellint extracts page text, builds retrieval data, maps the document structure and looks for submission registers and design obligations.

3. Follow operation progress

   The operation may take several minutes for a large tender. You can close the progress panel or leave the page without cancelling the work.

4. Read the source understanding

   Review the saved document outline and register findings. They show how Vellint interpreted the source before it proposed deliverables.

Result The project moves to catalogue review with a proposed set of deliverables.

Review the deliverable catalogue

The catalogue defines the design documents the project will produce. Review it before any deliverable is prepared. This step belongs to the project manager.

Choose one decision for every row

1. Open Catalogue assessment

   Read the model’s coverage note and any uncertainty it has identified.

2. Correct individual rows

   Edit the name, system, maturity or decision. Use Add deliverable when a required document is missing.

3. Revise with guidance when the gap is broader

   Describe missing subsystems, document families or incorrect mappings in plain language. The catalogue is revised in the same working thread and your accepted rows remain part of the review.

4. Approve the catalogue

   Approval becomes available when no row needs review and every included row has a name, maturity and source evidence.

Result Included CDD and PDD rows become available for preparation. Detailed Design rows remain visible but cannot yet be prepared.

Prepare a deliverable

Engineers and project managers can prepare an approved Concept or Preliminary deliverable. Preparation gathers the relevant evidence, requirements, interfaces, constraints and unresolved inputs for that specific document.

1. Open Deliverables

   Select the required row and confirm its maturity and source basis.

2. Select Prepare controlled design

   Vellint searches the indexed source set and organizes the material against the controlled recipe for that maturity.

3. Inspect the preparation artifacts

   Use the document index to read evidence, requirements, interfaces, assumptions and other generated records. Follow page citations back to the source PDF where needed.

4. Check readiness

   Preparation separates available evidence from missing information and material questions. Missing detail remains visible; it is not silently invented.

Result The deliverable moves to decisions when human direction is required, or becomes ready for its company template when no blocking question remains.

Answer questions and apply decisions

Preparation asks only for material direction needed to complete the design basis. Engineers and project managers can answer these questions.

1. Read the basis before answering

   Open the linked evidence and understand why the question was raised.

2. Give a usable engineering response

   State the selected option, governing source or assumption. Add the reason when the answer resolves a conflict.

3. Save partial responses if needed

   Save responses keeps progress without applying an incomplete baseline.

4. Select Apply controlled decisions

   This creates the decision baseline used for drafting. Once a draft is generated, those answers are locked to preserve lineage.

Result Final preparation material is assembled and the deliverable becomes ready to draft.

Register the company template

Every document needs a human-provided Markdown template. The template controls heading order and presentation while the selected CDD or PDD recipe remains responsible for mandatory engineering subjects.

# Purpose and scope

# Design basis

# System architecture

## Interfaces

# Assumptions and open inputs

1. Open Document

   Load a .md or .markdown file, or type the structure in the editor.

2. Review the headings

   Use the organization’s normal section names. Keep the structure appropriate to the selected maturity.

3. Select Register template

   Vellint maps the headings to the controlled recipe. Required subjects missing from the template are retained in appendices rather than omitted.

4. Select Draft document

   Drafting begins only after the template is registered and the decision baseline is ready.

Draft, inspect and revise

Drafting produces a sectioned working document. Valid sections appear as they complete, so the team can see progress without waiting for the entire document.

1. Read section by section

   Use the document index to move through the draft. Check technical meaning, maturity, assumptions and open inputs.

2. Inspect statement provenance

   Open a trace to see the evidence and decisions supporting a statement.

3. Revise with a focused instruction

   Open Revise on the section you are reviewing. Describe the required change, its technical basis and the outcome you expect.

4. Add a section when the structure needs it

   Use Add a section in the document index, name the section and provide its purpose and placement. The new section joins the controlled working draft.

5. Read the revision summary

   After a revision, the activity record identifies the sections changed and summarizes the effect. Confirm that the change addressed your instruction.

6. Mark the section reviewed

   Select Mark reviewed only after checking its content and traceability. A later change reopens the affected review.

Result Every current section is reviewed and the document is ready for final review.

Run final review and save a revision

Final review supplements the team’s section review. It checks the assembled document for traceability, unsupported claims and required subject coverage.

1. Open Final review

   Confirm that every current section is marked reviewed, then select Run final document review.

2. Read the verdict and findings

   Approved is ready to save. Qualified can be saved with visible assumptions or open inputs. Changes required must be revised and reviewed again.

3. Resolve blocking findings

   Use a focused revision instruction, review each changed section and rerun final review.

4. Save the immutable revision

   A project manager confirms Save revision. The saved revision is read-only and remains available in revision history.

5. Export when needed

   Download the combined Markdown or PDF from the document index. Check the exported file before issuing it outside the project.

Result The project has an immutable, traceable document revision while the working draft remains available for future controlled change.