Portable procedure recreation

Recreate an existing procedure

Keep your source file with you, use the AI provider you choose, and bring one validated response back to create an editable Procedure Platform procedure.

Keep your source file with you

Do not upload the original procedure to Procedure Platform. Have the PDF, DOCX, spreadsheet, or image ready to attach directly to an approved AI provider.

One conversation. One response.The prompt below lets you choose whether the AI returns only the procedure content or also a draft presentation that matches the source document.

Share files only where your policy allows.

Source procedures may contain confidential, proprietary, export-controlled, personal, security-sensitive, or restricted information. Follow your company’s AI and information-security policy and use an approved provider.

Choose what to recreate

Use the source document’s content only, or ask the AI to also reconstruct a draft PPL presentation from its visual design.

AI response contentsProcedure Definition onlyRecreate the meaning, sections, and steps. Procedure Platform will use the Quick Start schema and Clean Industrial PDF presentation.Procedure Definition + source presentationRecreate the procedure and return a draft PPL that approximates the source document’s page, typography, colors, numbering, and callouts. A schema may also be included when useful.

Copy the recreation prompt

Open an AI provider, attach the original file in that conversation, paste this prompt, and ask for the complete JSON response.

You are helping recreate an existing industrial procedure inside Procedure Platform.

RECREATION MODE: Procedure Definition + source presentation (PPL).
The user will attach the original procedure file directly in this conversation. The file may be a PDF, DOCX, XLSX, image, or another format your provider supports. Procedure Platform must not receive the original file. Read it carefully and return one complete JSON response containing a Procedure Definition and a draft Procedure Presentation Language (PPL) file reconstructed from the source. A draft Procedure Schema may be included as an optional extra when it can be inferred reliably, but it is not required for this mode.

SECURITY AND CONFIDENTIALITY: The source may contain confidential, proprietary, export-controlled, personal, security-sensitive, or restricted information. The user must follow company policy and only share the file with an approved AI provider. Do not transmit, summarize, or invent information that is not present in the file. Procedure Platform will only receive the JSON response pasted back by the user.

OUTPUT RULES: Return ONLY one valid JSON object. No Markdown fences, preface, comments, trailing explanation, or second document. Use the exact property names and enum values below. Use plain ASCII double quotes for JSON structure. Escape any literal straight double quote inside procedure wording with a backslash, for example: Press the \"START\" button. Do not output HTML, JavaScript, CSS, executable content, external URLs, or data:text URLs.

SOURCE RECREATION RULES:
- Preserve the source title, document number, revision, facility, department, purpose, scope, responsibilities, prerequisites, definitions, references, hazards, controls, PPE, tools, materials, equipment, warnings, cautions, notes, verification text, expected results, images/captions, sections, subsections, step order, approval information, and revision history when present.
- Do not summarize away repetitive or operationally important steps. Preserve the original sequence and meaning.
- Convert visual layout into semantic content: headings become sections/subsections; instructions become instruction steps; warnings, cautions, notes, verification, expected results, images, and references remain separate semantic content when supported.
- Preserve source placement of standalone tables. When a table appears between procedure steps, include tables[].placement with the exact sectionId and afterStepId or beforeStepId. For example, a table titled ORSAT Testing Results that follows step 83 must be anchored after that source step rather than left as an unplaced top-level table. An unplaced table is rendered as front matter.
- AUTOMATIC PAGE ORIENTATION: Inspect the source page geometry before choosing the PPL. If the source page width is greater than its height, set procedurePresentation.page.orientation to exactly "landscape". If the height is greater than the width, set it to exactly "portrait". Do not use portrait as a default and do not copy the orientation from the example below. Preserve the source orientation even when the procedure has long text or many columns. If the source mixes orientations, use the predominant orientation and add an informational review item describing the limitation.
- Do not invent equipment identifiers, tag numbers, setpoints, limits, measurements, PPE, hazards, approvals, citations, names, dates, or site facts. If text is missing, illegible, ambiguous, or requires local knowledge, use a concise placeholder and add an unresolved question.
- Never claim the recreated procedure is safe, approved, certified, legally compliant, or compliant with a standard. Standards observations are review considerations only.
- Record source logos and images as imageRecommendations unless you can provide a supported embedded image. Never invent an image URL.

PROCEDURE DEFINITION: procedureDefinition must follow this shape. Keep required properties even when empty:
{"format":"procedure-definition","version":"1.0","id":"generated-or-source-id","title":"","documentNumber":"","revision":"0","facility":"","department":"","preamble":{"purpose":"","scope":"","responsibilities":"","prerequisites":"","definitions":"","references":"","hazards":"","controls":"","requiredPpe":"","toolsMaterials":"","equipment":""},"sections":[{"id":"section-1","title":"","description":"","level":1,"outlineLabel":"A","steps":[{"id":"step-1","position":1,"instruction":"","verification":"","warning":"","caution":"","expectedResult":"","ppe":"","note":"","keyPoints":"","signoffRole":"","imageUrl":null,"type":"instruction"}]}],"metadata":{},"approvals":"","revisionHistory":"","documentControl":{"sourceManual":"","sectionReference":"","firstIssueDate":"","currentIssueNumber":"","currentIssueDate":"","previousIssueDate":"","amendments":[]},"tables":[]}
Supported step type values are exactly: instruction, warning, caution, note, verification, expected-result, image, reference. Use position for source order. Step numbering in the PDF is derived from array order. Every section and step needs a unique id. Preserve an explicit source section label such as A, B, or C in outlineLabel when present; do not put that label into section.title. Preserve keyPoints as a separate field for source-side locations, limits, conditions, and notes, and preserve signoffRole when the source assigns a role such as VMA Operator or Maintenance. Use documentControl for issue dates, amendment records, source manual, section references, and document-control metadata. Use approvals for source approval/amendment narrative that should appear with document control. Use tables for source tables that carry meaning, such as safety systems, materials, references, ORSAT testing results, or amendment history; preserve columns, row order, and placement instead of flattening them into prose. A table placement object has the shape {"sectionId":"section-id","afterStepId":"step-id"} or uses beforeStepId.

OPTIONAL PROCEDURE SCHEMA: If you include procedureSchema, it must be a valid draft Procedure Schema describing information expectations observed in the source. Use this exact top-level shape:
{"format":"procedure-schema","version":"1.0","id":"recreated-schema-id","name":"Recreated information requirements","schemaVersion":"1.0.0","intendedUse":"A draft schema reconstructed from the supplied procedure.","guidance":"This draft requires organizational review and is not a compliance certification.","requiredPreamble":[],"requiredMetadata":[],"allowedStepTypes":["instruction","warning","caution","note","verification","expected-result","image","reference"],"rules":[]}
Each schema rule must contain id, severity, field, message, reason, and guidance. Rule severity is exactly required, recommended, or informational. Use required only for information that is always necessary to interpret the procedure and is clearly required by the source. Never make a field required merely because it appears in one step, one table, or one source section. Preserve source variation; use recommended or informational for inferred, conditional, organization-specific, or uncertain expectations. This reconstructed schema is a draft quality policy and must not block recreation of the source procedure.

PROCEDURE PRESENTATION LANGUAGE: procedurePresentation must be a valid declarative PPL that approximates the source document’s actual presentation. Do not return generic defaults unless the source really uses them. Inspect the entire source and reproduce page size, orientation, margins, typography scale, heading hierarchy, numbering, colors, callout treatment, running headers, watermarks, document-control blocks, step-table columns, signoff lines, and page-break behavior using the supported properties below.
{"format":"procedure-presentation-language","version":"1.0","id":"recreated-ppl-id","name":"Recreated presentation","pplVersion":"1.1.0","page":{"size":"letter","orientation":"portrait","margin":"0.45in"},"typography":{"bodySize":10.5,"headingColor":"#111827","accentColor":"#f05a00"},"sections":{"showNumber":true,"pageBreakBefore":false,"numbering":"lettered"},"callouts":{"warningColor":"#b42318","cautionColor":"#9a6700","noteColor":"#475467"},"layout":{"mode":"industrial-table","sectionHeadingStyle":"band","repeatHeader":true,"showPageNumber":true},"branding":{"companyName":"Example Company","watermarkText":"CONTROLLED COPY","watermarkColor":"#98a2b3","watermarkOpacity":0.18},"header":{"documentLabel":"Document control sheet","titleLabel":"Document number","sectionReferenceLabel":"Section reference","issueNumberLabel":"Issue number","pageLabel":"Page","showRunningHeader":true},"stepTable":{"stepLabel":"Steps","verificationLabel":"Initial, date & time","keyPointsLabel":"Key points","showKeyPoints":true,"showSignatureLine":true,"signatureRole":"Authorized operator"},"footer":{"approvalLabels":["Authorized by","Title","Date"],"approvalNote":"Only required to be completed and signed on first page"}}
PPL property rules: page.size is letter or a4; page.orientation is portrait or landscape; page.margin is a plain CSS length such as 0.45in; typography.bodySize is a number; all colors are hexadecimal; sections.numbering is numeric, lettered, or none; layout.mode is standard or industrial-table; layout.sectionHeadingStyle is plain, band, or underline; branding.watermarkOpacity is between 0 and 1; stepTable booleans are true or false. If the source has lettered outline headings such as A, B, and C, set sections.numbering to lettered and do not include the letters in section.title. If the source has repeated step columns such as Steps, Initial/Date/Time, and Key Points, use industrial-table and map those labels exactly. If the source has a document-control cover, preserve its semantic values in Procedure Definition documentControl, approvals, and document-control tables, and use header, branding, and footer to reproduce the presentation. PPL controls presentation only. Do not output CSS, arbitrary layout instructions, external URLs, data URLs, fonts that require remote loading, or executable code. If a source feature cannot be represented by these PPL properties, list it in reviewItems or standardsConsiderations instead of silently claiming it was reproduced.

REVIEW FORMAT: reviewItems and unresolvedQuestions are arrays. Each item must contain id, affectedField when applicable, severity, question, whyItMatters, canContinue, and status. severity must be exactly safety-critical, required, recommended, or informational. status must be exactly unresolved, accepted, corrected, or not-applicable. Never use critical, warning, high, medium, or low. imageRecommendations must contain id, affectedSectionOrStep, recommendedImageType, whatItShouldShow, whyItWouldHelp, safetyCritical, and captionOrAnnotationGuidance. Keep assumptions and standardsConsiderations separate from operational instructions.

REQUIRED RESPONSE ENVELOPE:
{"exchangeFormat":"procedure-platform-recreation-response","exchangeVersion":"1.0.0","procedureDefinition":{},"procedurePresentation":{},"reviewItems":[],"imageRecommendations":[],"assumptions":[],"unresolvedQuestions":[],"standardsConsiderations":[],"generationMetadata":{}}

FINAL CHECK BEFORE RETURNING: Ensure this is one valid JSON object; procedureDefinition and procedurePresentation are present; procedureSchema is optional; every required property is present; all ids are unique; step positions preserve source order; all step types and severities are supported; uncertain facts are marked for human review; no Markdown or commentary appears outside the JSON.
Return the complete response object now.

11,659 charactersIncludes Procedure Definition and PPL instructions

Open ChatGPT Open Claude Open Gemini Open Microsoft Copilot Open Another AI

Provider buttons open the normal provider website. Procedure Platform does not prefill or send the prompt for you.

Paste the complete AI response

Paste the response returned by the AI. JSON code fences and a short introductory sentence are okay; Procedure Platform removes those wrappers automatically and detects whether a source-derived PPL is included.

0 / 4,000,000 charactersOne JSON envelope; code fences are okay

Read the AI Exchange guide · Create a new procedure with AI