Work management for operations teams
Requests come in through a form, each job carries its own checklist, recurring items come back on their own, and the permissions matrix keeps edit rights where they belong.
A request queue that runs itself, mostly
- 1
Take requests through a public form
Turn the board's Form view into an intake link for facilities, purchasing, onboarding or any other queue. Each submission becomes an item with the fields you asked for, and an automation can notify whoever is on duty.
- 2
Put the checklist in the item
Every item has a checklist for the small steps, and can hold subitems when a step needs its own owner or date. Save a finished item as a template so the next job starts with the same steps, or let an automation create the first subitem.
- 3
Let recurring items come back on their own
Month-end close, weekly reports, quarterly audits: set the item to repeat daily, weekly on chosen days, monthly or yearly, on completion or on schedule. The next occurrence copies the fields, assignees and followers and resets its checklist. For a whole cycle, Duplicate board still works.
- 4
Set the permissions matrix
Workspace roles (Owner, Admin, Member, Guest) and board roles (Owner, Editor, Contributor, Viewer) decide who changes structure, who edits items and who only reads. On Pro you adjust what each role may do.
What operations teams lean on most
Public intake forms
One link per queue. Submissions become items, and the person submitting does not need an account.
Learn moreBoards and subitems
Table view with groups, inline editing and bulk actions; Kanban for the queue; subitems for the checklist inside each job.
Learn moreAutomations
When an item is created, create a subitem, move it to a group and notify someone. When status changes, set a due date.
Learn moreRecurring items and templates
Items that repeat on a schedule or when completed, checklists inside items and item templates per board.
Learn morePermissions matrix
Workspace and board roles on every plan. On Pro, a matrix that sets what each role is allowed to do.
Learn moreDashboards
Open requests by type, items per status and progress per group, built from the board's own columns.
Learn moreUpdates on the item
Questions, approvals and files stay in the item's updates, with @mentions and notifications.
Learn moreStart from the Project tasks template
Groups for To do, In progress, In review and Done with Timeline, Progress, Notes and Files. Rename the groups to your stages and add a Dropdown for the request type.
Questions operations teams ask
Can people outside the team submit requests?
Yes. The Form view publishes as a public link and submitters do not need an account. Each submission becomes an item on the board with the fields the form asks for.
How do checklists work?
Each item has a checklist for small steps, with a progress bar and a badge on the row. When a step needs its own owner, status or date, use subitems instead. Save an item as a template so every new job starts with the same steps.
How do I handle recurring work?
Set the item to repeat: daily, weekly on chosen weekdays, monthly on a day or the last day, or yearly, every N if you like, either when it is completed or on schedule. The next occurrence is created with the same fields, people and an unticked checklist. For a whole cycle, duplicate a master board.
Who can change what?
Workspace roles are Owner, Admin, Member, Guest. Board roles are Owner, Editor, Contributor, Viewer. The Pro plan adds a permissions matrix so you can adjust what each role is allowed to do.
The same boards, for other teams
Agencies
Project management for agencies
Software teams
Bug tracking and planning for software teams
Marketing teams
Content calendar for marketing teams
Small business
Simple CRM and task tracking for small business
Not sure which fits? Look at how boards work or compare TallyWeek with other tools.
Start a free workspace for your team.
14 days of Pro with no card, then Free for up to 3 members with every view and every automation.