See the work without losing the detail.
A compact project library keeps customers, status, dates and progress beside a selected-project inspector. Search, filter and group around the work.
SoraProjects · Planerad app för arbetshantering
Se arbetet. Känn till nästa steg.
En kompakt plats för projekt, uppgifter, tid och nästa tydliga steg.
De detaljerade designkoncepten nedan är på engelska.
Planned app in Business & collaboration. These original, fictional design concepts do not provide a live task service, timer, invoice, payment or automation. Features, access, package limits and pricing need release review.
More work in view. Details within reach.
Use the same compact library pattern as the rest of SoraSpace: navigation, readable records and the selected item’s details. Phone workflows will drill into a record with a clear Back route; wide tables in these static concepts scroll locally.
| ID | Project | Customer | State | Due | Progress |
|---|---|---|---|---|---|
| P-101 | Coastal catalogue | Example Studio | In progress | 20 Nov 2027 | 25% |
| P-102 | Archive review | North Example Lab | Planerat | 28 Nov 2027 | 0% |
| P-103 | Annual report | Harbour Example Co | In progress | 30 Nov 2027 | 40% |
| P-104 | Exhibition kit | Example Studio | In progress | 24 Nov 2027 | 60% |
| P-105 | Field-study notes | North Example Lab | In progress | 25 Nov 2027 | 50% |
| P-106 | Print collection | Harbour Example Co | Planerat | 26 Nov 2027 | 0% |
| P-107 | Website refresh | Harbour Example Co | In progress | 22 Nov 2027 | 35% |
| P-108 | Reading guide | North Example Lab | In progress | 29 Nov 2027 | 15% |
| P-109 | Workshop notes | Example Studio | Paused | 1 Dec 2027 | 10% |
| P-110 | Launch retrospective | Harbour Example Co | Complete | 1 Nov 2027 | 100% |
Ten fictional projects. Search, grouping and saved-view controls are planned; the illustration does not store a preference.
From a small task to the whole project.
Keep tasks, jobs and subjobs together.
Plan assignments, priorities, dates, comments and linked files with human labels. Software-specific terms and sprints stay optional.
Choose a view of the same records.
List, board, calendar and timeline are planned views of the same work you can access. A layout change should not create duplicate tasks.
Make dependencies visible.
Show what is blocked, which milestone is next and what a changed date may affect. Validate relationships and cycles before applying changes.
Record time with context.
Plan manual entries, one active timer per person, rate snapshots and approval. Recover interrupted tracking without duplicating billable time.
Keep scope changes deliberate.
Review estimates and alterations as revisions. A requested change should not silently replace an accepted scope or fee.
Connect work and billing carefully.
Hand approved time and scope to draft finance workflows, while keeping issue, send and payment permissions distinct. No invoice or payment is created here.
Start with useful templates.
Plan editable templates for creative commissions, academic work, client projects and small-business operations, with custom fields where useful.
Understand progress and capacity.
Plan permission-aware progress, workload, time and budget summaries in Business & collaboration. Capacity builds on agreed working patterns and allocations.
Make responsibility and dependencies clear.
Keep assigned work, due dates and estimates together. A blocked task should explain what needs to happen first.
| ID | Work item | Assigned to | State | Due · 2027 | Estimate | Depends on |
|---|---|---|---|---|---|---|
| T01 | Scope brief | Alex | Done | 5 Nov | 2 h | — |
| T02 | Asset inventory | Robin | Done | 6 Nov | 1 h | — |
| T03 | Sidlayout | Robin | In progress | 10 Nov | 5 h | T01 |
| T04 | Photo edits | Alex | In progress | 11 Nov | 2 h | T02 |
| T05 | Copy review | Alex | To do | 12 Nov | 2 h | T06 |
| T06 | Asset approval | Client reviewer | To do | 11 Nov | 0 h | T02 |
| T07 | Review pack | Robin | To do | 15 Nov | 2 h | T03 |
| T08 | Handoff | Alex | To do | 20 Nov | 1 h | T07 |
Copy review · selected task
- Task
- T05
- Assigned to
- Alex Example
- Waiting for
- T06 · Asset approval
- Due
- 12 November 2027
- Estimate
- 2 hours
Keep the next step clear.
Jobs and subjobs can keep their own assignees, dates, notes and linked files. Blocked work should name what it is waiting for.
Planned dependency checks prevent cycles. Moving a due date should show related work that may need review.
Review dependencyOpen linked fileThe same work, viewed another way.
The board and timeline below show the same eight fictional work items as the list above. These are original concepts, not copied competitor screens.
To do 4
Alex · 12 Nov
Client reviewer · 11 Nov
Robin · 15 Nov
Alex · 20 Nov
In progress 2
Robin · 10 Nov
Alex · 11 Nov
Done 2
Alex · 5 Nov
Robin · 6 Nov
Work item
4 Nov8 Nov12 Nov16 Nov20 Nov
T01 · Scope brief4–5 Nov
T02 · Asset inventory5–6 Nov
T03 · Page layout7–10 Nov
T04 · Photo edits8–11 Nov
T05 · Copy review12 Nov
T06 · Asset approval10–11 Nov
T07 · Review pack13–15 Nov
T08 · Handoff18–20 Nov
Time is useful when its context stays with it.
Review who recorded work, what it belongs to and whether it is approved for billing. Keep historic rates explicit and distinguish hourly work from fixed fees.
| Date · 2027 | Person | Work | Hours | Billable | Rate · AUD/h | Review |
|---|---|---|---|---|---|---|
| 5 Nov | Alex | Scope brief | 2 | Yes | 80.00 | Approved |
| 7 Nov | Robin | Sidlayout | 1.5 | Yes | 80.00 | Submitted |
| 7 Nov | Alex | Client call | 0.5 | No | — | Approved |
| 8 Nov | Alex | Photo edits | 2 | Yes | 80.00 | Approved |
| 8 Nov | Robin | Asset check | 1 | Yes | 80.00 | Submitted |
| 8 Nov | Alex | Internal notes | 0.5 | No | — | Approved |
Review before billing.
- Tracked time
- 7.5 hours
- Approved billable
- 4 hours · AUD 320.00
- Submitted billable
- 2.5 hours · AUD 200.00
- Non-billable
- 1 hour
- Accepted estimate
- 15 billable hours · AUD 1,200.00
Reliable time, clear choices.
Plan manual records and one active timer per person, with interruption recovery and reviewed rate snapshots. Submitted time is not approved invoice content.
Hourly and fixed-fee work need different billing rules. A fixed fee must not silently acquire extra time charges.
Review timeAdd manual entryNo timer, timesheet or invoice is created by this sample.
A change request is not an accepted change.
Keep scope decisions and approved billing sources traceable. Financial examples use AUD and do not establish supported tax, currency, provider or invoice-issuing behaviour.
Accepted estimate · sample revision 1
Coastal catalogue
- Billing
- Hourly · AUD 80.00/h
- Accepted estimate
- 15 hours · AUD 1,200.00
- Requested alteration
- 3 hours · AUD 240.00
- Requested total
- 18 hours · AUD 1,440.00
- Decision
- Pending review · not applied
The requested alteration does not overwrite the accepted scope. Keep the original, decision, approver and reviewed revision traceable.
Review alterationKeep accepted scopeFinance handoff · illustration
Draft billing preview
- Source
- 4 approved billable hours
- Rate snapshot
- AUD 80.00/h
- Draft subtotal
- AUD 320.00 before configured taxes
- Issue state
- Not issued
- Payment state
- Not requested
Drafting, issuing, sending and payment collection are separate actions with separate permissions. Scope increases and submitted time are not automatically invoiced.
Explore planned finance workflows →Useful summaries, with the right access.
Bring work summaries into Business & collaboration, then return to the permitted records behind each widget.
Business & collaboration · Projects
Fictional snapshot · 8 November 2027 · example authorised project view
Give each role the right work.
| Example role | Planned scope |
|---|---|
| Contributor | Assigned tasks and authorised files |
| Project manager | Plan work; propose scope changes |
| Finance issuer | Separately authorised invoice issue |
One workspace, deliberate access.
Projects, time, rates and linked files remain permission-scoped. A project role does not automatically expose private research, personal mail or another store’s customer data.
Real widgets will need authorised records, freshness information and a route back to the filtered list. These values are fictional design examples.
A few project questions.
Do I have to use a software-development workflow?
No. The plan uses project, job and task labels that suit creative, academic and business work. Optional specialist workflows can build on the same foundation.
Are tasks, timers and boards available now?
No. These are planned design concepts. Shared work, access controls, reliable saving and recovery still need development and release testing.
Will an estimate or time record charge my client?
No. Estimate approval, invoice drafting, invoice issue, explicit sending and payment collection are separate planned workflows. A draft is not an issued or paid invoice.
Can I connect customers and files?
Permission-aware links to shared contacts, files and business records are planned. Linking a project does not grant access to every customer, document or financial record.
One business workspace. Familiar ways to work.
Choose the tools that fit your work as they become available.
Explore SoraCRM →