One Person DepartmentA Workable Week · Priorities and boundaries
Map your responsibilities before planning another busy week
Map what must keep moving, agree a simpler standard and plan a week that leaves room for interruptions and help.
Before filling another weekly plan, write down what you are keeping running. “Office administration” can conceal supplier invoices, purchasing, staff changes, building requests and the questions everyone brings to your desk. A calendar cannot settle which responsibility takes priority when two of them need the same hour.
Start with a small responsibility map. Its purpose is to make choices visible: what must continue, what a simpler version would look like, what can wait and which decision belongs to someone else. You can use it inside a larger organisation, in a part-time role or when volunteering. It does not require you to be the owner of the whole organisation.
Start with the hours you actually have
The situation below is illustrative. One office coordinator has 24 working hours across Monday, Tuesday, Thursday and Friday. They support purchasing, invoice administration, routine staff records and office requests. Wednesday is not a working day. They are not the person authorised to approve every purchase, decide staffing matters or resolve every facilities problem.
Those 24 hours are the available working time, after breaks. Meetings, reading requests and writing handover notes must fit within them. The example does not assume evening availability or an unpaid Wednesday check-in.
Write your own available hours at the top of the page. Subtract any fixed work that already occupies them, such as a scheduled meeting or a reception shift. Use the remainder when making new promises. If availability changes from week to week, make that visible before agreeing a response time.
Make a responsibility map, not an endless task list
Group work by the service or outcome someone relies on. For each group, name the smallest useful standard, the consequences of waiting and the person who can decide an exception. In this example, dates and service standards are internal agreements, not statements of legal or professional requirements.
Illustrative responsibility map
Scroll sideways to read all five columns.
| Responsibility | Essential this week | Keep simple | Can wait | Help or decision needed |
|---|---|---|---|---|
| Supplier invoices | Prepare complete items for the agreed finance review. | One checked list with missing information clearly marked. | Redesigning the tracking sheet. | The finance lead decides disputed items and any change to the review date. |
| Purchasing | Progress the requests already agreed for this week. | Review ordinary requests in two planned windows. | Nonessential purchases without an agreed date. | The budget holder approves spending and decides competing priorities. |
| Routine staff records | Complete authorised changes needed for agreed internal dates. | A short record of the request, action and outstanding question. | Reformatting older records without a current need. | The responsible manager resolves unclear instructions or exceptions. |
| Office and facilities requests | Log faults and pass time-sensitive issues to the designated contact. | One shared list of open items and the next responsible person. | Cosmetic improvements with no agreed deadline. | The facilities contact handles work outside the coordinator’s authority. |
Your map may have different rows. A marketing coordinator might use campaign commitments, incoming requests and supplier work. A volunteer might separate weekly member administration from an occasional event. The test is whether the map explains what people depend on you for, rather than merely listing every small action you could take.
Do not mark every row “essential”. Ask what actually needs to happen this week, what standard is sufficient and who accepts the consequence if something moves. If the answer is unclear, record a decision to obtain rather than quietly taking on another obligation.
Turn the map into a bounded week
The coordinator sets aside 12 hours for protected routine work and eight for requests, coordination and review. Four hours remain unallocated for the things that do not arrive neatly in advance. This is an example allocation, not a universal ratio or a promise that four hours will absorb every interruption.
Scroll the table sideways if needed. All four columns are part of the example.
| Day | Protected routine work: 3 hours | Requests, coordination and review: 2 hours | Unallocated: 1 hour |
|---|---|---|---|
| Monday | Prepare the invoice list and review agreed purchases. | Read new requests, obtain missing decisions and confirm this week's priorities. | Leave free for an interruption or an item taking longer than expected. |
| Tuesday | Process authorised staff changes and follow up office items. | Handle the request queue and confirm who covers Wednesday. | Leave free rather than booking another improvement task. |
| Thursday | Continue the agreed routines and follow up unresolved items. | Review requests received during the absence and ask for priority decisions. | Use only as needed; an urgent item may displace planned work. |
| Friday | Finish purchase/invoice follow-ups and record outstanding work. | Review the week, prepare the next request window and confirm handovers. | Leave room for a late exception or an unfinished essential item. |
The total is 24 hours, including the unallocated time. Put those blocks in the calendar before accepting another deadline. Within a block, keep a short list of the actual next actions; the table is a capacity agreement, not a minute-by-minute timetable.
If a routine needs five hours rather than three, do not keep the table tidy by pretending it still fits. Move another commitment, agree a simpler standard or ask for help. A week that repeatedly needs more hours than are available needs a decision about workload or service, not a more elaborate colour scheme.
Give a new request somewhere to go
Keep one visible list for ordinary requests, with the desired outcome, requested date and next decision. A request arriving by message can still be recorded there; you do not need to make people learn a new application before agreeing how the work will be handled.
When a new request conflicts with the plan, make the trade-off concrete:
I can prepare the purchase request on Thursday. Completing it on Tuesday would move the staff-record work we agreed for that morning. Please confirm which should take priority, or who can help with one of them.
Use wording that fits your authority. If you cannot change priorities yourself, name the person who can. “Urgent” should lead to an agreed route and a decision, rather than silently making every request your next task.
Make the non-working day explicit
For Wednesday, this example needs a coverage note, not an assumption that the coordinator will read messages anyway:
This note is illustrative. Use actual people, permissions and routes in your own workplace, and ask them to confirm the arrangement. A name on a document does not by itself give someone time, access or authority to do the work.
Choose one agreement to make next
Do not try to document the whole department before next Monday. Pick the row that creates the most repeated conflict. Write its essential outcome, a simpler acceptable standard and the decision you need. Bring that row and the available hours to the person who can agree the trade-off.
After the week, compare what happened with the map. Which work displaced the plan? Which request needed another person’s decision? What remained unfinished even after simplification? Use those observations to revise one commitment or coverage arrangement. If the essential work still exceeds capacity, keep that gap visible and ask for a decision about scope, support or timing.