AI back-office checklist for freelancers
AI can draft a lot of the admin around your work: payment follow-ups, proposal outlines, a weekly review, first replies to support emails. This checklist is the order we'd set that up in, so that a draft never turns into something you didn't mean to send.
Tip: print this page or save it as a PDF (your browser's Print command) and tick the boxes by hand.
1. Start with one job
"Use AI for the business" is too big to check. One job you already do every week is small enough to get right.
- Pick one admin job you already do: chasing a late invoice, outlining a proposal, the weekly review, or a first reply to a support email.
- Write one line on what "done" looks like, for example "a polite follow-up I'd sign, with the right invoice number, amount and due date".
- Use a tool you already have access to. You don't need a new subscription to try this.
- Note the date and the tool you used. When the tool changes, you'll know what to re-check.
Not sure which jobs suit AI? Which AI task fits which freelance job goes through them one by one.
2. Write your rules before your prompts
A few standing rules do more than a clever prompt. Save them where the tool sees them every time: its custom instructions if it has them, or a note you paste in first.
- Facts only. The AI must not invent clients, amounts, dates, policies, quotes or reviews. If something is missing, it asks you instead of guessing.
- A person sends. Drafts can come from AI. Emails, posts, invoices and filings go out only after a person has read them.
- No claims you can't back up. Nothing you publish promises results, savings or income, and nothing says "tested" unless you tested it.
- Say when you don't know. A draft that says "I'm not sure, I'll check" is better than a confident wrong answer.
The third rule isn't only good manners. In Canada, for example, the Competition Bureau says: "It is against the law to make materially false or misleading representations to promote a product, service or business interest." Other countries have similar rules, and they apply to the words you publish, whoever drafted them.
3. Keep private things out
- Find out what your AI tool does with what you type: whether it's kept, and whether it can be used to train the tool. Look for a data or privacy setting, and check whether a business plan treats it differently.
- Leave out what the job doesn't need. Write
[CLIENT],[AMOUNT]or[INVOICE #]and fill the real details in yourself. - Never paste passwords, API keys, login codes, bank details or ID numbers.
- If a client's contract says their material is confidential, don't paste it into a tool their contract doesn't allow.
Privacy law still applies. The Privacy Commissioner of Canada puts it plainly about generative AI tools: "they do not occupy a space outside of current legislative frameworks." In the UK, the UK Information Commissioner’s Office has guidance for organisations using AI. If you handle other people's personal information, read your own regulator's guidance.
4. Decide what a person must approve
Write the list once, even if the person is you. It's what stops a busy day from turning into "the AI sent it".
- Money: prices, discounts, refunds, spending and anything to do with payouts.
- Identity: new accounts in the business name, bank and ID checks, and anything signed.
- Anything public: social posts, website copy, legal pages and product listings.
- People: anything a client or customer asks a person to handle.
- A short way to ask: one line saying what you want to do, why, and what happens if the answer is no.
5. Drafts stay drafts
The pattern that works: you give it the facts → it drafts → you edit → you send. The editing step is the job.
- No automatic sending to clients, and no automatic posting.
- Check every number and date against your own records: invoice number, amount, currency, due date, days late.
- Read anything about money out loud once. If it sounds harsher (or vaguer) than you'd say it, fix it.
- Keep the version you actually sent, not the draft.
6. Test before anything goes live, and after
This is the rule we hold ourselves to: nothing customer-facing ships untested.
- Read it as a stranger would. Is every claim, number, date and "works with" statement true today?
- Click every link.
- If you sell something, make a test purchase (a $0 test or one you refund) and open the file in each app you say it works in.
- After it's live, open the live version in a fresh browser window and check it again.
- If you couldn't test something, say so on the page instead of implying you did.
7. Review the week
Ten minutes on a Friday is enough. AI is good at turning your rough notes into the summary; the notes have to come from you.
- What shipped, what's stuck, what went wrong, and what to test next.
- Decisions waiting for you (the approval list from step 4).
- Money in a private note only. Leave a figure blank rather than letting anyone guess it.
- Once a quarter: re-read your rules and your saved prompts, and update anything that depends on a particular tool.
8. Know when to ask a professional
Filings, contracts, debt collection, employment and anything regulated are questions for an accountant, a bookkeeper or a lawyer. AI can help you organise your documents and write down your questions before the appointment. It doesn't replace the answer.
Related free pages
- Which AI task fits which freelance job (what to give the AI, and what to check, job by job)
- Four copy-ready payment reminder emails you can use as they are, or as the facts for an AI draft
- Free quote and estimate generator and free invoice generator (they run in your browser; nothing is sent)
Sources
Read on . Everything else on this page is our own working process, not legal advice.
- Office of the Privacy Commissioner of Canada: Principles for responsible, trustworthy and privacy-protective generative AI technologies
- ICO (UK): Artificial intelligence guidance for organisations
- Competition Bureau Canada: Misleading representations and deceptive marketing practices
Found something wrong or out of date? Tell us via Support and we'll fix it.