Tasks in Lagniappe live on the page they are about. A task can be a simple reminder, but the system is strongest when tasks repeat, collect structured information, and leave behind history.

It is less a kanban-first project manager and more an operational log: what needs doing, what it belongs to, who did it, and what happened each time.

A task is attached to a page: a property, person, vehicle, client, appliance, website, or whatever else you track. Opening the page shows the document, structured data, files, notes, and tasks in one place.

Completing a task records who completed it and when. If the task has a form, the entered values are part of the completion record.

When a completed task is reset for the next cycle, the previous completion becomes a read-only history entry. Answer fields and checklist items start fresh; the form, assignee, schedule, and page remain in place. Use Fill from latest history on an available field when an earlier answer is useful for the new submission.

This works well for maintenance logs, inspections, recurring reports, medical or pet visits, document renewals, and other work where the record matters as much as the reminder.

Tasks can have manual due dates or recurring schedules:

• Recurring: every N days, weeks, months, or years.
• Scheduled: calendar rules such as weekdays, month days, or yearly dates.
• Periodic: describe the repetition in words and AI converts it into a structured schedule.

Scheduled tasks can automatically set the next due date and reset after completion. A task can stay marked complete until its automatic reopening happens. You can also postpone a due date without replacing the repeating rule.

Tasks can be assigned to users. An assignee can view and edit the assigned task even without access to its origin page, so work can be delegated without exposing the rest of that page. Assignment does not reveal the origin page or unrelated tasks, and applicable page and form restrictions still apply. An unassigned task remains visible to users who can see its page.

Projects track a type of work across many pages. A project can define task templates, and each template can have its own form. Tasks created from a template still live on their pages, but the project gives you a cross-page view.

Example: an “Annual Maintenance” project can show HVAC, roof, and pest tasks across every property while each task stays attached to the property page where it belongs.

• If you only need disposable checklist items, this model may feel a touch heavier than you need.
• For boards, sprints, dependencies, burndown charts, or time tracking, a dedicated project-management tool is a better home.
• Task history pays off most when forms and completion habits are designed with a little intention up front.
• Assignment grants access to work that task, not to browse its origin page; applicable page and form restrictions still apply.