Out of Scope Productions is a Third Person Consulting company. Visit TPC →
Out of ScopeProductions
← Quick Start BriefsSolo practices · Engineering · Contractors · Quality

The Practice of One: Best Practices for a Solo Firm

When you're the engineer, the project manager and the office, your methods live in your head and your inbox, and every contractor learns them from scratch. This brief shows how to write them down once, in a size that fits one person: a few procedures, a contractor system, quality checks at the points that matter, and a learning plan. The running example is an independent mechanical engineer who designs systems and works with contractors to build them.

1. Start with what can hurt you

Don't try to document everything. List the work you repeat, then mark the jobs where a mistake is expensive, unsafe or can't be undone. Standardize those first. SOP-SYS-06

  • Name the real gap. "Contractors keep installing to the superseded drawing" is a gap you can fix; "I need better processes" isn't. Write it as what you observed against the outcome you want. DGN-FRM-01
  • Write for the work as you actually do it, not as a textbook says it should be done. A procedure you don't follow is worse than none. SOP-DES-01 · DGN-GAP-01
  • Find the knowledge only you hold. If you were off for a month, which decisions would stall? Those go to the top of the list. KIN-CAP-06
  • Capture as you work, with the time budgeted: ten minutes at the end of a job beats a lost weekend once a year. KIN-CAP-02

2. A procedure system for one

A solo firm needs the same structure as a large one, at a much smaller scale. Keep a simple hierarchy: a short policy, a handful of procedures, and the forms and records they produce. A completed checklist is a record, not a procedure. SOP-SYS-02 · SOP-SYS-03

  • Fewer, better procedures, each on one complete template: purpose, scope, who does it, the steps, the limits that count and the records it leaves. SOP-DES-07 · SOP-DES-08 · SOP-DES-09
  • One current version at the point of use. Superseded drawings and old PDFs in a contractor's truck are the classic failure. Stamp versions on anything you share. SOP-DIG-01 · SOP-DIG-03
  • Keep a register of the codes and standards you rely on, with the edition your jurisdiction actually adopted, rather than hard-coding them into every procedure. SOP-SYS-07 · SOP-DES-11 · CM-STD-02
  • Review on triggers (a code change, a near miss, a new kind of job), with a yearly date as the backstop. SOP-GOV-01
Figure 1. The first month, one step a week
Week 1List your repeat workMark what's expensive, unsafe or irreversible if it goes wrong.
Week 1Pick three processesFor example: design review and issue, site visits and inspection reports, changes in the field.
Week 2Write them on one templateThen walk through each one on a real job before you call it done.
Week 2Start a contractor registerWho they are, what they do for you, how much rides on them, what you've agreed.
Week 3Add hold points to your current jobThe stages you must see before work covers them up.
Week 4Set your learning plan and review datesPut them in the calendar, not in a document.

Test each procedure on real work before you rely on it; the first draft is always missing a step. SOP-DES-06

3. Working with contractors

Your contractors are your workforce, so treat them as part of your system rather than outside it. Tier them by what happens if they fail, and spend your checking time accordingly. VCM-SUP-01

  • Keep a short approved list with the criteria you used and a date to look at it again. VCM-SUP-02
  • Flow your obligations down in writing. A one-page matrix of which of your client's requirements each contractor must meet, signed, saves arguments later. VCM-CMP-01
  • Keep a live register of notice deadlines. Most disputes start with document errors and missed notices, not bad work. VCM-ADM-01 · VCM-ADM-02
  • Run the payment clock exactly. In Ontario, prompt-payment rules set the timelines for invoices, notices of non-payment and payment down the chain. VCM-PAY-01
  • Treat a field change as a design change. "Just move it 300 mm" goes through your review like any other revision. SOP-GOV-03
  • Coordinate the site. When several contractors share a site, give that coordination its own short procedure. SOP-USE-07

4. Quality without a quality department

You can't inspect everything, so decide in advance what you will see. Write a simple inspection and test plan for each work package, and put hold points at the stages that can't be undone, before insulation, ceilings or concrete hide the work. QMS-ITP-01 · QMS-ITP-02

  • Put hold and witness points in the contract, so stopping work to inspect isn't a negotiation on the day. QMS-ITP-03
  • Keep checklists to the items that kill or cost, and remember a ticked box isn't a verified outcome. SOP-CHK-03 · SOP-CHK-04
  • Find a second set of eyes. On high-consequence work, arrange a review with a peer qualified for that work, and have it happen as the design develops, not once before issue. SOP-GOV-02 · SOP-GOV-08
  • Never soften an issued inspection report. If something changes, issue a revision that says so. SOP-CAN-04
  • If you use AI to draft, you verify and own the result; anything you seal is yours. SOP-DIG-04 · SOP-CAN-05

5. A learning plan you'll keep

Licensure hours are a floor, not a measure of competence. Know your regulator's model and check it with them, then spend your continuing-education time on what actually goes wrong in your kind of work. LSC-CPD-01 · LSC-CPD-02 · LSC-CPD-05

  • Choose case-based, practised sessions over on-demand catalogues of hours. LSC-CPD-03 · LSC-CPD-04
  • Practise deliberately. Years on the job aren't the same as practice; pick one skill a quarter and work on it with feedback. LSC-EXP-01 · LSC-EXP-02
  • Space it out, timed to when you'll use it: learn the new code edition in the weeks before your next job that needs it. LSC-PRC-02 · LSC-TRF-03
  • Keep your research in order. Mark each source by authority (adopted code, standard, manufacturer guidance, your own notes) so you never act on a draft as if it were law. KIN-GOV-02

6. Keep it alive

A system for one person survives only if it costs little to maintain. Book the time as a non-billable line, like insurance, and let real events drive the changes. LSC-ORG-02

  • Treat deviations as data. When you skip a step, ask whether the step or the job was wrong. SOP-USE-01
  • A lesson counts only when something changes: a procedure, a checklist, a contract clause. A note in a folder isn't a lesson learned. SOP-GOV-06 · KIN-CAP-03
  • Measure with records you already keep: revisions after issue, deficiencies at handover, notices missed. LSC-ORG-03

The checklist. Three procedures for your highest-consequence work, on one template, tested on a real job. One current version wherever contractors work. A register of codes and editions. An approved contractor list with tiers, flow-downs and a notice-deadline register. Hold points at the irreversible stages, written into contracts. A peer reviewer for high-consequence work. A learning plan aimed at real failures. Time booked to keep it all current.

Practise it. The As Written series puts procedure decisions in front of you, and First Time Right does the same for inspection and quality, in Project: Countdown!

General guidance for professional practices, not legal or engineering advice. Contract, payment and licensing rules depend on your jurisdiction and your regulator.