Overview
Resolving an Assignment is the moment Mobaro turns work-being-done into work-on-the-record. This article covers the patterns that produce a clean, defensible, useful Assignment trail — and the patterns that quietly degrade it.
The bottom line: An Assignment resolution is read by the next shift, by an auditor six months from now, and by a manager investigating an incident. Write the resolution for those readers, not for yourself in the moment.
What "solving" an Assignment means
Solving an Assignment in Mobaro means marking it complete with a description of what was done. Depending on the Assignment template, solving may also require:
A photo or attachment.
A sign-off from a higher authority.
A specific outcome flag (resolved / partially resolved / could not resolve).
The resolution is timestamped, linked to the resolving User, and locked into the audit trail.
Five practices for clean resolutions
1. Describe what you actually did, not what you intended
"Replaced sensor unit on lap-bar 4" is a useful resolution. "Fixed the issue" is not. Be specific about the action taken — what part, which Asset, which step. The reader six months from now does not have your context.
2. Note anything you found that was not in the Assignment
If the Assignment was about brake wear and you noticed a separate issue with the safety harness — write it down. The next inspection or shift relies on this carryover. If the side-finding is significant, create a follow-up Assignment or a Handover Note rather than burying it in the resolution.
3. Attach evidence when it adds value
A photo of the replaced part, the calibration screen, or the after-state of the area is worth more than a paragraph of description. Attach evidence when it would meaningfully change the reader's understanding. Skip evidence when the description is already complete on its own.
4. Use the outcome flag honestly
If you couldn't resolve the issue, mark it as such. Do not close an Assignment with a "resolved" status when the underlying problem remains. Mobaro allows organizations to distinguish between "completed and resolved" and "completed and could not resolve" specifically because both states matter — and they branch into different downstream actions. Ask your Super User for organization-specific use cases.
When to mark an Assignment as not-solvable
Some Assignments cannot be resolved by the assigned team — for example, a part is on backorder, an issue requires manufacturer involvement, or a regulatory inspection has to clear first. Mark these explicitly:
Use the Could not resolve outcome flag (requires organizational setup).
Document the specific blocker in the resolution description.
Reassign or escalate to whoever can move it forward.
If the issue creates an operational risk, publish a Handover Note documenting the open state.
Reopening a closed Assignment
If a previously resolved Assignment turns out to be incomplete — for example, the issue recurs — Mobaro supports reopening:
1. Open the Assignment
Find the Assignment in the audit trail or Assignments list.
2. Use the Reopen action
The Reopen action is only available on the Mobaro Backend.
3. Add a description of why the Assignment is being reopened
This explanation becomes part of the audit trail.
The original resolution is preserved in the audit trail; the reopen creates a new event in the timeline rather than overwriting the prior close.
Common patterns
Pattern: photo + one sentence
For most operational Assignments, one clear photo plus one descriptive sentence is the right resolution density. Don't write paragraphs; don't skip the photo.
Pattern: split scope into multiple Assignments
If the resolution would have to describe two unrelated fixes, create a second Assignment for the unrelated work and resolve each separately. One Assignment, one scope.
Anti-patterns to avoid
Watch out for these patterns, which quietly degrade the Assignment trail:
"Completed" with empty description — an Assignment closed with no resolution description is functionally a missed Assignment from a reporting perspective. Always include something — even one sentence is better than nothing.
"Resolved" with caveats hidden in the description — if the description says "resolved but…" the outcome flag should not be "resolved." Use "partially resolved" or "could not resolve" — the flag is what reports filter on.
Burying side-findings in the resolution — if you found something material that wasn't in the original Assignment, create a follow-up Assignment or Handover Note. A buried side-finding rarely gets acted on.
Skipping evidence on high-stakes work — for safety-critical or regulatory work, the photo or attachment is the audit defense. Don't omit it to save 10 seconds.
Frequently asked questions
Q: Can I edit a resolution after the Assignment is closed?
A: Resolutions are typically locked once submitted to preserve the audit trail. To add information, append a comment to the Assignment or reopen it.
Q: How long are resolved Assignments retained?
A: Indefinitely. Resolutions feed long-running compliance reporting.
Q: Can someone other than the assignee resolve an Assignment?
A: Depending on configuration, yes. Other Users with the right Role can resolve on behalf of the assignee — useful when work is reassigned mid-flight.