Agree on a short list of approved AI tools, teach juniors to check before they trust, and practice on the same AI answer together. A confident wrong answer looks right to someone who hasn't seen the right one yet.
Three things that help
Teams run into trouble when each engineer learns AI alone, or not at all.
- 1Agree on a short list of AI tools your firm uses.
- 2Teach juniors to check before they trust.
- 3Practice on the same AI answer together.
Start from a firm AI policy
On project data and sign-off, point your team to official guidance: your state licensing board and NSPE Board of Ethical Review Case 24-2.
NCSEA publishes a sample AI policy for firms. NCSEA Generative AI Program
Check what your AI tools keep
Before your team pastes project documents into any AI tool, find out three things: what it stores, who can see it, and whether it trains on what you type. Your firm's AI policy then decides what may be pasted at all.
Calcs.com answers these questions for CalcsAI on its AI page. CalcsAI data and privacy
Run one shared session
Pick one AI answer from your own work with a mistake in it you already know about. Have everyone check it alone with the four questions from week 2, then compare what each person caught.
Close on who owns the result. AI can draft, summarize and organize. The engineer of record checks, reviews and signs.
Want Calcs.com to run it with your firm? Book an AI workshop or hackathon for your team.
Book a firm AI workshopTry it
Pick the AI answer you'd use for a first team session, and note the mistake you want people to find.
Last reviewed:
