Technology + data
Your files and data should not be an afterthought.
Before TLS uses a tool, the project needs an answer to a few ordinary questions: What goes into it? Who can see it? Where does it live? How do you get it back?
Choose the tools
The project decides the method.
TLS and the client choose the tools together when that choice affects private data, authorship, the delivered work, or the organization's ability to run the system later.
Private material
Permission alone is not always enough.
TLS does not put ordinary private client files or unpublished manuscripts into a generative system unless the project names the task, provider, data route, and client's authorization. Credentials never go into one. Student records, regulated information, and community-held or culturally restricted material require the right legal, specialist, or community review first. Leave all of that out of the public inquiry form.
Review + disclosure
A person signs off on the result.
If generative tools materially shape copy, images, code, analysis, or another client deliverable, TLS records that use at the right project level. TLS reviews the delivered work against the agreed sources and requirements. Legal, licensing, and rights decisions still belong with qualified people.
A non-generative route
Some projects should use ordinary software only.
When the project can support it, TLS can agree to a non-generative production method. The written scope says what is allowed, what stays out, and who checks the work. We use the phrase “AI-free” only when the production record can prove it.
Community-held material
Work involving Indigenous knowledge, community-held material, or culturally sensitive information needs separately approved governance and specialist review. The people with authority over the material decide the terms.