As a developer you have a chain of agreements per project: from letter of intent and anterior agreement to purchase, construction and lease agreements, with addenda that change the terms along the way. Lynk reads those documents, turns the terms into labels and tracks the obligations per project. Here is how to start.
1. Set up your document types and labels
A document type determines which labels the AI extracts from a document. Lynk prepares a standard set together with you, so you do not have to start by writing prompts. Typical document types for developers:
Letter of intent, option agreement and anterior agreement
Sale and purchase agreement, land issue agreement and development agreement
Cooperation agreement and construction agreement (including turn-key)
Lease agreement and financing agreement
Permits and site investigation reports (soil, asbestos, flora and fauna)
Addendum / amendment and termination letter
Start with the document types you use most and add more later. See Document types and Contract labels.
2. Create your objects
Projects, entities and contract parties are objects in Lynk. Each project gets its own page with all contracts, actions and deadlines. Add your projects and entities before you upload documents, or send us a list; the AI then links the documents to them automatically. See What are objects?
3. Connect your storage
Connect your SharePoint site, or use Lynk Storage. Your existing folder structure stays intact. You can also email documents to the unique inbox address of your workspace. See Storage and SharePoint and Inbox.
4. Upload the first documents and review them
Start with one project: the main agreements and the addenda. About twenty documents is enough to see the difference.
The AI determines the document type, links addenda to the main agreement in a dossier, fills the labels and suggests actions. Everything the AI suggests is purple.
Review the suggestions and accept, edit or reject them. Mark good values as a sample so the AI learns how you read contracts. See Reviewing AI suggestions and Editing a label and marking it as a sample.
Check the dossier: is every addendum in the right order under the main agreement? See Contract families.
5. Create your first views and actions
Views give you overviews across all projects, without spreadsheets. Views developers use a lot:
All actions before the start of construction, per project
Termination and end dates for the coming months (calendar view)
Securities and bank guarantees per project, with amount and expiry date
A board of projects × document types, to see which document is still missing
Obligations from the contracts become actions with an assignee, a deadline and an email reminder. See Creating a table view and Assigning actions and setting reminders.
Note: Set up your document types and labels first, then upload in bulk. A label added later can still be filled for existing documents with a column scan. Stuck? We are happy to set up the workspace together with you. Send us a message via the chat in the bottom right.