About the manual.
A practical publication for professionals who want AI to carry more of their work without handing over their judgment.
What this is
AI Field Manual teaches working professionals how to apply AI to the responsibilities they already have. Each guide starts from one real task, such as triaging a server's event logs, turning a meeting into decisions and owners, or answering a contractor's RFI. It then walks through doing that task with AI, start to finish.
It is not a news site, a tool directory or a prompt marketplace. The guides are written to work with any capable general-purpose AI assistant, unless a guide names a specific tool and says why.
Who it's for
Five disciplines, chosen because their work involves a lot of reading, sorting and drafting that AI can take on, and a lot of judgment that it can't:
- IT and systems administration
- Project management
- Marketing
- Architecture and design
- Executive assistants
How guides are written
Every guide follows the same four house rules:
- The work stays yours. Each guide names the decisions that never move to the tool.
- Specific beats general. One real task, with real inputs and a real output.
- Verify before you trust. Each guide includes the checks that catch a confident wrong answer.
- Your data has a perimeter. Each guide covers what to remove before anything leaves your machine, and treats your organization's policy as the final word.
Guides are reviewed and updated regularly, and each one shows when it was last reviewed.
Who writes it
AI Field Manual is written by Terrell Haynes, a senior systems administrator with about twenty years in IT. He runs IT single-handedly for a New York–area organization, managing Microsoft 365, Entra ID, Azure and the network, and earlier worked in IT at a magazine publisher, a global architecture firm, a national beverage distributor and a large consulting firm.
That career has meant supporting the people these guides are for: project managers, marketers, architects and designers, and the executive assistants who keep leaders on schedule. The IT guides come from his own daily work. The other disciplines' guides come from years of working alongside those teams, and every factual claim in them, from building codes to advertising rules to statistics, is checked against primary sources such as the code text, the regulator's guidance or the standard itself. If you work in one of these fields and spot something wrong, corrections are welcome: see the contact page.
Independence
No AI company pays for placement in a guide, and guides do not use affiliate links. The site is supported by advertising and by sales of the field editions.
Get in touch
Corrections, guide requests and questions are welcome. See the contact page.