There are a few approaches that you can take.
Create on your model:
public function getFormattedActiveMethod() {
return $this->attributes['active'] ? 'active' : 'not active';
}
And then you can use it like: $user->formattedActive (or whathever you want to call it, as long your method name matches getCamelCaseNameAttribute()).
You can also add this attribute into the $appends property array, so it will show up when you cast the model to array/json.
Approach 2: Presenter Pattern
Simply create a new class just to present data to your views. It's a good approach to prevent the Model from bloating and also separate your logic.
There are a few packages that helps you to achieve it, like robclancy/presenter, laracasts/Presenter, ShawnMcCool/laravel-auto-presenter and even League's Fractal, that can help you building a consistent API too.
Depending on the size of your project, it's better to take this approach.
accessor, but I wouldn't.