Work management for operations teams
Requests come in through a form, each job carries its checklist as subitems, recurring work starts from a duplicated board, 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 subitems
Every item can hold subitems. Add the steps a job always needs by hand, or let an automation create a subitem when an item is created, so the first step is never forgotten.
- 3
Repeat work by duplicating a board
Month-end close, quarterly audits, onboarding runs: keep a master board and choose Duplicate board from the board menu when the next cycle starts. Groups, columns, items and automations come along.
- 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 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 can have subitems, which act as the checklist for that job. Add them by hand, or use the Create a subitem automation action so every new request starts with the same first step.
How do I handle recurring work?
Keep a master board with the groups, columns, items and automations you need, then choose Duplicate board from the board menu at the start of each cycle. You can also create a fresh board from a template each time.
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.