Process Documentation and Training
Document how the work gets done.
I help organizations document and standardize their processes and train their teams to follow them consistently, through visual SOPs, workflow documentation, systems annotations and training materials.
Nexus Credit Consulting and Solutions LLC · 442 5th Ave # 1806, New York, NY 10018-2794
Services
Visual standard operating procedures
Step-by-step SOPs built around flowcharts, screenshots and checklists, so a new team member can follow the work without asking.
Workflow and process documentation
Process maps and written procedures that capture how work moves between people, systems and handoffs.
Systems and software annotations
Annotated screenshots and visual guides showing how internal systems and tools are used, one click at a time.
Training materials
Training guides, job aids and short instructional videos for onboarding and ongoing skills development.
Work samples
One process, documented four ways.
These samples follow a single everyday process, vendor invoice approval, so you can see how the map, the procedure, the annotated screen and the training aid fit together. They are illustrative examples I built to show the format, not client work.
Fig. A · Process map
Sample SOP · Vendor invoice approval
Purpose: Make sure every vendor invoice is checked, approved and paid accurately and on time. Scope: Starts when an invoice arrives. Ends when it is archived.
| Step | Action | Owner | Tool | Notes |
|---|---|---|---|---|
| 1 | Receive the invoice and log it in the AP register. | AP clerk | AP inbox, register | Log within 1 business day. |
| 2 | Match the invoice to the purchase order and receiving record. | AP clerk | PO system | Check vendor, amount, quantity. |
| 3 | Decision: if it matches, go to step 5. If not, go to step 4. | AP clerk | PO system | See flowchart, diamond 1. |
| 4 | Request a corrected invoice from the vendor, then return to step 1. | AP clerk | Email template | Record the request date. |
| 5 | Enter the cost coding and route to the approver. | AP clerk | AP system | Fig. B, callouts 1 to 3. |
| 6 | Review the invoice and approve or return it with a reason. | Approver | AP system | Fig. B, callouts 4 and 5. |
| 7 | Schedule payment, then record and archive the approved invoice. | AP clerk | AP system | File with PO and approval record. |
Quality checklist
- ☐ Vendor, amount and quantity match the PO.
- ☐ Cost coding is complete for every line.
- ☐ Approval is recorded before payment is scheduled.
- ☐ Invoice, PO and approval are filed together.
Fig. B · Annotated screen
What each callout means
- 1Confirm the vendor name and invoice number match the PO.
- 2Check the invoice total against the PO total.
- 3Select the cost code for each line item.
- 4Add a comment if anything needs explaining.
- 5Approve, or Return with a reason. Never leave an invoice pending.
Illustrative screen with invented data, built to show the annotation style.
Fig. C · Quick-reference job aid
Approving an invoice in 5 steps
- Open the invoice from your approval queue.
- Check the vendor, total and PO number.
- Confirm the cost codes look right.
- Add a comment if anything needs explaining.
- Select Approve, or Return with a reason.
Stop and escalate if
The total does not match the PO, the vendor is not on the approved list, or you did not expect the purchase.
Fig. D · Training module outline
Invoice approval: a 15-minute module
- Objective: Approvers can review and approve an invoice correctly without help.
- Walkthrough (5 min): The process map and the annotated screen.
- Practice (6 min): Two sample invoices, one that matches and one that does not.
- Check (3 min): Three questions on when to approve, return or escalate.
- Take-away: The one-page job aid.
The same content can be delivered as a short instructional video.
Free download
A ready-to-use SOP template.
The same structure I use on client work, as a branded PDF you can print or fill in. It has sections for purpose, scope, roles, a process map, a step-by-step procedure table, a quality checklist, escalation rules and revision history. Free to use and adapt for your own organization.
- —Title block with owner, version and review date
- —Roles and responsibilities table
- —Space for your process map
- —Step table with owner, tool and notes
- —Quality checklist and escalation table
- —Revision history
How a project runs
Step 1
Scope
A short call to agree what is being documented, who will use it and the format.
Step 2
Observe and map
I walk through the work with the people who do it and map each step and decision.
Step 3
Draft and review
You get a draft SOP, flowchart and checklist to review, with changes made until it is accurate.
Step 4
Hand off
Final files in editable formats, plus a short guide to keeping them up to date.
Deliverables are agreed up front and handed over as editable files, with the source flowcharts, so your team can keep them current.
Get in touch
Tell me what needs documenting
A short conversation is enough to scope a project and agree what you will receive.