Projects & sessions

Projects

A project is the top-level container for a tax engagement. Each project is scoped to one tax client and typically one financial year.

Projects contain:

• Documents — all uploaded files
• Evidence — every extracted fact and filed item
• Situation — the structured tax data (properties, employers, income, deductions)
• Workbook — the Live Report spreadsheet
• Memory — persistent notes that carry across sessions

When to create a new project

• New financial year (FY2026 vs FY2027)
• Different tax client (your return vs a partner’s return)
• Different entity (personal vs trust vs SMSF)

Project isolation

Projects are strictly isolated. Lodgey has no knowledge of other projects when working inside one. It won’t reference, compare, or mix information across projects. If you need to share data between projects, you’ll need to re-upload or re-enter the relevant information.

Sessions

A session is a single chat conversation within a project. You can have many sessions per project.

All sessions within a project share:

• The same documents and evidence
• The same situation data
• The same workbook
• The same memory

Think of sessions as separate meetings about the same client. Lodgey treats them as a continuous conversation history for that project.

Starting a new session

When you start a new session in an existing project, Lodgey automatically reads the project memory to pick up context from previous sessions. You don’t need to re-explain your situation.

A good opening message for a returning session:

What did we cover last time? What's still missing?

When sessions end

Sessions are stateful within themselves — the full conversation history persists. But each session gets its own isolated execution environment. Temporary files created by Lodgey’s sandbox (Python scripts, calculation outputs) don’t persist between sessions.

Memory

Lodgey saves important findings, decisions, and context to the project’s long-term memory. This includes:

• Key facts discovered (property details, employer changes, loan refinancing dates)
• Decisions made (depreciation method chosen, cost base approach confirmed)
• Pending actions (documents still needed, follow-ups required)

Memory is structured with markdown headings and automatically merged across sessions. When Lodgey writes to memory, it updates existing sections and adds new ones without overwriting unrelated content.