An internal process guide should help someone complete a task with the right inputs and know whether the result is ready to hand over. Explain what starts the process, who uses it, the working steps and what to do when a check fails.

Choose one real task for the guide. A short document for reviewing a submitted file is easier to maintain than a broad guide called “How our team works.”

Process-guide structure from entry conditions to handoff

Make the starting point and completion condition visible.

State the starting conditions

Name the intended reader and the event that starts the task. List the files, access and information they need before step one.

For a document submission review, that might include the submitted file, a review checklist, the expected version and the name of the person who can answer questions.

Write steps with visible results

Step

Expected result

Open the submitted file

The reviewer can read the intended document

Check its identity and version

The file matches the submission record

Review the required sections

Missing items and questions are recorded

Send the review outcome

The owner knows the next action

Replace this example with your actual workflow. Mention the tools and controls the reader will see, and put a screenshot beside a step when it resolves a genuine ambiguity.

Exception path for an incomplete document submission

An exception should tell the reader what to do next.

Explain the exception path

If a required file is missing, say who to contact, what to record and when to resume. “Resolve the issue” leaves the difficult part to the reader.

Keep exceptions close to the step where they occur. If several steps share the same escalation route, provide a clear reference to that route.

Try the guide with a new reader

Ask someone who knows the general work but has not performed this exact task to follow the guide. Note where they pause, what they ask and whether they can recognize a completed result.

Update the wording and screenshots when the process changes. Give the guide an owner and a review date so readers know who maintains it.

Ulet can keep the guide as a local DOCX or Markdown file alongside related materials. Use Ulet for the written guide.