How to document a task
How to Document a Task

How to Document a Task

Introduction

Do the task → Save the steps → Test the guideFollow the numbered steps in order. The path runs from top to bottom.Do the taskSave the stepsTest the guide
A new person follows your guide and checks the same result.

Help your team repeat good work with steps they can follow. This guide shows how to record a real task and check that someone else can use the guide. Start as you do the work, and save the steps, screenshots, and proof.

Start with the result you want, the source material, and the people it serves: your Goals, Content, Targeting (GCT) brief. This task uses Learn, Do, Teach: learn the method, do the work, then teach it. Find related work in the Task Library, our directory of repeatable tasks.

Important Note

Our Task Library is public. You can browse the full list of tasks and each task's dedicated page. However, admin access—editing the library, login credentials, and access to internal systems—is restricted to team members. If you're a team member who needs admin access, contact operations@yourcontentfactory.com.

Task Checklist

Information that you will need:

  1. All information related to the task such as the steps, URLs, and login credentials.
  2. Additional instructions, if any. Don’t be afraid to ask.
  3. Access to the Task Library (to add your guide).

Tools that you will need:

  1. Google Docs (login required)
  2. Image Editor
  3. A screen recorder (Descript, Loom, Camtasia, etc.)
  4. WordPress (login required)

Important Things To Do and Consider

Write down instructions on how to do a particular task so that others can read your instructions and do it without confusion. You want to make it easy to understand and straightforward (using a step-by-step format) so that anyone with zero experience can follow your directions to achieve the same result.

While doing the task, you need to do these:

  1. Identify steps and take down notes to document each step. Divide the task into granular steps to make the process easier to follow.

  2. Remember the online tools you used to complete the task and save the URLs.

  3. Take screenshots of every step. You're not limited to one screenshot per step. You can add more if it will help the reader understand what you're trying to explain better. Add highlights to essential parts of a screenshot. You can use a simple tool such as the Windows Paint program to add these highlights.

Document how you're doing a task. Don't wait until the end before documenting it because you will forget the small details. Take those notes down, and take screenshots along the way.

Also, never make assumptions about things that you might take for granted. What is basic to you may not be basic to others. For example, there are a lot of acronyms that some people might not know. How do you get access to a particular tool? How do you get access to a website or PPC account?

Recall how you felt when you did the task for the first time. Try to remember the difficulties you encountered. How did you solve the problem? Think, while doing something, what are helpful tips that you can share? Don't just take screenshots and submit them. Think, what are the pro tips you picked up along the way that people need to know? It’s not a bad idea to approach this with a beginner’s mindset. Think like a beginner, but explain it like a pro.

Screenshot highlighting pro tips shared

Think about all the possibilities where someone could commit an error and focus there. The higher the probability that a team member will trip, the higher the chances that person will make a mistake. That's where you're going to put in the most effort. Don’t be afraid to be very detailed in your documentation. The better a task is explained, the easier it will be understood and digested.

Suggest alternative ways to do the task or any step in the process. If it's about link-building or SEO, teach them how to use a particular tool. You may write, “I always choose two categories for a blog post." Share your techniques because that's where your expertise will shine.

Tips

Here are some tips to help you create an awesome guide:

  1. You should provide a reference in the guide to teach the reader how to create an eBook when explaining a process like "How to Publish Guides as Free eBooks," for example. Provide a link somewhere in the guide where it makes sense. You can't teach a student driver how to park without teaching him how to drive first.
  2. Always show the successful outcome of a task. Show the reader what it's supposed to look like. For example, if it's about uploading an eBook, include an image showing it on the site, successfully uploaded. It's always helpful to provide a visual reference for beginners.
  3. Include tips that will help people accomplish the task. For example, eBooks that don't include a bulleted list are always rejected. Inform them to help them save time by doing it right the first time.

Creating the guide

When you’re ready to document all the steps in the process, you need to do the following:

  1. List each step, and explain in detail what happens at each one. Explain what the expected output is at the end of each step.
  2. Add tools that make the job easier and explain how to use them. Don’t forget to include links, so they’ll know where to go to access those tools. Think about the tools they will need, and explain how they can access them.
  3. Add the screenshots you saved while doing the task and documenting the steps. Remember to add highlights and labels when necessary.
  4. Inform the reader that the guide is available in the Task Library. Don’t forget to add a link so people can get to the library from the guide.

Checklists

After the short opening and meaningful visual, add a brief checklist to show the overall process. The checklist should be short and straightforward. Think of the essential things they need to know right from the start. You should also include a list of things to check against the completed task to ensure that every detail of the process is covered at the end of your guide. This is a quality assurance (QA) or verification checklist: the checks that prove the result.
Image

There should be an easy way to verify if the task was done correctly at the end. A verification checklist, in this case, can be helpful. It will serve as a reminder of things that they should have done. They can look at this checklist before submitting their work to ensure they didn’t miss a thing.

For example, when someone submits a blog post, we want to know if they remembered to include important things such as the title, images/screenshots, a link to the Task Library at the end, etc. Does the guide link to its parent topic and the owned training it uses? Keep provider links for exact proof or a required action. Every link should help the reader finish the task.

An example of complete documentation of a task

Please check this page, How to Inventory a YouTube Channel, to give you an example of what it should look like. It documents all the steps required to inventory a YouTube channel. Here, the VA took the granular approach to explain the process. He included every single step and added a lot of screenshots to explain every step. He included all the crucial elements that make the documentation truly helpful.

He began the page with a checklist to give the reader a view of what is involved. This includes the steps, suggested tools, and a few reminders. It is a simple task, but as you can see, many steps are involved. Add as many steps as necessary, but don’t overdo it.

A screenshot of a guide
He also included a lot of screenshots with highlighted areas to make it easier for the reader to follow instructions.
A sample of what a good screenshot looks like with important areas highlighted
He also included the tools he used to help with the successful completion of the task.
Image
He added a mention of the Task Library and added a link to it at the end of the page so that the reader can take a look at the other things available on the site.
A screenshot of the Task Library mention at the bottom of the page
Please keep these things in mind so that your instructions will be easy to follow.

Making a demo

Finally, when you've done that task many times successfully, record a screen share. You can do a screen share inside Descript by hitting the screen recording button. You could use Loom, Skype, Camtasia, or whatever you prefer to record your screen while explaining what you're doing, click by click.
A screenshot of an instructional video

Learn how to use WordPress

A screenshot of the WordPress visual editor

Use the WordPress posting task when the guide is ready for an authorized release. First find the existing recipe for this task and improve that page. Create a new guide only when the gap is verified. Each execution has its own written meta article; it does not need a competing recipe. Link the guide to its record in the current Task Library so readers can find the task and its related work.

For example, building a website might involve additional tasks such as graphic design, blogging, analytics, etc. These bundles are a combination of tasks. Remember that these don't just live by themselves when we're bundling them. They live together in a particular bundle.

We live by the Learn-Do-Teach framework, where you're learning how to do a task from someone who's done it repeatedly and successfully. You're doing it yourself and enhancing our documentation because we update our training continuously.

We might be using a different tool now. We might have to replace the screenshots or remove certain features that aren't there anymore. The bottom line is that we make it easy to understand and follow. We're documenting everything as we're doing it. We're taking notes and teaching others how to do it as well. We are recording screen shares to enhance the training so people can follow our instructions.

For all of us, we are not only earning money and having a living as digital marketers, but we're helping other people earn a living as well.

Adding it to the Task Library

Register the reviewed guide in the current Task Library and check that its task record links back to the canonical page. A directory entry does not certify the recipe. Use the Document a Task record for this guide and check its current review status.

Historical Task Library sheet

The original tutorial used this earlier Task Library sheet. It remains a source reference; use the current catalog and maintained task source for updates.

A sample of an entry in the Task Library

Incentive Program

We have an existing incentive program for documenting expertise where you can earn bonuses for teaching others what you know by creating the training. For more information on the program, please visit "Document Your Expertise and Teach Others."

Verification Checklist

The documented task must meet the following criteria:

#1. The page stays at its approved canonical URL and follows our current article writing guidelines.

#2. The page opens with a meaningful visual and 2–3 short sentences at eighth-grade level or below. These explain who the task is for, what it does, why it matters, and the outcome. The Task Checklist comes next.

#3. The checklist includes all necessary tools, tips, URLs, and login methods for easy access and smooth execution of the task.

#4. This task page is designed for beginners. Explain unfamiliar terms on first mention and link their owned training. State the required inputs and authorized access; never assume access to another person’s account.

#5. State the trigger and starting condition, then give ordered steps and decision points. Link required earlier tasks and name the outputs they must provide.

#6. The process highlights potential sources of error and ways to prevent them.

#7. Each step includes at least one screenshot that highlights its crucial parts.

#8. The page links to its parent guide and relevant owned training. Provider links support precise evidence or required actions.

#9. All anchored text on the page directs users to the intended pages or documents.

#10. The page features a video demonstration of the task, with a live explanation and mouse clicks for clarity.

#11. Name the expected output and the observable pass/fail checks. Show the verified result; mark a failed, partial, or unchecked example honestly.

#12. The page concludes with a verification checklist that allows readers to confirm they have completed all necessary tasks.

 

For Internal Workers:

#13. The task page at the bottom features a clickable link to the Task Library page.

#14. The Task Library page has a clickable reference to the task page.

#15. The guide is correctly mapped in the current Task Library. A missing record remains a registration gap, not a completed mapping.

#16. Indicators that signal when something is for internal workers (VAs) only are present.

#17, There is a link to the checklist or course the task is a part of.

#18. There is a link to the Ultimate Action Guide.

#19. The lower Content Factory context shows the task’s actual stage, prerequisites, and next task or receiving function. It does not replace the lead visual.

#20. This documentation execution has a written meta article recording the run, with the canonical task, recipe revision, result, checks, and evidence. Publication follows existing authority. Revisions keep the same execution ID.

That's it. Now, let's see you create your first guide.
If you enjoyed this tutorial, be sure to explore our Task Library for a plethora of additional tasks waiting to be mastered!

Where this task fits in the Content Factory

Documenting a task turns real work and source evidence into a reusable guide. That is Process in the Content Factory, our four-stage content process. An authorized public release is the separate Post task.

1. ProduceCapture real work
THIS TASK2. ProcessTurn sources into useful assets
3. PostPublish and connect approved assets
4. PromoteShare proven work and measure results
Follow the numbered stages from Produce to Promote. Each stage links to its part of the Content Factory guide.

Start, finish, and next step

Start when
A real task is being performed and needs to become a reusable guide.
Have ready
The real task and its source evidence, notes and screenshots from each step, the required tools, and authorized access. Read the definitive article recipe standard and current article writing guidelines before drafting.
Follow the steps
  1. Perform the task and capture each step
  2. Write a plain-language introduction and process checklist
  3. Explain ordered steps and expected outputs
  4. Add source screenshots and error prevention
  5. Test the verification checklist
  6. Link the guide in the Task Library
Finish with
A task guide that a new person can use to reach and verify the same outcome.
Measure the result
  • Inputs and access methods are explicit
  • Each step states its expected output
  • The verification checklist checks the actual result
  • The guide links its parent and owned prerequisite training
  • The current Task Library record links the canonical guide and shows its actual review status.
Hand off next
Give the checked guide, source evidence, metadata, and release state to the publishing function. When release is authorized, follow the WordPress posting task, verify the live page, and update the current Task Library record. Use the execution’s meta article to propose supported improvements.

Open Document a Task in the Task Library. Use that record to find this recipe, its current status, and the evidence from task executions.

Close the learning loop. Write a meta article: the record of this execution with the starting state, recipe version, result, checks, failures, and next owner. Link it back to this recipe and register the run under the same Task Library task. Reuse one execution ID for revisions and retries. A partial or failed run stays labeled that way. Public release follows the recorded publication authority; writing the run record is part of doing the task. Writing and revising that record belong to the original execution; they do not start another meta-article task. Use the findings to propose and verify a recipe improvement. See how recipes and execution records work together.

What Makes a Task Guide Definitive

A repeatable task needs one maintained recipe, its definitive task article. A standard operating procedure (SOP) is that written method. The Task Library connects the task record to the recipe and run evidence. A topic or framework hub explains a broader subject and links its recipes. A story, comparison, or reference does not become task-definitive because its opening was improved.

Follow the definitive article guide and current article writing guidelines. A complete task guide includes the following components:

  1. A clear title naming the task
  2. A compact, meaningful diagram or picture in the first screen, visible before the reader scrolls or clicks. An empty box or a visual that appears only after interaction does not pass
  3. A specific Goals, Content, Targeting opening: 2–3 short sentences at eighth-grade level or below that explain who this serves, what it does, why it matters, and the outcome
  4. A brief Task Checklist, after the opening and visual, naming the trigger and starting state, inputs, authorized access, linked prerequisite tasks, and the outputs they provide
  5. Ordered instructions and decisions with screenshots and the expected output at each step
  6. A QA / Verification Checklist with observable pass/fail checks for the promised result, plus the next task, receiving function, and handoff artifact
  7. A Related Resources section with cross-links to parent articles, sibling SOPs, the Task Library, and meta-documentation articles like How to Document a Task and Creating Winning Documents
  8. A Video Demonstration showing the task performed live with explanation
  9. A Skill MD file at the end — a machine-readable summary of the task that AI agents can use to execute or assist with the task

The Self-Learning Feedback Loop

Our documentation system is designed to improve itself continuously. Here is how the feedback loop works:

You complete a project (e.g., inventory a YouTube channel for a client). Write a meta article recording this execution, with its task, recipe revision, inputs, actual steps, result, checks, failures, and evidence. Keep the required internal job record as well. Writing the meta article is required; publication follows the existing authority and the suitability of its contents. Keep it private or in draft when needed, and label partial or failed results honestly. Revisions and retries within the run keep one execution ID. Reviewed run evidence improves the task recipe, making it better — adding new tips, correcting outdated steps, or expanding the verification checklist. The improved definitive article then trains the next person (or agent) who performs that task, leading to better execution. Better execution creates better evidence for the next improvement.

Project work → written meta article → checked lesson → improved task recipe → better project work

The record makes improvement possible; someone must inspect the evidence and accept a supported change. A clean run need not change the recipe. Writing the meta article belongs to the original execution and does not start an endless series of new meta articles. Count distinct executions separately from dated historical public-article volume.

Related Resources